e19fd1d050
This change adds two network boot interfaces, ``http`` and ``http-ipxe``. These interfaces are based upon the underlying PXE boot interface code in ironic, and where this differs is it signals to Ironic that we must do the boot loader needful in terms of telling DHCP to send a URL instead of a filename and IP address for PXE as a starting point. The naming of the interfaces focuses more on the transport mechanism and then specific style. Very similar to existing ``pxe`` and ``ipxe`` interface modeling, except in the ``ipxe`` case, it is more a specific loader and mechanism to be utilized. Related-Bug: #2032380 Change-Id: Ie7ace88b62b9179f640ef2a732dd228e12bd320d
22 lines
1.1 KiB
YAML
22 lines
1.1 KiB
YAML
---
|
|
features:
|
|
- |
|
|
Adds a ``http`` boot interface, based upon the ``pxe`` boot interface
|
|
which informs the DHCP server of an HTTP URL to boot the machine from,
|
|
and then requests the BMC boot the machine in UEFI HTTP mode.
|
|
- |
|
|
Adds a ``http-ipxe`` boot interface, based upon the ``ipxe`` boot interface
|
|
which informs the DHCP server of an HTTP URL to boot the machine from,
|
|
and then requests the BMC boot the machine in UEFI HTTP mode.
|
|
issues:
|
|
- |
|
|
Testing of the ``http`` boot interface with Ubuntu 22.04 provided Grub2
|
|
yielded some intermittent failures which appear to be more environmental
|
|
in nature as the signed Shim loader would start, then load the GRUB
|
|
loader, and then some of the expected files might be attempted to be
|
|
accessed, and then fail due to an apparent transfer timeout. Consultation
|
|
with some grub developers concur this is likely environmental, meaning
|
|
the specific grub build or CI performance related. If you encounter any
|
|
issues, please do not hestitate to reach out to the Ironic developer
|
|
community.
|