Chapter 1. Introduction to provisioning Provisioning is a process that starts with a bare physical or virtual machine and ends with a fully configured, ready-to-use operating system. Using Red Hat Satellite, you can define and automate fine-grained provisioning for a large number of hosts. 1.1. Provisioning methods in Red Hat Satellite With Red Hat Satellite, you can provision hosts by using the following methods. Bare-metal hosts Satellite provisions bare-metal hosts primarily by using PXE boot and MAC address identification. When provisioning bare-metal hosts with Satellite, you can do the following: Create host entries and specify the MAC address of the physical host to provision. Boot blank hosts to use the Satellite Discovery service, which creates a pool of hosts that are ready for provisioning. Cloud providers Satellite connects to private and public cloud providers to provision instances of hosts from images stored in the cloud environment. When provisioning from cloud with Satellite, you can do the following: Select which hardware profile to use. Provision cloud instances from specific providers by using their APIs. Virtualization infrastructure Satellite connects to virtualization infrastructure services, such as Red Hat Virtualization and VMware. When provisioning virtual machines with Satellite, you can do the following: Provision virtual machines from virtual image templates. Use the same PXE-based boot methods that you use to provision bare-metal hosts. 1.2. Supported cloud providers You can connect the following cloud providers as compute resources to Satellite: Red Hat OpenStack Platform Amazon EC2 Google Compute Engine Microsoft Azure 1.3. Supported virtualization infrastructures You can connect the following virtualization infrastructures as compute resources to Satellite: KVM (libvirt) Red Hat Virtualization (deprecated) VMware OpenShift Virtualization 1.4. Network boot provisioning workflow The provisioning process follows a basic PXE workflow: You create a host and select a domain and subnet. Satellite requests an available IP address from the DHCP Capsule Server that is associated with the subnet or from the PostgreSQL database in Satellite. Satellite loads this IP address into the IP address field in the Create Host window. When you complete all the options for the new host, submit the new host request. Depending on the configuration specifications of the host and its domain and subnet, Satellite creates the following settings: A DHCP record on Capsule Server that is associated with the subnet. A forward DNS record on Capsule Server that is associated with the domain. A reverse DNS record on the DNS Capsule Server that is associated with the subnet. PXELinux, Grub, Grub2, and iPXE configuration files for the host in the TFTP Capsule Server that is associated with the subnet. A Puppet certificate on the associated Puppet server. A realm on the associated identity server. The host is configured to boot from the network as the first device and HDD as the second device. The new host requests a DHCP reservation from the DHCP server. The DHCP server responds to the reservation request and returns TFTP -server and filename options. The host requests the boot loader and menu from the TFTP server according to the PXELoader setting. A boot loader is returned over TFTP. The boot loader fetches configuration for the host through its provisioning interface MAC address. The boot loader fetches the operating system installer kernel, init RAM disk, and boot parameters. The installer requests the provisioning template from Satellite. Satellite renders the provision template and returns the result to the host. The installer performs installation of the operating system. The installer registers the host to Satellite using Subscription Manager. The installer notifies Satellite of a successful build in the postinstall script. The PXE configuration files revert to a local boot template. The host reboots. The new host requests a DHCP reservation from the DHCP server. The DHCP server responds to the reservation request and returns TFTP -server and filename options. The host requests the bootloader and menu from the TFTP server according to the PXELoader setting. A boot loader is returned over TFTP. The boot loader fetches the configuration for the host through its provision interface MAC address. The boot loader initiates boot from the local drive. If you configured the host to use any Puppet classes, the host configures itself using the modules. The fully provisioned host performs the following workflow: The host is configured to boot from the network as the first device and HDD as the second device. The new host requests a DHCP reservation from the DHCP server. The DHCP server responds to the reservation request and returns TFTP -server and filename options. The host requests the boot loader and menu from the TFTP server according to the PXELoader setting. A boot loader is returned over TFTP. The boot loader fetches the configuration settings for the host through its provisioning interface MAC address. For BIOS hosts: The boot loader returns non-bootable device so BIOS skips to the device (boot from HDD). For EFI hosts: The boot loader finds Grub2 on a ESP partition and chainboots it. If the host is unknown to Satellite, a default bootloader configuration is provided. When Discovery service is enabled, it boots into discovery, otherwise it boots from HDD. This workflow differs depending on custom options. For example: Discovery If you use the discovery service, Satellite automatically detects the MAC address of the new host and restarts the host after you submit a request. Note that TCP port 8443 must be reachable by the Capsule to which the host is attached for Satellite to restart the host. PXE-less Provisioning After you submit a new host request, you must boot the specific host with the boot disk that you download from Satellite and transfer using a USB port of the host. Compute Resources Satellite creates the virtual machine and retrieves the MAC address and stores the MAC address in Satellite. If you use image-based provisioning, the host does not follow the standard PXE boot and operating system installation. The compute resource creates a copy of the image for the host to use. Depending on image settings in Satellite, seed data can be passed in for initial configuration, for example using cloud-init . Satellite can connect using SSH to the host and execute a template to finish the customization. Note By default, deleting the provisioned profile host from Satellite does not destroy the actual VM on the external compute resource. To destroy the VM when deleting the host entry on Satellite, navigate to Administer > Settings > Provisioning and configure this behavior using the destroy_vm_on_host_delete setting. If you do not destroy the associated VM and attempt to create a new VM with the same resource name later, it will fail because that VM name already exists in the external compute resource. You can still register the existing VM to Satellite using the standard host registration workflow you would use for any already provisioned host. 1.5. Required boot order for network boot For physical or virtual BIOS hosts Set the first booting device as boot configuration with network. Set the second booting device as boot from hard drive. Satellite manages TFTP boot configuration files, so hosts can be easily provisioned just by rebooting. For physical or virtual EFI hosts Set the first booting device as boot configuration with network. Depending on the EFI firmware type and configuration, the OS installer typically configures the OS boot loader as the first entry. To reboot into installer again, use the efibootmgr utility to switch back to boot from network.

Commands: