Chapter 2. Configuring provisioning resources

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 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 > Provisioning Setup > Architectures.
2. Click Create Architecture.
3. In the Name field, enter a name for the architecture.
4. From the Operating Systems list, select an operating system. If none are available, you can create and assign them under Hosts > Provisioning Setup > Operating Systems.
5. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Hosts > Provisioning Setup > Hardware Models.
2. Click Create Model.
3. In the Name field, enter a name for the hardware model.
4. Optionally, in the Hardware Model and Vendor Class fields, you can enter corresponding information for your system.
5. In the Info field, enter a description of the hardware model.
6. 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 Managing content.

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 Managing content.
3. When you create a host, in the Operating System tab, for Media Selection, select the Synced Content checkbox.

Procedure

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

4. In the Path enter the URL 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/

5. 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.
6. Click the Organizations and Locations tabs, to change the provisioning context. Satellite Server adds the installation medium to the set provisioning context.
7. Click Submit to save your installation medium.

Procedure

1. In the Satellite web UI, navigate to Hosts > Templates > Partition Tables.
2. Click Create Partition Table.
3. In the Name field, enter a name for the partition table.
4. Select the Default checkbox if you want to set the template to automatically associate with new organizations or locations.
5. Select the Snippet checkbox if you want to identify the template as a reusable snippet for other partition tables.
6. 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.

7. In the Template editor field, enter the layout for the disk partition.

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

   zerombr
   clearpart --all --initlabel
   autopart

   For more information, see Section 2.10, “Dynamic partition example”.

   You can also use the file browser in the template editor to import the layout from a file.

8. In the Audit Comment field, add a summary of changes to the partition layout.
9. 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.
10. Click Submit to save your partition table.

CLI procedure

1. Create a plain text file, such as ~/My_Partition_Table, that contains the partition layout.

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

   zerombr
   clearpart --all --initlabel
   autopart

   For more information, see Section 2.10, “Dynamic partition example”.

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

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

Procedure

1. In the Satellite web UI, navigate to Hosts > Templates > 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.

CLI procedure

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 \
   --file ~/my-template \
   --locations "My_Location" \
   --name "My_Provisioning_Template" \
   --organizations "My_Organization" \
   --type provision

Procedure

1. In the Satellite web UI, navigate to Hosts > Templates > Provisioning Templates.
2. Find the template that you want to use.
3. Click Clone to duplicate the template.
4. In the Name field, enter a name for the provisioning template.
5. Select the Default checkbox to set the template to associate automatically with new organizations or locations.
6. 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.
7. In the Audit Comment field, enter a summary of changes to the provisioning template for auditing purposes.
8. Click the Type tab and if your template is a snippet, select the Snippet checkbox. A snippet is not a standalone provisioning template, but a part of a provisioning template that can be inserted into other provisioning templates.
9. From the Type list, select the type of the template. For example, Provisioning template.
10. 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.
11. 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.
12. Click the Organizations and Locations tabs to add any additional contexts to the template.
13. Click Submit to save your provisioning template.

Procedure

1. In the Satellite web UI, navigate to Hosts > Templates > Provisioning Templates and click Create Template.

2. In the Name field, enter a name for your custom provisioning snippet. The name has to start with the name of a provisioning template that supports including custom provisioning snippets:

   • Append ` custom pre` to the name of a provisioning template to run code before provisioning a host.
   • Append ` custom post` to the name of a provisioning template to run code after provisioning a host.
3. On the Type tab, select Snippet.
4. Click Submit to create your custom provisioning snippet.

CLI procedure

1. Before you create a template with the CLI, create a plain text file that contains your custom snippet.

2. Create the template using hammer:

   # hammer template create \
   --file "/path/to/My_Snippet" \
   --locations "My_Location" \
   --name "My_Template_Name_custom_pre" \ --organizations "_My_Organization" \
   --type snippet

Procedure

1. In the Satellite web UI, navigate to Hosts > Templates > Provisioning Templates.
2. Select a provisioning template.
3. On the Association tab, select all applicable operating systems.
4. Click Submit to save your changes.

CLI procedure

1. Optional: View all templates:

   # hammer template list

2. Optional: View all operating systems:

   # hammer os list

3. Associate a template with an operating system:

   # hammer template add-operatingsystem \
   --id My_Template_ID \
   --operatingsystem-id My_Operating_System_ID

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.

CLI procedure

1. Create a new compute profile:

   # hammer compute-profile create --name "My_Compute_Profile"

2. Set attributes for the compute profile:

   # hammer compute-profile values create \
   --compute-attributes "flavor=m1.small,cpus=2,memory=4GB,cpu_mode=default \
   --compute-resource "My_Compute_Resource" \
   --compute-profile "My_Compute_Profile" \
   --volume size=40GB

3. Optional: To update the attributes of a compute profile, specify the attributes you want to change. For example, to change the number of CPUs and memory size:

   # hammer compute-profile values update \
   --compute-resource "My_Compute_Resource" \
   --compute-profile "My_Compute_Profile" \
   --attributes "cpus=2,memory=4GB" \
   --interface "type=network,bridge=br1,index=1" \
   --volume "size=40GB"

4. Optional: To change the name of the compute profile, use the --new-name attribute:

   # hammer compute-profile update \
   --name "My_Compute_Profile" \
   --new-name "My_New_Compute_Profile"

Procedure

1. Generate an encrypted password:

   $ python3 -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 your Satellite Server, configure the firewall to allow VNC service on ports 5900 to 5930.

   # 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 your virtual machine. Ensure the machine is powered on and then select Console.