Chapter 7. Manually Installing and Configuring a Broker Host

Prerequisites:

This chapter describes how to manually install and configure the OpenShift Enterprise broker host. The example host contains the broker application, MongoDB, ActiveMQ, and BIND. Each of these components is covered in individual sections.
Perform all of the procedures in this section only after the base operating system is fully installed and configured, and before you install and configure any node hosts.

Warning

The OpenShift Enterprise security model assumes that broker and node components are installed on separate hosts. Running a broker and node on the same host is not supported.

7.1. Configuring Broker Host Entitlements

OpenShift Enterprise requires several packages that are not available in the standard Red Hat Enterprise Linux channels. A broker host requires a subscription for the appropriate OpenShift Enterprise channels to receive these extra packages.

Table 7.1. OpenShift Enterprise Broker Host Channels

Channel Name Purpose Required Provided By
Red Hat OpenShift Enterprise 2.2 Infrastructure. Base channel for OpenShift Enterprise 2.2 broker hosts. Yes. "OpenShift Enterprise Broker Infrastructure" subscription.
Red Hat OpenShift Enterprise 2.2 Client Tools. Provides access to the OpenShift Enterprise 2.2 client tools. Not required for broker functionality, but required during installation for testing and troubleshooting purposes. "OpenShift Enterprise Broker Infrastructure" subscription.
Red Hat Software Collections 1. Provides access to the latest version of programming languages, database servers, and related packages. Yes. "OpenShift Enterprise Broker Infrastructure" subscription.
You must register your host through either Red Hat Subscription Management (RHSM) or Red Hat Network (RHN) Classic to attach any of the above subscriptions and enable the proper channels. Instructions for either of these subscription methods are provided in the following sections. Choose one subscription method and follow the relevant instructions before proceeding to Section 7.2, “Configuring Yum on Broker Hosts”.

7.1.1. Using Red Hat Subscription Management on Broker Hosts

For additional information on managing your subscription entitlements with Red Hat Subscription Management, see the Red Hat Subscription Management guides at http://access.redhat.com/site/documentation.

Procedure 7.1. To Configure Broker Host Entitlements with Red Hat Subscription Management:

  1. On your Red Hat Enterprise Linux instance, register the system:

    Example 7.1. Registering Using the Subscription Manager

    # subscription-manager register
				
Username:
Password:

The system has been registered with id: 3tghj35d1-7c19-4734-b638-f24tw8eh6246
  2. Locate the desired OpenShift Enterprise subscription pool IDs in the list of available subscriptions for your account:

    Example 7.2. Finding the OpenShift Enterprise Pool ID

    # subscription-manager list --available
				
+-------------------------------------------+
    Available Subscriptions
+-------------------------------------------+

Subscription Name:      OpenShift Enterprise Broker Infrastructure
SKU:                    SYS####
Pool Id:                Example_3affb61f013b3ef6a5fe0b9a
Quantity:               1
Service Level:          Layered
Service Type:           L1-L3
Multi-Entitlement:      No
Ends:                   01/01/2020
System Type:            Physical
  3. Attach the desired subscription. Replace pool-id in the following command with your relevant Pool ID value from the previous step: 
    # subscription-manager attach --pool pool-id
  4. Enable only the Red Hat OpenShift Enterprise 2.2 Infrastructure channel: 
    # subscription-manager repos --enable rhel-6-server-ose-2.2-infra-rpms
  5. Confirm that yum repolist displays the enabled channel: 
    # yum repolist

repo id                            repo name

rhel-6-server-ose-2.2-infra-rpms   Red Hat OpenShift Enterprise 2.2 Infrastructure (RPMs)
    OpenShift Enterprise broker hosts require a customized yum configuration to install correctly. For continued steps to correctly configure yum, see Section 7.2, “Configuring Yum on Broker Hosts”.

7.1.2. Using Red Hat Network Classic on Broker Hosts

For additional information regarding Red Hat Network (RHN) Classic, see the Red Hat Subscription Management guides at http://access.redhat.com/site/documentation.

Note

While Red Hat Network (RHN) Classic can be used to subscribe to channels, it is primarily intended for existing, legacy systems. Red Hat strongly recommends that you use Red Hat Subscription Management for new installations. For details on how to migrate from RHN Classic to RHSM, see the OpenShift Enterprise Administration Guide.

Procedure 7.2. To Configure Entitlements with Red Hat Network (RHN) Classic:

  1. On your Red Hat Enterprise Linux instance, register the system. Replace username and password in the following command with your Red Hat Network account credentials. 
    # rhnreg_ks --username username --password password
  2. Enable only the Red Hat OpenShift Enterprise 2.2 Infrastructure channel. 
    # rhn-channel -a -c rhel-x86_64-server-6-ose-2.2-infrastructure
  3. Confirm that yum repolist displays the enabled channel. 
    # yum repolist

repo id                                       repo name

rhel-x86_64-server-6-ose-2.2-infrastructure   Red Hat OpenShift Enterprise 2.2 Infrastructure - x86_64
    OpenShift Enterprise broker hosts require a customized yum configuration to install correctly. For continued steps to correctly configure yum, see Section 7.2, “Configuring Yum on Broker Hosts”.