NFV Orchestration (Tacker) Specifications
Go to file
Nguyen Hai cb198146a3 Change tacker-specs webpage from oslosphinx to openstackdocstheme
+ Changes tacker-specs webpage from oslosphinx to openstackdocstheme.
+ Clean up some example templates and update links.

Change-Id: I639c86a37e93a16171960f7b20a2538e118e4b97
Closes-Bug: #1754960
2018-03-13 12:41:45 +09:00
doc/source Change tacker-specs webpage from oslosphinx to openstackdocstheme 2018-03-13 12:41:45 +09:00
specs Change tacker-specs webpage from oslosphinx to openstackdocstheme 2018-03-13 12:41:45 +09:00
tests Add ocata dir for tacker-specs 2016-08-20 02:22:07 +00:00
.gitignore Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:40:58 +00:00
.testr.conf Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
LICENSE Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
README.rst Change tacker-specs webpage from oslosphinx to openstackdocstheme 2018-03-13 12:41:45 +09:00
requirements.txt Change tacker-specs webpage from oslosphinx to openstackdocstheme 2018-03-13 12:41:45 +09:00
setup.cfg Change tacker-specs webpage from oslosphinx to openstackdocstheme 2018-03-13 12:41:45 +09:00
setup.py Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
tox.ini Change tacker-specs webpage from oslosphinx to openstackdocstheme 2018-03-13 12:41:45 +09:00

README.rst

Team and repository tags

image

OpenStack Tacker Specifications

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

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

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

Launchpad blueprints for Tacker can be found at:

https://blueprints.launchpad.net/tacker

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 checkin the generated HTML files as a part of your commit.