N0. Does the project use the Neutron REST API or relies on proprietary backends?
The project 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 other backends.
N1. Does the project integrate/use neutron-lib?
Yes. The migration report shows that there are currently ~300 total imports. Neutron is imported ~80 times and Neutron-lib only ~10 times, for a migration percentage of 13.0400%
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?
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 BGP extensions have 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).
No api-ref target, but the project has API documentation in tree. This should migrate over to neutron-lib’s api-ref.
D3. Does the project have a releasenotes tox target, functional and continously working? Provide proof.
Yes. Though nothing has been release noted.
D4. Describe the types of documentation available: developer, end user, administrator, deployer.
Developer documentation is rather rich for a project of this age, user and deployer documentation is provided in the networking guide.
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?
Yes, but it lacks 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).
Yes. Though it looks like there is only basic API coverage.
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 maintenance is responsibility of the neutron-stable-maint team.
L1. If the project requires a client library, how does it implement CLI and API bindings?
There are client extensions. It looks like OSC transition has stalled badly.
|N0 | Y|
|N1 | Y|
|N2 | N|
|N3 | N|
|N4 | Y|
|N5 | Y|
|D1 | Y|
|D2 | Y|
|D3 | Y|
|D4 | Y|
|C1 | N|
|C2 | Y|
|C3 | Y|
|C4 | N|
|C5 | Y|
|C6 | N|
|C7 | N|
|C8 | Y|
|R1 | Y|
|R2 | Y|
|R3 | Y|
|R4 | Y|
|S1 | Y|
Since the project setup at the beginning of Newton, lots has been achieved. There are some gaps that need to be filled, and a focussed team should have no problem on achieving those in time of the Ocata-1 deadline.