Provisioning Guide

Procedure 2.1. To Specify the Default Location:

1. On the main menu, click Administer → Locations and then click Default_Location in the Name column.
2. Click Organizations to display the list of organizations.
3. Click Default_Organization to add it to the Selected items list, and then click Submit.

Procedure 2.2. To Specify the Default Organization:

1. On the main menu, click Administer → Organizations and then click Default_Organization in the Name column.
2. Click Locations to display the list of available locations.
3. Click Default_Location to add it to the Selected items list, and then click Submit.

Procedure 2.3. To Associate the Domain with the Default Organization:

1. On the main menu, click Infrastructure → Domains to open the Domains screen.
2. Click example.org in the Description column. This opens the Edit Domain screen where you can update the details of the domain.
3. On the Domain tab, change the DNS domain to reflect the host name of the Satellite.
4. Set the DNS Capsule value to the Satellite server.
5. On the Locations tab, click Default_Location to add it to the Selected items list. This associates the domain with the default location.
6. On the Organizations tab, click Default_Organization to add it to the Selected items list. This associates the domain with the default organization.
7. Click Submit to apply your changes.

Procedure 2.4. To Select the Default Subnet:

1. On the main menu, click Infrastructure → Subnets.
2. Click New Subnet and then complete the following information. Remember to update the details to suit your own deployment:
   • Name: Provisioning_Net
   • Network address: 172.17.13.0
   • Network mask: 255.255.255.0
   • Gateway Address: 172.17.13.1
   • Primary DNS Server: 172.17.13.2
   • Secondary DNS Server: Leave blank
   • Start of IP Range: 172.17.13.100
   • End of IP Range: 172.17.13.150
   • VLAN ID: Leave blank
3. Click Submit.
4. Click Provisioning_Net to edit the subnet.
5. On the Domains tab, select example.org
6. On the Capsules tab, change the DNS, DHCP, and TFTP capsules to reflect the host name of the Satellite.
7. On the Locations tab, select Default_Location under All items to associate the domain with the default location.
8. On the Organizations tab, select Default_Organization under All items to associate the domain with the default organization.

Procedure 2.5. To Associate Installation Media with Organizations and Locations:

1. On the main menu, click Hosts → Installation Media
2. In the Name column, click the name of the media that you want to use.
3. On the Locations tab, add the required location to the list of selected items.
4. On the Organizations tab, add the required organization to the list of selected items, and then click Submit.

Procedure 3.1. To Create a Manifest for Satellite 6:

1. Navigate to access.redhat.com and click SUBSCRIPTIONS on the main menu.
2. In the Red Hat Subscription Management section, under Subscription Management Applications, click Satellite.
3. Locate the system for which you need to create a manifest. Ensure you select the correct version.
4. For each subscription that you want to attach, select the check box for that subscription, and specify the quantity of subscriptions to attach.
5. Click Attach Selected.

   Note

   It can take several minutes for all the subscriptions to attach. Refresh the screen every few minutes until you receive confirmation that the subscriptions are attached.
6. After the subscriptions have been attached, click Download Manifest and save the manifest file to a known location.

Procedure 3.2. To Upload a Manifest to your Satellite Server:

1. If you have not already selected the correct Organization, click Any Context → Any Organization → Default_Organization.
2. Click Content → Red Hat Subscriptions.
3. Click Manage Manifest to open the Subscriptions page.
4. Click Browse to select a suitable manifest, and then click Open.
5. Click Upload to upload the manifest to the Satellite server.

Procedure 3.3. To Enable Red Hat Repositories:

1. Select Content → Red Hat Repositories.
2. On the Kickstarts tab, navigate to Red Hat Enterprise Linux Server → Red Hat Enterprise Linux 6 Server (Kickstart) and select the Red Hat Enterprise Linux 6 Server Kickstart x86_64 6.5 (or later) repository.

   Important

   Do NOT select the 6Server Kickstart repository; future versions of Satellite hide these unnecessary Kickstart repositories.
3. On the RPMs tab, navigate to Red Hat Enterprise Linux Server → Red Hat Enterprise Linux 6 Server (RPMs) and select the Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server repository.
4. On the RPMs tab, navigate to Red Hat Enterprise Linux Server → Red Hat Enterprise Linux 6 Server - Satellite Tools (RPMs) and select the Red Hat Enterprise Linux 6 Server - Satellite Tools RPMs x86_64 repository.

Procedure 3.4. To Create a Custom Product:

1. Click Content → Products and then click New Product.
2. Enter Custom Products in the Name field. The label is automatically generated. You do not need to enter a GPG key, synchronization plan or description.
3. Click Save.
4. After the screen refreshes, click Create Repository.
5. Enter Puppet Modules for the name. The label is automatically generated.
6. In the Type field, select puppet. Leave the URL field blank.
7. Click Save.

Procedure 3.5. To Upload a Puppet Module to the Repository:

1. Download the motd puppet module from https://forge.puppetlabs.com/jeffmccune/motd. The file that you download will have a .tar.gz extension.
2. Click Content → Products and then click Custom Products in the Name field.
3. On the Repositories tab, click Puppet Modules to modify the Puppet Modules repository.
4. In the Upload Puppet Module section, click Browse, and navigate to the motd module that you downloaded.
5. Click Upload.

Procedure 3.6. To Synchronize Repositories to Your Satellite:

1. Click Content → Sync Status to display the list of available products.
2. Navigate to Red Hat Enterprise Linux Server → 6Server → x86_64.
3. Select the following products:

   • Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server.
   • Red Hat Enterprise Linux 6 Server - Satellite Tools RPMs x86_64.
4. Navigate to Red Hat Enterprise Linux Server → 6.6 → x86_64 and select Red Hat Enterprise Linux 6 Server Kickstart x86_64 6.6.
5. Click Synchronize Now.

Procedure 4.1. To Create an Application Life Cycle Environment:

1. Click Content → Life Cycle Environments to open the Life Cycle Environment Paths screen.
2. Click Add New Environment to display the New Environment page. The Library is the origin of all content that you can use in your environments.
3. Type Dev in the Name field; the label is automatically populated with the same name, but you can change it to suit your needs. You can add a description of your environment if desired.
4. Click Save to save the new environment and return to the previous page.
5. Click Add New Environment again and this time create an environment called QA.
6. Click Save.

Procedure 4.2. To Create a Content View:

1. Click Content → Content Views and then click Create New View.
2. Type RHEL6 x86_64 in the Name field; the label is automatically populated.
3. Ensure the Composite View check box is cleared, and then click Save.

Procedure 4.3. To Add the Red Hat Enterprise Linux RPM Repositories:

1. On the Content Selection screen, on the Add tab, select the check box next to each of the following repositories:
   • Red Hat Enterprise Linux 6 Server Kickstart x86_64 6Server
   • Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server
   • Red Hat Enterprise Linux 6 Server - Satellite Tools RPMs x86_64
2. Click Add Repositories. After the page has refreshed, you can see the list of repositories in your Content View on the List/Remove tab.

Procedure 4.4. To Add a Puppet Module:

1. Ensure you are still on the Content Views page; on the main menu, click Content → Content Views.
2. On the Puppet Modules tab, click Add New Module to display a list of available Puppet Modules. You can use the Filter field to help locate the required module.
3. Click Select Version to select the motd module.
4. Click Select Version next to the version of the module that you want to add.

   Note

   If you select "Use Latest" when you select which Puppet module version to use, it means that whenever a new version of the Content View is published, the latest version of that module is included in the published view.

Procedure 4.5. To Publish a Content View to the Library:

1. Click Content → Content Views to display the Content Views page.
2. Click the name of the Content View that you want to publish.
3. Click Publish New Version to display the Publish New Version page. This specifies the version and allows you to enter a comment to reflect any changes made to the content view.
4. Click Save to publish the Content View to the Library. You can monitor the publication progress on the screen that appears.
5. When the publishing process is complete, click Promote to display the list of available Promotion Paths (Library -> Dev -> QA).
6. Select the check box for the Dev environment, and then click Promote Version.

Procedure 4.6. To Create an Activation Key:

1. On the main menu, click Content → Activation Keys and then click New Activation Key.
2. In the Name field, type ak-Reg_to_Dev.
3. For the purposes of this example, clear the Content Host Limit check box.
   You can use this field to control how many times a given Activation Key is used. For example, if you associate the key with a subscription that has a limited quantity, you can set the limit on the Activation Key to eliminate exceeding that quantity.
4. Select the check box for the Dev environment.
5. In the Content View drop-down list, select the RHEL 6 x86_64 Content View, and then click Save.

Procedure 4.7. To Edit Activation Key Parameters:

1. On the Activation Keys page, click Subscriptions → Add to display the list of available subscriptions.
2. Select the check box next to each subscription that you want to attach to each host that uses this activation key.
3. Click Add Selected.

Procedure 5.1. To Create a Provisioning Template:

1. On the main menu, click Hosts → Provisioning Templates.
2. In the Name column, click Satellite Kickstart Default in the list of provisioning templates. This displays the configuration tabs where you can customize the template.
3. On the Association tab, select RHEL Server 6.5 from the list of applicable operating systems, and then click Submit.
4. In the Name column, click Kickstart default PXELinux in the list of provisioning templates.
5. On the Association tab, select RHEL Server 6.5 from the list of applicable operating systems, and then click Submit.
6. On the main menu, click Hosts → Operating Systems and then click RHEL Server 6.5. This displays the configuration tabs where you can customize the operating system.
7. On the Partition Table tab, select Kickstart Default.
8. On the Installation Media tab, ensure Default_Organization/Library/Red_Hat_6_Server_Kickstart_x86_64_6Server is visible and selected.
9. On the Templates tab, select Kickstart default PXELinux from the PXELinux drop-down list.
10. Select Satellite Kickstart Default from the Provision drop-down list, and then click Submit.

Procedure 5.2. To Create a Host Group:

1. On the main menu, click Configure → Host Groups, and then click New Host Group.
2. On the Host Group tab, complete the following values:
   • Name: RHEL6Server-x86_64
   • Lifecycle Environment: Default_Organization/DEV
   • Content View: RHEL_6_x86_64

     Note

     This field only appears after you enter a value in the Life Cycle Environment field.
   • Content Source: The FQDN of your Capsule (which may be the Satellite Server).
   • Puppet CA: The FQDN of your Satellite.
   • Puppet Master: The FQDN of your Satellite.
3. On the Puppet Classes tab, select the motd puppet module from the list of available classes.
4. On the Network tab, select the following values:

   • Domain: example.org
   • Subnet: Provisioning_Net
   • Realm: For the purposes of this example, leave this field blank. If you have configured realm management, for example IPA, select the appropriate realm here.
5. On the Operating System tab, select the following values:

   • Architecture: x86_64
   • Operating system: RHEL Server 6.5
   • Media: Default_Organization/Library Red Hat Server 6.5 x86_64. In this example, this is automatically populated.

     Note

     If this field is not automatically populated, it means the Organization and Location associations are not correctly configured. See Procedure 2.5, “To Associate Installation Media with Organizations and Locations:”.
   • Partition table: Kickstart default
   • Root password: changeme
6. On the Locations tab, select Default_location.
7. On the Organizations tab, select Default_Organization.
8. On the Activation Keys tab, select ak-Reg_To_Dev from the Activation Keys list.
9. Click Submit.

Procedure 6.1. To Provision a Host:

1. On the main menu, click Hosts → New Host to open the New Host page.
2. On the Host tab, complete the following values:

   • Name: Choose a suitable name for your host. For example, host1.example.org.
   • Host Group: Select RHEL6Server-x86_64

     Note

     New hosts inherit the default values configured for the host group. This means you can quickly build a host without reentering those values.
   • Content Source: The $FQDN of your Satellite. This is automatically selected based on the Host Group.
3. On the Network tab, complete the following values:
   • MAC Address: The MAC address of the new host. The Satellite server reserves a DHCP address using this value. Ensure you enter it correctly.
   • Subnet: Provisioning_Net This value is automatically populated.
   • IP Address: This value is automatically populated.
   Do not make any changes to the Puppet Classes, Operating System, Parameters, or Additional Information tabs.
4. Click Submit.
5. Power on your host (either physical host or virtual machine); it will PXE-boot and begin its installation process.