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
| Parameter | Value |
|---|---|
| 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
|
Log in to the Satellite Server web UI, https://satellite.lab.example.com, as the admin user with redhat as the password.
In the upper-left corner of the web page, set the organization to Finance.
Set the location to Tokyo.
Enable and synchronize the RHEL 9 kickstart repositories.
Click → . In the drop-down menu under the search bar, clear the checkmark and select the type.
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.
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.
Click → , and then click the 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 .
Wait for the process to complete.
Add the two kickstart repositories to the FinanceServerBase content view.
Publish and promote the new content view version to the Build lifecycle environment.
Click → , and then click the FinanceServerBase content view link.
In the 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 .
Click . Your version might differ from the example output. Click to enable the switch. Select the checkbox for the lifecycle environment. Click .
Review the details and click . Wait for the process to complete.
Enable and configure the DNS, DHCP, and TFTP services on the capsule.lab.example.com host for the Finance configuration.
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 ~]#
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.logReturn to the workstation system as the student user.
[root@capsule ~]#exitlogout [student@capsule ~]$exitlogout [student@workstation ~]$
Create the tokyo.lab.example.com DNS domain for the Finance organization and the Tokyo location.
Create the Tokyo Data Center subnet, 172.25.250.0/24, and configure its DHCP address range and DNS server.
Click → .
In the capsule.lab.example.com row, select Import IPv4 subnets from the list in the column.
In the 172.25.250.0/24 page, enter the details from the table in the Instructions section. Leave the other fields unchanged. Click .
Click → , and then click the link.
Enter 172.25.250.50 in the field and enter 172.25.250.100 in the field.
Click the tab, and then click the domain to move it to the list.
Click the tab.
Select capsule.lab.example.com in each of the , , , and fields.
Click the tab, and verify that the location is in the list.
Click the tab, and verify that the organization is in the list. Click .