e04ef0fcbe
Currently IPMI is not fully supported by OpenBMC. Instead, OpenBMC's power and boot device is controlled through a RESTful interface. While IPMI may be a supported mechanism in the future for OpenBMC, the recommended way to interact with it will continue to be its RESTful API. This means that servers running OpenBMC will require a new module to control its power, a new module to set the boot device, and a hardware type that has these modules supported. This patch adds a spec for these items. Partial-bug: #1634635 Change-Id: Ie272f3ad2d4ae5bcb1bd542007dfcdb4adfcb799 |
||
|---|---|---|
| doc/source | ||
| priorities | ||
| specs | ||
| tests | ||
| .gitignore | ||
| .gitreview | ||
| .testr.conf | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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 doc/source/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=rfePrior 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/ironicFor more information about working with gerrit, see:
http://docs.openstack.org/infra/manual/developers.html#development-workflowTo validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
$ toxAfter 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.