openstack
/
ironic
Code Issues Proposed changes

docs: revise notes around iso booting for clarity 

Had someone try to boot the tinycore ISO on a UEFI machine, and they
got a nice error. Just turns out we needed to update our docs a little
bit to provide appropriate clarity.

Change-Id: I1adfb62ea22d0b58740ceadc8c338fc04d9b78de
This commit is contained in:
Julia Kreger 2024-05-01 10:14:20 -07:00
parent dec5780fca
commit 021117e354
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
devstack/lib/ironic
View File

@ -612,6 +612,9 @@ PHYSICAL_NETWORK=${NEUTRON_PHYSICAL_NETWORK:-${PHYSICAL_NETWORK:-}}
# NOTE(TheJulia): As of May 19th, 2023, mirrors.dotsrc.org was
# accessible via ipv4 and ipv6, it appears to be the only v6
# accessible tinycore mirror..
# NOTE(TheJulia): The TinyCore Image *is* only compatible with
# BIOS booting. iPXE loaders with UEFI mode will ERROR pointing
# to https://ipxe.org/err/7f22208e.
IRONIC_RAMDISK_IMAGE=${IRONIC_RAMDISK_IMAGE:-http://mirrors.dotsrc.org/tinycorelinux/14.x/x86/release/Core-current.iso}
IRONIC_LOADER_PATHS=${IRONIC_LOADER_PATHS:-}

5
doc/source/admin/ramdisk-boot.rst
View File

@ -113,6 +113,11 @@ For example,
This is a limitation of iPXE and the overall boot process of the
operating system where memory allocated by iPXE is released.
When choosing your boot ISO, your ISO image will need to be sufficient to boot
the hardware under normal conditions. For example, if the ISO is only
compatible with BIOS booting, then a host in UEFI mode will not boot.
This is not a limitation of Ironic, but an architectural limitation.
By default the Bare Metal service will cache the ISO locally and serve from its
HTTP server. If you want to avoid that, set the following: