206134cf58
By default, Ironic makes persistent changes to the system boot order at the end of an instance deployment. This may not be desired in all cases, e.g. when DC policies require to leave the persistent system boot order unchanged. While keeping the persistent approach as the default, this patch proposes to extent the existing 'force_persistent_boot_device' field in the node's driver_info for (i)PXE in a way that allows to have all boot device changes to be non-persistent. Change-Id: If3a19f74fb0dfbcff2cde4cd5a8cc1edf5de3058 Story: #2004846 Task: #29058
18 lines
819 B
YAML
18 lines
819 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds capability to control the persistency of boot order changes during
|
|
instance deployment via (i)PXE on a per-node level. The option
|
|
'force_persistent_boot_device' in the node's driver info for the (i)PXE
|
|
drivers is extended to allow the values 'Default' (make all changes
|
|
but the last one upon deployment non-persistent), 'Always' (make all
|
|
changes persistent), and 'Never' (make all boot order changes
|
|
non-persistent).
|
|
deprecations:
|
|
- |
|
|
The values 'True'/'False' for the option 'force_persistent_boot_device'
|
|
in the node's driver info for the (i)PXE drivers are deprecated and
|
|
support for them may be removed in a future release. The former default
|
|
value 'False' is replaced by the new value 'Default', the value 'True'
|
|
is replaced by 'Always'.
|