openstack
/
neutron-specs
Code Issues Proposed changes
OpenStack Networking (Neutron) Specifications
658 Commits 1 Branch 0 Tags 28 MiB
Python 100%
Go to file
Bence Romsics dca619fd9e QoS minimum bandwidth allocation in Placement API 
This spec describes how to model, from Neutron, a new resource provider
in the Placement API to describe the bandwidth allocation.

Based on a Rocky PTG discussion this is a re-work of the spec.

Co-Authored-By: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
Co-Authored-By: Bence Romsics <bence.romsics@ericsson.com>
Co-Authored-By: Balazs Gibizer <balazs.gibizer@ericsson.com>

Related-Bug: #1578989
Change-Id: Ib995837f6161bcceb09735a5601d8b79a25a7354
See-Also: Ie7be551f4f03957ade9beb64457736f400560486
 		2018-05-15 21:09:50 +00:00
doc Delete redundant rst files and update README 2018-04-11 15:24:45 +09:00
images Introduce address scopes 2015-06-10 11:54:40 -06:00
misc Removed networking_general_api_information.rst 2016-08-27 21:07:47 +00:00
specs QoS minimum bandwidth allocation in Placement API 2018-05-15 21:09:50 +00:00
tests Add Stadium project scorecard 2016-10-13 16:06:30 -07:00
.gitignore Changed .gitignore file to ignore .idea (Pycharm) and *~ (emacs) 2014-07-01 01:33:18 +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 Delete redundant rst files and update README 2018-04-11 15:24:45 +09:00
requirements.txt Need to follow the new PTI for document build 2018-02-28 23:58:22 +09:00
setup.cfg Need to follow the new PTI for document build 2018-02-28 23:58:22 +09:00
setup.py Update sphinx to 1.5 2017-03-31 00:20:56 +00:00
tox.ini Need to follow the new PTI for document build 2018-02-28 23:58:22 +09: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.