12.5. Registration

12.5.1. Registering a Host

These steps show how to register hosts in Red Hat Satellite Server. Hosts provisioned by Satellite Server appear on the Hosts page accessible through HostsAll hosts. Hosts registered to the Satellite Server via Red Hat Subscription Manager, which can occur either during the post phase of a kickstart or through the terminal, will appear on the Content Hosts page accessible through HostsContent Hosts.
You must meet the following conditions before continuing with this task:

Procedure 12.6. Registering Systems

  1. Open a terminal console and login as root on the command line.
  2. Clear old system data in preparation for registering. This makes sure that your updated system data is uploaded correctly.
    subscription-manager clean
    
  3. Register the system using the Red Hat Subscription Manager (RHSM):
    # subscription-manager register --org [your_org_name] --activationkey [your_activation_key]
    

    Note

    Activation keys will allow you to add environments, provisioning templates and dictate what subscriptions are available and should be applied to the registering system.
    There are various options that may be added. For more information, use the command man subscription-manager.
The command line output after the registration should look like:
# subscription-manager register --org MyOrg --activationkey TestKey-1
The system has been registered with id: 62edc0f8-855b-4184-b1b8-72a9dc793b96
The system should now appear in the Red Hat Satellite Server.

Note

For systems with Red Hat Enterprise Linux 6.3, the release version defaults to version 6.0. To ensure that it is pointing to the 6.3 repository, please follow these steps:
  1. On Red Hat Satellite, select HostsContent Hosts.
  2. Select the system that needs to be changed and click Edit.
  3. Click on the Operating System tab.
  4. Select '6.3' from the Operating system drop-down menu.
  5. Click Save.

12.5.2. Installing the Katello Agent

Prerequisites

The Red Hat Common repository must be enabled in the Red Hat Satellite Server as it provides the required packages.

These steps show how to install and enable the Katello agent. The katello-agent must be enabled so that the Red Hat Satellite Server or Capsule Server can provide information about errata that are applicable for the system.
To install katello-agent:
  1. Open a terminal console and log in as root on the command line.
  2. Install the katello-agent using the following command:
    # yum install katello-agent
    

12.5.3. Installing and Configuring the Puppet Agent

This section describes how to install and configure the Puppet agent on a Satellite 6 host. When you have correctly installed and configured the Puppet agent, you can navigate to HostsAll hosts to list all hosts visible to Red Hat Satellite Server.

Important

The puppet package is part of the Red Hat Common repository. Ensure you enable this repository before you proceed.

Procedure 12.7. Installing and Enabling the Puppet Agent

  1. Open a terminal console and log in as root.
  2. Install the Puppet agent:
    # yum install puppet
    
  3. Configure the puppet agent to start at boot:
    • On Red Hat Enterprise Linux 6:
      # chkconfig puppet on
    • On Red Hat Enterprise Linux 7:
      # systemctl enable puppet

Procedure 12.8. Configuring the Puppet Agent

Prerequisites

You must meet the following conditions before continuing with this task:

  • The host must be registered to the Red Hat Satellite Server.
  • The Red Hat Common repository must be enabled.
  • Puppet packages must be installed on the host.
  1. Configure the Puppet agent by changing the /etc/puppet/puppet.conf file:
    # vi /etc/puppet/puppet.conf
    
    [main]
        # The Puppet log directory.
        # The default value is '$vardir/log'.
        logdir = /var/log/puppet
    
        # Where Puppet PID files are kept.
        # The default value is '$vardir/run'.
        rundir = /var/run/puppet
    
        # Where SSL certificates are kept.
        # The default value is '$confdir/ssl'.
        ssldir = $vardir/ssl
    
    [agent]
        # The file in which puppetd stores a list of the classes
        # associated with the retrieved configuratiion.  Can be loaded in
        # the separate ``puppet`` executable using the ``--loadclasses``
        # option.
        # The default value is '$confdir/classes.txt'.
        classfile = $vardir/classes.txt
        pluginsync = true
        report = true
        ignoreschedules = true
        daemon = false
        ca_server = satellite.example.com
        server = satellite.example.com
    
        # Where puppetd caches the local configuration.  An
        # extension indicating the cache format is added automatically.
        # The default value is '$confdir/localconfig'.
        localconfig = $vardir/localconfig
    
  2. Run the Puppet agent on the host:
    # puppet agent -t --server satellite.example.com
  3. Sign the SSL certificate for the puppet client through the Satellite Server web interface:
    1. Log in to the Satellite Server through the web interface.
    2. Select InfrastructureCapsules.
    3. Click Certificates to the right of the required host.
    4. Click Sign.

Note

Once the Puppet agent is configured on the host it will be listed under All Hosts but only when Any Context is selected as the host will not be assigned to an organization or location. To assign the host to an organization see Section 3.1.3, “Editing an Organization” and to assign the host to a location see Section 3.2.2, “Editing a Location”.