openstack
/
ironic-specs
Code Issues Proposed changes
OpenStack Baremetal (Ironic) Specifications
457 Commits 1 Branch 0 Tags 20 MiB
Python 100%
Go to file
Ruby Loo 5370fd3878 Rolling upgrades: different object versions 
This updates the rolling upgrades spec to change the design
of how ironic services will handle the different IronicObject
versions during a rolling upgrade.

It also adds some more alternatives.

Change-Id: I3c6caa639aa75ed87bddd59bf514e2d904db6e0a
Partial-Bug: #1526283
 		2017-06-06 16:21:21 -04:00
doc/source Merge "Add priorities for the Pike cycle" 2017-03-10 10:34:42 +00:00
priorities Remove Pike priorities that cannot make it due to recent team changes 2017-04-28 17:31:19 +02:00
specs Rolling upgrades: different object versions 2017-06-06 16:21:21 -04: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 TrivialFix: Update the path of template.rst file. 2016-12-09 16:01:57 +07: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 Pin the python version for tox -edocs 2017-03-02 15:07:54 +00: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:

http://blueprints.launchpad.net/ironic

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.

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.