Bookmark this page

Lab: Prepare Network Resources for Host Provisioning

Configure a Capsule Server with the required resources for 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.

  • Configure Capsule Server to provide the DNS, DHCP, and TFTP services.

  • Create domain and subnet resources for an organization and a location.

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

Instructions

The Finance team wants to provision systems on the 172.25.250.0/24 subnet in the Tokyo location. The content hosts in Tokyo are members of the tokyo.lab.example.com DNS domain and are supported by the external Capsule Server.

You are requested to configure the Capsule Server to provide the DNS, DHCP, and TFTP services. You must configure the tokyo.lab.example.com DNS zone as authoritative. The DHCP service must provide the 172.25.250.50 - 172.25.250.100 IP address range for provisioning.

Add the enabled and synchronized RHEL 9 kickstart repositories to the FinanceServerBase content view for availability from the Build lifecycle environment.

Use the parameters in the following tables for the Finance team's provisioning configuration:

Table 8.4. Service Parameters

ParameterValue
DNS interface eth0
DNS forwarders 172.25.250.254
DNS zone tokyo.lab.example.com
DNS reverse 250.25.172.in-addr.arpa
DHCP interface eth0
DHCP range 172.25.250.50 to 172.25.250.100
DHCP name servers 172.25.250.220
DHCP gateway 172.25.250.254

Table 8.5. Tokyo Subnet Details

FieldValue
Name Tokyo Data Center
Primary DNS Server 172.25.250.220
IPAM DHCP

  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 Finance. Set the location to Tokyo.

  3. Enable and synchronize the RHEL 9 kickstart repositories.

    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 9.0 repository to expand the version information. Click the plus sign (+) to the right of x86_64 to enable that repository and version.

    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 9.0 repository to expand the version information. Click the plus sign (+) to the right of x86_64 to enable that repository and version.

    4. Click ContentProducts, and then click the Red Hat Enterprise Linux for x86_64 link. 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. Click Sync Now. Wait for the process to complete.

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

    1. Click ContentContent Views, and then click the FinanceServerBase 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 differ from the example output. Click to enable the Promote switch. Select the checkbox for the Build lifecycle environment. Click Next.

    4. Review the details and click Finish. Wait for the process to complete.

  5. Enable and configure the DNS, DHCP, and TFTP services on the capsule.lab.example.com host for the Finance configuration.

    1. Log in to the capsule system as the student user and switch to the root user.

      [student@workstation ~]$ ssh student@capsule
      [student@capsule ~]$ sudo -i
      [root@capsule ~]#
    2. Enable the DNS, DHCP, and TFTP services by using the parameters from the table in the Instructions section.

      [root@capsule ~]# satellite-installer --scenario capsule \
      --foreman-proxy-dns true \
      --foreman-proxy-dns-interface eth0 \
      --foreman-proxy-dns-forwarders 172.25.250.254 \
      --foreman-proxy-dns-zone tokyo.lab.example.com \
      --foreman-proxy-dns-reverse 250.25.172.in-addr.arpa \
      --foreman-proxy-dhcp true \
      --foreman-proxy-dhcp-interface eth0 \
      --foreman-proxy-dhcp-range "172.25.250.50 172.25.250.100" \
      --foreman-proxy-dhcp-nameservers 172.25.250.220 \
      --foreman-proxy-dhcp-gateway 172.25.250.254 \
      --foreman-proxy-tftp true
      ...output omitted...
        Success!
        * Capsule is running at https://capsule.lab.example.com:9090
      
        The full log is at /var/log/foreman-installer/capsule.log
    3. Return to the workstation system as the student user.

      [root@capsule ~]# exit
      logout
      [student@capsule ~]$ exit
      logout
      [student@workstation ~]$
  6. Create the tokyo.lab.example.com DNS domain for the Finance organization and the Tokyo location.

    1. In the Satellite web UI, click InfrastructureDomains, and then click Create Domain. Enter tokyo.lab.example.com in the DNS Domain field. Select capsule.lab.example.com in the DNS Capsule field.

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

    3. In the Organizations tab, verify that the Finance organization is in the Selected items list. Click Submit.

  7. Create the Tokyo Data Center subnet, 172.25.250.0/24, and configure its DHCP address range and DNS server.

    1. Click InfrastructureCapsules.

    2. In the capsule.lab.example.com row, select Import IPv4 subnets from the Edit list in the Actions column.

    3. In the 172.25.250.0/24 page, enter the details from the table in the Instructions section. Leave the other fields unchanged. Click Submit.

    4. Click InfrastructureSubnets, and then click the Tokyo Data Center link.

    5. Enter 172.25.250.50 in the Start Of Ip Range field and enter 172.25.250.100 in the End Of Ip Range field.

    6. Click the Domains tab, and then click the tokyo.lab.example.com domain to move it to the Selected items list.

    7. Click the Capsules tab. Select capsule.lab.example.com in each of the DHCP Capsule, TFTP Capsule, Reverse DNS Capsule, and Template Capsule fields.

    8. Click the Locations tab, and verify that the Tokyo location is in the Selected items list.

    9. Click the Organizations tab, and verify that the Finance organization is in the Selected items list. Click Submit.

Evaluation

As the student user on the workstation machine, use the lab command to grade your work. Correct any reported failures and rerun the command until successful.

[student@workstation ~]$ lab grade network-review

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

Revision: rh403-6.11-3ad886e