openstack
/
tacker-specs
Code Issues Proposed changes
NFV Orchestration (Tacker) Specifications
100 Commits 1 Branch 0 Tags 17 MiB
Python 100%
Go to file
Nguyen Hai cf9b74dcf3 import zuul job settings from project-config 
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: Ib556c6fc1ba8ca3b9867d47df9e289aaa73fb016
Story: #2002586
Task: #24324
 		2018-08-17 20:15:37 +09:00
doc Refactor and clean up specs dir 2018-04-05 15:21:56 +09:00
specs Merge "Support shared vim for policy action execution" 2018-07-26 07:41:45 +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
.zuul.yaml import zuul job settings from project-config 2018-08-17 20:15:37 +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
setup.cfg Refactor and clean up specs dir 2018-04-05 15:21:56 +09:00
setup.py Add base tacker-specs framework 2014-06-03 17:55:27 +09:00
test-requirements.txt Refactor and clean up specs dir 2018-04-05 15:21:56 +09:00
tox.ini Refactor and clean up specs dir 2018-04-05 15:21:56 +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.