Chapter 3. Installing Satellite Server
3.1. Registering to Red Hat Subscription Management
Registering the host to Red Hat Subscription Management enables the host to subscribe to and consume content for any subscriptions available to the user. This includes content such as Red Hat Enterprise Linux, Red Hat Software Collections (RHSCL), and Red Hat Satellite.
Register your Satellite Server, using your user name and password.
# subscription-manager register Username: Password: The system has been registered with ID: 541084ff2-44cab-4eb1-9fa1-7683431bcf9a
3.2. Identifying and Attaching the Satellite Subscription to the Host
After you have registered your host, you need to identify your Satellite subscription Pool ID. The Pool ID enables you to attach the required subscription to your host. The Satellite subscription provides access to the Satellite content, as well as Red Hat Enterprise Linux, Red Hat Software Collections (RHSCL), and Red Hat Satellite. This is the only subscription required.
To identify your Satellite subscription, enter the following command:
# subscription-manager list --all --available
The outputs displays something similar to the following:
Subscription Name: Red Hat Satellite Provides: Red Hat Satellite 6 Red Hat Enterprise Linux Server Red Hat Satellite Red Hat Enterprise Linux Load Balancer (for RHEL Server) SKU: MCT0370 Pool ID: 8a85f9874152663c0541943739717d11 Available: 3 Suggested: 1 Service Level: Premium Service Type: L1-L3 Multi-Entitlement: No Ends: 10/07/2014 System Type: Physical
- Make a note of the Pool ID so that you can attach it to your Satellite host. Your Pool ID will be different than the example provided.
To attach your subscription to your Satellite Server, enter the following command, using your Pool ID:
# subscription-manager attach --pool=8a85f9874152663c0541943739717d11
The outputs displays something similar to the following:
Successfully attached a subscription for: Red Hat Satellite
To verify that the subscriptions are successfully attached, enter the following command:
# subscription-manager list --consumed
The outputs displays something similar to the following:
+-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Red Hat Satellite Provides: Red Hat Satellite Red Hat Enterprise Linux Server Red Hat Software Collections (for RHEL Server) Red Hat Satellite Red Hat Satellite 6 Red Hat Software Collections (for RHEL Server) Red Hat Satellite Capsule Red Hat Enterprise Linux Load Balancer (for RHEL Server) Red Hat Satellite with Embedded Oracle Red Hat Satellite Capsule Red Hat Enterprise Linux High Availability (for RHEL Server) SKU: MCT0370 Contract: 10293569 Account: 5361051 Serial: 1653856191250699363 Pool ID: 8a85f9874152663c0541943739717d11 Active: True Quantity Used: 1 Service Level: Premium Service Type: L1-L3 Status Details: Starts: 10/08/2013 Ends: 10/07/2014 System Type: Physical
3.3. Configuring Repositories
Disable all existing repositories.
# subscription-manager repos --disable "*"
Enable the Red Hat Satellite and Red Hat Enterprise Linux and Red Hat Software Collections repositories.
The following example uses Red Hat Enterprise Linux 7.
# subscription-manager repos --enable rhel-7-server-rpms \ --enable rhel-server-rhscl-7-rpms \ --enable rhel-7-server-satellite-6.2-rpms
NoteIf you are using a different version of Red Hat Enterprise Linux, change the repository based on your specific version.
Clear out any metadata.
# yum clean all
Verify that the repositories have been enabled.
# yum repolist enabled
3.4. Installing Satellite Server
Install the Satellite Server package.
# yum install satellite
Install Satellite Server and perform the initial configuration.
# satellite-installer --scenario satellite \ --foreman-initial-organization "$ORG" \ --foreman-initial-location "$LOCATION" \ --foreman-admin-password redhat \ --capsule-puppet true \ --foreman-proxy-puppetca true \ --foreman-proxy-tftp true \ --enable-foreman-plugin-discovery
3.5. Configuring the Hammer CLI
You can create saved credentials so that you do not have to type them in each time you issue a command. You can also configure the server so that the admin
user defaults to logging into a specific organization and location.
Create the
~/.hammer/cli_config.yml
file if it does not already exist.# mkdir ~/.hammer # touch
~/.hammer/cli_config.yml
To protect your password, make sure the file is only readable by the current user. For example, if you plan to issue hammer commands as root, execute the following command.
# chmod 600 ~/.hammer/cli_config.yml
Add the following content to the file.
:foreman: :host: 'https://satellite.example.net/' :username: 'admin' :password: 'redhat'
ImportantDo not use tabs in your
~/.hammer/cli_config.yml
file. Always use indentation by spaces.Configure the
admin
user to default to logging in to the specified organization and location.# hammer user update --login admin \ --default-location-id 1 \ --default-organization-id 1 \ --locations "$LOCATION" \ --organizations "$ORG"
3.6. Creating a Manifest
- Go to the Red Hat Customer Portal and log in.
- Click SUBSCRIPTIONS.
- In the Red Hat Subscription Management section, click Satellite.
- Click Register a Satellite.
- In the Name field, type Satellite_Server_example.
- Select Satellite 6.2 as the version and click Register.
- Click Attach a subscription.
- Select the check box for each subscription that you want to attach and specify the number of subscriptions.
Click Attach Selected.
It can take several minutes for all the subscriptions to attach.
- Click Download Manifest and save the manifest file to a known location.
3.7. Uploading a Manifest to Your Satellite Server
Uploading a Manifest Using the Web UI
- Verify that you are in the correct Organization.
-
Click Content
Red Hat Subscriptions. - Click Manage Manifest to open the Subscriptions page.
- Click Browse, select the manifest file you created, and click Open.
- Click Upload to upload the manifest to the Satellite Server.
Uploading a Manifest Using Hammer CLI
Upload a manifest to Satellite Server.
# hammer subscription upload \ --organization-label org_label \ --file path_to_manifest