diff options
author | Zuul <zuul@review.opendev.org> | 2020-05-28 12:28:04 +0000 |
---|---|---|
committer | Gerrit Code Review <review@openstack.org> | 2020-05-28 12:28:04 +0000 |
commit | c358dac03db943faf7fe3ccce120c7bad63c46ec (patch) | |
tree | 81ce61193a2466f86d7866ddae485dcae18cd7de /doc | |
parent | 81e8f819f2fe69ccd1f9c9c3f8aaac5c09db74c1 (diff) | |
parent | 51eff6010f954efcc87c262f693247bc4c41380a (diff) | |
download | ironic-c358dac03db943faf7fe3ccce120c7bad63c46ec.tar.gz |
Merge "Add the noop management interface to the redfish hardware type"
Diffstat (limited to 'doc')
-rw-r--r-- | doc/source/admin/drivers.rst | 35 | ||||
-rw-r--r-- | doc/source/admin/drivers/ipmitool.rst | 25 |
2 files changed, 36 insertions, 24 deletions
diff --git a/doc/source/admin/drivers.rst b/doc/source/admin/drivers.rst index 627702cf2..267409403 100644 --- a/doc/source/admin/drivers.rst +++ b/doc/source/admin/drivers.rst @@ -104,6 +104,41 @@ not compatible with them. There are three ways to deal with this situation: .. note:: This feature is available starting with ironic 11.1.0 (Rocky series, API version 1.45). +.. _static-boot-order: + +Static boot order configuration +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Some hardware is known to misbehave when changing the boot device through the +BMC. To work around it you can use the ``noop`` management interface +implementation with the ``ipmi`` and ``redfish`` hardware types. In this case +the Bare Metal service will not change the boot device for you, leaving +the pre-configured boot order. + +For example, in case of the :ref:`pxe-boot`: + +#. Via any available means configure the boot order on the node as follows: + + #. Boot from PXE/iPXE on the provisioning NIC. + + .. warning:: + If it is not possible to limit network boot to only provisioning NIC, + make sure that no other DHCP/PXE servers are accessible by the node. + + #. Boot from hard drive. + +#. Make sure the ``noop`` management interface is enabled, for example: + + .. code-block:: ini + + [DEFAULT] + enabled_hardware_types = ipmi,redfish + enabled_management_interfaces = ipmitool,redfish,noop + +#. Change the node to use the ``noop`` management interface:: + + openstack baremetal node set <NODE> --management-interface noop + Unsupported drivers ------------------- diff --git a/doc/source/admin/drivers/ipmitool.rst b/doc/source/admin/drivers/ipmitool.rst index b6d64f17d..dd051d988 100644 --- a/doc/source/admin/drivers/ipmitool.rst +++ b/doc/source/admin/drivers/ipmitool.rst @@ -171,30 +171,7 @@ protocol version:: Static boot order configuration ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Some hardware is known to misbehave when changing the boot device through the -IPMI protocol. To work around it you can use the ``noop`` management interface -implementation with the ``ipmi`` hardware type. In this case the Bare Metal -service will not change the boot device for you, leaving the pre-configured -boot order. - -For example, in case of the :ref:`pxe-boot`: - -#. Via any available means configure the boot order on the node as follows: - - #. Boot from PXE/iPXE on the provisioning NIC. - - .. warning:: - If it is not possible to limit network boot to only provisioning NIC, - make sure that no other DHCP/PXE servers are accessible by the node. - - #. Boot from hard drive. - -#. Make sure the ``noop`` management interface is enabled, see example in - `Enabling the IPMI hardware type`_. - -#. Change the node to use the ``noop`` management interface:: - - openstack baremetal node set <NODE> --management-interface noop +See :ref:`static-boot-order`. .. TODO(lucasagomes): Write about privilege level .. TODO(lucasagomes): Write about force boot device |