049fd40719
With the proposal to solve the bug that PXE interface should
be using non-persistent boot for cleaning/deploying phases as
default(commit: c7091fb8e2), it's
necessary to create a flag to enable persistent behavior when
you set the boot device.
This flag will override a non-persistent behavior in the
cleaning and deploy process.
Change-Id: I1f47393c17a3f5319fffd963ec0a016b41865c5d
Closes-Bug: 1703945
Co-Authored-By: Stenio Araujo <steniaraujo@lsd.ufcg.edu.br>
27 lines
959 B
ReStructuredText
27 lines
959 B
ReStructuredText
.. pxe:
|
|
|
|
==============================
|
|
Configuring PXE boot interface
|
|
==============================
|
|
|
|
Enable persistent boot device for deploy/clean operation
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Ironic uses non-persistent boot for cleaning/deploying phases as default,
|
|
in PXE interface. For some drivers, a persistent change is far more
|
|
costly than a non-persistent one, so this can bring performance improvements.
|
|
|
|
Enable persistent boot device on node
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
1. Set the flag ``force_persistent_boot_device`` to ``True`` in the node's ``driver_info``::
|
|
|
|
$ openstack baremetal node set --driver-info force_persistent_boot_device=True <node>
|
|
|
|
.. note::
|
|
It's recommended to check if the node's state has not changed as there
|
|
is no way of locking the node between these commands.
|
|
|
|
Once the flag is present, the next cleaning and deploy steps will be done
|
|
with persistent boot for that node.
|