10.5. Registration

Procedure 10.2. To Configure a Host for Registration:

1. Take note of the fully qualified domain name (FQDN) of the Satellite Server or Capsule Server, for example server.example.com.
2. On the host, open a terminal and log in as root.
3. Install the consumer RPM from the Satellite Server or Capsule Server to which the host is to be registered. The consumer RPM updates the content source location of the host and allows the host to download content from the content source specified in Red Hat Satellite.

   # rpm -Uvh http://server.example.com/pub/katello-ca-consumer-latest.noarch.rpm

   Important

   Any running Docker Daemons will be restarted.

   Note

   katello-ca-consumer-hostname-1.0-1.noarch.rpm is an additional katello-ca-consumer RPM available that contains the server's host name. The katello-ca-consumer-latest.noarch.rpm rpm will always reflect the most updated version. Both serve the same purpose.

Procedure 10.3. To Register Hosts:

1. On the host, open a terminal and log in as root.
2. Clear any old host data related to Red Hat Subscription Manager (RHSM):

   # subscription-manager clean
   

3. Register the host using RHSM:

   # subscription-manager register --org your_org_name --activationkey your_activation_key

   Example 10.1. Command Output after Registration:

   # subscription-manager register --org MyOrg --activationkey TestKey-1
   The system has been registered with id: 62edc0f8-855b-4184-b1b8-72a9dc793b96
   

Procedure 10.5. To Verify the Satellite Tools Repository is Enabled:

1. Open the Satellite web UI, navigate to Content → Red Hat Repositories and click on the RPMs tab.
2. Find and expand the Red Hat Enterprise Linux Server item.
3. Find and expand the Red Hat Satellite Tools 6.2 (for RHEL VERSION Server) (RPMs) item.
   If the Red Hat Satellite Tools 6.2 items are not visible, it may be because they are not included in the subscription manifest obtained from the Customer Portal. To correct that, log in to the Customer Portal, add these repositories, download the subscription manifest and import it into Satellite.
4. Ensure the Enabled check box beside the repository's name is selected. If not, select it.

Procedure 10.6. To Install Katello Agent:

1. On the host, verify that the satellite-tools repository is enabled. If you registered the host using an activation key with auto-attache enabled, the repository is enabled automatically already.

   # yum repolist enabled | grep -i satellite-tools

   If the satellite-tools is not enabled, enable it using the following command:

   # subscription-manager repos --enable=rhel-version-server-satellite-tools-6.2-rpms

2. Install the katello-agent RPM package using the following command:

   # yum install katello-agent

3. Ensure the goferd service is running.
   • On Red Hat Enterprise Linux 6, enter the following command:

     # service goferd start

   • On Red Hat Enterprise Linux 7, enter the following command:

     # systemctl start goferd

Procedure 10.7. To Verify the Satellite Tools Repository is Enabled:

1. Open the Satellite web UI, navigate to Content → Red Hat Repositories and click on the RPMs tab.
2. Find and expand the Red Hat Enterprise Linux Server item.
3. Find and expand the Red Hat Satellite Tools 6.2 (for RHEL VERSION Server) (RPMs) item.
   If the Red Hat Satellite Tools 6.2 items are not visible, it may be because they are not included in the subscription manifest obtained from the Customer Portal. To correct that, log in to the Customer Portal, add these repositories, download the subscription manifest and import it into Satellite.
4. Ensure the Enabled check box beside the repository's name is selected. If not, select it.

Procedure 10.8. To Install and Enable the Puppet Agent:

1. On the host, open a terminal console and log in as the root user.
2. Verify that the satellite-tools repository is enabled, using the following command:

   # yum repolist enabled | grep -i satellite-tools

   If the satellite-tools is not enabled, enable it using the following command:

   # subscription-manager repos --enable=rhel-version-server-satellite-tools-6.2-rpms

3. Install the Puppet agent RPM package using the following command:

   # yum install puppet
   

4. 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 10.9. To Configure the Puppet Agent:

1. Configure the Puppet agent by specifying the server and environment settings in 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 = /var/lib/puppet/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
       environment = KT_Example_Org_Library_RHEL6Server_3
   
       # Where puppetd caches the local configuration.  An
       # extension indicating the cache format is added automatically.
       # The default value is '$confdir/localconfig'.
       localconfig = $vardir/localconfig
   
   ...
   

   Important

   Set the environment parameter to the name of the Puppet environment to which the host belongs. A Puppet environment is a collection of Puppet modules that can be associated with a host or a host group.

   • To find the host's Puppet environment, navigate to Hosts → All Hosts and inspect the Environment column in the host table.
   • To assign a Puppet environment to a host, navigate to Hosts → All Hosts and click Edit next to the selected host.
   • To list Puppet environments enabled on the Satellite Server, navigate to Configure → Environments. You can also inspect the /etc/puppet/environments/ directory on the Satellite Server to find what Puppet modules and manifests are associated with Puppet environments.

   For more information see the Red Hat Satellite Puppet Guide.
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 UI:
   1. Log in to the Satellite Server through the web UI.
   2. Select Infrastructure → Capsules.
   3. Select Certificates from the drop-down menu to the right of the required Capsule.
   4. Click Sign to the right of the required host.
   5. Enter the puppet agent command again:

      # puppet agent -t --server satellite.example.com

Procedure 10.10. Installing the Bootstrap Script on the Host:

1. Ensure you are in the correct directory. For example, to change to /root:

   # cd

2. Download the script:

   # wget http://satellite6.example.com/pub/bootstrap.py

   This will install the script to the current directory.
3. Make the script executable:

   # chmod +x bootstrap.py

4. To confirm that the script can now be run, view the usage statement as follows:

   # ./bootstrap.py -h

5. Optionally, when the transition process is complete, remove the script:

   # cd
   # rm bootstrap.py

Procedure 10.11. Running the Bootstrap Script

Prerequisites

1. Enter the bootstrap command as follows with values suitable for your environment.
   For the --server option, specify the FQDN name of Satellite Server or Capsule Server. For --location, --organization, and --hostgroup options, use quoted names, not labels, as arguments to the options. See Section 10.5.6, “Advanced Bootstrap Script Configuration” for advanced use cases.

   # bootstrap.py --login=admin \
   --server satellite6.example.com \
   --location="Example Location" \
   --organization="Example Organization" \
   --hostgroup="Example Host Group" \
   --activationkey=activation_key

   The script will prompt you for the password corresponding to the Satellite user name you entered with the --login option.
2. The script will run and send notices of progress to stdout. Watch for output prompting you to approve the certificate. For example:

   [NOTIFICATION], [2016-04-26 10:16:00], [Visit the UI and approve this certificate via Infrastructure->Capsules]
   [NOTIFICATION], [2016-04-26 10:16:00], [if auto-signing is disabled]
   [RUNNING], [2016-04-26 10:16:00], [/usr/bin/puppet agent --test --noop --tags no_such_tag --waitforcert 10]

   The host will wait indefinitely until an administrator approves the Puppet certificate.
   1. In the web UI, navigate to Infrastructure → Capsules.
   2. Select Certificates to the right of the name of the Capsule corresponding to the FQDN given with --server option.
   3. In the Actions column select Sign to approve the host's Puppet certificate.
   4. Return to the host to see the remainder of the bootstrap process completing.
3. In the web UI, navigate to Hosts → All hosts and ensure that the host is connected to the correct host group.