N0. Does the project use the Neutron REST API or relies on proprietary backends?
Neutron-vpnaas implements its own set of Neutron API extensions on top of the Neutron core framework and it does so by using the service plugin model. The API exposed has open source implementations, and it provides a pluggable mechanism for proprietary backends.
N1. Does the project integrate/use neutron-lib?
Yes. The migration report shows that there are currently ~600 total imports. Neutron is imported ~150 times and Neutron-lib only ~15 times, for a migration percentage of 10.0500%
N2. Do project members actively contribute to help neutron-lib achieve its goal?
None of the project core members have merged anything meaningful into neutron-lib (source: https://review.openstack.org/#/q/project:openstack/neutron-lib+status:merged,75).
N3. Do project members collaborate with the core team to enable subprojects to loosely integrate with the Neutron core platform by helping with the definition of modular interfaces?
N4. How does the project provide networking services? Does it use modular interfaces as provided by the core platform?
Yes, for the most part, but as far as the agent side is concerned, the project relies on the use of a VPN agent that specializes the base L3 agent, this is prone to breakage, and leads to deployment complications when VPN and L3 services are deployed together.
N5. If the project provides new API extensions, have API extensions been discussed and accepted by the Neutron drivers team? Please provide links to API specs, if required.
The vpnaas API has been widely discussed and accepted.
D1. Does the project have a doc tox target, functional and continuously working? Provide proof (links to logs.openstack.org).
D2. If the project provide API extensions, does the project have an api-ref tox target, functional and continously working? Provide proof (links to logs.openstack.org).
There is an API reference but no-one has confirmed its accuracy at the time of writing.
D3. Does the project have a releasenotes tox target, functional and continously working? Provide proof.
D4. Describe the types of documentation available: developer, end user, administrator, deployer.
Developer documentation is sparse, user documentation is virtually non-existent.
C1. Does the project have a Grafana dashboard showing historical trends of all the jobs available? Provide proof (links to grafana.openstack.org).
C2. Does the project have CI for unit coverage? Provide proof (links to logs.openstack.org)
C3. Does the project have CI for functional coverage? If so, does it include DB migration and sync validation?
C4. Does the project have CI for fullstack coverage?
C5. Does the project have CI for Tempest coverage? If so, specify nature (API and/or Scenario).
Latest Bot proposal shows a mixed picture, API coverage is non-voting.
C6. Does the project require CI for Grenade coverage?
Yes. But it has none.
C7. Does the project provide multinode CI?
C8. Does the project support Python 3.x? Provide proof.
R1. Does the project adopt semver?
R2. Does the project have release deliverables? Provide proof as available in the release repo.
Yes, the release is responsibility of the neutron-release team.
R3. Does the project use upper-constraints?
- Does the project integrate with OpenStack Proposal Bot for requirements updates?
S1. Does the project have stable branches and/or tags? Provide history of backports.
Yes, stable maintainance is responsibility of the neutron-stable team.
L1. If the project requires a client library, how does it implement CLI and API bindings?
There are Neutron CLI and API bindings, but none for OSC.
|N0 | Y|
|N1 | Y|
|N2 | N|
|N3 | N|
|N4 | N|
|N5 | Y|
|D1 | Y|
|D2 | N|
|D3 | Y|
|D4 | N|
|C1 | N|
|C2 | Y|
|C3 | Y|
|C4 | N|
|C5 | N|
|C6 | N|
|C7 | N|
|C8 | Y|
|R1 | Y|
|R2 | Y|
|R3 | Y|
|R4 | Y|
|S1 | Y|
At the time of writing the project scores positively in about half of the criteria. The neutron-vpnaas project has been in the doldrums for quite a while and the release notes show it. Closing the gap on all the remaining unmet criteria in time for Ocata-1 (Nov 14 2016) knowing the level of commitment required and lack of resources available makes it clear that this project is ready to be left to its own destiny.