Provisioning Guide

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

2. Depending on the configuration specifications of the host and its domain and subnet, Satellite creates the following settings:

   • A DHCP record on the Capsule Server that is associated with the subnet.
   • A forward DNS record on the 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.
3. The new host requests a DHCP reservation from the DHCP server.
4. The DHCP server responds to the reservation request and returns TFTP next-server and filename options.
5. The host requests the boot loader and menu from the TFTP server according to the PXELoader setting.
6. A boot loader is returned over TFTP.
7. The boot loader fetches configuration for the host through its provisioning interface MAC address.
8. The boot loader fetches the operating system installer kernel, init RAM disk, and boot parameters.
9. The installer requests the provisioning template from Satellite.
10. Satellite renders the provision template and returns the result to the host.

11. The installer performs installation of the operating system.

    • The installer registers the host to Satellite using Red Hat Subscription Manager.
    • The installer installs management tools such as katello-agent and puppet.
    • The installer notifies Satellite of a successful build in the postinstall script.
12. The PXE configuration files revert to a local boot template.
13. The host reboots.
14. The new host requests a DHCP reservation from the DHCP server.
15. The DHCP server responds to the reservation request and returns TFTP next-server and filename options.
16. The host requests the bootloader and menu from the TFTP server according to the PXELoader setting.
17. A boot loader is returned over TFTP.
18. The boot loader fetches the configuration for the host through its provision interface MAC address.
19. The boot loader initiates boot from the local drive.
20. If you configured the host to use any Puppet classes, the host configures itself using the modules.

Procedure

1. Click Any Organization and select the organization.
2. Click Any Location and select the location to use.

Procedure

1. In the Satellite web UI, navigate to Hosts > Operating systems and click New Operating system.
2. In the Name field, enter a name to represent the operating system entry.
3. In the Major field, enter the number that corresponds to the major version of the operating system.
4. In the Minor field, enter the number that corresponds to the minor version of the operating system.
5. In the Description field, enter a description of the operating system.
6. From the Family list, select the operating system’s family.
7. From the Root Password Hash list, select the encoding method for the root password.
8. From the Architectures list, select the architectures that the operating system uses.
9. Click the Partition table tab and select the possible partition tables that apply to this operating system.
10. Optional: if you use non-Red Hat content, click the Installation media tab and select the installation media that apply to this operating system. For more information, see Section 2.8, “Adding Installation Media to Satellite”.
11. Click the Templates tab and select a PXELinux template, a Provisioning template, and a Finish template for your operating system to use. You can select other templates, for example an iPXE template, if you plan to use iPXE for provisioning.
12. Click Submit to save your provisioning template.

Procedure

1. On Satellite Server, run the following Bash script:

   PARTID=$(hammer --csv partition-table list | grep "Kickstart default," | cut -d, -f1)
   PXEID=$(hammer --csv template list --per-page=1000 | grep "Kickstart default PXELinux" | cut -d, -f1)
   SATID=$(hammer --csv template list --per-page=1000 | grep "provision" | grep ",Kickstart default" | cut -d, -f1)
   
   for i in $(hammer --no-headers --csv os list | awk -F, {'print $1'})
   do
      hammer partition-table add-operatingsystem --id="${PARTID}" --operatingsystem-id="${i}"
      hammer template add-operatingsystem --id="${PXEID}" --operatingsystem-id="${i}"
      hammer os set-default-template --id="${i}" --config-template-id=${PXEID}
      hammer os add-config-template --id="${i}" --config-template-id=${SATID}
      hammer os set-default-template --id="${i}" --config-template-id=${SATID}
   done

2. Display information about the updated operating system to verify that the operating system is updated correctly:

   # hammer os info --id 1

Procedure

1. In the Satellite web UI, navigate to Hosts > Architectures and click Create Architecture.
2. In the Name field, enter a name for the architecture.
3. From the Operating Systems list, select an operating system. If none are available, you can create and assign them under Hosts > Operating Systems.
4. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > Hardware Models and click Create Model.
2. In the Name field, enter a name for the hardware model.
3. Optionally, in the Hardware Model and Vendor Class fields, you can enter corresponding information for your system.
4. In the Info field, enter a description of the hardware model.
5. Click Submit to save your hardware model.

Procedure

1. Add the synchronized kickstart repository that you want to use to the existing Content View, or create a new Content View and add the kickstart repository.

   For Red Hat Enterprise Linux 8, ensure that you add both Red Hat Enterprise Linux 8 for x86_64 - AppStream Kickstart x86_64 8 and Red Hat Enterprise Linux 8 for x86_64 - BaseOS Kickstart x86_64 8 repositories.

   If you use a disconnected environment, you must import the Kickstart repositories from a Red Hat Enterprise Linux binary DVD. For more information, see Importing Kickstart Repositories in the Content Management Guide.

2. Publish a new version of the Content View where the kickstart repository is added and promote it to a required lifecycle environment. For more information, see Managing Content Views in the Content Management Guide.
3. When you create a host, in the Operating System tab, for Media Selection, select the Synced Content check box.

Procedure

1. In the Satellite web UI, navigate to Hosts > Installation Media and click Create Medium.
2. In the Name field, enter a name to represent the installation media entry.

3. In the Path enter the URL or NFS share that contains the installation tree. You can use following variables in the path to represent multiple different system architectures and versions:

   • $arch - The system architecture.
   • $version - The operating system version.
   • $major - The operating system major version.

   • $minor - The operating system minor version.

     Example HTTP path:

     http://download.example.com/centos/$version/Server/$arch/os/

     Example NFS path:

     nfs://download.example.com:/centos/$version/Server/$arch/os/

     Synchronized content on Capsule Servers always uses an HTTP path. Capsule Server managed content does not support NFS paths.

4. From the Operating system family list, select the distribution or family of the installation medium. For example, CentOS and Fedora are in the Red Hat family.
5. Click the Organizations and Locations tabs, to change the provisioning context. Satellite Server adds the installation medium to the set provisioning context.
6. Click Submit to save your installation medium.

Procedure

1. In the Satellite web UI, navigate to Hosts > Partition Tables and click Create Partition Table.
2. In the Name field, enter a name for the partition table.
3. Select the Default check box if you want to set the template to automatically associate with new organizations or locations.
4. Select the Snippet check box if you want to identify the template as a reusable snippet for other partition tables.
5. From the Operating System Family list, select the distribution or family of the partitioning layout. For example, Red Hat Enterprise Linux, CentOS, and Fedora are in the Red Hat family.

6. In the Template editor field, enter the layout for the disk partition. For example:

   zerombr
   clearpart --all --initlabel
   autopart

   You can also use the Template file browser to upload a template file.

   The format of the layout must match that for the intended operating system. For example, Red Hat Enterprise Linux 7.2 requires a layout that matches a kickstart file.

7. In the Audit Comment field, add a summary of changes to the partition layout.
8. Click the Organizations and Locations tabs to add any other provisioning contexts that you want to associate with the partition table. Satellite adds the partition table to the current provisioning context.
9. Click Submit to save your partition table.

For CLI Users

1. Before you create a partition table with the CLI, create a plain text file that contains the partition layout. This example uses the ~/my-partition file.

2. Create the installation medium using the hammer partition-table create command:

   # hammer partition-table create --name "My Partition" --snippet false \
   --os-family Redhat --file ~/my-partition --organizations "My_Organization" \
   --locations "My_Location"

Procedure

1. In the Satellite web UI, navigate to Hosts > Provisioning Templates and click Create Template.
2. In the Name field, enter a name for the provisioning template.
3. Fill in the rest of the fields as required. The Help tab provides information about the template syntax and details the available functions, variables, and methods that can be called on different types of objects within the template.

For CLI Users

1. Before you create a template with the CLI, create a plain text file that contains the template. This example uses the ~/my-template file.

2. Create the template using the hammer template create command and specify the type with the --type option:

   # hammer template create --name "My Provisioning Template" \
   --file ~/my-template --type provision --organizations "My_Organization" \
   --locations "My_Location"

Procedure

1. In the Satellite web UI, navigate to Hosts > Provisioning Templates and search for the template that you want to use.
2. Click Clone to duplicate the template.
3. In the Name field, enter a name for the provisioning template.
4. Select the Default check box to set the template to associate automatically with new organizations or locations.
5. In the Template editor field, enter the body of the provisioning template. You can also use the Template file browser to upload a template file.
6. In the Audit Comment field, enter a summary of changes to the provisioning template for auditing purposes.
7. Click the Type tab and if your template is a snippet, select the Snippet check box. A snippet is not a standalone provisioning template, but a part of a provisioning template that can be inserted into other provisioning templates.
8. From the Type list, select the type of the template. For example, Provisioning template.
9. Click the Association tab and from the Applicable Operating Systems list, select the names of the operating systems that you want to associate with the provisioning template.
10. Optionally, click Add combination and select a host group from the Host Group list or an environment from the Environment list to associate provisioning template with the host groups and environments.
11. Click the Organizations and Locations tabs to add any additional contexts to the template.
12. Click Submit to save your provisioning template.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles and click Create Compute Profile.
2. In the Name field, enter a name for the profile.
3. Click Submit. A new window opens with the name of the compute profile.
4. In the new window, click the name of each compute resource and edit the attributes you want to set for this compute profile.

Procedure

1. Generate an encrypted password:

   # python -c 'import crypt,getpass;pw=getpass.getpass(); print(crypt.crypt(pw)) if (pw==getpass.getpass("Confirm: ")) else exit()'

2. Copy the password for later use.
3. In the Satellite web UI, navigate to Administer > Settings.
4. On the Settings page, select the Provisioning tab.
5. In the Name column, navigate to Root password, and click Click to edit.
6. Paste the encrypted password, and click Save.

Procedure

1. On the VM host system, configure the firewall to allow VNC service on ports 5900 to 5930:

   • On Red Hat Enterprise Linux 6:

     # iptables -A INPUT -p tcp --dport 5900:5930 -j ACCEPT
     # service iptables save

   • On Red Hat Enterprise Linux 7:

     # firewall-cmd --add-port=5900-5930/tcp
     # firewall-cmd --add-port=5900-5930/tcp --permanent

2. In the Satellite web UI, navigate to Infrastructure > Compute Resources and select the name of a compute resource.
3. In the Virtual Machines tab, select the name of a VM host. Ensure the machine is powered on and then select Console.

1. To preview the DHCP records that are going to be added to the DHCP server, enter the following command:

   # foreman-rake orchestration:dhcp:add_missing subnet_name=NAME

2. If you are satisfied by the preview changes in the previous step, apply them by entering the above command with the perform=1 argument:

   # foreman-rake orchestration:dhcp:add_missing subnet_name=NAME perform=1

3. To keep DHCP records in Satellite and in the DHCP server synchronized, you can remove unwanted DHCP records from the DHCP server. Note that Satellite assumes that all managed DHCP servers do not contain third-party records, therefore, this step might delete those unexpected records. To preview what records are going to be removed from the DHCP server, enter the following command:

   # foreman-rake orchestration:dhcp:remove_offending subnet_name=NAME

4. If you are satisfied by the preview changes in the previous step, apply them by entering the above command with the perform=1 argument:

   # foreman-rake orchestration:dhcp:remove_offending subnet_name=NAME perform=1

1. Enter the satellite-installer command to configure the required network services:

   # satellite-installer --foreman-proxy-dhcp true \
   --foreman-proxy-dhcp-managed true \
   --foreman-proxy-dhcp-gateway "192.168.140.1" \
   --foreman-proxy-dhcp-interface "eth1" \
   --foreman-proxy-dhcp-nameservers "192.168.140.2" \
   --foreman-proxy-dhcp-range "192.168.140.10 192.168.140.110" \
   --foreman-proxy-dhcp-server "192.168.140.2" \
   --foreman-proxy-dns true \
   --foreman-proxy-dns-managed true \
   --foreman-proxy-dns-forwarders "8.8.8.8; 8.8.4.4" \
   --foreman-proxy-dns-interface "eth1" \
   --foreman-proxy-dns-reverse "140.168.192.in-addr.arpa" \
   --foreman-proxy-dns-server "127.0.0.1" \
   --foreman-proxy-dns-zone "example.com" \
   --foreman-proxy-tftp true \
   --foreman-proxy-tftp-managed true

2. Find the Capsule Server that you configure:

   # hammer proxy list

3. Refresh features of the Capsule Server to view the changes:

   # hammer proxy refresh-features --name "satellite.example.com"

4. Verify the services configured on the Capsule Server:

   # hammer proxy info --name "satellite.example.com"

1. In the Satellite web UI, navigate to Infrastructure > Domains and click Create Domain.
2. In the DNS Domain field, enter the full DNS domain name.
3. In the Fullname field, enter the plain text name of the domain.
4. Click the Parameters tab and configure any domain level parameters to apply to hosts attached to this domain. For example, user defined Boolean or string parameters to use in templates.
5. Click Add Parameter and fill in the Name and Value fields.
6. Click the Locations tab, and add the location where the domain resides.
7. Click the Organizations tab, and add the organization that the domain belongs to.
8. Click Submit to save the changes.

1. In the Satellite web UI, navigate to Infrastructure > Subnets, and in the Subnets window, click Create Subnet.
2. In the Name field, enter a name for the subnet.
3. In the Description field, enter a description for the subnet.
4. In the Network address field, enter the network address for the subnet.
5. In the Network prefix field, enter the network prefix for the subnet.
6. In the Network mask field, enter the network mask for the subnet.
7. In the Gateway address field, enter the external gateway for the subnet.
8. In the Primary DNS server field, enter a primary DNS for the subnet.
9. In the Secondary DNS server, enter a secondary DNS for the subnet.
10. From the IPAM list, select the method that you want to use for IP address management (IPAM). For more information about IPAM, see Section 3.1, “Network Resources”.
11. Enter the information for the IPAM method that you select. Click the Remote Execution tab and select the Capsule that controls the remote execution.
12. Click the Domains tab and select the domains that apply to this subnet.
13. Click the Capsules tab and select the Capsule that applies to each service in the subnet, including DHCP, TFTP, and reverse DNS services.
14. Click the Parameters tab and configure any subnet level parameters to apply to hosts attached to this subnet. For example, user defined Boolean or string parameters to use in templates.
15. Click the Locations tab and select the locations that use this Capsule.
16. Click the Organizations tab and select the organizations that use this Capsule.
17. Click Submit to save the subnet information.

1. On Capsule, enter the following command:

   # satellite-installer --enable-foreman-proxy-plugin-dhcp-infoblox \
   --foreman-proxy-dhcp true \
   --foreman-proxy-dhcp-managed false \
   --foreman-proxy-dhcp-provider infoblox \
   --foreman-proxy-plugin-dhcp-infoblox-record-type fixedaddress \
   --foreman-proxy-dhcp-server infoblox.example.com \
   --foreman-proxy-plugin-dhcp-infoblox-username admin \
   --foreman-proxy-plugin-dhcp-infoblox-password infoblox \
   --foreman-proxy-plugin-dhcp-infoblox-network-view default \
   --foreman-proxy-plugin-dhcp-infoblox-dns-view default

2. In the Satellite web UI, navigate to Infrastructure > Capsules and select the Capsule with the Infoblox DHCP module and click Refresh.
3. Ensure that the dhcp features are listed.
4. For all domains managed through Infoblox, ensure that the DNS Capsule is set for that domain. To verify, in the Satellite web UI, navigate to Infrastructure > Domains, and inspect the settings of each domain.
5. For all subnets managed through Infoblox, ensure that DHCP Capsule and Reverse DNS Capsule is set. To verify, in the Satellite web UI, navigate to Infrastructure > Subnets, and inspect the settings of each subnet.

1. On Capsule, enter the following command to configure the Infoblox module:

   # satellite-installer --enable-foreman-proxy-plugin-dns-infoblox \
   --foreman-proxy-dns true \
   --foreman-proxy-dns-managed false \
   --foreman-proxy-dns-provider infoblox \
   --foreman-proxy-plugin-dns-infoblox-dns-server infoblox.example.com \
   --foreman-proxy-plugin-dns-infoblox-username admin \
   --foreman-proxy-plugin-dns-infoblox-password infoblox \
   --foreman-proxy-plugin-dns-infoblox-dns-view default

   Optionally, you can change the value of the --foreman-proxy-plugin-dns-infoblox-dns-view option to specify a DNS Infoblox view other than the default view.

2. In the Satellite web UI, navigate to Infrastructure > Capsules and select the Capsule with the Infoblox DNS module and click Refresh.
3. Ensure that the dns features are listed.

1. On Capsule Server, install the Foreman discovery service:

   # yum install foreman-discovery-image

2. On Capsule Server, enable the httpboot service:

   # satellite-installer --foreman-proxy-httpboot true

3. In the Satellite web UI, navigate to Administer > Settings, and click the Provisioning tab.
4. Locate the Default PXE global template entry row and in the Value column, change the value to discovery.

1. Virtual machine starts
2. iPXE retrieves the network credentials using DHCP
3. iPXE retrieves the HTTP address using DHCP
4. iPXE chainloads the iPXE template from the template Capsule
5. iPXE loads the kernel and initial RAM disk of the installer

Procedure

1. Copy a boot file to the TFTP directory on your Satellite Server:

   • For EFI systems, copy the ipxe.efi file:

     # cp /usr/share/ipxe/ipxe.efi /var/lib/tftpboot/

   • For BIOS systems, copy the undionly.kpxe file:

     # cp /usr/share/ipxe/undionly.kpxe /var/lib/tftpboot/undionly.0

2. In the Satellite web UI, navigate to Hosts > Provisioning Templates, enter Kickstart default iPXE and click Search.
3. Optional: If you want to change the template, click Clone, enter a unique name, and click Submit.
4. Click the name of the template you want to use.
5. If you clone the template, you can make changes you require on the Template tab.
6. Click the Association tab, and select the operating systems that your host uses.
7. Click the Locations tab, and add the location where the host resides.
8. Click the Organizations tab, and add the organization that the host belongs to.
9. Click Submit to save the changes.
10. Navigate to Hosts > Operating systems and select the operating system of your host.
11. Click the Templates tab.
12. From the iPXE Template list, select the template you want to use.
13. Click Submit to save the changes.
14. Navigate to Hosts > All Hosts.
15. In the Hosts page, select the host that you want to use.
16. Select the Templates tab.
17. From the iPXE template list, select Review to verify that the Kickstart default iPXE template is the correct template.

18. To use the iPXE bootstrapping feature for Satellite, configure the dhcpd.conf file as follows:

    if exists user-class and option user-class = "iPXE" {
      filename "http://satellite.example.com/unattended/iPXE?bootstrap=1";
    } elsif option architecture = 00:06 {
      filename "ipxe.efi";
    } elsif option architecture = 00:07 {
      filename "ipxe.efi";
    } elsif option architecture = 00:09 {
      filename "ipxe.efi";
    } else {
      filename "undionly.0";
    }

    If you use an isolated network, use a Capsule Server URL with TCP port 8000, instead of the URL of Satellite Server.

    Note

    Use http://satellite.example.com/unattended/iPXE?bootstrap=1 when Capsule HTTP endpoint is disabled (installer option --foreman-proxy-http false). Template Capsule plug-in has the default value 8000 when enabled and can be changed with --foreman-proxy-http-port installer option. In that case, use http://capsule.example.com:8000. You must update the /etc/dhcp/dhcpd.conf file after every upgrade.

Chainbooting iPXE directly or with UNDI workflow

1. Host powers on
2. PXE driver retrieves the network credentials using DHCP
3. PXE driver retrieves the PXELinux firmware pxelinux.0 using TFTP
4. PXELinux searches for the configuration file on the TFTP server
5. PXELinux chainloads iPXE ipxe.lkrn or undionly-ipxe.0
6. iPXE retrieves the network credentials using DHCP again
7. iPXE retrieves HTTP address using DHCP
8. iPXE chainloads the iPXE template from the template Capsule
9. iPXE loads the kernel and initial RAM disk of the installer

Procedure

1. In the Satellite web UI, navigate to Hosts > Provisioning Templates, enter PXELinux chain iPXE or, for BIOS systems, enter PXELinux chain iPXE UNDI, and click Search.
2. Optional: If you want to change the template, click Clone, enter a unique name, and click Submit.
3. Click the name of the template you want to use.
4. If you clone the template, you can make changes you require on the Template tab.
5. Click the Association tab, and select the operating systems that your host uses.
6. Click the Locations tab, and add the location where the host resides.
7. Click the Organizations tab, and add the organization that the host belongs to.
8. Click Submit to save the changes.
9. In the Provisioning Templates page, enter Kickstart default iPXE into the search field and click Search.
10. Optional: If you want to change the template, click Clone, enter a unique name, and click Submit.
11. Click the name of the template you want to use.
12. If you clone the template, you can make changes you require on the Template tab.
13. Click the Association tab, and associate the template with the operating system that your host uses.
14. Click the Locations tab, and add the location where the host resides.
15. Click the Organizations tab, and add the organization that the host belongs to.
16. Click Submit to save the changes.
17. Navigate to Hosts > Operating systems and select the operating system of your host.
18. Click the Templates tab.
19. From the PXELinux template list, select the template you want to use.
20. From the iPXE template list, select the template you want to use.
21. Click Submit to save the changes.
22. Navigate to Hosts > All Hosts, and select the host you want to use.
23. Select the Templates tab, and from the PXELinux template list, select Review to verify the template is the correct template.
24. From the iPXE template list, select Review to verify the template is the correct template. If there is no PXELinux entry, or you cannot find the new template, navigate to Hosts > All Hosts, and on your host, click Edit. Click the Operating system tab and click the Provisioning Template Resolve button to refresh the list of templates.

25. To use the iPXE bootstrapping feature for Satellite, configure the dhcpd.conf file as follows:

    if exists user-class and option user-class = "iPXE" {
      filename "http://satellite.example.com/unattended/iPXE?bootstrap=1";
    } elsif option architecture = 00:06 {
      filename "ipxe.efi";
    } elsif option architecture = 00:07 {
      filename "ipxe.efi";
    } elsif option architecture = 00:09 {
      filename "ipxe.efi";
    } else {
      filename "undionly.0";
    }

    If you use an isolated network, use a Capsule Server URL with TCP port 8000, instead of the URL of Satellite Server.

    Note

    For http://satellite.example.com/unattended/iPXE, you can also use a Red Hat Satellite Capsule http://capsule.example.com:8000/unattended/iPXE. You must update the /etc/dhcp/dhcpd.conf file after every upgrade.

Procedure

1. Install the ipxe-bootimgs RPM package:

   # yum install ipxe-bootimgs

2. Copy the iPXE firmware to the TFTP server’s root directory. Do not use symbolic links because TFTP runs in the chroot environment.

   • For EFI systems, copy the ipxe.efi file:

     # cp /usr/share/ipxe/ipxe.lkrn /var/lib/tftpboot/

   • For BIOS systems, copy the undionly.kpxe file:

     # cp /usr/share/ipxe/undionly.kpxe /var/lib/tftpboot/undionly-ipxe.0

3. Correct the file contexts:

   # restorecon -RvF /var/lib/tftpboot/

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. Click the Organization and Location tabs and change the context to match your requirements.
4. From the Host Group list, select a host group that you want to use to populate the form.
5. Click the Interface tab, and on the host’s interface, click Edit.

6. Verify that the fields are populated with values. Note in particular:

   • The Name from the Host tab becomes the DNS name.
   • Satellite Server automatically assigns an IP address for the new host.
7. In the MAC address field, enter a MAC address for the host. This ensures the identification of the host during the PXE boot process.
8. Ensure that Satellite Server automatically selects the Managed, Primary, and Provision options for the first interface on the host. If not, select them.
9. In the MAC address field, enter a MAC address of the host’s provisioning interface. This ensures the identification of the host during the PXE boot process.
10. Click OK to save. To add another interface, click Add Interface. You can select only one interface for Provision and Primary.
11. Click the Operating System tab, and verify that all fields contain values. Confirm each aspect of the operating system.

12. 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 Section 2.11, “Provisioning Templates”.

13. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.

14. Click Submit to save the host details.

    For more information about network interfaces, see Adding network interfaces.

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name that you want to become the provisioned system’s host name.
3. Click the Organization and Location tabs and change the context to match your requirements.
4. From the Host Group list, select a host group that you want to use to populate the form.
5. Click the Interface tab, and on the host’s interface, click Edit.

6. Verify that the fields are populated with values. Note in particular:

   • The Name from the Host tab becomes the DNS name.
   • Satellite Server automatically assigns an IP address for the new host.
7. In the MAC address field, enter a MAC address for the host.
8. Ensure that Satellite Server automatically selects the Managed, Primary, and Provision options for the first interface on the host. If not, select them.
9. Click the Operating System tab, and verify that all fields contain values. Confirm each aspect of the operating system.

10. 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 Section 2.11, “Provisioning Templates”.

11. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
12. Click Submit to save the host details.

Procedure

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

   # satellite-maintain packages install grub2-efi

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

   # satellite-installer --scenario satellite \
   --foreman-proxy-httpboot true \
   --foreman-proxy-http true \
   --foreman-proxy-tftp true

3. In the Satellite web UI, navigate to Hosts > Create Host.
4. In the Name field, enter a name for the host.
5. Click the Organization and Location tabs and change the context to match your requirements.
6. From the Host Group list, select a host group that you want to use to populate the form.
7. Click the Interface tab, and on the host’s interface, click Edit.

8. Verify that the fields are populated with values. Note in particular:

   • The Name from the Host tab becomes the DNS name.
   • Satellite Server automatically assigns an IP address for the new host.
9. In the MAC address field, enter a MAC address of the host’s provisioning interface. This ensures the identification of the host during the PXE boot process.
10. Ensure that Satellite Server automatically selects the Managed, Primary, and Provision options for the first interface on the host. If not, select them.
11. Click OK to save. To add another interface, click Add Interface. You can select only one interface for Provision and Primary.
12. Click the Operating System tab, and verify that all fields contain values. Confirm each aspect of the operating system.
13. From the PXE Loader list, select Grub2 UEFI HTTP.

14. 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 Section 2.13, “Creating Provisioning Templates”.

15. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.

16. Click Submit to save the host details.

    For more information about network interfaces, see Adding network interfaces.

17. Set the host to boot in UEFI mode from network.
18. Start the host.
19. From the boot menu, select Kickstart default PXEGrub2.

For CLI Users

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

   # satellite-maintain packages install grub2-efi

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

   # satellite-installer --scenario satellite \
   --foreman-proxy-httpboot true \
   --foreman-proxy-http true \
   --foreman-proxy-tftp true

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

   # hammer host create --name "My_Host" \
   --organization "My_Organization" \
   --location "My_Location" \
   --hostgroup "My_Host_Group" \
   --mac "aa:aa:aa:aa:aa:aa" \
   --build true \
   --enabled true \
   --managed true \
   --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" \
   --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.

1. In the Satellite web UI, navigate to Hosts > Provisioning Templates.
2. Create a provisioning template, or clone and edit an existing template. For more information, see Section 2.13, “Creating Provisioning Templates”.
3. In the template, click the Template tab.

4. In the Template editor field, add the create_users snippet to the %post section:

   <%= snippet('create_users') %>

5. Select the Default check box.
6. Click the Association tab.
7. From the Application Operating Systems list, select an operating system.
8. Click Submit to save the provisioning template.

9. Create a host that is associated with the provisioning template or rebuild a host using the OS associated with the modified template. For more information, see Creating a Host in the Managing Hosts guide.

   The SSH keys of the Owned by user are added automatically when the create_users snippet is executed during the provisioning process. You can set Owned by to an individual user or a user group. If you set Owned by to a user group, the SSH keys of all users in the user group are added automatically.

Procedure

1. Enter the following commands on Capsule Server:

   # satellite-maintain packages install foreman-discovery-image tfm-rubygem-smart_proxy_discovery

2. Restart the satellite-maintain services:

   # satellite-maintain service restart

3. In the Satellite web UI, navigate to Infrastructure > Capsule.
4. Click the Capsule Server and select Refresh from the Actions list. Locate Discovery in the list of features to confirm the Discovery service is now running.

1. If a discovered host uses a subnet defined in Satellite, the host uses the first organization and location associated with the subnet.
2. If the discovery_organization or discovery_location fact values are set, the discovered host uses these fact values as an organization and location. To set these fact values, navigate to Administer > Settings > Discovered, and add these facts to the Default organization and Default location fields. Ensure that the discovered host’s subnet also belongs to the organization and location set by the fact, otherwise Satellite refuses to set it for security reasons.
3. If none of the previous conditions exists, Satellite assigns the first Organization and Location ordered by name.

1. In the Satellite web UI, navigate to Administer > Settings and click the Provisioning tab.
2. For the Default PXE global template entry, in the Value column, enter discovery.

1. In the Satellite web UI, navigate to Hosts > Discovered host. Select the host you want to use and click Provision to the right of the list.

2. Select from one of the two following options:

   • To provision a host from a host group, select a host group, organization, and location, and then click Create Host.
   • To provision a host with further customization, click Customize Host and enter the additional details you want to specify for the new host.

3. Verify that the fields are populated with values. Note in particular:

   • The Name from the Host tab becomes the DNS name.
   • Satellite Server automatically assigns an IP address for the new host.
   • Satellite Server automatically populates the MAC address from the Discovery results.
4. Ensure that Satellite Server automatically selects the Managed, Primary, and Provision options for the first interface on the host. If not, select them.
5. Click the Operating System tab, and verify that all fields contain values. Confirm each aspect of the operating system.

6. Click Resolve in Provisioning template to check the new host can identify the right provisioning templates to use. The host must resolve to the following provisioning templates:

   • kexec Template: Discovery Red Hat kexec

   • provision Template: Satellite Kickstart Default

     For more information about associating provisioning templates, see Section 2.11, “Provisioning Templates”.

7. Click Submit to save the host details.

For CLI Users

1. Identify the discovered host to use for provisioning:

   # hammer discovery list

2. Select a host and provision it using a host group. Set a new host name with the --new-name option:

   # hammer discovery provision --name "host_name" \
   --new-name "new_host_name" --organization "My_Organization" \
   --location "My_Location" --hostgroup "My_Host_Group" --build true \
   --enabled true --managed true

   This removes the host from the discovered host listing and creates a host entry with the provisioning settings. The Discovery image automatically resets the host so that it can boot to PXE. The host detects the DHCP service on Satellite Server’s integrated Capsule and starts installing the operating system. The rest of the process is identical to normal PXE workflow described in Section 6.3, “Creating Hosts with Unattended Provisioning”.

1. In the Satellite web UI, navigate to Configure > Discovery rules, and select Create Rule.
2. In the Name field, enter a name for the rule.
3. In the Search field, enter the rules to determine whether to provision a host. This field provides suggestions for values you enter and allows operators for multiple rules. For example: cpu_count > 8.
4. From the Host Group list, select the host group to use as a template for this host.

5. In the Hostname field, enter the pattern to determine host names for multiple hosts. This uses the same ERB syntax that provisioning templates use. The host name can use the @host attribute for host-specific values and the rand function for a random number. For more information about provisioning templates, see Section 2.11, “Provisioning Templates”.

   • myhost-<%= rand(99999) %>
   • abc-<%= @host.facts['bios_vendor'] %>-<%= rand(99999) %>
   • xyz-<%= @host.hostgroup.name %>
   • srv-<%= @host.discovery_rule.name %>

   • server-<%= @host.ip.gsub('.','-') + '-' + @host.hostgroup.subnet.name %>

     When creating host name patterns, ensure that the resulting host names are unique, do not start with numbers, and do not contain underscores or dots. A good approach is to use unique information provided by Facter, such as the MAC address, BIOS, or serial ID.

6. In the Hosts limit field, enter the maximum number of hosts that you can provision with the rule. Enter 0 for unlimited.
7. In the Priority field, enter a number to set the precedence the rule has over other rules. Rules with lower values have a higher priority.
8. From the Enabled list, select whether you want to enable the rule.
9. To set a different provisioning context for the rule, click the Organizations and Locations tabs and select the contexts you want to use.
10. Click Submit to save your rule.

11. Navigate to Hosts > Discovered Host and select one of the following two options:

    • From the Discovered hosts list on the right, select Auto-Provision to automatically provisions a single host.
    • On the upper right of the window, click Auto-Provision All to automatically provisions all hosts.

Attended Use

1. Copy this media to either a CD, DVD, or a USB stick. For example, to copy to a USB stick at /dev/sdb:

   # dd bs=4M \
   if=/usr/share/foreman-discovery-image/foreman-discovery-image-3.4.4-5.iso \
   of=/dev/sdb

2. Insert the Discovery boot media into a bare metal host, start the host, and boot from the media. The Discovery Image displays an option for either Manual network setup or Discovery with DHCP:

   If you select Manual network setup, the Discovery image requests a set of network options. This includes the primary network interface that connects to Satellite Server. This Discovery image also asks for network interface configuration options, such as an IPv4 Address, IPv4 Gateway, and an IPv4 DNS server.

3. After entering these details, select Next.
4. If you select Discovery with DHCP, the Discovery image requests only the primary network interface that connects to Satellite Server. It attempts to automatically configure the network interface using a DHCP server, such as one that a Capsule Server provides.

5. After the primary interface configuration, the Discovery image requests the Server URL, which is the URL of Satellite Server or Capsule Server offering the Discovery service. For example, to use the integrated Capsule on Satellite Server, use the following URL:

   https://satellite.example.com:9090

6. Set the Connection type to Proxy, then select Next.
7. Optional: The Discovery image also provides a set of fields to input Custom facts for the Facter tool to relay back to Satellite Server. These are entered in a name-value format. Provide any custom facts you require and select Confirm to continue.

1. Open the /usr/share/foreman-discovery-image/foreman-discovery-image.ks file for editing:

   # vim /usr/share/foreman-discovery-image/foreman-discovery-image.ks

2. Replace the repo lines in the kickstart file with the repository URLs:

   repo --name=rhel --baseurl=file:///var/lib/pulp/published/yum/https/repos/Default_Organization/Library/content/dist/rhel/server/7/7.7/x86_64
   repo --name=sat --baseurl=file:///var/lib/pulp/published/yum/https/repos/Default_Organization/Library/content/dist/rhel/server/7/7Server/x86_64/sat-capsule/6.8/os

3. Run the livecd-creator tool:

   # livecd-creator --title="Discovery-Image" \
   --compression-type=xz \
   --cache=var/cache/build-fdi \
   --config /usr/share/foreman-discovery-image/foreman-discovery-image.ks \
   --fslabel fdi \
   --tmpdir /var/tmp

   If you change fdi in the --fslabel option, you must also change the root label on the kernel command line when loading the image. fdi or the alternative name is appended to the .iso file that is created as part of this procedure. The PXE Discovery tool uses this name when converting from .iso to PXE.

   Use /var/tmp because this process requires close to 3GB of space and /tmp might have problems if the system is low on swap space.

4. Verify that your fdi.iso file is created:

   # ls *.iso -h

To boot the iso file over a network:

1. To extract the initial ramdisk and kernel files from the .iso file over a network, enter the following command:

   # discovery-iso-to-pxe fdi.iso

2. Create a directory to store your boot files:

   # mkdir /var/lib/tftpboot/boot/myimage

3. Copy the initrd0.img and vmlinuz0 files to your new directory.
4. Edit the KERNEL and APPEND entries in the /var/lib/tftpboot/pxelinux.cfg file to add the information about your own initial ramdisk and kernel files.

1. To convert the .iso file to an .iso hybrid file for PXE provisioning, enter the following command:

   # isohybrid --partok fdi.iso

   If you have grub2 packages installed, you can also use the following command to install a grub2 bootloader:

   # isohybrid --partok --uefi fdi.iso

2. To add md5 checksum to the .iso file so it can pass installation media validation tests in Satellite, enter the following command:

   # implantisomd5 fdi.iso

Procedure

1. Create the following directory structure:

   .
   ├── autostart.d
   │   └── 01_zip.sh
   ├── bin
   │   └── ntpdate
   ├── facts
   │   └── test.rb
   └── lib
       ├── libcrypto.so.1.0.0
       └── ruby
           └── test.rb

   • The autostart.d directory contains scripts that are executed in POSIX order by the image when it starts, but before the host is registered to Satellite.
   • The bin directory is added to the $PATH variable; you can place binary files in this directory and use them in the autostart scripts.
   • The facts directory is added to the FACTERLIB variable so that custom facts can be configured and sent to Satellite.
   • The lib directory is added to the LD_LIBRARY_PATH variable and lib/ruby is added to the RUBYLIB variable, so that binary files in /bin can be executed correctly.

2. After creating the directory structure, create a .zip file archive with the following command:

   zip -r my_extension.zip .

3. To inform the Discovery image of the extensions it must use, place your zip files on your TFTP server with the Discovery image, and then update the APPEND line of the PXELinux template with the fdi.zips option where the paths are relative to the TFTP root. For example, if you have two archives at $TFTP/zip1.zip and $TFTP/boot/zip2.zip, use the following syntax:

   fdi.zips=zip1.zip,boot/zip2.zip

Procedure

1. On Satellite Server, switch to the foreman user:

   # su foreman -s /bin/bash

2. Generate the key pair:

   $ ssh-keygen

3. Copy the public key to the KVM server:

   $ ssh-copy-id root@kvm.example.com

4. Exit the bash shell for the foreman user:

   $ exit

5. Install the libvirt-client package:

   # satellite-maintain packages install libvirt-client

6. Use the following command to test the connection to the KVM server:

   # su foreman -s /bin/bash -c 'virsh -c qemu+ssh://root@kvm.example.com/system list'

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click Create Compute Resource.
2. In the Name field, enter a name for the new compute resource.
3. From the Provider list, select Libvirt.
4. In the Description field, enter a description for the compute resource.

5. In the URL field, enter the connection URL to the KVM server. For example:

    qemu+ssh://root@kvm.example.com/system

6. From the Display type list, select either VNC or Spice.

7. Optional: To secure console access for new hosts with a randomly generated password, select the Set a randomly generated password on the display connection check box. You can retrieve the password for the VNC console to access the guest virtual machine console from the output of the following command executed on the KVM server:

   # virsh edit your_VM_name
   <graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' passwd='your_randomly_generated_password'>

   The password is randomly generated every time the console for the virtual machine is opened, for example, with virt-manager.

8. Click Test Connection to ensure that Satellite Server connects to the KVM server without fault.
9. Verify that the Locations and Organizations tabs are automatically set to your current context. If you want, add additional contexts to these tabs.
10. Click Submit to save the KVM connection.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click the name of the KVM connection.
2. Click Create Image.
3. In the Name field, enter a name for the image.
4. From the Operating System list, select the image’s base operating system.
5. From the Architecture list, select the operating system architecture.
6. In the Username field, enter the SSH user name for image access. This is normally the root user.
7. In the Password field, enter the SSH password for image access.

8. In the Image path field, enter the full path that points to the image on the KVM server. For example:

    /var/lib/libvirt/images/TestImage.qcow2

9. Optional: Select the User Data check box if the image supports user data input, such as cloud-init data.
10. Click Submit to save the image details.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles.
2. In the Compute Profiles window, click the name of an existing compute profile, or click Create Compute Profile, enter a Name, and click Submit.
3. Click the name of the KVM compute resource.
4. In the CPUs field, enter the number of CPUs to allocate to the new host.
5. In the Memory field, enter the amount of memory to allocate to the new host.
6. From the Image list, select the image to use if performing image-based provisioning.
7. From the Network Interfaces list, select the network parameters for the host’s network interface. You can create multiple network interfaces. However, at least one interface must point to a Capsule-managed network.
8. In the Storage area, enter the storage parameters for the host. You can create multiple volumes for the host.
9. Click Submit to save the settings to the compute profile.

For CLI Users

1. To create a compute profile, enter the following command:

   # hammer compute-profile create --name "Libvirt CP"

2. To add the values for the compute profile, enter the following command:

   # hammer compute-profile values create --compute-profile "Libvirt CP" \
   --compute-resource "My_KVM_Server" \
   --interface "compute_type=network,compute_model=virtio,compute_network=examplenetwork" \
   --volume "pool_name=default,capacity=20G,format_type=qcow2" \
   --compute-attributes "cpus=1,memory=1073741824"

Procedure

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. Click the Organization and Location tabs to ensure that the provisioning context is automatically set to the current context.
4. From the Host Group list, select the host group that you want to use to populate the form.
5. From the Deploy on list, select the KVM connection.
6. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings.
7. Click the Interface tab and click Edit on the host’s interface.

8. Verify that the fields are automatically populated, particularly the following items:

   • The Name from the Host tab becomes the DNS name.
   • Satellite Server automatically assigns an IP address for the new host.
   • The MAC address field is blank. The KVM server assigns a MAC address to the host.
   • The Managed, Primary, and Provision options are automatically selected for the first interface on the host. If not, select them.
   • The KVM-specific fields are populated with settings from your compute profile. Modify these settings if required.
9. Click the Operating System tab, and confirm that all fields automatically contain values.

10. Select the Provisioning Method that you want to use:

    • For network-based provisioning, click Network Based.
    • For image-based provisioning, click Image Based.
11. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
12. Click the Virtual Machine tab and confirm that these settings are populated with details from the host group and compute profile. Modify these settings to suit your needs.
13. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
14. Click Submit to save the host entry.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click Create Compute Resource.
2. In the Name field, enter a name for the new compute resource.
3. From the Provider list, select RHV.
4. In the Description field, enter a description for the compute resource.
5. In the URL field, enter the connection URL for the Red Hat Virtualization Manager’s API in the following form: https://rhv.example.com/ovirt-engine/api/v3.
6. Optionally, select the Use APIv4 check box to evaluate the new Red Hat Virtualization Manager API.
7. In the User field, enter the name of a user with permissions to access Red Hat Virtualization Manager’s resources.
8. In the Password field, enter the password of the user.
9. Click Load Datacenters to populate the Datacenter list with data centers from your Red Hat Virtualization environment.
10. From the Datacenter list, select a data center.
11. From the Quota ID list, select a quota to limit resources available to Satellite.
12. In the X509 Certification Authorities field, enter the certificate authority for SSL/TLS access. Alternatively, if you leave the field blank, a self-signed certificate is generated on the first API request by the server.
13. Click the Locations tab and select the location you want to use.
14. Click the Organizations tab and select the organization you want to use.
15. Click Submit to save the compute resource.

Procedure

1. In Red Hat Virtualization, create a virtual machine to use for image-based provisioning in Satellite.

2. On the virtual machine, install cloud-init:

   yum install cloud-init

3. To the /etc/cloud/cloud.cfg file, add the following information:

   datasource_list: ["NoCloud", "ConfigDrive"]

4. In Red Hat Virtualization, create an image from this virtual machine.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click the name of the Red Hat Virtualization connection.
2. Click Create Image.
3. In the Name field, enter a name for the image.
4. From the Operating System list, select the image’s base operating system.
5. From the Architecture list, select the operating system architecture.
6. In the Username field, enter the SSH user name for image access. This is normally the root user.
7. In the Password field, enter the SSH password for image access.
8. From the Image list, select an image from the Red Hat Virtualization compute resource.
9. Optional: Select the User Data check box if the image supports user data input, such as cloud-init data.
10. Click Submit to save the image details.

Procedure

1. In the Satellite web UI, navigate to Hosts > Provisioning Templates, and click Create Template.
2. In the Name field, enter a name for the template.

3. In the Editor field, enter the following template details:

   <%#
   kind: user_data
   name: Cloud-init
   -%>
   #cloud-config
   hostname: <%= @host.shortname %>
   
   <%# Allow user to specify additional SSH key as host paramter -%>
   <% if @host.params['sshkey'].present? || @host.params['remote_execution_ssh_keys'].present? -%>
   ssh_authorized_keys:
   <% if @host.params['sshkey'].present? -%>
     - <%= @host.params['sshkey'] %>
   <% end -%>
   <% if @host.params['remote_execution_ssh_keys'].present? -%>
   <% @host.params['remote_execution_ssh_keys'].each do |key| -%>
     - <%= key %>
   <% end -%>
   <% end -%>
   <% end -%>
   runcmd:
     - |
       #!/bin/bash
   <%= indent 4 do
       snippet 'subscription_manager_registration'
   end %>
   <% if @host.info['parameters']['realm'] && @host.realm && @host.realm.realm_type == 'Red Hat Identity Management' -%>
     <%= indent 4 do
       snippet 'idm_register'
     end %>
   <% end -%>
   <% unless @host.operatingsystem.atomic? -%>
       # update all the base packages from the updates repository
       yum -t -y -e 0 update
   <% end -%>
   <%
       # safemode renderer does not support unary negation
       non_atomic = @host.operatingsystem.atomic? ? false : true
       pm_set = @host.puppetmaster.empty? ? false : true
       puppet_enabled = non_atomic && (pm_set || @host.params['force-puppet'])
   %>
   <% if puppet_enabled %>
       yum install -y puppet
       cat > /etc/puppet/puppet.conf << EOF
     <%= indent 4 do
       snippet 'puppet.conf'
     end %>
       EOF
       # Setup puppet to run on system reboot
       /sbin/chkconfig --level 345 puppet on
   
       /usr/bin/puppet agent --config /etc/puppet/puppet.conf --onetime --tags no_such_tag <%= @host.puppetmaster.blank? ? '' : "--server #{@host.puppetmaster}" %> --no-daemonize
       /sbin/service puppet start
   <% end -%>
   phone_home:
    url: <%= foreman_url('built') %>
    post: []
    tries: 10pp

4. Click the Type tab and from the Type list, select User data template.
5. Click the Association tab, and from the Applicable Operating Systems list, select the operating system that you want associate with the template.
6. Click the Locations tab, and from the Locations list, select the location that you want to associate with the template.
7. Click the Organizations tab, and from the Organization list, select the organization that you want to associate with the template.
8. Click Submit.
9. Navigate to Hosts > Operating Systems, and select the operating system you want to associate with the template.
10. Click the Templates tab, and from the User data template list, select the name of the new template.
11. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles.
2. In the Compute Profiles window, click the name of an existing compute profile, or click Create Compute Profile, enter a Name, and click Submit.
3. Click the name of the Red Hat Virtualization compute resource.
4. From the Cluster list, select the target host cluster in the Red Hat Virtualization environment.
5. From the Template list, select the RHV template to use for the Cores and Memory settings.
6. In the Cores field, enter the number of CPU cores to allocate to the new host.
7. In the Memory field, enter the amount of memory to allocate to the new host.
8. From the Image list, select image to use for image-based provisioning.

9. In the Network Interfaces area, enter the network parameters for the host’s network interface. You can create multiple network interfaces. However, at least one interface must point to a Capsule-managed network. For each network interface, enter the following details:

   1. In the Name field, enter the name of the network interface.
   2. From the Network list, select The logical network that you want to use.

10. In the Storage area, enter the storage parameters for the host. You can create multiple volumes for the host. For each volume, enter the following details:

    1. In the Size (GB) enter the size, in GB, for the new volume.
    2. From the Storage domain list, select the storage domain for the volume.
    3. From the Preallocate disk, select either thin provisioning or preallocation of the full disk.
    4. From the Bootable list, select whether you want a bootable or non-bootable volume.
11. Click Submit to save the compute profile.

For CLI Users

1. To create a compute profile, enter the following command:

   # hammer compute-profile create --name "Red Hat Virtualization CP"

2. To set the values for the compute profile, enter the following command:

   # hammer compute-profile values create --compute-profile "Red Hat Virtualization CP" \
   --compute-resource "My_RHV" \
   --interface "compute_interface=Interface_Type,compute_name=eth0,compute_network=satnetwork" \
   --volume "size_gb=20G,storage_domain=Data,bootable=true" \
   --compute-attributes "cluster=Default,cores=1,memory=1073741824,start=true""

Procedure

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. Click the Organization and Location tabs to ensure that the provisioning context is automatically set to the current context.
4. From the Host Group list, select the host group that you want to use to populate the form.
5. From the Deploy on list, select the Red Hat Virtualization connection.
6. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings.
7. Click the Interface tab and click Edit on the host’s interface.

8. Verify that the fields are automatically populated, particularly the following items:

   • The Name from the Host tab becomes the DNS name.
   • Satellite Server automatically assigns an IP address for the new host.
   • The MAC address field is blank. The Red Hat Virtualization server assigns a MAC address to the host.
   • The Managed, Primary, and Provision options are automatically selected for the first interface on the host. If not, select them.
   • The Red Hat Virtualization-specific fields are populated with settings from your compute profile. Modify these settings if required.
9. Click the Operating System tab, and confirm that all fields automatically contain values.

10. Select the Provisioning Method that you want to use:

    • For network-based provisioning, click Network Based.
    • For image-based provisioning, click Image Based.
11. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
12. Click the Virtual Machine tab and confirm that these settings are populated with details from the host group and compute profile. Modify these settings to suit your needs.
13. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
14. Click Submit to save the host entry.

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources, and in the Compute Resources window, click Create Compute Resource.
2. In the Name field, enter a name for the resource.
3. From the Provider list, select VMware.
4. In the Description field, enter a description for the resource.
5. In the VCenter/Server field, enter the IP address or host name of the vCenter server.
6. In the User field, enter the user name with permission to access the vCenter’s resources.
7. In the Password field, enter the password for the user.
8. Click Load Datacenters to populate the list of data centers from your VMware vSphere environment.
9. From the Datacenter list, select a specific data center to manage from this list.
10. In the Fingerprint field, ensure that this field is populated with the fingerprint from the data center.
11. From the Display Type list, select a console type, for example, VNC or VMRC. Note that VNC consoles are unsupported on VMware ESXi 6.5 and later.

12. Optional: In the VNC Console Passwords field, select the Set a randomly generated password on the display connection check box to secure console access for new hosts with a randomly generated password. You can retrieve the password for the VNC console to access guest virtual machine console from the libvirtd host from the output of the following command:

    # virsh edit your_VM_name
    <graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0' passwd='your_randomly_generated_password'>

    The password randomly generates every time the console for the virtual machine opens, for example, with virt-manager.

13. From the Enable Caching list, you can select whether to enable caching of compute resources. For more information, see Section 11.8, “Caching of Compute Resources”.
14. Click the Locations and Organizations tabs and verify that the values are automatically set to your current context. You can also add additional contexts.
15. Click Submit to save the connection.

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and in the Compute Resources window, click the VMware vSphere connection.
2. In the Name field, enter a name for the image.
3. From the Operatingsystem list, select the image’s base operating system.
4. From the Architecture list, select the operating system architecture.
5. In the User field, enter the SSH user name for image access. This is normally the root user.
6. In the Password field, enter the SSH password for image access.
7. From the User data list, select whether you want the images to support user data input, such as cloud-init data.
8. In the Image field, enter the relative path and name of the template on the vSphere environment. Do not include the data center in the relative path.
9. Click Submit to save the image details.

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles and, in the Compute Profiles window, click the name of the compute profile, and then click the vSphere connection.
2. In the CPUs field, enter the number of CPUs to allocate to the new host.
3. In the Cores per socket field, enter the number of cores to allocate to each CPU.
4. In the Memory field, enter the amount of memory to allocate to the new host.
5. In the Cluster field, enter the name of the target host cluster on the VMware environment.
6. From the Resource pool list, select an available resource allocations for the host.
7. In the Folder field, enter the folder to organize the host.
8. From the Guest OS list, select the operating system you want to use in VMware vSphere.
9. From the SCSI controller list, select the disk access method for the host.
10. From the Virtual H/W version list, select the underlying VMware hardware abstraction to use for virtual machines.
11. You can select the Memory hot add or CPU hot add check boxes if you want to add more resources while the virtual machine is powered.
12. From the Image list, select the image to use if performing image-based provisioning.
13. From the Network Interfaces list, select the network parameters for the host’s network interface. You can create multiple network interfaces. However, at least one interface must point to a Capsule-managed network.
14. Select the Eager zero check box if you want to use eager zero thick provisioning. If unchecked, the disk uses lazy zero thick provisioning.
15. Click Submit to save the compute profile.

For CLI Users

1. To create the compute profile, enter the following command:

   # hammer compute-profile create --name "VMWare CP"

2. To add the values for the compute profile, enter the following command:

   # hammer compute-profile values create --compute-profile "VMWare CP" \
   --compute-resource "My_vSphere" \
   --interface "compute_type=VirtualE1000,compute_network=mynetwork \
   --volume "size_gb=20G,datastore=Data,name=myharddisk,thin=true" \
   --compute-attributes "cpus=1,corespersocket=2,memory_mb=1024,cluster=MyCluster,path=MyVMs,start=true"

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter the name that you want to become the provisioned system’s host name.
3. Click the Organization and Location tabs to ensure that the provisioning context is automatically set to the current context.
4. From the Host Group list, select the host group that you want to use to populate the form.
5. From the Deploy on list, select the VMware vSphere connection.
6. From the Compute Profile list, select a profile to use to automatically populate virtual machine-based settings.
7. Click the Interface tab and click Edit on the host’s interface.

8. Verify that the fields are automatically populated with values. Note in particular:

   • The Name from the Host tab becomes the DNS name.
   • The Satellite Server automatically assigns an IP address for the new host.
9. Ensure that the MAC address field is blank. The VMware vSphere server assigns one to the host.
10. Verify that the Managed, Primary, and Provision options are automatically selected for the first interface on the host. If not, select them.
11. In the interface window, review the VMware vSphere-specific fields that are populated with settings from our compute profile. Modify these settings to suit your needs.
12. Click the Operating System tab, and confirm that all fields automatically contain values.

13. Select the Provisioning Method that you want:

    • For network-based provisioning, click Network Based.
    • For image-based provisioning, click Image Based.
    • For boot-disk provisioning, click Boot disk based.
14. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
15. Click the Virtual Machine tab and confirm that these settings are populated with details from the host group and compute profile. Modify these settings to suit your requirements.
16. Click the Parameters tab and ensure that a parameter exists that provides an activation key. If not, add an activation key.
17. Click Submit to save the host entry.

Associating the userdata and Cloud-init Templates with the Operating System

1. In the Satellite web UI, navigate to Hosts > Operating Systems, and select the operating system that you want to use for provisioning.
2. Click the Template tab.
3. From the Cloud-init template list, select Cloudinit default.
4. From the User data template list, select UserData open-vm-tools.
5. Click Submit to save the changes.

1. On the virtual machine that you use to create the image, install cloud-init, open-vm-tools, and perl:

   # yum -y install cloud-init open-vm-tools perl

2. Create a configuration file for cloud-init:

   # vi /etc/cloud/cloud.cfg.d/example_cloud-init_config.cfg

3. Add the following information to the example_cloud_init_config.cfg file:

   datasource_list: [NoCloud]
   datasource:
     NoCloud:
       seedfrom: https://satellite.example.com/userdata/
   EOF

4. Enable the CA certificates for the image:

   # update-ca-trust enable

5. Download the katello-server-ca.crt file from Satellite Server:

   # wget -O /etc/pki/ca-trust/source/anchors/cloud-init-ca.crt http://satellite.example.com/pub/katello-server-ca.crt

6. To update the record of certificates, enter the following command:

   # update-ca-trust extract

7. Use the following commands to clean the image:

   # systemctl stop rsyslog
   # systemctl stop auditd
   # package-cleanup --oldkernels --count=1
   # yum clean all

8. Use the following commands to reduce logspace, remove old logs, and truncate logs:

   # logrotate -f /etc/logrotate.conf
   # rm -f /var/log/*-???????? /var/log/*.gz
   # rm -f /var/log/dmesg.old
   # rm -rf /var/log/anaconda
   # cat /dev/null > /var/log/audit/audit.log
   # cat /dev/null > /var/log/wtmp
   # cat /dev/null > /var/log/lastlog
   # cat /dev/null > /var/log/grubby

9. Remove udev hardware rules:

   # rm -f /etc/udev/rules.d/70*

10. Remove the uuid from ifcfg scripts:

    # cat > /etc/sysconfig/network-scripts/ifcfg-ens192 <<EOM
    DEVICE=ens192
    ONBOOT=yes
    EOM

11. Remove the SSH host keys:

    # rm -f /etc/ssh/SSH_keys

12. Remove root user’s shell history:

    # rm -f ~root/.bash_history
    # unset HISTFILE

13. Remove root user’s SSH history:

    # rm -rf ~root/.ssh/known_hosts

Procedure

1. Enter the following satellite-installer command to enable the Container-native Virtualization plugin for Satellite:

   # satellite-installer --enable-foreman-plugin-kubevirt

2. Generate a bearer token to use for HTTP and HTTPs authentication. On the Container-native Virtualization server, list the secrets that contain tokens:

   # kubectl get secrets

3. List the token for your secret:

   # kubectl get secrets YOUR_SECRET -o jsonpath='{.data.token}' | base64 -d | xargs

   Make a note of this token to use later in this procedure.

4. In the Satellite web UI, navigate to Infrastructure > Compute Resources, and click Create Compute Resource.
5. In the Name field, enter a name for the new compute resource.
6. From the Provider list, select Container-native Virtualization.
7. In the Description field, enter a description for the compute resource.
8. In the Hostname field, enter the address of the Container-native Virtualization server that you want to use.
9. In the API Port field, enter the port number that you want to use for provisioning requests from Satellite to Container-native Virtualization.
10. In the Namespace field, enter the user name of the Container-native Virtualization virtual cluster that you want to use.
11. In the Token field, enter the bearer token for HTTP and HTTPs authentication.
12. Optional: In the X509 Certification Authorities field, enter a certificate to enable client certificate authentication for API server calls.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click Create Compute Resource.
2. In the Name field, enter a name for the new compute resource.
3. From the Provider list, select RHEL OpenStack Platform.
4. In the Description field, enter a description for the compute resource.
5. In the URL field, enter the URL for the OpenStack Authentication keystone service’s API at the tokens resource. Use the following format: http://openstack.example.com:5000/v3.0/tokens.
6. In the User and Password fields, enter the authentication user and password for Satellite to access the environment.
7. In the Domain field, enter the domain for V3 authentication.
8. From the Tenant list, select the tenant or project for Satellite Server to manage.
9. To use external networks as primary networks for hosts, select the Allow external network as main network check box.
10. Click the Locations and Organizations tabs and verify that the location and organization that you want to use are set to your current context. Add any additional contexts that you want to these tabs.
11. Click Submit to save the Red Hat OpenStack Platform connection.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click the name of the Red Hat OpenStack Platform connection.
2. Click Create Image.
3. In the Name field, enter a name for the image.
4. From the Operating System list, select the image’s base operating system.
5. From the Architecture list, select the operating system architecture.
6. In the Username field, enter the SSH user name for image access. This is normally the root user.
7. In the Password field, enter the SSH password for image access.
8. From the Image list, select an image from the Red Hat OpenStack Platform compute resource.
9. Optional: Select the User Data check box if the image supports user data input, such as cloud-init data.
10. Click Submit to save the image details.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles.
2. In the Compute Profiles window, click the name of an existing compute profile, or click Create Compute Profile, enter a Name, and click Submit.
3. Click the name of the Red Hat OpenStack Platform compute resource.
4. From the Flavor list, select the hardware profile on Red Hat OpenStack Platform to use for the host.
5. From the Availability zone list, select the target cluster to use within the Red Hat OpenStack Platform environment.
6. From the Image list, select the image to use for image-based provisioning.
7. From the Tenant list, select the tenant or project for the Red Hat OpenStack Platform instance.
8. From the Security Group list, select the cloud-based access rules for ports and IP addresses.
9. From the Internal network, select the private networks for the host to join.
10. From the Floating IP network, select the external networks for the host to join and assign a floating IP address.
11. From the Boot from volume, select whether a volume is created from the image. If not selected, the instance boots the image directly.
12. In the New boot volume size (GB) field, enter the size, in GB, of the new boot volume.
13. Click Submit to save the compute profile.

Procedure

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. Click the Organization and Location tabs to ensure that the provisioning context is automatically set to the current context.
4. From the Host Group list, select the host group that you want to use to populate the form.
5. From the Deploy on list, select the Red Hat OpenStack Platform connection.
6. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings.
7. From the Lifecycle Environment list, select the environment.
8. Click the Interfaces tab and click Edit on the host’s interface.

9. Verify that the fields are automatically populated, particularly the following items:

   • The Name from the Host tab becomes the DNS name.
   • The MAC address field is blank. Red Hat OpenStack Platform assigns a MAC address to the host during provisioning.
   • Satellite Server automatically assigns an IP address for the new host.
   • The Managed, Primary, and Provision options are automatically selected for the first interface on the host. If not, select them.
10. Click the Operating System tab, and confirm that all fields automatically contain values.
11. If you want to change the image that populates automatically from your compute profile, from the Images list, select a different image to base the new host’s root volume on.
12. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
13. Click the Virtual Machine tab and confirm that these settings are populated with details from the host group and compute profile. Modify these settings to suit your needs.
14. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
15. Click Submit to save the host entry.

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and in the Compute Resources window, click Create Compute Resource.
2. In the Name field, enter a name to identify the Amazon EC2 compute resource.
3. From the Provider list, select EC2.
4. In the Description field, enter information that helps distinguish the resource for future use.
5. Optional: From the HTTP proxy list, select an HTTP proxy to connect to external API services. You must add HTTP proxies to Satellite before you can select a proxy from this list. For more information, see Section 14.3, “Using an HTTP Proxy with Compute Resources”.
6. In the Access Key and Secret Key fields, enter the access keys for your Amazon EC2 account. For more information, see Managing Access Keys for your AWS Account on the Amazon documentation website.
7. Optional: Click the Load Regions button to populate the Regions list.
8. From the Region list, select the Amazon EC2 region or data center to use.
9. Click the Locations tab and ensure that the location you want to use is selected, or add a different location.
10. Click the Organizations tab and ensure that the organization you want to use is selected, or add a different organization.
11. Click Submit to save the Amazon EC2 connection.
12. Select the new compute resource and then click the SSH keys tab, and click Download to save a copy of the SSH keys to use for SSH authentication. Until BZ1793138 is resolved, you can download a copy of the SSH keys only immediately after creating the Amazon EC2 compute resource. If you require SSH keys at a later stage, follow the procedure in Section 14.7, “Connecting to an Amazon EC2 instance using SSH”.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > HTTP Proxies, and select New HTTP Proxy.
2. In the Name field, enter a name for the HTTP proxy.
3. In the URL field, enter the URL for the HTTP proxy, including the port number.
4. Optional: Enter a username and password to authenticate to the HTTP proxy, if your HTTP proxy requires authentication.
5. Click Test Connection to ensure that you can connect to the HTTP proxy from Satellite.
6. Click the Locations tab and add a location.
7. Click the Organization tab and add an organization.
8. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and select an Amazon EC2 connection.
2. Click the Images tab, and then click New Image.
3. In the Name field, enter a name to identify the image for future use.
4. From the Operating System list, select the operating system that corresponds with the image you want to add.
5. From the Architecture list, select the operating system’s architecture.
6. In the Username field, enter the SSH user name for image access. This is normally the root user.
7. In the Password field, enter the SSH password for image access.
8. In the Image ID field, enter the Amazon Machine Image (AMI) ID for the image. This is usually in the following format: ami-xxxxxxxx.
9. Optional: Select the User Data check box if the images support user data input, such as cloud-init data. If you enable user data, the Finish scripts are automatically disabled. This also applies in reverse: if you enable the Finish scripts, this disables user data.
10. Optional: In the IAM role field, enter the Amazon security role used for creating the image.
11. Click Submit to save the image details.

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles and click the name of your profile, then click an EC2 connection.
2. From the Flavor list, select the hardware profile on EC2 to use for the host.
3. From the Image list, select the image to use for image-based provisioning.
4. From the Availability zone list, select the target cluster to use within the chosen EC2 region.
5. From the Subnet list, add the subnet for the EC2 instance. If you have a VPC for provisioning new hosts, use its subnet.
6. From the Security Groups list, select the cloud-based access rules for ports and IP addresses to apply to the host.
7. From the Managed IP list, select either a Public IP or a Private IP.
8. Click Submit to save the compute profile.

Procedure

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. From the Host Group list, you can select a host group to populate most of the new host’s fields.
4. From the Deploy on list, select the EC2 connection.
5. From the Compute Profile list, select a profile to use to automatically populate virtual machine-based settings.
6. Click the Interface tab, and then click Edit on the host’s interface, and verify that the fields are populated with values. Leave the Mac Address field blank. The Satellite Server automatically selects and IP address and the Managed, Primary, and Provision options for the first interface on the host.
7. Click the Operating System tab and confirm that all fields are populated with values.
8. Click the Virtual Machine tab and confirm that all fields are populated with values.
9. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
10. Click Submit to save your changes.

1. To locate the compute resource list, on your Satellite Server base system, enter the following command, and note the ID of the compute resource that you want to use:

   # hammer compute-resource list

2. Switch user to the postgres user:

   # su - postgres

3. Initiate the postgres shell:

   $ psql

4. Connect to the Foreman database as the user postgres:

   # postgres=# \c foreman

5. Select the secret from key_pairs where compute_resource_id = 3:

   # select secret from key_pairs where compute_resource_id = 3; secret

6. Copy the key from after -----BEGIN RSA PRIVATE KEY----- until -----END RSA PRIVATE KEY-----.

7. Create a .pem file and paste your key into the file:

   # vim Keyname.pem

8. Ensure that you restrict access to the .pem file:

   # chmod 600 Keyname.pem

9. To connect to the Amazon EC2 instance, enter the following command:

   ssh -i Keyname.pem   ec2-user@example.aws.com

1. In the Red Hat Satellite web UI, navigate to Hosts > Provisioning Templates.
2. In the Provisioning Templates page, enter Kickstart default finish into the search field and click Search.
3. On the Kickstart default finish template, select Clone.
4. In the Name field, enter a unique name for the template.

5. In the template, prefix each command that requires root privileges with sudo, except for subscription-manager register and yum commands, or add the following line to run the entire template as the sudo user:

   sudo -s << EOS
   _Template_ _Body_
   EOS

6. Click the Association tab, and associate the template with a Red Hat Enterprise Linux operating system that you want to use.
7. Click the Locations tab, and add the the location where the host resides.
8. Click the Organizations tab, and add the organization that the host belongs to.
9. Make any additional customizations or changes that you require, then click Submit to save your template.
10. Navigate to Hosts > Operating systems and select the operating system that you want for your host.
11. Click the Templates tab, and from the Finish Template list, select your finish template.
12. Navigate to Hosts > Create Host and enter the information about the host that you want to create.
13. Click the Parameters tab and navigate to Host parameters.

14. In Host parameters, click the Add Parameter button three times to add three new parameter fields. Add the following three parameters:

    1. In the Name field, enter remote_execution_ssh_keys. In the corresponding Value field, enter the output of cat /usr/share/foreman-proxy/.ssh/id_rsa_foreman_proxy.pub.
    2. In the Name field, enter remote_execution_ssh_user. In the corresponding Value field, enter ec2-user.
    3. In the Name field, enter activation_keys. In the corresponding Value field, enter your activation key.
15. Click Submit to save the changes.

Procedure

1. In GCE, generate a service account key in JSON format and upload this file to the /usr/share/foreman/ directory on Satellite Server.

2. On Satellite Server, change the owner for the service account key to the foreman user:

   # chown foreman /usr/share/foreman/gce_key.json

3. Configure permissions for the service account key to ensure that the file is readable:

   # chmod 0600 /usr/share/foreman/gce_key.json

4. Restore SELinux context for the service account key:

   # restorecon -vv /usr/share/foreman/gce_key.json

5. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click Create Compute Resource.
6. In the Name field, enter a name for the compute resource.
7. From the Provider list, select Google.
8. Optional: In the Description field, enter a description for the resource.
9. In the Google Project ID field, enter the project ID.
10. In the Client Email field, enter the client email.
11. In the Certificate Path field, enter the path to the service account key. For example, /usr/share/foreman/gce_key.json.
12. Click Load Zones to populate the list of zones from your GCE environment.
13. From the Zone list, select the GCE zone to use.
14. Click Submit.

For CLI Users

1. In GCE, generate a service account key in JSON format and upload this file to the /usr/share/foreman/ directory on Satellite Server.

2. On Satellite Server, change the owner for the service account key to the foreman user:

   # chown foreman /usr/share/foreman/gce_key.json

3. Configure permissions for the service account key to ensure that the file is readable:

   # chmod 0600 /usr/share/foreman/gce_key.json

4. Restore SELinux context for the service account key:

   # restorecon -vv /usr/share/foreman/gce_key.json

5. Use the hammer compute-resource create command to add a GCE compute resource to Satellite:

   # hammer compute-resource create --name 'gce_cr' \
   --provider 'gce' \
   --project 'gce_project_id' \
   --key-path 'gce_key.json' \
   --zone 'us-west1-b' \
   --email 'gce_email'

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click the name of the Google Compute Engine connection.
2. Click Create Image.
3. In the Name field, enter a name for the image.
4. From the Operating System list, select the image’s base operating system.
5. From the Architecture list, select the operating system architecture.
6. In the Username field, enter the SSH user name for image access. Specify a user other than root, because the root user cannot connect to a GCE instance using SSH keys. The username must begin with a letter and consist of lowercase letters and numbers.
7. From the Image list, select an image from the Google Compute Engine compute resource.
8. Optional: Select the User Data check box if the image supports user data input, such as cloud-init data.
9. Click Submit to save the image details.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles.
2. In the Compute Profiles window, click the name of an existing compute profile, or click Create Compute Profile, enter a Name, and click Submit.
3. Click the name of the GCE compute resource.
4. From the Machine Type list, select the machine type to use for provisioning.
5. From the Image list, select the image to use for provisioning.
6. From the Network list, select the GCE network to use for provisioning.
7. Optional: Select the Associate Ephemeral External IP check box to assign a dynamic ephemeral IP address that Satellite uses to communicate with the host. This public IP address changes when you reboot the host. If you need a permanent IP address, reserve a static public IP address on GCE and attach it to the host.
8. In the Size (GB) field, enter the size of the storage to create on the host.
9. Click Submit to save the compute profile.

For CLI Users

1. Create a compute profile to use with the GCE compute resource:

   # hammer compute-profile create --name gce_profile

2. Add GCE details to the compute profile.

   # hammer compute-profile values create --compute-profile gce_profile \
   --compute-resource 'gce_cr' \
   --volume "size_gb=20" \
   --compute-attributes "machine_type=f1-micro,associate_external_ip=true,network=default"

Procedure

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. Click the Organization and Location tabs to ensure that the provisioning context is automatically set to the current context.
4. From the Host Group list, select the host group that you want to use to populate the form.
5. From the Deploy on list, select the Google Compute Engine connection.
6. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings.
7. From the Lifecycle Environment list, select the environment.
8. Click the Interfaces tab and click Edit on the host’s interface.

9. Verify that the fields are automatically populated, particularly the following items:

   • The Name from the Host tab becomes the DNS name.
   • The MAC address field is blank. Google Compute Engine assigns a MAC address to the host during provisioning.
   • Satellite Server automatically assigns an IP address for the new host.
   • The Domain field is populated with the required domain.
   • The Managed, Primary, and Provision options are automatically selected for the first interface on the host. If not, select them.
10. Click the Operating System tab, and confirm that all fields automatically contain values.
11. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
12. Click the Virtual Machine tab and confirm that these settings are populated with details from the host group and compute profile. Modify these settings to suit your needs.
13. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
14. Click Submit to save the host entry.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click Create Compute Resource.
2. In the Name field, enter a name for the compute resource.
3. From the Provider list, select Azure Resource Manager.
4. Optional: In the Description field, enter a description for the resource.
5. In the Client ID field, enter the Application or client ID.
6. In the Client Secret field, enter the client secret.
7. In the Subscription ID field, enter the subscription ID.
8. In the Tenant ID field, enter the Directory or tenant ID.
9. Click Load Regions. This tests if your connection to Azure Resource Manager is successful and loads the regions available in your subscription.
10. From the Azure Region list, select the Azure region to use.
11. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click the name of the Microsoft Azure Resource Manager connection.
2. Click Create Image.
3. In the Name field, enter a name for the image.
4. From the Operating System list, select the image’s base operating system.
5. From the Architecture list, select the operating system architecture.
6. In the Username field, enter the SSH user name for image access. You cannot use the root user.
7. Optional: In the Password field, enter a password to authenticate with.

8. In the Azure Image Name field, enter an image name in the format prefix://UUID.

   • For a custom image, use the prefix custom. For example, custom://image-name.
   • For a shared gallery image, use the prefix gallery. For example, gallery://image-name.

   • For public and RHEL Bring Your Own Subscription (BYOS) images, use the prefix marketplace. For example, marketplace://OpenLogicCentOS:7.5:latest.

     For more information, see Find Linux VM images in the Azure Marketplace with the Azure CLI.

9. Optional: Select the User Data check box if the image supports user data input, such as cloud-init data.
10. Click Submit to save the image details.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles.
2. In the Compute Profiles window, click the name of an existing compute profile, or click Create Compute Profile, enter a Name, and click Submit.
3. Click the name of the Azure compute resource.
4. From the Resource group list, select the resource group to provision to.
5. From the VM Size list, select a size of a virtual machine to provision.
6. From the Platform list, select Linux. Satellite does not support provisioning virtual machines running Microsoft operating systems.
7. In the Username field, enter a user name to authenticate with. Note that the username that you enter for compute profile must be the same that you use when creating an image.

8. To authenticate the user, use one of the following options:

   • To authenticate using a password, enter a password in the Password field.
   • To authenticate using an SSH key, enter an SSH key in the SSH Key field.
9. Optional: If you want the virtual machine to use a premium virtual machine disk, select the Premium OS Disk check box.
10. From the OS Disk Caching list, select the disc caching setting.
11. Optional: In the Custom Script Command field, enter commands to perform on the virtual machine when the virtual machine is provisioned.
12. Optional: If you want to run custom scripts when provisioning finishes, in the Comma separated file URIs field, enter comma-separated file URIs of scripts to use. The scripts must contain sudo at the beginning because Red Hat Satellite downloads files to the /var/lib/waagent/custom-script/download/0/ directory on the host and scripts require sudo privileges to be executed.
13. Optional: If you want to create an additional volume on the VM, click the Add Volume button, enter the Size in GB and select the Data Disk Caching method.
14. Click Add Interface.
15. From the Azure Subnet list, select the Azure subnet to provision to.
16. From the Public IP list, select the public IP setting.
17. Optional: If you want the virtual machine to use a static private IP, select the Static Private IP check box.
18. Click Submit.

For CLI Users

1. Create a compute profile to use with the Azure Resource Manager compute resource:

   # hammer compute-profile create --name compute_profile_name

2. Add Azure details to the compute profile. With the username setting, enter the SSH user name for image access. Note that the username that you enter for compute profile must be the same that you use when creating an image.

   # hammer compute-profile values create \
   --compute-profile "compute_profile_name" \
   --compute-resource azure_cr_name \
   --compute-attributes="resource_group=resource_group,vm_size=Standard_B1s,username=azure_user,password=azure_password,platform=Linux,script_command=touch /var/tmp/text.txt" \
   --interface="compute_public_ip=Dynamic,compute_network=mysubnetID,compute_private_ip=false"
   --volume="disk_size_gb=5,data_disk_caching=None"

   Optional: If you want to run scripts on the virtual machine after provisioning, specify the following settings:

   • To enter the script directly, with the script_command setting, enter a command to be executed on the provisioned virtual machine.
   • To run a script from a URI, with the script_uris setting, enter comma-separated file URIs of scripts to use. The scripts must contain sudo at the beginning because Red Hat Satellite downloads files to the /var/lib/waagent/custom-script/download/0/ directory on the host and therefore scripts require sudo privileges to be executed.

Procedure

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. Click the Organization and Location tabs to ensure that the provisioning context is automatically set to the current context.
4. From the Host Group list, select the host group that you want to use to populate the form.
5. From the Deploy on list, select the Microsoft Azure Resource Manager connection.
6. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings.
7. From the Lifecycle Environment list, select the environment.
8. Click the Interfaces tab and click Edit on the host’s interface.

9. Verify that the fields are automatically populated, particularly the following items:

   • The Name from the Host tab becomes the DNS name.
   • The MAC address field is blank. Microsoft Azure Resource Manager assigns a MAC address to the host during provisioning.
   • The Azure Subnet field is populated with the required Azure subnet.
   • The Managed, Primary, and Provision options are automatically selected for the first interface on the host. If not, select them.
10. Optional: If you want to use a static private IP address, from the IPv4 Subnet list select the Satellite subnet with the Network Address field matching the Azure subnet address. In the IPv4 Address field, enter an IPv4 address within the range of your Azure subnet.
11. Click the Operating System tab, and confirm that all fields automatically contain values.
12. For Provisioning Method, ensure Image Based is selected.
13. From the Image list, select the Azure Resource Manager image that you want to use for provisioning.
14. In the Root Password field, enter the root password to authenticate with.
15. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
16. Click the Virtual Machine tab and confirm that these settings are populated with details from the host group and compute profile. Modify these settings to suit your needs.
17. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
18. Click Submit to save the host entry.