N0. Does the project use the Neutron REST API or rely on proprietary backends?
Neutron-fwaas 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 ~400 total imports. Neutron is imported ~100 times and Neutron-lib only ~20 times, for a migration percentage of 18.045%. The project has periodic validation with neutron-lib.
N2. Do project members actively contribute to help neutron-lib achieve its goal?
Yes. For example: https://review.openstack.org/389825
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?
The team has worked successfully in delivering the L3 agent extension framework, that enabled the team to break the fork of the L3 agent. However, this framework should be contributed to neutron-lib to help increase the positive score of N2, which is in progress. See: Migrate neutron agent extensions to neutron-lib <https://review.openstack.org/#/c/385045/_>
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 fwaas v1 and v2 API 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).
The API reference for the v2 API has not merged at the time of writing, see FWaaS v2 API reference
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 stale.
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 grim picture. No API/Scenario coverage for the v2 API, though v1 has it.
C6. How does a project validate upgrades on a continuous basis? Does the project require or support CI for Grenade coverage?
No, but it does in the experimental queue. Some tests need to be identified as smoke tests.
C7. Does the project provide multinode CI?
No, but it is in progress.
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 Neutron CLI and API bindings for v1, none released for v2 yet.
|N0 | Y|
|N1 | Y|
|N2 | Y|
|N3 | Y|
|N4 | Y|
|N5 | Y|
|D1 | Y|
|D2 | N|
|D3 | Y|
|D4 | N|
|C1 | Y|
|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 17 out of 22 criteria. Even though the fwaas team has made quite a progress during the Newton cycle, closing the gap on all the remaining unmet criteria in time for Ocata-1 (Nov 14 2016) seems challenging.