Chapter 3. Configuring Provisioning Resources

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 3.10, “Using Third Party Installation Media”.
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.

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

1. In the Satellite web UI, navigate to Hosts > Architectures, and in the Architectures window, 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.

1. In the Satellite web UI, navigate to Hosts > Hardware Models, and in the Hardware Models window, 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.

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.

1. In the Satellite web UI, navigate to Hosts > Partition Tables and, in the Partition Tables window, click Create Partition Table.
2. In the Name field, enter a name to represent 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.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles, and in the Compute Profiles window, click Create Compute Profile.
2. In the Name field, enter a name for the profile and click Submit.

1. Generate an encrypted password. You can use the following command to generate a 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 that you generate, and click Save.

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