As discussed in an openstack-discuss thread  we could improve the extraroute API to better support Neutron API clients, especially Heat. The problem is that the current extraroute API does not allow atomic additions/deletions of particular routing table entries. In the current API the routes attribute of a router (containing all routing table entries) must be updated at once. Therefore additions and deletions must be performed on the client side. Therefore multiple clients race to update the routes attribute and updates may get lost.  http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005121.html Change-Id: I10407a74102bfd16e3a0b8d2bd08c92acb4cc27f Partial-Bug: #1826396
|4 years ago|
|doc||4 years ago|
|images||4 years ago|
|misc||6 years ago|
|specs||4 years ago|
|tests||5 years ago|
|.gitignore||5 years ago|
|.gitreview||4 years ago|
|.stestr.conf||5 years ago|
|.zuul.yaml||4 years ago|
|LICENSE||9 years ago|
|README.rst||5 years ago|
|requirements.txt||5 years ago|
|setup.cfg||4 years ago|
|setup.py||6 years ago|
|tox.ini||4 years ago|
Team and repository tags
OpenStack Neutron Specifications
This git repository is used to hold approved design specifications for additions to the Neutron project. Reviews of the specs are done in gerrit, using a similar workflow to how we review and merge changes to the code itself.
The layout of this repository is:
You can find an example spec in specs/template.rst.
Specifications are proposed for a given release by adding them to the specs/<release> directory and posting it for review. The implementation status of a blueprint for a given release can be found by looking at the blueprint in launchpad. Not all approved blueprints will get fully implemented.
Specifications have to be re-proposed for every release. The review may be quick, but even if something was previously approved, it should be re-reviewed to make sure it still makes sense as written.
Prior to the Juno development cycle, this repository was not used for spec reviews. Reviews prior to Juno were completed entirely through Launchpad blueprints:
Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:
For more information about working with gerrit, see:
To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
tox, the documentation will be available for viewing in HTML format in the
doc/build/ directory. Please do not check in the generated HTML files as a part of your commit.