9750f945db
Previously: - expect one kernel image and one ramdisk image - expect every overcloud node to use the same kernel and and ramdisk Now: - expect any number of kernel/ramdisk images - expect each overcloud node to use the most suitable kernel/ramdisk in accordance with arch/platform of that node (but recognizing that, for any given node, the form that the "most suitable" image takes may vary) Currently only Glance images are considered; support for file images as introduced in Train will come in a subsequent patch. Blueprint: multiarch-support Change-Id: I5a49b60fd32d9032b4dec1a01a3fdad6fddf42aa
17 lines
760 B
YAML
17 lines
760 B
YAML
---
|
|
features:
|
|
- |
|
|
The behavior of the ``ironic-boot-configuration`` validation has changed
|
|
in order to suppport multi-arch. It now checks that each node has the
|
|
correct associated ramdisk and kernel image according to the node's
|
|
architecture and platform, and, when it does appear that the correct image
|
|
is associated, checks that there is only one image in Glance with that
|
|
name. Also, the vars ``deploy_kernel_name`` and ``deploy_ramdisk_name``
|
|
have changed to ``deploy_kernel_name_base`` and
|
|
``deploy_ramdisk_name_base`` respectively.
|
|
other:
|
|
- |
|
|
The ``deployment-images`` validation has been removed, as its intended
|
|
functionality became inseparable from ``ironic-boot-configuration`` in the
|
|
multi-arch case.
|