Sumit Naiksatam 20ecc759fc L3-Policy mapping to Address Scope & Subnetpool
Starting in the Mitaka release Neutron defines and supports the use of Address
Scopes. Subnet-pools were defined in the earlier Kilo release and can now be
used within Address Scopes. The notion of an address scope has existed in GBP
in the form of L3-Policy. The GBP L3-Policy manages the address-scope and
subnet-pools with its own home-grown implementation. It would be preferable to
leverage the Neutron address-scopes and subnet-pools instead.

Change-Id: I9e4335073dc8ec0cb85db909560c49e0dddefe82
Defines: blueprint address-scope-mapping
2016-08-17 22:21:39 -07:00
2014-10-05 20:40:52 -07:00
2015-10-17 22:29:52 +00:00
2014-10-05 20:40:52 -07:00

Group Based Policy Specifications

This git repository is used to hold approved design specifications for additions to the Group Based Policy 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.

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
Group Based Policy Design Specifications
Readme 986 KiB
Languages
reStructuredText 98.7%
Python 1.3%