Red Hat Training

A Red Hat training course is available for Red Hat Satellite

Integration with Red Hat Satellite 6

Red Hat CloudForms 4.0

A short guide to integrating Red Hat Satellite 6 features into Red Hat CloudForms

Red Hat CloudForms Documentation Team

Abstract

Red Hat CloudForms provides integration with Red Hat Satellite 6 servers. This allows Red Hat CloudForms users to leverage features from Red Hat Satellite 6, such as bare metal provisioning and configuration management. This guide includes instructions for adding Red Hat Satellite 6 as a provider in Red Hat CloudForms Management Engine, and information about the features provided by Red Hat Satellite 6 within Red Hat CloudForms.
If you have a suggestion for improving this guide or have found an error, please submit a Bugzilla report at http://bugzilla.redhat.com against Red Hat CloudForms Management Engine for the Documentation component. Please provide specific details, such as the section number, guide name, and CloudForms version so we can easily locate the content.

Chapter 1. Introduction

Satellite 6 is a subscription and system management tool that provides a way to provision hosts (both virtual and bare metal) and configure them using a set of Puppet modules. Red Hat CloudForms provides functionality to integrate with a Red Hat Satellite 6 server and take advantage of its features. This includes:

  • Monitoring the inventory of your Red Hat Satellite 6 server, including independent hosts and hosts provisioned using hostgroups.
  • Reprovisioning existing bare metal system hosts to new host groups.
  • Applying Red Hat CloudForms Management Engine policy tags to hosts.

This guide provides a step-by-step workflow on how to integrate Red Hat CloudForms 4.0 and Red Hat Satellite 6 together.

Important

Red Hat CloudForms only reprovisions existing systems in a Red Hat Satellite 6 environment. Provisioning systems from Red Hat Satellite 6’s bare metal discovery service is planned for a future release.

1.1. Defining the Workflow

This guide uses the following workflow:

  1. Add a Red Hat Satellite 6 server details to Red Hat CloudForms Management Engine.
  2. Refresh the state of your Red Hat Satellite 6 provider in Red Hat CloudForms Management Engine.
  3. Select an existing bare metal host from Red Hat Satellite 6 for reprovisioning.
  4. Apply policy tags to Red Hat Satellite 6 hosts.

Chapter 2. Defining the Hostgroup Hierarchy

Red Hat CloudForms Management Engine displays the Red Hat Satellite 6 infrastructure in a host group and host relationship. A host group defines a set of default values that hosts inherit when placed in that group. Hosts can belong to only one host group, but host groups can be nested in hierarchies. You can create a "base" or "parent" host group that represents all hosts in your organization, and then create nested or "child" host groups under that parent to provide specific settings.

Chapter 3. Adding a Satellite 6 Provider to CloudForms

To start provisioning bare metal machines, you need at least one Red Hat Satelllite 6 provider added to Red Hat CloudForms Management Engine. The following procedure show how to do this.

  1. Log in to your Red Hat CloudForms Management Engine UI as the administration user.
  2. Navigate to InfrastructureConfiguration Management. The providers list appears and should be empty.
  3. Select ConfigurationAdd a new Provider. An empty form for your new Satellite 6 provider appears.
  4. Enter a Name for the provider. This is just a plain text name to help identify your provider in the Red Hat CloudForms Management Engine UI. For example, Satellite 6.
  5. Enter a URL for the provider. This is the root URL for the Satellite 6 server and can be either an IP address or a hostname. For example, http://satellite6.example.com.
  6. Select Verify Peer Certificate to use encrypted communication with the provider. This requires the SSL certificates from your Red Hat Satellite 6 provider.
  7. Enter a Username for a user on the provider. Ideally, this would be a user in Satellite 6 with administrative access.
  8. Enter a Password and enter it again to Verify Password.
  9. Click Validate to test your connection with the Red Hat Satellite 6 server.
  10. Click Add to confirm your settings and save the provider.

Red Hat CloudForms Management Engine saves the Satellite 6 provider in its database and triggers a refresh of resources detected in the provider.

Chapter 4. Triggering a Refresh of a Satellite 6 Provider

Your Satellite 6 provider can still create new hosts independently of Red Hat CloudForms. Your Red Hat CloudForms appliance detects these changes after an automatic refresh period. However, you can trigger a manual refresh to avoid waiting for the automatic refresh.

  1. If you have not navigated elsewhere, the InfrastructureConfiguration Management screen displays your Red Hat Satellite 6 server.
  2. Select your Red hat Satellite 6 provider using the checkbox and click ConfigurationRefresh Relationships and Power States. This triggers the refresh.
  3. When the refresh complete, click on the Red Hat Satellite 6 provider to check the updated contents.

The page now displays an updated list of host groups in the provider.

Chapter 5. Displaying Red Hat Satellite 6 Contents

Red Hat CloudForms provides to methods for viewing the contents of a Red Hat Satellite 6 provider. These methods are:

  • Providers - This presents the Red Hat Satellite 6 contents as a hierarchy of host groups belonging to a provider and then individual hosts belonging to each provider.
  • Configured Systems - This presents a list of all hosts on your Red Hat Satellite 6 server. This also provides a method to apply predefined filters to organized specific machines.

Change between these two views using the accordion menu on the left of the user interface.

Chapter 6. Reprovisioning a Bare Metal Host in Red Hat CloudForms

The current inventory of your Red Hat Satellite 6 server is now visible in Red Hat CloudForms Management Engine. The next procedure is an example of reprovisioning an existing bare metal system into a new hostgroup. For this example, your Red Hat Satellite 6 environment requires the following:

  • An existing bare metal system stored as a host object in your Red Hat Satellite 6 server. This system can either:

    • A standalone system previously provisioned without a host group.
    • A system previously provisioned using a host group.
  • A target host group. This host group contains the system configuration to apply to the host when reprovisioning it. This includes:

    • A new operating system installation, including a new partition table.
    • A new networking configuration that the Red Hat Satellite 6 server defines and manages.
    • Registration to any Red Hat subscriptions and repositories assigned to the hostgroup.
    • Application of any Puppet modules assigned to the hostgroup.
  1. If you have not navigated elsewhere, the InfrastructureConfiguration Management screen displays your Red Hat Satellite 6 server.
  2. Select Configured Systems from the accordion menu on the left. This displays our system list.
  3. Select one or more hosts to reprovision. Use the checkboxes to select these systems.
  4. Select LifecycleProvision Configured Systems. This displays the form for provisioning details.
  5. Under the Request tab, enter the following details:

    1. E-Mail address
    2. First Name
    3. Last Name
    4. This form also contains optional fields for users to enter a plain text Note to inform Red Hat CloudForms administrators of any special details and a field their manager’s Name in case administrators require approval from a user’s manager.
  6. Select the Purpose tab and select any Red Hat CloudForms policy tags that apply to the system.
  7. Select the Catalog tab. This screen displays the list of chosen machines to reprovision and their current details. Select a target host group from the Configuration Profile list. Red Hat CloudForms communicates to Red Hat Satellite to apply the configuration from this host group to the selected host and reprovision the system.
  8. Select the Customize tab. This screen displays some customizable fields for the selected system. You can change the Root Password or change the Hostname and IP Address. Note that these fields are optional as the host group in Red Hat Satellite 6 contains this information. The fields here will override the settings from the hostgroup.

    Important

    Provisioning bare metal systems still requires access to the network that Red Hat Satellite 6 manages. This is because Red Hat Satellite controls PXE booting, kickstarts, and Puppet configuration for bare metal systems. Ensure the IP address you enter in Red Hat CloudForms Management Engine can access a DHCP service that Red Hat Satellite 6 provides either through the main server or through a Red Hat Satellite 6 Capsule server.

  9. Select the Customize tab. This screen allows you to either launch the provisioning process Immediately on Approval or using a schedule. Click Schedule to show the date and time fields you use to schedule the provisioning.
  10. When you have completed all sections of the provisioning form, click Submit.

This submits the provisioning request. Depending on the request settings on your Red Hat CloudForms appliance, this provisioning request might require approval from an administrator. If not, the provisioning request launches depending on your choice for the Schedule.

Note

Previously provisioned hosts might require manual selection of PXE boot from the boot menu or else they might boot to hard disk and not reprovision.

Chapter 7. Tagging a Bare Metal Host in Red Hat CloudForms

Red Hat CloudForms can also control policy settings of bare metal systems from Red Hat Satellite 6 through tagging. Tagging attaches levels of metadata to help define the policy rules required for a set of systems.

  1. If you have not navigated elsewhere, the InfrastructureConfiguration Management screen displays your Red Hat Satellite 6 server.
  2. Select Configured Systems from the accordion menu on the left. This displays your system list.
  3. Select one or more hosts to tag. Use the checkboxes to select these systems.
  4. Select PolicyEdit Tags. This displays the form we use for tagging systems.
  5. Under Tag Assignment, select a tag from Select a customer tag to assign and then choose a value from Select a value to assign. For example, you can tag this system as located in Chicago by selecting Location as the tag and Chicago as the value. Once selected, the user interface automatically adds this tag and value to the table below.
  6. After adding your chosen tags and values, click Save.

The bare metal system is now configured with a set of policy tags.

Note

For more information on tags and system policy, see Defining Policies and Profiles.