11.3. Configuring Provisioning Settings

11.3.1. Domains

Satellite has the ability to assign domain names with Red Hat Satellite Capsule Server DNS. This provides users with a means to group and name hosts within a particular domain.

11.3.1.1. Creating a Domain

This procedure shows how to add a Domain.

Procedure 11.5. Creating a Domain

  1. Click InfrastructureDomains.
  2. Click the New Domain button.
  3. Type a Name for the Domain. This is the DNS domain name.
  4. Type a Description for the Domain.
  5. Choose a DNS-enabled Red Hat Satellite Capsule Server from the DNS Capsule selection box.
  6. Click the Locations tab and click the desired locations to add them to the Selected Items list.
  7. Click the Organizations tab and click the desired organizations to add them to the Selected Items list.

    Important

    Ensure that the Locations and Organizations are configured as they will help with future debugging.
  8. Click Submit.
Satellite creates a Domain and registers it on the DNS server configured with the selected Smart Proxy.

11.3.2. Subnets

Satellite has the ability to create networks for groups of systems. Subnets use standard IP address settings to define the network and use the Red Hat Satellite Capsule Server's DHCP features to assign IP addresses to systems within the subnet.

11.3.2.1. Creating a Subnet

The following procedure shows how to create a Subnet:

Procedure 11.6. Creating a Subnet

  1. Click InfrastructureSubnets.
  2. Click the New Subnet button.
  3. Type a Name for the Subnet.
  4. Type the IP address for the Subnet into the Network box.
  5. Type the mask for the network's IP address into the Network mask box.
  6. Type the Gateway address for the Subnet.
  7. Type the Primary DNS server and Secondary DNS server for the Subnet.
  8. Define the IP assignment range with the Start of IP range and End of IP range fields.
  9. Define the VLAN ID for the subnet.
  10. Select the applicable domain for the subnet from the Domains tab.
  11. Click the Capsules tab, and select a Red Hat Satellite Capsule Server for the DHCP Proxy, TFTP Proxy, and DNS Proxy services.
  12. Click the Locations tab and click the desired locations to add them to the Selected Items list.
  13. Click the Organizations tab and click the desired organizations to add them to the Selected Items list.

    Important

    Ensure that the Locations and Organizations are configured as they will help with future debugging.
  14. Click the Submit button.

11.3.3. Architectures

An architecture in Satellite represents a logical grouping of hosts and operating systems. Architectures are created by Satellite automatically when hosts check in with Puppet. However, none exist with a default installation and require creation.

11.3.3.1. Creating an Architecture

This procedure shows how to create an architecture.

Procedure 11.7. To Create an Architecture:

  1. Click HostsArchitectures and then click New Architecture.
  2. Type a Name for the architecture.
  3. Select any Operating Systems that include this architecture. If none are available, you can create and assign them under HostsOperating Systems.
  4. Click Submit.

11.3.4. Compute Resources

Compute resources are hardware abstractions from virtualization and cloud providers. Satellite uses compute resources to provision virtual machines and containers. Supported private providers include Red Hat Enterprise Virtualization, oVirt, OpenStack, VMware, Libvirt, and Docker. Supported public cloud providers include Amazon EC2, Google Compute Engine, and Rackspace.

11.3.4.1. Creating a Compute Resource

The following procedure shows how to add a Compute Resource.

Procedure 11.8. Creating a Compute Resource

  1. Navigate to InfrastructureCompute Resources.
  2. Click New Compute Resource.
  3. Type a Name for the Compute Resource.
  4. Select a Provider type.
  5. Optionally, enter a Description.
  6. Depending on the provider type chosen, the next few fields ask for authentication and datacenter details. Refer to the following table for more information about each provider type.

    Table 11.2. Provider Settings

    Type
    Description
    RHEV
    Suits Red Hat Enterprise Virtualization environments. Requires the URL of the Manager API, a valid Username and Password, and a Datacenter on the system to abstract compute resources. Click Load Datacenters to populate the drop-down menu. Optionally, you can specify a Quota ID and provide one or more certificate authorities in the X509 Certification Authorities field.
    Libvirt
    Suits Libvirt-based environments. Requires the URL of the virtual machine. Select the Display type. Click Test Connection to test if the virtual machine is available. Select Console passwords to set a randomly generated password on the display connection.
    VMware
    Suits VMware-based environments. Requires the hostname of the VCenter/Server, a valid VMware Username and Password, and a Datacenter to abstract compute resources. Click Load Datacenters to populate the drop-down menu. You can specify a certificate Fingerprint and select Console passwords to set a randomly generated password on the display connection.
    RHEL OpenStack Platform
    Suits OpenStack-based environments. Requires the URL of the OpenStack server, a valid OpenStack Username and Password, and a Tenant to abstract compute resources. Click Load Tenants to populate the drop-down menu.
    Rackspace
    Suits Rackspace public cloud accounts. Requires the URL of the Rackspace API, a valid Rackspace Username and API Key, and a Region to abstract compute resources. Click Test Connection to make sure your connection to the chosen region is valid.
    EC2
    Suits Amazon EC2 public cloud accounts. Requires the Access Key and Secret Key available from any valid Amazon EC2 account. Requires a Region to act as a Datacenter for resource abstraction. Click Load Regions to populate the selection drop-down menu.
    Google
    Suits Google Compute Engine public cloud accounts. Requires the Google Project ID, a valid Client Email and a Certificate path to the p12 file. You can also specify a Zone to abstract compute resources. Click Load zones to populate the drop-down menu.
    Docker
    Suits container registries. Requires the URL of the internal or external compute resource. Optionally, specify a Username, Password, and a contact Email. Click Test Connection to test if the connection is available.
  7. Click the Locations tab and click the desired locations to add them to the Selected Items list.
  8. Click the Organizations tab and click the desired organizations to add them to the Selected Items list.

    Important

    Ensure that the Locations and Organizations are configured as they will help with future debugging.
  9. Click Submit.

11.3.5. Hardware Models

Hardware models help run unattended Solaris installations. For Solaris SPARC-based machines, users define the CPU and Vendor information, while other architectures do not need to do so.

11.3.5.1. Creating a Hardware Model

This procedure shows how to add a Hardware Model.

Procedure 11.9. Creating a Hardware Model

  1. Click HostsHardware Models.
  2. Click the New Model button.
  3. Type a Name for the Hardware Model.
  4. For Sparc Solaris builds, enter the CPU Hardware model and Vendor class. Other architectures do not require values in these fields.
  5. Enter a description of the Hardware Model in the Information textbox.
  6. Click Submit.

11.3.6. Installation Media

Red Hat Satellite uses installation media (ISO images) as content for kickstart trees and new host installations.

11.3.6.1. Adding Installation Media

This procedure shows how to add new Installation Media to Satellite.
  1. Click HostsInstallation Media.
  2. Click the New Installation Medium button.
  3. Type a Name for the Installation Media.
  4. Type a Path to the Installation Medium. Options include either a URL or a valid NFS server.
  5. Select an Operating System Family to define the Installation Media's type.
  6. Click the Locations tab and click the desired locations to add them to the Selected Items list.
  7. Click the Organizations tab and click the desired organizations to add them to the Selected Items list.

    Important

    Ensure that the Locations and Organizations are configured as they will help with future debugging.
  8. Click the Submit button.

11.3.7. Operating Systems

Operating Systems define combinations of installation methods and media and are grouped within families. As a default, Red Hat Satellite uses a RedHat family. Families allow Satellite to change certain behaviors when provisioning hosts.

11.3.7.1. Adding an Operating System

This procedure shows how to add a Operating System to Satellite.

Procedure 11.10. Adding an Operating System

  1. Click HostsOperating Systems.
  2. Click the New Operating system button.
  3. Type a Name for the Operating System.
  4. Define the Major Version of the Operating System.
  5. Define the Minor Version of the Operating System.
  6. Select the OS Family to define the Operating System type.
  7. Select the Architectures from the list of available Architectures. If none are available, create and assign them under HostsArchitectures.
  8. Click the Partition tables tab, then add the applicable file system layouts from the list.
  9. Click the Installation Media tab, then add the applicable file system layouts from the list.
  10. Click the Submit button.

11.3.8. Partition Tables

Partition tables define the partitions and file system layout for new installations when provisioning systems. Satellite users specify the host's disk layout as an explicit sequence of partitions or use a dynamic disk layout script.

11.3.8.1. Defining a New Partition Table

This procedure shows how to define a new Partition Table for new installations.
  1. Click HostsPartition Tables.
  2. Click the New Partition Table button.
  3. Type a Name for the partition table.
  4. Enter the Layout for the Partition Table. The Layout textbox also accepts dynamic disk partitioning scripts.
  5. Select the operating system from the OS Family tab to define the Operating System type for the partitions.
  6. Click the Submit button.

11.3.9. Provisioning Templates

Provisioning templates provide the systematic means to run unattended installations. Provisioning templates can be executed via several methods including bash scripts, kickstart scripts, and PXE-based installations.

11.3.9.1. Creating a Provisioning Template

This procedure shows how to create a Provisioning Template.

Procedure 11.11. Creating a Provisioning Template

  1. Click HostsProvisioning Templates.
  2. Click the New Template button.
  3. Type a Name for the template.
  4. Enter your template in the Template editor field. Alternatively, upload your template with the Template file browser below the Template editor textbox. This replaces the content in the Template editor field with the content of your chosen file.
  5. Enter a comment in the Audit Comment field. Satellite adds the comment to the template history to track changes. View the template history under the History tab.
  6. Click the Type tab, then select Snippet to store the template code without defining it as particular script or template type, or select the type from the Type dropdown menu.
  7. Select the Association tab to associate the template to Hostgroups, Environments and Operating Systems. Select the operating systems from the Applicable Operating Systems list. Click the Add Combination button and select a Hostgroup and Environment to limit the template's use.
  8. Click the Submit button.