4dfde43b25
Change-Id: I932157f80f58d17ce66df60fde31bb812f74d05f
21 lines
869 B
YAML
21 lines
869 B
YAML
---
|
|
features:
|
|
- |
|
|
Adds support to deploy to nodes with different CPU architectures
|
|
from a single conductor. This depends on
|
|
two new configuration options, ``[pxe]/pxe_config_template_by_arch``
|
|
and ``[pxe]/pxe_bootfile_name_by_arch``. Each is a
|
|
dictionary mapping CPU architecture to PXE config template or
|
|
PXE boot file name, respectively.
|
|
|
|
As an example, the syntax might look like::
|
|
|
|
pxe_config_template_by_arch=aarch64:pxe_grubaa64_config.template,ppc64:pxe_ppc64_config.template
|
|
|
|
Ironic attempts to map the CPU architecture in this mapping to
|
|
the ``properties/cpu_arch`` field for a node. If the node's CPU
|
|
architecture is not found in the mapping, ironic will fall back to
|
|
the standard options ``pxe_config_template``,
|
|
``pxe_bootfile_name``, ``uefi_pxe_config_template``,
|
|
and ``uefi_pxe_bootfile_name``.
|