Chapter 5. Configuring a Self-Registered Satellite

A Red Hat Satellite server is normally registered to the Red Hat Customer Portal, then activated as a Satellite Server and gets new content from the Red Hat Customer Portal. A self-registered Red Hat Satellite 6 Server is registered to itself rather than the Red Hat Customer Portal.
Once a Red Hat Satellite 6 server is installed, there are several advantages to registering it as a client to itself:
  • The same life cycle management procedures can be applied to the Satellite 6 server itself that have been applied to the rest of the managed estate.
  • By subscribing the Satellite 6 server to its own content views, it will receive the same updates on the same schedule as the rest of the managed hosts.
  • A virt-who service can be run directly on the Satellite 6 server without the need for an additional host.
There are also several limitations of a self-registered Satellite server:
  • A self-registered Satellite Server cannot test package updates by using life cycle environments. It is essential to make a full backup of a self-registered Satellite Server before doing an upgrade to untested packages.
  • Not all puppet modules are supported by a self-registered Satellite server. When applying puppet modules to a self-registered Satellite server ensure that they will not create an unsupported configuration.

5.1. Registering a Satellite to Itself

Before a self-registered Satellite can be configured to get updates from itself, the Satellite subscription must be added to the Satellite’s manifest. When the subscription is in the manifest, the appropriate Satellite repositories can be synchronized into the Satellite.

Procedure 5.1. To Register a Satellite to Itself:

  1. If the Satellite is already registered to the Red Hat Customer Portal, unregister the Satellite from the Red Hat Customer Portal using the following commands:
    # subscription-manager remove --all
    # subscription-manager unregister
    
  2. The Satellite subscription on the Red Hat Customer Portal is now available and can be transferred into the Satellite's manifest. For further information on Manifests see Section 4.1.1, “Accessing Red Hat Content Providers”.
    Transfer the subscription to the Satellite's manifest:
    1. Navigate to https://access.redhat.com and click SUBSCRIPTIONS on the main menu at the top of the page.
    2. Scroll down to the Red Hat Subscription Management section, and click Satellite under Subscription Management Applications.
    3. Select the required Satellite server by clicking its host name in the table.
    4. Click Attach a subscription and select subscriptions you want to attach. Specify the quantity for each subscription, and click Attach Selected.
  3. Refresh the manifest on the Satellite Server:
    1. Log in to the Satellite server.
    2. Ensure that the correct organization is selected.
    3. Click ContentRed Hat Subscriptions and then click Manage Manifest at the upper right of the page.
    4. In the Subscription Manifest section, click Actions and under the Subscription Manifest subsection, click Refresh Manifest.
  4. Enable Red Hat repositories using the Satellite web interface:
    1. Click ContentRed Hat Repositories.
    2. Navigate to the required repositories. Click each repository set from which you want to select repositories and select the check box for each required repository. The repository is automatically enabled.
      For Red Hat Enterprise Linux 6 the repositories that need to be enabled are:
      • Red Hat Enterprise Linux 6 Server RPMs x86_64 6Server
      • Red Hat Satellite 6.1 for RHEL 6 Server RPMs x86_64
      • Red Hat Software Collections RPMs for Red Hat Enterprise Linux 6 Server x86_64 6Server
      • Red Hat Enterprise Linux 6 Server - Satellite Tools RPMs x86_64 Repository
      For Red Hat Enterprise Linux 7 the repositories that need to be enabled are:
      • Red Hat Enterprise Linux 7 Server RPMs x86_64 6Server
      • Red Hat Satellite 6.1 for RHEL 7 Server RPMs x86_64
      • Red Hat Software Collections RPMs for Red Hat Enterprise Linux 7 Server x86_64 6Server
      • Red Hat Enterprise Linux 7 Server - Satellite Tools RPMs x86_64 Repository
  5. Synchronize the Satellite server:
    1. Navigate to ContentSync Status. Based on the subscriptions and repositories enabled, the list of product repositories available for synchronization is displayed.
    2. Click the arrow next to the product name to see available content.
    3. Select the content you want to synchronize.
    4. Click Synchronize Now to starting synchronizing. The status of the synchronization process will appear in the Result column. If synchronization is successful, Sync complete will appear in the Result column. If synchronization failed, Error syncing will appear.

    Note

    Content synchronization can take a long time. The length of time required depends on the speed of disk drives, network connection speed, and the amount of content selected for synchronization.
  6. Optionally, create a content view to represent the Satellite server. This will allow the Satellite to follow the same life cycle management procedures as the rest of the content on the server. For further information about content views see the Content Views chapter in the Red Hat Satellite 6.1 User Guide
    1. To create a content view:
      1. Log into the web interface as a Satellite administrator.
      2. Click ContentContent Views.
      3. Click Create New View.
      4. Specify the Name of the content view. The Label field is automatically populated when the Name field is filled out. Optionally, provide a description of the content view.
      5. Click Save.
    2. Edit the content view to add the Red Hat Enterprise Linux server and Satellite repositories:
      1. Click ContentContent Views and choose the Content View to add repositories to.
      2. Click Yum Content and select Repositories from the drop-down menu. From the submenu, click Add.
      3. Select the required repositories to add and click Add Repositories. The required repositories for a self-registered Satellite are all the repositories for the Satellite itself, any supporting repositories and the repository for the Base OS. The repositories required for a self-registered Satellite are listed in Step 4 of this procedure.
  7. Download and install the required certificates by running:
    # rpm -Uvh /var/www/html/pub/katello-ca-consumer-latest.noarch.rpm
  8. Register the Satellite server and attach the appropriate entitlements using subscription manager. When registering the server you must specify the organization to which the server belongs, also the life cycle environment.
    # subscription-manager register --org=organization --environment=environment

    Example 5.1. 

    # subscription-manager register --org=ExampleCompany --environment=Library
    You will be prompted for your Red Hat Satellite user name and password. The Satellite Server administrator can configure new users. See the Users and Roles chapter in the Red Hat Satellite 6.1 User Guide for more information.
  9. Find the pool IDs for the Satellite and for Red Hat Enterprise Linux by running the following command:
    # subscription-manager list --available
  10. Attach the entitlements by running the following command:
    # subscription-manager attach --pool Red_Hat_Satellite_Pool_ID --pool Red_Hat_Enterprise_Linux_ID
    A content host has now been created for the Satellite server inside of the Satellite server.
  11. Enable the repositories required for the Satellite server by running the following command:
    # subscription-manager repos --enable=repository-to-be-enabled
    See Step 4 of this procedure for the list of repositories that need to be enabled.
  12. Install the Katello Agent package to allow errata management and package installation through the Satellite web interface. The katello-agent package depends on the gofer package that provides the goferd service. The goferd service must be enabled so that the Red Hat Satellite Server or Capsule Server can provide information about errata that are applicable for content hosts.
    To install the katello-agent run the following command:
    # yum install katello-agent
    The goferd service is started and enabled automatically after successful installation of katello-agent.