Igor Duarte Cardoso ac282399d4 Neutron Common Classification Framework
This patch documents the Common Classification Framework.

Neutron features/projects that may need classification are:
- Security group rules
- openstack/neutron-fwaas
- openstack/networking-sfc
- openstack/networking-bgpvpn
- openstack/tap-as-a-service
- Neutron QoS

Furthermore, there are other projects with classication APIs, such as
openstack/group-based-policy and it's possible that others will want
to support classifications in their own APIs, further reinventing the wheel
and fragmenting the language used in the OpenStack ecosystem when it comes
to defining traffic classifications.

Change-Id: I6df22d9e766d8aeabc2f99262cadeec332d809b0
Related-Bug: #1476527
2017-06-15 15:53:32 +00:00
2017-04-15 00:12:04 +00:00
2015-06-10 11:54:40 -06:00
2016-10-13 16:06:30 -07:00
2014-03-28 19:24:51 +00:00
2014-04-14 03:08:02 +00:00
2014-04-14 03:08:02 +00:00
2016-11-25 15:37:16 +01:00
2017-03-31 00:20:56 +00:00
2017-03-31 00:20:56 +00:00
2014-04-14 03:08:02 +00:00

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 doc/source/specs/template.rst. A skeleton that contains all the sections required for a spec file is located in doc/source/specs/skeleton.rst and can be copied, then filled in with the details of a new blueprint for convenience.

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:

http://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.

Description
OpenStack Networking (Neutron) Specifications
Readme 29 MiB
Languages
Python 100%