Managing Red Hat subscriptions

orcharhino can import content from the Red Hat Content Delivery Network (CDN). orcharhino requires a Red Hat subscription manifest to find, access, and download content from the corresponding repositories. You must have a Red Hat subscription manifest containing a subscription allocation for each organization on orcharhino Server. All subscription information is available in your Red Hat Customer Portal account.

Before you can complete the tasks in this chapter, you must create a Red Hat subscription manifest in the Customer Portal.

Use this chapter to import a Red Hat subscription manifest and manage the manifest within the orcharhino management UI.

Subscription allocations and organizations

You can manage more than one organization if you have more than one subscription allocation. orcharhino requires a single allocation for each organization configured in orcharhino Server. The advantage of this is that each organization maintains separate subscriptions so that you can support multiple organizations, each with their own Red Hat accounts.

Future-dated subscriptions

You can use future-dated subscriptions in a subscription allocation. When you add future-dated subscriptions to content hosts before the expiry date of the existing subscriptions, you can have uninterrupted access to repositories.

Manually attach the future-dated subscriptions to your content hosts before the current subscriptions expire. Do not rely on the auto-attach method because this method is designed for a different purpose and might not work. For more information, see Attaching Red Hat Subscriptions to Content Hosts.

When a future-dated subscription becomes active, you must refresh the manifest to synchronize repository content. For more information, see Updating and Refreshing Red Hat Subscription Manifests.

Additional resources

Configuring orcharhino Server to Consume Content from a Custom CDN in Installing orcharhino Server

Running Red Hat Enterprise Linux on managed hosts requires a subscription from Red Hat. Ensure to provide valid licenses for all used Red Hat products. Using insufficient, invalid, or otherwise inadequate licenses might violate your terms with Red Hat.

We recommend using a Manifest file from your Red Hat account to import available content to orcharhino. Navigate to Content > Subscriptions to see available and consumed Red Hat subscriptions.

Importing a Red Hat subscription manifest into orcharhino Server

Use the following procedure to import a Red Hat subscription manifest into orcharhino Server.

Simple Content Access (SCA) is set on the organization, not the manifest. Importing a manifest does not change your organization’s Simple Content Access status.

Prerequisites

You must have a Red Hat subscription manifest file exported from the Red Hat Customer Portal.

Procedure

In the orcharhino management UI, ensure the context is set to the organization you want to use.
In the orcharhino management UI, navigate to Content > Subscriptions and click Manage Manifest.
In the Manage Manifest window, click Choose File.
Navigate to the location that contains the Red Hat subscription manifest file, then click Open.

CLI procedure

Copy the Red Hat subscription manifest file from your local machine to orcharhino Server:
```
$ scp ~/manifest_file.zip root@orcharhino.example.com:~/.
```
Log in to orcharhino Server as the root user and import the Red Hat subscription manifest file:
```
# hammer subscription upload \
--file ~/manifest_file.zip \
--organization "My_Organization"
```

You can now enable repositories and import Red Hat content. For more information, see Importing Content in Managing Content.

If you upload a Red Hat Manifest to orcharhino, ensure that it does not enable Simple Content Access (SCA). Otherwise, all content hosts automatically consume all repositories published within their selected content view and lifecycle environment. This affects not only RHEL content, but also content for all other operating systems.

Disabling Simple Content Access

You can disable simple content access (SCA) for organizations.

Prerequisite

You have uploaded a Red Hat Manifest file into orcharhino and enabled SCA. The button to disable SCA is only visible if SCA is enabled.

Procedure

Navigate to Administer > Organizations.
Select an organization.
On the Primary tab, deselect Simple Content Access.
Click Submit to save your change.

Locating a Red Hat subscription

When you import a Red Hat subscription manifest into orcharhino Server, the subscriptions from your manifest are listed in the Subscriptions window. If you have a high volume of subscriptions, you can filter the results to find a specific subscription.

Prerequisites

You must have a Red Hat subscription manifest file imported to orcharhino Server. For more information, see Importing a Red Hat Subscription Manifest into Server.

Procedure

In the orcharhino management UI, ensure the context is set to the organization you want to use.
In the orcharhino management UI, navigate to Content > Subscriptions.
In the Subscriptions window, click the Search field to view the list of search criteria for building your search query.
Select search criteria to display further options.
When you have built your search query, click the search icon.

For example, if you place your cursor in the Search field and select expires, then press the space bar, another list appears with the options of placing a >, <, or = character. If you select > and press the space bar, another list of automatic options appears. You can also enter your own criteria.

Adding Red Hat subscriptions to subscription allocations

Use the following procedure to add Red Hat subscriptions to a subscription allocation in the orcharhino management UI.

Prerequisites

You must have a Red Hat subscription manifest file imported to orcharhino Server. For more information, see Importing a Red Hat Subscription Manifest into Server.

Procedure

In the orcharhino management UI, ensure the context is set to the organization you want to use.
In the orcharhino management UI, navigate to Content > Subscriptions.
In the Subscriptions window, click Add Subscriptions.
On the row of each subscription you want to add, enter the quantity in the Quantity to Allocate column.
Click Submit

Removing Red Hat subscriptions from subscription allocations

Use the following procedure to remove Red Hat subscriptions from a subscription allocation in the orcharhino management UI.

Manifests must not be deleted. If you delete the manifest from the Red Hat Customer Portal or in the orcharhino management UI, all of the entitlements for all of your content hosts will be removed.

Prerequisites

You must have a Red Hat subscription manifest file imported to orcharhino Server. For more information, see Importing a Red Hat Subscription Manifest into Server.

Procedure

In the orcharhino management UI, ensure the context is set to the organization you want to use.
In the orcharhino management UI, navigate to Content > Subscriptions.
On the row of each subscription you want to remove, select the corresponding checkbox.
Click Delete, and then confirm deletion.

Updating and refreshing Red Hat subscription manifests

Every time that you change a subscription allocation, you must refresh the manifest to reflect these changes. For example, you must refresh the manifest if you take any of the following actions:

Renewing a subscription
Adjusting subscription quantities
Purchasing additional subscriptions

You can refresh the manifest directly in the orcharhino management UI. Alternatively, you can import an updated manifest that contains the changes.

Procedure

In the orcharhino management UI, ensure the context is set to the organization you want to use.
In the orcharhino management UI, navigate to Content > Subscriptions.
In the Subscriptions window, click Manage Manifest.
In the Manage Manifest window, click Refresh.

Attaching Red Hat subscriptions to content hosts

Using activation keys is the main method to attach subscriptions to content hosts during the provisioning process. However, an activation key cannot update an existing host. If you need to attach new or additional subscriptions, such as future-dated subscriptions, to one host, use the following procedure.

This procedure is only valid if you have Simple Content Access (SCA) disabled on your orcharhino. With SCA enabled, you do not need to have subscriptions attached to your hosts. Note that SCA is enabled by default for newly created organizations. To learn more about SCA, see Simple Content Access.

For more information about updating multiple hosts, see Updating Red Hat Subscriptions on Multiple Hosts.

For more information about activation keys, see Managing Activation Keys.

orcharhino Subscriptions

In orcharhino, you must maintain a Red Hat Enterprise Linux Satellite subscription, formerly known as Red Hat Enterprise Linux Smart Management, for every Red Hat Enterprise Linux host that you want to manage.

However, you are not required to attach orcharhino subscriptions to each content host. orcharhino subscriptions cannot attach automatically to content hosts in orcharhino because they are not associated with any product certificates. Adding a orcharhino subscription to a content host does not provide any content or repository access. If you want, you can add a orcharhino subscription to a manifest for your own recording or tracking purposes.

Prerequisites

You must have a Red Hat subscription manifest file imported to orcharhino Server. For more information, see Importing a Red Hat Subscription Manifest into Server.

Procedure

In the orcharhino management UI, ensure the context is set to the organization you want to use.
In the orcharhino management UI, navigate to Hosts > Content Hosts.
On the row of each content host whose subscription you want to change, select the corresponding checkbox.
From the Select Action list, select Manage Subscriptions.
Optionally, enter a key and value in the Search field to filter the subscriptions displayed.
Select the checkbox to the left of the subscriptions that you want to add or remove and click Add Selected or Remove Selected as required.
Click Done to save the changes.

CLI procedure

On your orcharhino Server, list all available subscriptions:

# hammer subscription list \
--organization-id My_Organization_ID

Attach a subscription to your host:

# hammer host subscription attach \
--host My_Host_Name \
--subscription-id My_Subscription_ID

Updating Red Hat subscriptions on multiple hosts

Use this procedure for post-installation changes to multiple content hosts at the same time.

Procedure

In the orcharhino management UI, ensure the context is set to the organization you want to use.
In the orcharhino management UI, navigate to Hosts > Content Hosts.
On the row of each content host whose subscription you want to change, select the corresponding checkbox.
From the Select Action list, select Manage Subscriptions.
Optionally, enter a key and value in the Search field to filter the subscriptions displayed.
Select the checkbox to the left of the subscriptions to be added or removed and click Add Selected or Remove Selected as required.
Click Done to save the changes.

Content Delivery Network structure

Information in this section applies only if you consume Red Hat content using a Red Hat manifest.

Red Hat Content Delivery Network (CDN), located at cdn.redhat.com, is a geographically distributed series of static webservers which include content and errata designed to be used by systems. This content can be accessed directly through a system registered using Subscription Manager or through the orcharhino management UI. The accessible subset of the CDN is configured through subscriptions attached to a system using Red Hat Subscription Management or using orcharhino Server.

Red Hat Content Delivery network is protected by X.509 certificate authentication to ensure that only valid users can access it.

Directory structure of the CDN

$ tree -d -L 11
└── content  (1)
    ├── beta  (2)
    │   └── rhel  (3)
    │       └── server  (4)
    │           └── 7 (5)
    │               └── x86_64  (6)
    │                   └── sat-tools  (7)
    └── dist
        └── rhel
            └── server
                └── 7
                ├── 7.2
                │   └── x86_64
                │       └── kickstart
                └── 7Server
                    └── x86_64
                        └── os

1	The `content` directory.
2	Directory responsible for the lifecycle of the content. Common directories include `beta` (for Beta code), `dist` (for Production) and `eus` (For Extended Update Support) directories.
3	Directory responsible for the Product name. Usually `rhel` for Red Hat Enterprise Linux.
4	Directory responsible for the type of the Product. For Red Hat Enterprise Linux this might include `server`, `workstation`, and `computenode` directories.
5	Directory responsible for the release version, such as `7`, `7.2` or `7Server`.
6	Directory responsible for the base architecture, such as `i386` or `x86_64`.
7	Directory responsible for the repository name, such as `sat-tools`, `kickstart`, `rhscl`. Some components have additional subdirectories which might vary.

This directory structure is also used in the Red Hat Subscription Manifest.

The text and illustrations on this page are licensed by ATIX AG under a Creative Commons Attribution–Share Alike 3.0 Unported ("CC-BY-SA") license. This page also contains text from the official Foreman documentation which uses the same license ("CC-BY-SA").