openstack/ironic-specs
Code Issues Proposed changes
OpenStack Baremetal (Ironic) Specifications
516 Commits 1 Branch 0 Tags 20 MiB
Python 100%
9839d23bff
Go to file
Ruby Loo 9839d23bff two finished specs 
The ansible deploy hardware type was finished in Queens 10.1 release
and the additional capabilities were added to ironic inspection in
Pike 9.2 release.

Change-Id: I0ce54a7afbbfb0deb1794bab2abea85def6bff7f
2018-03-08 14:03:06 -05:00
doc/source two finished specs 2018-03-08 14:03:06 -05:00
priorities Move traits from "high" to "essential" priority 2017-12-15 12:11:09 -08:00
specs two finished specs 2018-03-08 14:03:06 -05:00
tests Allow spec to have RFE from any ironic project 2017-03-06 17:52:53 -05: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 Replace http with https for doc links 2017-09-08 08:49:27 +00:00
requirements.txt Add RSS feed 2014-09-10 16:00:19 -04:00
setup.cfg Changed the home-page of Ironic-specs in setup.cfg 2016-10-23 22:03:42 +05:30
setup.py Initial commit 2014-05-22 15:51:33 -07:00
test-requirements.txt Use doc8 style checker 2015-09-30 20:29:50 +00:00
tox.ini Remove py27 env from tox.ini 2017-10-25 17:54:59 +03:00

README.rst

Team and repository tags

image

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/approved/
specs/backlog/
specs/not-implemented/
specs/<release>/
specs/<juno|kilo|liberty>-implemented/

There are also placeholder directories for old links that have been moved.

Specifications must follow the template which can be found at specs/template.rst.

Specifications are proposed by adding them to the specs/approved directory, adding a soft link to it from the specs/not-implemented directory, and posting it for review. When a specification is fully implemented, the link in specs/not-implemented directory should be moved to the appropriate specs/<release> directory. Not all approved specifications will get fully implemented.

Starting with the Mitaka development cycle, all approved specifications (implemented and not-implemented) will reside in the specs/approved directory.

Also starting with the Mitaka development cycle, our Launchpad bug tracking system is used for tracking the work related to a specification. (This replaces the use of Launchpad blueprints). The bug should be tagged with 'rfe', its title should be prefixed with '[RFE]' and the Importance should be set to 'Wishlist'. For existing RFE bugs, see:

https://bugs.launchpad.net/ironic/+bugs?field.tag=rfe

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/ironic

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.

To quickly preview just the rst syntax rendering (without Sphinx features) of a single spec file execute the following command:

$ tox -evenv rst2html.py <path-to-your-spec.rst> <path-to-output.html>

and open <path-to-output.html> in your browser. Running full tox is still advised before submitting your patch.