Design Specifications for OpenStack-Ansible
Go to file
Jeremy Stanley 5461b6c4cb Update .gitreview for project rename
Change-Id: Ie715db2c936bfd3f559623525622f9cf3b2612cb
2015-09-11 20:58:14 +00:00
doc/source Move specs to appropriate cycle folders 2015-09-07 10:44:32 +01:00
specs Move specs to appropriate cycle folders 2015-09-07 10:44:32 +01:00
tests Cleaned up specs directory 2015-07-24 08:33:20 -05:00
tools Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
.gitignore Add tox generated files to .gitignore 2015-08-03 12:28:36 +01:00
.gitreview Update .gitreview for project rename 2015-09-11 20:58:14 +00:00
.testr.conf Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
LICENSE Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
README.rst Add tox generated files to .gitignore 2015-08-03 12:28:36 +01:00
requirements.txt Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
setup.cfg Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
setup.py Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00
tox.ini Initial commit for OS-Ansible-Deployment specs 2015-03-17 14:19:19 -05:00

README.rst

OS-Ansible-Deployment Specifications

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

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/openstack-ansible

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.