openstack/ironic
Code Issues Proposed changes

Merge "Remove doc of classic drivers from the admin guide"

Browse Source
This commit is contained in:
Zuul 2018-07-04 05:19:11 +00:00 committed by Gerrit Code Review
commit ea302a8cd5
3 changed files with 5 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/source/admin/interfaces/boot.rst
View File

@ -33,8 +33,7 @@ understanding of the whole deployment process.
architectures that do not have BIOS support at all. architectures that do not have BIOS support at all.
The ``pxe`` boot interface is used by default for many hardware types, The ``pxe`` boot interface is used by default for many hardware types,
including ``ipmi``, and for all classic drivers with names starting with including ``ipmi``. Some hardware types, notably ``ilo`` and ``irmc`` have their
``pxe_``. Some hardware types, notably ``ilo`` and ``irmc`` have their
specific implementations of the PXE boot interface. specific implementations of the PXE boot interface.
Additional configuration is required for this boot interface - see Additional configuration is required for this boot interface - see

11
doc/source/admin/interfaces/deploy.rst
View File

@ -24,9 +24,6 @@ when creating or updating a node::
openstack baremetal node create --driver ipmi --deploy-interface iscsi openstack baremetal node create --driver ipmi --deploy-interface iscsi
openstack baremetal node set <NODE> --deploy-interface iscsi openstack baremetal node set <NODE> --deploy-interface iscsi
The ``iscsi`` deploy interface is also used in all of the *classic drivers*
with names starting with ``pxe_`` and ``iscsi_``.
.. _iSCSI: https://en.wikipedia.org/wiki/ISCSI .. _iSCSI: https://en.wikipedia.org/wiki/ISCSI
.. _direct-deploy: .. _direct-deploy:
@ -46,14 +43,10 @@ You can specify this deploy interface when creating or updating a node::
openstack baremetal node create --driver ipmi --deploy-interface direct openstack baremetal node create --driver ipmi --deploy-interface direct
openstack baremetal node set <NODE> --deploy-interface direct openstack baremetal node set <NODE> --deploy-interface direct
The ``direct`` deploy interface is also used in all *classic drivers*
whose names include ``agent``.
.. note:: .. note::
For historical reasons the ``direct`` deploy interface is sometimes called For historical reasons the ``direct`` deploy interface is sometimes called
``agent``, and some *classic drivers* using it are called ``agent_*``. ``agent``. This is because before the Kilo release **ironic-python-agent**
This is because before the Kilo release **ironic-python-agent** used to used to only support this deploy interface.
only support this deploy interface.
.. _ansible-deploy: .. _ansible-deploy:

5
doc/source/admin/raid.rst
View File

@ -66,8 +66,7 @@ If the ``target_raid_config`` is an empty dictionary, it unsets the value of
done on the node. done on the node.
Each dictionary of logical disk contains the desired properties of logical Each dictionary of logical disk contains the desired properties of logical
disk supported by the hardware type or classic driver. These properties are disk supported by the hardware type. These properties are discoverable by::
discoverable by::
openstack baremetal --os-baremetal-api-version 1.15 driver raid property list <driver name> openstack baremetal --os-baremetal-api-version 1.15 driver raid property list <driver name>
@ -244,7 +243,7 @@ Workflow
======== ========
* Operator configures the bare metal node with a hardware type that has * Operator configures the bare metal node with a hardware type that has
a ``RAIDInterface`` other than ``no-raid`` (``None`` for classic drivers). a ``RAIDInterface`` other than ``no-raid``.
* For in-band RAID configuration, operator builds an agent ramdisk which * For in-band RAID configuration, operator builds an agent ramdisk which
supports RAID configuration by bundling the hardware manager with the supports RAID configuration by bundling the hardware manager with the