From 82026817727cfb84c846e5fa97e80d0ba98ec9cf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zuzana=20Lena=20Ansorgov=C3=A1?= Date: Mon, 12 Aug 2024 19:36:18 +0200 Subject: [PATCH] Improve intro for PXE provisioning concept (#3184) Co-authored-by: Maximilian Kolb --- .../con_using-pxe-to-provision-hosts.adoc | 32 +++++++++++++------ 1 file changed, 23 insertions(+), 9 deletions(-) diff --git a/guides/common/modules/con_using-pxe-to-provision-hosts.adoc b/guides/common/modules/con_using-pxe-to-provision-hosts.adoc index 4f7c96a777b..57e7fa66ada 100644 --- a/guides/common/modules/con_using-pxe-to-provision-hosts.adoc +++ b/guides/common/modules/con_using-pxe-to-provision-hosts.adoc @@ -34,20 +34,34 @@ endif::[] .BIOS and UEFI Support With {ProjectName}, you can perform both BIOS and UEFI based PXE provisioning. -Both BIOS and UEFI interfaces work as interpreters between the computer's operating system and firmware, initializing the hardware components and starting the operating system at boot time. - -ifdef::satellite[] -For information about supported workflows, see https://access.redhat.com/solutions/2674001[Supported architectures and provisioning scenarios]. -endif::[] +Both BIOS and UEFI interfaces work as interpreters between the operating system and firmware of a computer, initializing hardware components and starting the operating system at boot time. +.PXE loaders In {Project} provisioning, the PXE loader option defines the DHCP `filename` option to use during provisioning. -For BIOS systems, use the *PXELinux BIOS* option to enable a provisioned node to download the `pxelinux.0` file over TFTP. -For UEFI systems, use the *PXEGrub2 UEFI* option to enable a TFTP client to download `grub2/grubx64.efi` file, or use the *PXEGrub2 UEFI HTTP* option to enable an UEFI HTTP client to download `grubx64.efi` from {SmartProxy} with the HTTP Boot feature. + +* For BIOS systems, use the *PXELinux BIOS* option to enable a provisioned host to download the `pxelinux.0` file over TFTP. +* For UEFI systems, use the *PXEGrub2 UEFI* option to enable a TFTP client to download `grub2/grubx64.efi` file, or use the *PXEGrub2 UEFI HTTP* option to enable an UEFI HTTP client to download `grubx64.efi` from {SmartProxy} with the HTTP Boot feature. + ifndef::satellite[] -Use SecureBoot options to enable a client to download the `shim.efi` bootstrap bootloader that then loads the signed `grubx64.efi`. -Other PXE loaders like PXELinux UEFI, Grub2 ELF or iPXE Chain, require additional configuration. These workflows are not documented at the moment. +{ProjectName} supports UEFI Secure Boot. +SecureBoot PXE loaders enable a client to download the `shim.efi` bootstrap boot loader that then loads the signed `grubx64.efi`. +Use the *Grub2 UEFI SecureBoot* PXE loader for PXE-boot provisioning or *Grub2 UEFI HTTPS SecureBoot* for HTTP-boot provisioning. + +[IMPORTANT] +==== +You can only use Secure Boot to provision hosts with the same operating system version, major and minor, that runs on your TFTP {SmartProxy}. +==== +endif::[] + +ifdef::satellite[] +For more information about supported workflows, see https://access.redhat.com/solutions/2674001[Supported architectures and provisioning scenarios]. endif::[] +ifndef::satellite[] +Other PXE loaders, such as PXELinux UEFI, Grub2 ELF, or iPXE Chain, require additional configuration. +These workflows are not documented. +.Template association with operating systems For BIOS provisioning, you must associate a PXELinux template with the operating system. For UEFI provisioning, you must associate a PXEGrub2 template with the operating system. If you associate both PXELinux and PXEGrub2 templates, {Project} can deploy configuration files for both on a TFTP server, so that you can switch between PXE loaders easily. +endif::[]