Red Hat Satellite 6 Administration

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

Verify that the following repositories are synchronized and are promoted in the FinanceServerBase content view.

1. Click Content → Products, and then click the Red Hat Enterprise Linux for x86_64 link. Verify that the two repositories display a Success status in the Sync Status column.

2. Click Content → Content Views, and then click the FinanceServerBase link.

3. Click Version 1.0. Verify that the content view version contains the Red Hat Enterprise Linux 9 for x86_64 - BaseOS Kickstart 9.0 and Red Hat Enterprise Linux 9 for x86_64 - AppStream Kickstart 9.0 repositories. Verify that the content view version is in the Build lifecycle environment.

Verify that the FinanceServers activation key is configured to assign content hosts to the Build lifecycle environment with the FinanceServerBase content view.

1. Click Content → Activation Keys, and then click the FinanceServers link. In the Activation Key Content section, verify that the Build lifecycle environment and the FinanceServerBase content view are selected.

Synchronize the Build lifecycle environment from the Satellite Server to the Capsule Server.

1. Click Infrastructure → Capsules. On the capsule.lab.example.com row, click Edit.

2. Click the Lifecycle Environments tab. In the Available items list, click the Build environment to move it to the Selected items list. Click Submit.

3. On the Capsules page, click the capsule.lab.example.com link. Click Synchronize → Optimized Sync. Wait for the process to complete.

Enable and configure the DNS, DHCP, and TFTP services on the capsule system.

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
   [sudo] password for student: student
   [root@capsule ~]#

2. Enable the DNS, DHCP, and TFTP services.

   [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 sf.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.70 172.25.250.90' \
   --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 ~]$

Create and configure the San Francisco location's DNS domain and subnet in the Finance organization.

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

   [student@workstation ~]$ ssh student@satellite
   [student@satellite ~]$ sudo -i
   [sudo] password for student: student
   [root@satellite ~]#

2. Create the sf.lab.example.com DNS domain.

   [root@satellite ~]# hammer domain create \
   --organization Finance \
   --name sf.lab.example.com
   Domain [sf.lab.example.com] created.

3. Assign the domain parameters to the sf.lab.example.com domain.

   [root@satellite ~]# hammer domain update \
   --organizations Finance \
   --locations "San Francisco" \
   --name sf.lab.example.com \
   --dns capsule.lab.example.com
   Domain [sf.lab.example.com] updated.

4. Note the Capsule Server ID.

   [root@satellite ~]# hammer capsule list \
   --search capsule.lab.example.com \
   --fields Id,Name
   ---|------------------------
   ID | NAME
   ---|------------------------
   2  | capsule.lab.example.com
   ---|------------------------

5. Create the San Francisco Data Center subnet by using the Capsule Server ID from the previous command output.

   [root@satellite ~]# hammer subnet create \
   --name "San Francisco Data Center" \
   --organizations Finance \
   --locations "San Francisco" \
   --network 172.25.250.0 \
   --mask 255.255.255.0 \
   --dns-primary 172.25.250.220 \
   --ipam DHCP \
   --from 172.25.250.70 \
   --to 172.25.250.90 \
   --boot-mode DHCP \
   --dns capsule.lab.example.com \
   --dhcp capsule.lab.example.com \
   --tftp capsule.lab.example.com \
   --template-id 2 \
   --domains sf.lab.example.com
   Subnet created.

Create the Finance host group.

1. Click Configure → Host Groups, and then click Create Host Group.

2. Enter the following details. Leave the other fields unmodified. Submit the form only after the other tabs are completed.

   Table 13.5. Host Group Details

   Field	Value
   Name	Finance Host Group
   Lifecycle Environment	Build
   Content View	FinanceServerBase
   Content Source	capsule.lab.example.com

   
   

3. Click the Network tab. Select sf.lab.example.com in the Domain field. Select San Francisco Data Center (172.25.250.0/24) in the IPv4 Subnet field.

4. Click the Operating System tab, and then complete the page with the following details. Leave the other fields unmodified. Submit the form only after the other tabs are completed.

   Table 13.6. Host Group Operating System Details

   Field	Value
   Architecture	x86_64
   Operating system	RedHat 9.0
   Media Selection	Synced Content
   Partition Table	Kickstart default
   PXE loader	PXELinux BIOS

   
   

5. Click the Locations tab to verify that the San Francisco location is in the Selected items list.

6. Click the Organizations tab to verify that the Finance organization is in the Selected items list.

7. Click the Activation Keys tab, and then select FinanceServers in the Activation Keys field.

8. Click Submit.

Create a servere host resource.

1. Click Hosts → Create Host. Enter the following details. Leave the other fields unmodified. Submit the form only after the other tabs are completed.

   Table 13.7. New Host Details

   Field	Value
   Name	servere
   Organization	Finance
   Location	San Francisco
   Host Group	Finance Host Group

   
   

2. Click the Operating System tab. Enter redhat123 in the Root Password field. Click Resolve to confirm that the system can retrieve the provisioning templates.

3. Click the Interfaces tab, and then click Edit at the end of the interface row. Enter 52:54:00:00:fa:0e in the MAC Address field. Click Ok. Click Submit.

Access the servere console and initiate a PXE boot.

1. Locate your servere system console, as appropriate for your classroom environment. Open the console.

2. Reboot the server system by using the relevant technique for your classroom environment. The provisioning process starts automatically. If the provision process does not start, then select Kickstart default PXELinux in the Booting into OS installer menu. Wait for the provisioning to complete.

3. Wait for the installation to complete and for the system to reboot. From the console, log in as root with redhat123 as a password.

   Verify the system name.

   [root@servere ~]# hostname
   servere.sf.lab.example.com

4. When done, log out from servere and close the console.

   [root@servere ~]# exit
   logout