Neutron-dynamic-routing Scorecard

Neutron integration

  • 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%

  • 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?

    Not particularly.

  • N4. How does the project provide networking services? Does it use modular interfaces as provided by the core platform?

    Yes.

Documentation

Continuous Integration

  • C1. Does the project have a Grafana dashboard showing historical trends of all the jobs available? Provide proof (links to grafana.openstack.org).

    No.

  • C4. Does the project have CI for fullstack coverage?

    No.

  • C6. Does the project require CI for Grenade coverage?

    Yes. But it has none.

  • C7. Does the project provide multinode CI?

    No.

  • C8. Does the project support Python 3.x? Provide proof.

    Yes.

Release footprint

  • R1. Does the project adopt semver?

    Yes.

  • 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.

Stable backports

  • 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.

Client library

  • 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.

Scorecard

Scorecard
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
L1 N

Final remarks

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.

Table Of Contents

Previous topic

Networking-sfc Scorecard

Next topic

Neutron-fwaas Scorecard

Project Source

This Page