RETIRED, Design Specifications for OpenStack-Salt
Go to file
Ales Komarek 935ed9ebd4 Initial commit 2015-11-24 18:15:19 +01:00
doc/source Initial commit 2015-11-24 18:15:19 +01:00
specs Initial commit 2015-11-24 18:15:19 +01:00
.gitignore Initial commit 2015-11-24 18:15:19 +01:00
LICENSE Initial commit 2015-11-24 18:15:19 +01:00
README.rst Initial commit 2015-11-24 18:15:19 +01:00
requirements.txt Initial commit 2015-11-24 18:15:19 +01:00
setup.cfg Initial commit 2015-11-24 18:15:19 +01:00
setup.py Initial commit 2015-11-24 18:15:19 +01:00
tox.ini Initial commit 2015-11-24 18:15:19 +01:00

README.rst

OS-Salt-Deployment Specifications

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

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.