Procedure 2.1. Registering a Red Hat Enterprise Linux system using Subscription Management

1. Run the subscription-manager register command to register the system with Customer Portal Subscription Management.

   # subscription-manager register

2. Enter your Red Hat Customer Portal user name when prompted.

   Username: admin@example.com

   Important

   Your Red Hat Subscription must have Red Hat Enterprise Linux OpenStack Platform entitlements. If your subscription does not have Red Hat Enterprise Linux OpenStack entitlements then you may register for access to the evaluation program at http://www.redhat.com/products/enterprise-linux/openstack-platform/.
3. Enter your Red Hat Customer Portal password when prompted.

   Password:

4. When registration completes successfully the system is assigned a unique identifier.

   The system has been registered with id: IDENTIFIER

Procedure 2.2. Attaching Pool IDs to your subscription

1. Use the subscription-manager list command to locate the pool identifier of the Red Hat Enterprise Linux subscription.

   # subscription-manager list --available
   +-------------------------------------------+
       Available Subscriptions
   +-------------------------------------------+
   
   Product Name:          Red Hat Enterprise Linux Server
   Product Id:            69
   Pool Id:               POOLID
   Quantity:              1
   Service Level:         None
   Service Type:          None
   Multi-Entitlement:     No
   Expires:               01/01/2022
   Machine Type:          physical
   ...

   The pool identifier is indicated in the Pool Id field associated with the Red Hat Enterprise Linux Server product. The identifier will be unique to your subscription. Take note of this identifier as it will be required to perform the next step.

   Note

   The output displayed in this step has been truncated to conserve space. All other available subscriptions will also be listed in the output of the command.
2. Use the subscription-manager attach command to attach the subscription identified in the previous step.

   # subscription-manager attach --pool=POOLID
   Successfully attached a subscription for Red Hat Enterprise Linux Server.

   Replace POOLID with the unique identifier associated with your Red Hat Enterprise Linux Server subscription. This is the identifier that was located in the previous step.
3. Run the yum repolist command. This command ensures that the repository configuration file /etc/yum.repos.d/redhat.repo exists and is up to date.

   # yum repolist

   Once repository metadata has been downloaded and examined, the list of repositories enabled will be displayed, along with the number of available packages.

   repo id                  repo name                                    status
   rhel-7-server-rpms       Red Hat Enterprise Linux 7 Server (RPMs)      8,816
   repolist: 8,816

   Note

   The output displayed in this step may differ from that which appears when you run the yum repolist command on your system. In particular the number of packages listed will vary if or when additional packages are added to the rhel-7-server-rpms repository.

Procedure 2.3. Attaching Pool IDs to your subscription

1. Use the subscription-manager list command to locate the pool identifier of the relevant Red Hat Cloud Infrastructure or Red Hat Enterprise Linux OpenStack Platform entitlement.

   # subscription-manager list --available
   +-------------------------------------------+
       Available Subscriptions
   +-------------------------------------------+
   ...
   Product Name:          ENTITLEMENT
   Product Id:            ID_1
   Pool Id:               POOLID_1
   Quantity:              3
   Service Level:         None
   Service Type:          None
   Multi-Entitlement:     No
   Expires:               DATE
   Machine Type:          physical
   
   Product Name:          ENTITLEMENT
   Product Id:            ID_2
   Pool Id:               POOLID_2
   Quantity:              unlimited
   Service Level:         None
   Service Type:          None
   Multi-Entitlement:     No
   Expires:               DATE
   Machine Type:          virtual
   ...

   Locate the entry in the list where the Product Name matches the name of the entitlement that will be used to access Red Hat Enterprise Linux OpenStack Platform packages. Take note of the pool identifier associated with the entitlement, this value is indicated in the Pool Id field. The pool identifier is unique to your subscription and will be required to complete the next step.

   Note

   The output displayed in this step has been truncated to conserve space. All other available subscriptions will also be listed in the output of the command.
2. Use the subscription-manager attach command to attach the subscription identified in the previous step.

   # subscription-manager attach --pool=POOLID
   Successfully attached a subscription for ENTITLEMENT.

   Replace POOLID with the unique identifier associated with your Red Hat Cloud Infrastructure or Red Hat Enterprise Linux OpenStack Platform entitlement. This is the identifier that was located in the previous step.
3. Use either the subscription-manager or yum-config-manager commands to enable or disable the appropriate software repositories (channels).
   For example, to ensure that the repository for Red Hat Enterprise Linux OpenStack Platform 3 (Grizzly) has been disabled, run:

   # subscription-manager repos --disable rhel-server-ost-6-3-rpms
   Loaded plugins: product-id                                 
   ==== repo: rhel-server-ost-6-3-rpms ====
   [rhel-server-ost-6-3-rpms]
   bandwidth = 0
   base_persistdir = /var/lib/yum/repos/x86_64/6Server
   baseurl = https://cdn.redhat.com/content/dist/rhel/server/6/6Server/x86_64/openstack/3/os
   cache = 0
   cachedir = /var/cache/yum/x86_64/6Server/rhel-server-ost-6-3-rpms
   cost = 1000
   enabled = False
   ...

   Note

   The values True and 1 are equivalent. As a result the output on your system may instead contain this string:

   enabled = 1

4. Run the yum repolist command. This command ensures that the repository configuration file /etc/yum.repos.d/redhat.repo exists and is up to date.

   # yum repolist

   Once repository metadata has been downloaded and examined, the current list of enabled repositories will be displayed, along with the number of available packages. For example:

   repo id                repo name                                   status                  
   rhel-7-server-rpms     Red Hat Enterprise Linux 7 Server (RPMs)    11,610+460
   rhel-7-server-openstack-5.0-rpms  \
   Red Hat OpenStack 5.0 for Server 7 (RPMS)   487+143
   

5. Use the subscription-manager command to enable the Red Hat Enterprise Linux OpenStack Platform repository.

   # subscription-manager repos --enable=[reponame]

   Replace [reponame] with the appropriate repository name. For details, see Section 2.1.2.2, “RHN/CDN Channels”.
6. Install the yum-plugin-priorities package provided by the rhel-6-server-optional-rpms channel for Red Hat Enterprise Linux 6.7 or the rhel-7-server-optional-rpms channel for Red Hat Enterprise Linux 7.2:

   # yum install yum-plugin-priorities

7. If not yet installed, use the following to install yum-config-manager:

   # yum install yum-utils

8. Use the yum-config-manager command to set the priority of the Red Hat Enterprise Linux OpenStack Platform software repository to 1. This is the highest priority value supported by the yum-plugin-priorities plug-in.

   # yum-config-manager --enable [reponame] --setopt="[reponame].priority=1"

   For example:

   # yum-config-manager --enable rhel-7-server-openstack-5.0-rpms \
           --setopt="rhel-7-server-openstack-5.0-rpms.priority=1"
   Loaded plugins: product-id                                 
   ==== repo: rhel-7-server-openstack-5.0-rpms ====
   [rhel-7-server-openstack-5.0-rpms]
   bandwidth = 0
   base_persistdir = /var/lib/yum/repos/x86_64/6Server
   ...
   cost = 1000
   enabled = True
   ...
   priority = 1
   ...

9. Run the yum update command and reboot to ensure that the most up-to-date packages, including the kernel, are installed and running.

   # yum update
   # reboot