Fine tune Network Boot provisioning (#4040)

Lennonka · web-flow · commit fbb3af5bb5e5 · 2025-09-08T15:53:33.000+02:00
diff --git a/guides/common/assembly_using-network-boot-to-provision-hosts.adoc b/guides/common/assembly_using-network-boot-to-provision-hosts.adoc
@@ -2,7 +2,7 @@
 
 :using-network-boot-to-provision-hosts:
 :parent-context: {context}
-:context: using-netboot
+:context: using-network-boot
 
 include::modules/con_using-network-boot-to-provision-hosts.adoc[]
 
@@ -147,12 +147,16 @@ endif::[]
 
 include::modules/proc_creating-hosts-with-pxe-boot-provisioning.adoc[leveloffset=+1]
 
+include::modules/proc_configuring-smartproxy-for-uefi-http-booting.adoc[leveloffset=+1]
+
 include::modules/proc_creating-hosts-with-uefi-http-boot-provisioning.adoc[leveloffset=+1]
 
 include::modules/proc_deploying-ssh-keys-during-provisioning.adoc[leveloffset=+1]
 
 include::assembly_using-ipxe-to-reduce-provisioning-times.adoc[leveloffset=+1]
 
+include::modules/ref_pxe-loaders.adoc[leveloffset=+1]
+
 :context: {parent-context}
 :!parent-context:
 :!using-network-boot-to-provision-hosts:
diff --git a/guides/common/modules/con_configuring-smartproxy-for-secure-boot.adoc b/guides/common/modules/con_configuring-smartproxy-for-secure-boot.adoc
@@ -3,4 +3,4 @@
 [id="configuring-{smart-proxy-context}-for-secure-boot"]
 = Configuring {SmartProxy} for Secure Boot
 
-If you want to provision Secure Boot enabled hosts, configure your {SmartProxy} for the provisionable operating system.
+If you want to provision Secure Boot enabled hosts, configure your {SmartProxy} for the client operating system.
diff --git a/guides/common/modules/con_prerequisites-for-network-boot-provisioning.adoc b/guides/common/modules/con_prerequisites-for-network-boot-provisioning.adoc
@@ -5,14 +5,25 @@
 
 The requirements for network-boot provisioning include:
 
-* {SmartProxy} managing the network for the network-booted machines.
-For unattended provisioning and discovery-based provisioning, {Project} requires PXE server settings.
+* Provisioning infrastructure services (DNS, DHCP, TFTP) are integrated with {Project} and configured.
+ifndef::satellite[]
+* Provisioning templates are associated with a client operating system.
 +
-For more information about networking requirements, see xref:preparing-networking[].
+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} deploys configuration files for both on a TFTP server, so that you can switch between PXE loaders easily.
+endif::[]
+* A bare-metal machine or a blank virtual machine.
+The provisioned machine must appear on the same network as your provisioning infrastructure services.
 +
-For more information about the Discovery service, see xref:discovering-hosts-on-a-network[].
-
-* A bare-metal host or a blank VM.
+You can integrate a compute resource with {Project} and let the compute resource create virtual machines through this integration.
+You can also provision virtual machines from unintegrated infrastructure as you would bare-metal machines.
 include::snip_prerequisites-common-compute-resource.adoc[]
 
-For information about the security token for unattended and PXE-less provisioning, see xref:configuring-the-security-token-validity-duration[].
+[role="_additional-resources"]
+.Additional resources
+* {IntegratingProvisioningInfrastructureServicesDocURL}[{IntegratingProvisioningInfrastructureServicesDocTitle}]
+* xref:preparing-networking[]
+* xref:associating-templates-with-operating-systems[]
+* xref:discovering-hosts-on-a-network[]
+* xref:configuring-the-security-token-validity-duration[]
diff --git a/guides/common/modules/con_using-network-boot-to-provision-hosts.adoc b/guides/common/modules/con_using-network-boot-to-provision-hosts.adoc
@@ -3,87 +3,27 @@
 [id="using-network-boot-to-provision-hosts"]
 = Using network boot to provision hosts
 
-You can provision bare-metal instances with {Project} by using one of the following methods:
+After integrating provisioning infrastructure services with {Project}, you can provision hosts with {ProjectName} by booting hosts over a network.
+Once the host boots, {ProjectServer} or {SmartProxyServer} provides operating system installation content that the host downloads.
+After the operating system has been installed, the host registers to {Project} and {Project} performs an initial configuration of the host.
 
-Unattended Provisioning::
-New hosts are identified by a MAC address.
-{ProjectServer} provisions the host by using a PXE boot process.
-
-Unattended Provisioning with Discovery::
-New hosts use PXE boot to load the {Project} Discovery service.
-This service identifies hardware information about the host and lists it as an available host to provision.
-For more information, see xref:discovering-hosts-on-a-network[].
-
-PXE-less Provisioning::
-ifndef::satellite[]
-New hosts are provisioned with a boot disk or PXE-less discovery image that {ProjectServer} generates.
-
-PXE-less Provisioning with Discovery::
-New hosts use an ISO boot disk that loads the {Project} Discovery service.
-This service identifies hardware information about the host and lists it as an available host to provision.
-For more information, see xref:discovery-in-pxeless-mode[].
-endif::[]
-ifdef::satellite[]
-New hosts are provisioned with a boot disk image that {ProjectServer} generates.
-endif::[]
-
-ifndef::satellite[]
-[NOTE]
-====
-Discovery workflows are only available if the Discovery plug-in is installed.
-For more information, see xref:discovering-hosts-on-a-network[].
-====
-endif::[]
-
-.BIOS and UEFI support
-With {ProjectName}, you can perform both BIOS and UEFI based PXE provisioning.
+.BIOS and UEFI interfaces
 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.
+With {Project}, you can perform both BIOS and UEFI based PXE provisioning.
+For UEFI interfaces with an HTTP boot client, you can also perform UEFI HTTP provisioning.
 
-.PXE loaders
-In {Project} provisioning, the PXE loader option defines the DHCP `filename` option to use during provisioning.
-
-* For BIOS systems, select the *PXELinux BIOS* option to enable a provisioned host to download the `pxelinux.0` file over TFTP.
-* For UEFI systems, select the *Grub2 UEFI* option to enable a TFTP client to download `grubx64.efi` file, or select the *Grub2 UEFI HTTP* option to enable an UEFI HTTP client to download `grubx64.efi` with the HTTP Boot feature.
-
-{ProjectName} supports provisioning hosts with UEFI Secure Boot.
-SecureBoot PXE loaders enable a client to download the `shimx64.efi` bootstrap boot loader that then loads the signed `grubx64.efi`.
-Use the *Grub2 UEFI SecureBoot* PXE loader for PXE-boot provisioning.
-ifndef::satellite[]
-Use the *Grub2 UEFI HTTPS SecureBoot* PXE loader for HTTP-boot provisioning.
-endif::[]
-
+.UEFI Secure Boot
+{ProjectName} supports host provisioning with UEFI Secure Boot.
 ifdef::satellite[]
 By default, you can provision the same RHEL version as your {ProjectServer} on Secure Boot enabled hosts.
 To provision other versions of {RHEL}, you have to provide signed shim and GRUB2 binaries of those RHEL versions.
-For more information, see xref:configuring-{smart-proxy-context}-to-provision-rhel-on-Secure-Boot-enabled-hosts[].
 endif::[]
 ifndef::satellite[]
 By default, you can provision operating systems from the vendor of the operating system of your {ProjectServer} on Secure Boot enabled hosts.
 To provision operating systems on Secure Boot enabled hosts from different vendors, you have to provide signed shim and GRUB2 binaries provided by the vendor of your operating system.
 endif::[]
 ifndef::orcharhino,satellite[]
-For more information, see:
-
-* xref:configuring-{smart-proxy-context}-to-provision-almalinux-on-Secure-Boot-enabled-hosts[]
-* xref:configuring-{smart-proxy-context}-to-provision-debian-on-Secure-Boot-enabled-hosts[]
-* xref:configuring-{smart-proxy-context}-to-provision-rhel-on-Secure-Boot-enabled-hosts[]
-* xref:configuring-{smart-proxy-context}-to-provision-rocky-on-Secure-Boot-enabled-hosts[]
-* xref:configuring-{smart-proxy-context}-to-provision-ubuntu-on-Secure-Boot-enabled-hosts[]
-endif::[]
-
-ifdef::satellite[]
-For more information about supported workflows, see https://access.redhat.com/solutions/2674001[Supported architectures and provisioning scenarios].
-endif::[]
-ifndef::orcharhino,satellite[]
-Other PXE loaders like *PXELinux UEFI*, *Grub2 ELF* or *iPXE Chain*, require additional configuration.
-These workflows are not documented.
-endif::[]
-
-ifndef::satellite[]
-.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} deploys configuration files for both on a TFTP server, so that you can switch between PXE loaders easily.
+For more information, see xref:configuring-{smart-proxy-context}-for-secure-boot[].
 endif::[]
 
 .Bonded network interfaces
diff --git a/guides/common/modules/proc_configuring-smartproxy-for-uefi-http-booting.adoc b/guides/common/modules/proc_configuring-smartproxy-for-uefi-http-booting.adoc
@@ -0,0 +1,40 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="configuring-{smart-proxy-context}-for-uefi-http-booting"]
+= Configuring {SmartProxy} for UEFI HTTP booting
+
+You can provision hosts from {Project} by using the UEFI HTTP Boot if the hosts have this capability.
+Configure your {SmartProxy} for UEFI HTTP booting.
+
+.Prerequisites
+* Ensure that your environment meets the requirements for HTTP booting.
+For more information, see {PlanningDocURL}http-booting[HTTP booting] in _{PlanningDocTitle}_.
+
+.Procedure
+ifndef::satellite[]
+. On your {SmartProxy}, enable the `foreman-proxy-http`, `foreman-proxy-httpboot`, and `foreman-proxy-tftp` features:
++
+[options="nowrap" subs="+quotes,attributes"]
+----
+# {foreman-installer} \
+--foreman-proxy-http true \
+--foreman-proxy-httpboot true \
+--foreman-proxy-tftp true
+----
+endif::[]
+. Ensure that {SmartProxy} is associated with the provisioning subnet.
+In the {ProjectWebUI}, navigate to *Infrastructure* > *Subnets*.
+. Click *Edit Subnet* > *{SmartProxies}*.
+. Select the {SmartProxy} for both *TFTP* and *HTTPBoot* options.
+. Click *OK* to save.
+
+ifndef::satellite[]
+.Verification
+* Ensure that the {SmartProxy} has TFTP and HTTPBoot features recognized.
+In the {ProjectWebUI}, navigate to *Infrastructure* > *{SmartProxies}* and click on {SmartProxy} to see the list of recognized features.
+Click *Refresh Features* if any of the features are missing.
+endif::[]
+
+[role="_additional-resources"]
+.Next steps
+* xref:creating-hosts-with-uefi-http-boot-provisioning[]
diff --git a/guides/common/modules/proc_creating-hosts-with-pxe-boot-provisioning.adoc b/guides/common/modules/proc_creating-hosts-with-pxe-boot-provisioning.adoc
@@ -3,11 +3,24 @@
 [id="creating-hosts-with-pxe-boot-provisioning"]
 = Creating hosts with PXE boot provisioning
 
-Unattended provisioning is the simplest form of host provisioning.
+PXE boot provisioning is a method of unattended host provisioning that requires minimal interaction during the process.
+
 You enter the host details on {ProjectServer} and boot your host.
 {ProjectServer} automatically manages the PXE configuration, organizes networking services, and provides the operating system and configuration for the host.
 
-This method of provisioning hosts uses minimal interaction during the process.
+Create a host entry to add the host details.
+When you save the host entry, {Project} creates the relevant provisioning settings.
+This also includes creating the necessary directories and files for PXE booting.
+When you boot the host, the host requests a DHCP lease.
+The DHCP service responds with a lease which includes the location of the installation content.
+The host uses the installation content to install the operating system.
+
+ifdef::katello,satellite,orcharhino[]
+During the installation, the host registers to {ProjectServer} by using the activation key, installs the necessary host management tools from the {project-client-name} repository, and performs initial configuration.
+endif::[]
+ifndef::katello,satellite,orcharhino[]
+During the installation, the host registers to {ProjectServer} and performs initial configuration.
+endif::[]
 
 To use the CLI instead of the {ProjectWebUI}, see the xref:cli-creating-hosts-with-pxe-boot-provisioning[].
 
@@ -18,25 +31,15 @@ include::snip_steps-create-a-host-tab-interfaces.adoc[]
 Confirm each aspect of the operating system.
 . Optional: Click *Resolve* in *Provisioning template* to check the new host can identify the right provisioning templates to use.
 +
-For more information about associating provisioning templates, see xref:provisioning-templates[].
+For more information about provisioning templates, see xref:provisioning-templates[].
 ifdef::katello,satellite,orcharhino[]
 include::snip_step-parameter-ak.adoc[]
 endif::[]
 . Click *Submit* to save the host details.
-+
-For more information about network interfaces, see {ManagingHostsDocURL}configuring-network-interfaces[Configuring network interfaces] in _{ManagingHostsDocTitle}_.
-
-This creates the host entry and the relevant provisioning settings.
-This also includes creating the necessary directories and files for PXE booting the bare-metal host.
-If you start the physical host and set its boot mode to PXE, the host detects the DHCP service of {ProjectServer}'s integrated {SmartProxy}, receives HTTP endpoint of the Kickstart tree and installs the operating system.
-
-ifdef::katello,satellite,orcharhino[]
-When the installation completes, the host also registers to {ProjectServer} using the activation key and installs the necessary configuration and management tools from the {project-client-name} repository.
-endif::[]
 
 [id="cli-creating-hosts-with-pxe-boot-provisioning"]
 .CLI procedure
-. Create the host with the `hammer host create` command:
+. Create the host by using Hammer:
 +
 [options="nowrap" subs="+quotes"]
 ----
diff --git a/guides/common/modules/proc_creating-hosts-with-uefi-http-boot-provisioning.adoc b/guides/common/modules/proc_creating-hosts-with-uefi-http-boot-provisioning.adoc
@@ -3,70 +3,51 @@
 [id="creating-hosts-with-uefi-http-boot-provisioning"]
 = Creating hosts with UEFI HTTP boot provisioning
 
-You can provision hosts from {Project} using the UEFI HTTP Boot.
+You can provision hosts from {Project} by using the UEFI HTTP Boot if the hosts have this capability.
+In HTTP boot, configuration files are transferred over HTTP instead of TFTP as in PXE boot.
+Using this method can help reduce the booting time during host provisioning.
+HTTP is also more reliable for transfer of large files, such as Live images, than TFTP.
+
+You enter the host details on {ProjectServer} and boot your host.
+{ProjectServer} automatically manages the HTTP boot configuration, organizes networking services, and provides the operating system and configuration for the host.
+
+Create a host entry to add the host details.
+When you save the host entry, {Project} creates the relevant provisioning settings.
+This also includes creating the necessary directories and files for PXE booting.
+When you boot the host, the host requests a DHCP lease.
+The DHCP service responds with a lease which includes the location of the installation content.
+The host uses the installation content to install the operating system.
+
+ifdef::katello,satellite,orcharhino[]
+During the installation, the host registers to {ProjectServer} by using the activation key, installs the necessary host management tools from the {project-client-name} repository, and performs initial configuration.
+endif::[]
+ifndef::katello,satellite,orcharhino[]
+During the installation, the host registers to {ProjectServer} and performs initial configuration.
+endif::[]
 
 To use the CLI instead of the {ProjectWebUI}, see the xref:cli-creating-hosts-with-uefi-http-boot-provisioning_{context}[].
 
 .Prerequisites
-* Ensure that you meet the requirements for HTTP booting.
-ifndef::orcharhino[]
-For more information, see {PlanningDocURL}http-booting[HTTP booting] in _{PlanningDocTitle}_.
-endif::[]
+* Your {SmartProxy} has been configured for UEFI HTTP booting.
+For more information, see xref:configuring-{smart-proxy-context}-for-uefi-http-booting[].
 
 .Procedure
-. Enable `foreman-proxy-http`, `foreman-proxy-httpboot`, and `foreman-proxy-tftp` features.
-+
-[options="nowrap" subs="+quotes,attributes"]
-----
-# {foreman-installer} \
---foreman-proxy-http true \
---foreman-proxy-httpboot true \
---foreman-proxy-tftp true
-----
-. Ensure that the {SmartProxy} has TFTP and HTTPBoot features recognized.
-In the {ProjectWebUI}, navigate to *Infrastructure* > *{SmartProxies}* and click on {SmartProxy} to see the list of recognized features.
-Click *Refresh Features* if any of the features are missing.
-. Ensure that {SmartProxy} is associated with the provisioning subnet.
-In the {ProjectWebUI}, navigate to *Infrastructure* > *Subnets* > *Edit Subnet* > *{SmartProxies}* and select the {SmartProxy} for both *TFTP* and *HTTPBoot* options.
-. Click *OK* to save.
 include::snip_steps-create-a-host-tab-host.adoc[]
 include::snip_steps-create-a-host-tab-interfaces.adoc[]
 . Click the *Operating System* tab, and verify that all fields contain values.
 Confirm each aspect of the operating system.
 . From the *PXE Loader* list, select *Grub2 UEFI HTTP*.
 . Optional: Click *Resolve* in *Provisioning template* to check the new host can identify the right provisioning templates to use.
 +
-For more information about associating provisioning templates, see xref:creating-provisioning-templates[].
+For more information about provisioning templates, see xref:provisioning-templates[].
 ifdef::katello,satellite,orcharhino[]
 include::snip_step-parameter-ak.adoc[]
 endif::[]
 . Click *Submit* to save the host details.
-+
-For more information about network interfaces, see {ManagingHostsDocURL}configuring-network-interfaces[Configuring network interfaces] in _{ManagingHostsDocTitle}_.
-. Set the host to boot in UEFI mode from network.
-. Start the host.
-. From the boot menu, select *Kickstart default PXEGrub2*.
-
-This creates the host entry and the relevant provisioning settings.
-This also includes creating the necessary directories and files for UEFI booting the bare-metal host.
-When you start the physical host and set its boot mode to UEFI HTTP, the host detects the defined DHCP service, receives HTTP endpoint of {SmartProxy} with the Kickstart tree and installs the operating system.
-
-ifdef::katello,satellite,orcharhino[]
-When the installation completes, the host also registers to {ProjectServer} using the activation key and installs the necessary configuration and management tools from the {project-client-name} repository.
-endif::[]
 
 [id="cli-creating-hosts-with-uefi-http-boot-provisioning_{context}"]
 .CLI procedure
-. Enable `foreman-proxy-http`, `foreman-proxy-httpboot`, and `foreman-proxy-tftp true` features:
-+
-[options="nowrap" subs="+quotes,attributes"]
-----
-# {foreman-installer} \
---foreman-proxy-http true \
---foreman-proxy-httpboot true \
---foreman-proxy-tftp true
-----
-. Create the host with the `hammer host create` command.
+. Create the host by using Hammer:
 +
 [options="nowrap" subs="+quotes"]
 ----
@@ -81,7 +62,7 @@ $ hammer host create \
 --organization "_My_Organization_" \
 --pxe-loader "Grub2 UEFI HTTP"
 ----
-. Ensure the network interface options are set using the `hammer host interface update` command:
+. Configure the network interface:
 +
 [options="nowrap" subs="+quotes"]
 ----
@@ -91,14 +72,3 @@ $ hammer host interface update \
 --primary true \
 --provision true
 ----
-. Set the host to boot in UEFI mode from network.
-. Start the host.
-. From the boot menu, select *Kickstart default PXEGrub2*.
-
-This creates the host entry and the relevant provisioning settings.
-This also includes creating the necessary directories and files for UEFI booting the bare-metal host.
-When you start the physical host and set its boot mode to UEFI HTTP, the host detects the defined DHCP service, receives HTTP endpoint of {SmartProxy} with the Kickstart tree and installs the operating system.
-
-ifdef::katello,satellite,orcharhino[]
-When the installation completes, the host also registers to {ProjectServer} using the activation key and installs the necessary configuration and management tools from the {project-client-name} repository.
-endif::[]
diff --git a/guides/common/modules/ref_pxe-loaders.adoc b/guides/common/modules/ref_pxe-loaders.adoc
diff --git a/guides/common/modules/ref_required-boot-order-for-network-boot.adoc b/guides/common/modules/ref_required-boot-order-for-network-boot.adoc
diff --git a/guides/common/modules/snip_steps-create-a-host-tab-interfaces.adoc b/guides/common/modules/snip_steps-create-a-host-tab-interfaces.adoc
