mirror of
https://github.com/xcat2/xcat-core.git
synced 2026-10-12 08:12:33 +00:00
Vinícius Ferrão
b4bd8b331f
makedhcp gives a netboot=ipxe node xcat/ipxe/i386/undionly.kpxe for BIOS and xcat/ipxe/x86_64-sb/snponly-shim.efi for UEFI. That shim, which Microsoft signs, loads snponly.efi from its own directory, so the node also boots with UEFI Secure Boot on: the firmware does not load snponly.efi directly, as only the iPXE Secure Boot CA signs it. The node gets its boot script from xcat/ipxe/nodes only when it reports, in option 175, the iPXE features that the script needs: HTTP, bzImage and PXE for BIOS, HTTP and EFI for UEFI. A SAN node also needs iSCSI. Every other client of the node first gets the loader above. xNBA sends the same option, but xCAT recognizes xNBA by its user class, and the upstream loader sends the user class of a firmware iPXE. The upstream loader does not have to be in the local TFTP directory, because a node can load from another TFTP server. ISC applies the test in the host statements of the node, and nests each feature test inside its architecture test: dhcpd saves a host statement in dhcpd.leases without parentheses, and omshell reads only 1023 bytes of the line that sets it. Kea applies it in the classes of the node, which carry their own first-stage loader and the purpose ipxe-boot. As for an xnba node, a node in state boot or iscsiboot gets no boot file unless it boots from SAN. The statements and classes of netboot=xnba and netboot=pxe nodes do not change.