Chapter 7. Finalizing the Provisioning Configuration

Creating a Provisioning Template Using the Web UI

1. On the main menu, click Hosts Provisioning Templates.

2. In the Name column, select Kickstart Default iPXE or PXELinux in the list of provisioning templates.

   This displays the configuration tabs where you can customize the template.

3. On the Association tab, select the appropriate operating system and click Submit.

4. In the Name column, select the appropriate provisioning template.

   If you use PXE-less discovery, you should select the Discover Red Hat kexec provisioning template.

5. On the Association tab, select the appropriate operating system and click Submit.

6. On the main menu, click Hosts Operating Systems and select the appropriate operating system.

   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 Katello Kickstart Default from the provision drop-down list.
10. Select Discovery Red Hat kexec from the kexec drop-down list and click Submit.

Creating a Provisioning Template Using Hammer CLI

1. Create a provisioning template.

   $ hammer template create --name template_name --file path_to_template_file

   Copy to Clipboard Toggle word wrap

   If you use PXE-less discovery, you should use the kexec template type.

2. Add the operating system.

   $ hammer template add-operatingsystem id

   Copy to Clipboard Toggle word wrap

Creating Host Groups Using the Web UI

1. On the main menu, click Configure Host Groups, and then click New Host Group.

2. On the Host Group tab, input the following values:

   • Name: RHEL6Server-x86_64
   • Lifecycle Environment: Default_Organization/DEV
   • Content View: RHEL_6_x86_64
   • Content Source: The FQDN of your Capsule (in this case 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. If this field is not automatically populated, it means the Organization and Location associations are not correctly configured.
   • 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 the appropriate key.
9. Click Submit.

Creating Host Groups Using Hammer CLI

1. Create the host group.

   $ hammer hostgroup create --name "hostgroup_name" \
   --environment "environment_name" \
   --architecture "architecture_name" \
   --domain domain_name \
   --subnet subnet_name \
   --puppet-proxy proxy_name \
   --puppet-ca-proxy ca-proxy_name \
   --operatingsystem "os_name" \
   --partition-table "table_name" \
   --medium "medium_name" \
   --organization-ids org_ID1,org_ID2... \
   --location-ids loc_ID1,loc_ID2...

   Copy to Clipboard Toggle word wrap

2. Add an activation key.

   $ hammer hostgroup set-parameter --hostgroup "hostgroup_name" \
   --name "kt_activation_keys" \
   --value key_name

   Copy to Clipboard Toggle word wrap