OpenStack Networking (Neutron) Specifications
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
zhangbailin 148136ac0e
Change openstack-dev to openstack-discuss
4 years ago
doc Add placeholder for Train specs 4 years ago
images Introduce address scopes 8 years ago
misc Removed networking_general_api_information.rst 7 years ago
specs Merge "Network Segment Range Management" 4 years ago
tests Fix py27 job in specs repo 5 years ago
.gitignore Switch to stestr 5 years ago
.gitreview Added .gitreview 9 years ago
.stestr.conf Switch to stestr 5 years ago
.zuul.yaml Always run py27 test 5 years ago
LICENSE Add base neutron-specs framework 9 years ago
README.rst Delete redundant rst files and update README 5 years ago
requirements.txt Switch to stestr 5 years ago
setup.cfg Change openstack-dev to openstack-discuss 4 years ago Update sphinx to 1.5 6 years ago
tox.ini Update min tox version to 2.0 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

After running 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.