N0. Does the project use the Neutron REST API or relies on proprietary backends?
No. The project implements Neutron plugins.
N1. Does the project integrate/use neutron-lib?
No. Of the total ~200 total imports, neutron-lib is imported 0 times whereas Neutron is imported a few dozens. Some in flight, more needed.
N2. Do project members actively contribute to help neutron-lib achieve its goal?
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?
No, as the next point demonstrates.
N4. How does the project provide networking services? Does it use modular interfaces as provided by the core platform?
The project has adopted some questionable patterns. These patterns not only defeat the point of modularity but may lead to solutions that may be incredibly brittle. Team working to address this.
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.
It does not look like the project introduces new APIs.
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).
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.
There is some developer and deployer documentation. More being added.
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)
Yes. Though, it is puzzling why some test code is available under non-test modulee, test_election being an example.
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).
No, at the time of writing.
C6. Does the project require CI for Grenade coverage?
Potentially, but currently there is none.
C7. Does the project provide multinode CI?
R1. Does the project adopt semver?
R2. Does the project have release deliverables? Provide proof as available in the release repo.
R3. Does the project use upper-constraints?
No. In progress.
Does the project integrate with OpenStack Proposal Bot for requirements updates?
No. In progress.
S1. Does the project have stable branches and/or tags? Provide history of backports.
The lack of stable branches and the fact that the code somewhat handles branching in code is concerning.
L1. If the project requires a client library, how does it implement CLI and API bindings?
|N0 | Y|
|N1 | N|
|N2 | N|
|N3 | N|
|N4 | N|
|N5 | N|
|D1 | Y|
|D2 | N|
|D3 | N|
|D4 | Y|
|C1 | Y|
|C2 | N|
|C3 | N|
|C4 | N|
|C5 | N|
|C6 | N|
|C7 | N|
|C8 | N|
|R1 | Y|
|R2 | Y|
|R3 | N|
|R4 | N|
|S1 | N|
Final remarks: the modularity and maturity of the networking-calico codebase is substantially subpar compared to other Neutron subprojects. The absence of testing besides unit coverage is problematic to say the least. Some of the patterns chosen to provide networking solutions are an exemplification of the disconnect between the networking-calico and the Neutron core team. Work required is not insurmountable but it takes time.