openstack/neutron-specs
Code Issues Proposed changes
OpenStack Networking (Neutron) Specifications
725 Commits 1 Branch 0 Tags 29 MiB
Python 100%
6efe473ccf
Go to file
Slawek Kaplonski 6efe473ccf Move share SG as read only spec to Victoria 
It was merged recently in [1] but by mistake we merged it to the
Ussuri branch.

[1] https://review.opendev.org/#/c/724207/

Change-Id: I604956217d2370b72cd6825289fac9e79fafeda3
2020-05-15 08:08:49 +00:00
doc Add placeholder for Victoria specs 2020-05-15 09:56:02 +02:00
images Introduce port mirroring for sriov-vf 2018-11-28 08:07:15 -05:00
misc Removed networking_general_api_information.rst 2016-08-27 21:07:47 +00:00
specs Move share SG as read only spec to Victoria 2020-05-15 08:08:49 +00:00
tests Fix py27 job in specs repo 2018-05-30 10:28:57 +02:00
.gitignore Switch to stestr 2018-06-22 12:50:11 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:34:46 +00:00
.stestr.conf Switch to stestr 2018-06-22 12:50:11 +02:00
.zuul.yaml Switch py27 job to py36 2019-05-04 17:38:15 +00:00
LICENSE Add base neutron-specs framework 2014-04-14 03:08:02 +00:00
README.rst Delete redundant rst files and update README 2018-04-11 15:24:45 +09:00
requirements.txt Switch to stestr 2018-06-22 12:50:11 +02:00
setup.cfg Cleanup py27 support 2020-04-10 11:09:47 +02:00
setup.py Update sphinx to 1.5 2017-03-31 00:20:56 +00:00
tox.ini Cleanup py27 support 2020-04-10 11:09:47 +02:00

README.rst

Team and repository tags

image

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:

specs/<release>/

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:

https://blueprints.launchpad.net/neutron

Please note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:

https://wiki.openstack.org/wiki/Blueprints

For more information about working with gerrit, see:

https://docs.openstack.org/infra/manual/developers.html#development-workflow

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.