7d8e349096
This commit removes the CONF variables CONF.raid.share_physical_disks, CONF.raid.disk_type and CONF.raid.interface_type. This is because in heterogenous hardware environments, it is not possible to provide a single disk_type and interface_type as the default value as that will lead to cleaning failures (when it is unable to find suitable devices). If operator wants to use specific type of disks for a bare metal node, they should rather set it in node's target raid config. It also removes CONF.raid.share_physical_disks as it is not common to share physical disks across RAID disks (and if required can again be set to False in the node's target_raid_config). Change-Id: Ia5e2c2774c71d68506742edd15f68a37f1131761
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/ironicPlease note, Launchpad blueprints are still used for tracking the current status of blueprints. For more information, see:
https://wiki.openstack.org/wiki/BlueprintsFor 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.