OpenStack Baremetal (Ironic) Specifications
Go to file
Devananda van der Veen 6aceb0802a fix the filename for hardware-capabilities.rst
This spec file name did not match the blueprint title, and so the file
is being renamed.

Change-Id: I78de2fe97b7385a26693d22beb6c0c956a579b65
2014-12-08 22:21:16 -08:00
doc/source Allow short-specs 2014-11-19 15:16:58 -08:00
specs fix the filename for hardware-capabilities.rst 2014-12-08 22:21:16 -08:00
tests Add a test for license header 2014-11-26 08:22:22 -08:00
.gitignore Initial commit 2014-05-22 15:51:33 -07:00
.gitreview Updated .gitreview file for repo rename 2014-05-26 16:06:07 +00:00
.testr.conf Initial commit 2014-05-22 15:51:33 -07:00
LICENSE Initial commit 2014-05-22 15:51:33 -07:00
README.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:36 +00:00
requirements.txt Add RSS feed 2014-09-10 16:00:19 -04:00
setup.cfg Initial commit 2014-05-22 15:51:33 -07:00
setup.py Initial commit 2014-05-22 15:51:33 -07:00
tox.ini Initial commit 2014-05-22 15:51:33 -07:00

OpenStack Baremetal Provisioning Specifications

This git repository is used to hold approved design specifications for additions to the Baremetal Provisioning program, and in particular, the Ironic 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>/

Specifications must follow the template which can be found at 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:

http://blueprints.launchpad.net/ironic

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.