openstack
/
neutron-specs
Code Issues Proposed changes
OpenStack Networking (Neutron) Specifications
8 Commits 1 Branch 0 Tags 28 MiB
Python 100%
Go to file
Robert Kukura ec31bcfc58 Allow defining REST API with attribute tables 
When Neutron APIs are implemented using its declarative attribute map
facility, allow specification of REST resource APIs in terms of those
attributes. An example table format is included in template.rst.

Change-Id: I16aa17e847295839985cd0dec1264c8f6132dcfc
 		2014-04-18 15:52:09 -04:00
doc/source Added Sphinx diagram tools 2014-04-17 21:11:15 +00:00
specs Allow defining REST API with attribute tables 2014-04-18 15:52:09 -04:00
tests Merge "Added Sphinx diagram tools" 2014-04-18 19:50:06 +00:00
.gitignore Add base neutron-specs framework 2014-04-14 03:08:02 +00:00
.gitreview Added .gitreview 2014-03-28 19:24:51 +00:00
.testr.conf Add base neutron-specs framework 2014-04-14 03:08:02 +00:00
LICENSE Add base neutron-specs framework 2014-04-14 03:08:02 +00:00
README.rst Add base neutron-specs framework 2014-04-14 03:08:02 +00:00
requirements.txt Added Sphinx diagram tools 2014-04-17 21:11:15 +00:00
setup.cfg Add base neutron-specs framework 2014-04-14 03:08:02 +00:00
setup.py Add base neutron-specs framework 2014-04-14 03:08:02 +00:00
tox.ini Add base neutron-specs framework 2014-04-14 03:08:02 +00:00

README.rst

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 doc/source/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:

http://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://wiki.openstack.org/wiki/Gerrit_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 checkin the generated HTML files as a part of your commit.