Skip to content

Files

Latest commit

 

History

History
120 lines (111 loc) · 5.16 KB

proc_creating-hosts-with-uefi-http-boot-provisioning.adoc

File metadata and controls

120 lines (111 loc) · 5.16 KB

Creating Hosts with UEFI HTTP Boot Provisioning

You can provision hosts from {Project} using the UEFI HTTP Boot. This is the only method with which you can provision hosts in IPv6 network.

To use the CLI instead of the {ProjectWebUI}, see the CLI procedure.

Prerequisites

  • Ensure that you meet the requirements for HTTP booting. For more information, see {PlanningDocURL}http-booting-requirements[HTTP Booting Requirements] in {PlanningDocTitle}.

Procedure

  1. On {SmartProxy} that you use for provisioning, update the grub2-efi package to the latest version:

    # {project-package-update} grub2-efi

  2. Enable foreman-proxy-http, foreman-proxy-httpboot, and foreman-proxy-tftp features.

    # {installer-scenario} \
--foreman-proxy-http true \
--foreman-proxy-httpboot true \
--foreman-proxy-tftp true

  3. 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.

  4. 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.

  5. Click OK to save. snip_steps-create-a-host-tab-host.adoc snip_steps-create-a-host-tab-interfaces.adoc

  6. Click the Operating System tab, and verify that all fields contain values. Confirm each aspect of the operating system.

  7. From the PXE Loader list, select Grub2 UEFI HTTP.

  8. 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 [creating-provisioning-templates_{context}].

  9. Click Submit to save the host details.

    For more information about network interfaces, see {ManagingHostsDocURL}Adding_Network_Interfaces_managing-hosts[Adding network interfaces] in {ManagingHostsDocTitle}.

  10. Set the host to boot in UEFI mode from network.

  11. Start the host.

  12. 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.

CLI procedure

  1. On {SmartProxy} that you use for provisioning, update the grub2-efi package to the latest version:

    # {project-package-update} grub2-efi

  2. Enable foreman-proxy-http, foreman-proxy-httpboot, and foreman-proxy-tftp true features:

    # {installer-scenario} \
--foreman-proxy-http true \
--foreman-proxy-httpboot true \
--foreman-proxy-tftp true

  3. Create the host with the hammer host create command.

    # hammer host create \
--build true \
--enabled true \
--hostgroup "My_Host_Group" \
--location "My_Location" \
--mac "My_MAC_Address" \
--managed true \
--name "My_Host_Name" \
--organization "My_Organization" \
--pxe-loader "Grub2 UEFI HTTP"

  4. Ensure the network interface options are set using the hammer host interface update command:

    # hammer host interface update \
--host "My_Host_Name" \
--managed true \
--primary true \
--provision true

  5. Set the host to boot in UEFI mode from network.

  6. Start the host.

  7. 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.