Bookmark this page

Guided Exercise: Configure a Satellite Server for Host Provisioning

Configure a Capsule Server with additional repository content and resources to support content host provisioning.

Outcomes

  • Enable and synchronize the required kickstart repositories for content host provisioning.

  • Configure Capsule Server to provide the configuration and resources that are used during provisioning.

  • Prepare the provisioning templates, partition tables, and operating system resources.

As the student user on the workstation machine, use the lab command to prepare your system for this exercise.

This command prepares your environment and ensures that all required resources are available.

[student@workstation ~]$ lab start network-configure

Instructions

  1. Log in to the Satellite Server web UI, https://satellite.lab.example.com, as the admin user with redhat as the password.

  2. In the upper-left corner of the web page, set the organization to Operations. Set the location to Boston.

  3. Enable and synchronize the RHEL 9 kickstart repositories that are required for network-based provisioning. The RHEL 9 RPM content repositories are already enabled and synchronized in the Operations organization.

    1. Click ContentRed Hat Repositories. In the drop-down menu under the search bar, clear the RPM checkmark and select the Kickstart type.

    2. In the Available Repositories list, click the greater-than symbol (>) to the left of the Red Hat Enterprise Linux 9 for x86_64 - BaseOS (Kickstart) repository to expand the version information. Click the plus sign (+) to the right of x86_64 9.0 to enable that repository and version. Verify that the repository is in the Enabled Repositories list and is for RHEL 9.

    3. In the Available Repositories list, click the greater-than symbol to the left of the Red Hat Enterprise Linux 9 for x86_64 - AppStream (Kickstart) repository to expand the version information. Click the plus sign to the right of x86_64 9.0 to enable that repository and version. Verify that the repository is in the Enabled Repositories list and is for RHEL 9.

    4. Click ContentProducts, and then click Red Hat Enterprise Linux for x86_64.

    5. Select the checkboxes for the Red Hat Enterprise Linux 9 for x86_64 - AppStream Kickstart 9.0 and Red Hat Enterprise Linux 9 for x86_64 - BaseOS Kickstart 9.0 repositories. Verify that you select the two RHEL 9 kickstart repositories and not the RPM repositories. Click Sync Now. Wait for the process to complete.

  4. Add the two kickstart repositories to the OperationsServerBase content view. Publish and promote the new content view version to the Development lifecycle environment.

    1. Click ContentContent Views, and then click the OperationsServerBase content view link.

    2. In the Repositories tab, select the checkboxes for the Red Hat Enterprise Linux 9 for x86_64 - AppStream Kickstart 9.0 and Red Hat Enterprise Linux 9 for x86_64 - BaseOS Kickstart 9.0 repositories, and then click Add Repositories.

    3. Click Publish New Version. Your version might have a different value from SectionFigure 8.1: Publish new content view version. Enter Add kickstart repositories in the Description field. Click to enable the Promote switch. Select the checkbox for the Development lifecycle environment. Click Next.

      Figure 8.1: Publish new content view version
    4. Review the details and click Finish. Wait for the process to complete.

  5. Verify that the Capsule Server is configured to support the Operations organization in the Boston location. Synchronize the Development lifecycle environment to prepare for provisioning a new development content host.

    1. Click InfrastructureCapsules. Verify that the list contains the capsule.lab.example.com Capsule Server, which supports the Operations organization and the Boston location.

    2. In the capsule.lab.example.com row, click Edit. Click the Lifecycle Environments tab. In the All items list, click Development to move it to the Selected items list. Click Submit.

    3. In the Overview tab for the capsule.lab.example.com Capsule page, locate the Content Sync section. Select Optimized Sync from the Synchronize list. You can continue with the exercise steps without waiting for the process to complete.

  6. Verify that the default provisioning templates are available to the Boston location and for the Red Hat 9.0 operating system.

    1. Click HostsProvisioning Templates. In the filter field, enter kind = PXELinux, and then click the Search icon. In the Name field, click the Kickstart default PXELinux link.

    2. In the Association tab, verify that the RedHat 9.0 operating system is in the Selected items list.

    3. In the Locations tab, verify that the Boston location is in the Selected items list.

    4. Click HostsProvisioning Templates. In the filter field, enter kind = provision, and then click the Search icon. In the Name field, click the Kickstart default link.

    5. In the Association tab, verify that the RedHat 9.0 operating system is in the Selected items list.

    6. In the Locations tab, verify that the Boston location is in the Selected items list.

  7. Verify that the default partition table template is available to the Boston location.

    1. Click HostsPartition Tables. In the Name field, click the Kickstart default link.

    2. In the Locations tab, verify that the Boston location is in the Selected items list.

  8. Verify that the Red Hat 9.0 operating system references the required provisioning and partition table templates.

    1. Click HostsOperating Systems. Satellite Server automatically created the Red Hat 9.0 operating system entry when you enabled the RHEL 9 kickstart repositories. Click the RedHat 9.0 link.

    2. In the Partition Table tab, verify that the Kickstart default partition table is in the Selected items list.

    3. In the Templates tab, verify that the PXELinux template is set to Kickstart default PXELinux, and that the Provisioning template field is set to Kickstart default.

      The Capsule Server is now configured with the required repository content and provisioning templates.

Finish

On the workstation machine, change to the student user home directory and use the lab command to complete this exercise. This step is important to ensure that resources from previous exercises do not impact upcoming exercises.

[student@workstation ~]$ lab finish network-configure

Revision: rh403-6.11-3ad886e