Chapter 9. Manually Installing and Configuring Node Hosts

Prerequisites:

The following sections describe how to manually install and configure OpenShift Enterprise node hosts. These hosts support gears which, in turn, contain applications. Many of the steps required to configure a node are similar to the steps involved in configuring a broker, so some explanatory details are omitted from the following process.
Perform all of the procedures in this section only after the base operating system is fully installed and configured.

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.

9.1. Configuring Node Host Entitlements

OpenShift Enterprise requires several packages that are not available in the standard Red Hat Enterprise Linux channels. A node host requires a subscription for the appropriate OpenShift Enterprise channels to receive these extra packages.
Some subscriptions may be optional based on your requirements. For example, if you intend to install certain premium cartridges, they may require access to particular channels. The following table notes channels that are required for basic node host installation, as well as use cases for optional channels. Note that channel names may differ slightly between the RHSM and RHN Classic subscription methods.

Table 9.1. OpenShift Enterprise Node Host Channels

Channel Name Purpose Required Provided By
Red Hat OpenShift Enterprise 2.2 Application Node (for RHSM), or
Red Hat OpenShift Enterprise 2.2 Node (for RHN Classic).
Base channel for OpenShift Enterprise 2.2 node hosts. Yes. "OpenShift Enterprise" subscription.
Red Hat Software Collections 1. Provides access to the latest versions of programming languages, database servers, and related packages. Yes. "OpenShift Enterprise" subscription.
Red Hat OpenShift Enterprise 2.2 JBoss EAP add-on. Provides the JBoss EAP premium xPaaS cartridge. Only to support the JBoss EAP cartridge. "JBoss Enterprise Application Platform for OpenShift Enterprise" subscription.
JBoss Enterprise Application Platform. Provides JBoss EAP. Only to support the JBoss EAP cartridge. "JBoss Enterprise Application Platform for OpenShift Enterprise" subscription.
Red Hat OpenShift Enterprise 2.2 JBoss Fuse add-on. Provides the JBoss Fuse premium xPaaS cartridge (available starting in OpenShift Enterprise 2.1.7). Only to support the JBoss Fuse cartridge. "JBoss Fuse for xPaaS" subscription.
Red Hat OpenShift Enterprise 2.2 JBoss A-MQ add-on. Provides the JBoss A-MQ premium xPaaS cartridge (available starting in OpenShift Enterprise 2.1.7). Only to support the JBoss A-MQ cartridge. "JBoss A-MQ for xPaaS" subscription.
JBoss Enterprise Web Server 2. Provides Tomcat 6 and Tomcat 7. Only to support the JBoss EWS (Tomcat 6 and 7) standard cartridges. "OpenShift Enterprise" subscription.
Red Hat OpenShift Enterprise Client Tools 2.2. Provides access to the OpenShift Enterprise 2.2 client tools. Only if client tools are used on the node host. "OpenShift Enterprise" subscription.
You must register your node host using either the Red Hat Subscription Management (RHSM) or Red Hat Network (RHN) Classic subscription method to attach any of the above subscriptions and enable the proper channels. Instructions for both subscription methods are provided in Section 9.1.1, “Using Red Hat Subscription Management on Node Hosts” and Section 9.1.2, “Using Red Hat Network Classic on Node Hosts”. Choose one of these subscription methods and follow the relevant instructions before proceeding to Section 9.2, “Configuring Yum on Node Hosts”.

9.1.1. Using Red Hat Subscription Management on Node Hosts

You can use Red Hat Subscription Management (RHSM) as the subscription method for your node host, which allows the system to access the channels and packages required for installation. The following instructions describe the basic RHSM configuration steps to prepare an OpenShift Enterprise node host for installation. See the Red Hat Subscription Management documentation at https://access.redhat.com/documentation/en-US/Red_Hat_Subscription_Management if you require additional information on subscription management per your environment.

Procedure 9.1. To Configure Node Host Subscriptions Using Red Hat Subscription Management:

  1. Use the subscription-manager register command to register your Red Hat Enterprise Linux system.

    Example 9.1. Registering the System

    # subscription-manager register

Username:
Password:

The system has been registered with id: 3tghj35d1-7c19-4734-b638-f24tw8eh6246
  2. Use the subscription-manager list --available command and locate any desired OpenShift Enterprise subscription pool IDs in the output of available subscriptions on your account.

    Example 9.2. Finding Subscription Pool IDs

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

Subscription Name:      OpenShift Enterprise
SKU:                    MCT####
Pool Id:                Example_3cf49557013d418c52992690
Quantity:               1
Service Level:          Standard
Service Type:           L1-L3
Multi-Entitlement:      No
Ends:                   01/01/2020
System Type:            Physical
	
Subscription Name:      JBoss Enterprise Application Platform for OpenShift Enterprise
SKU:                    SYS####
Pool Id:                Example_3cf49557013d418c52182681
Quantity:               1
Service Level:          Premium
Service Type:           L1-L3
Multi-Entitlement:      No
Ends:                   01/01/2020
System Type:            Physical
    The "OpenShift Enterprise" subscription is the only subscription required for basic node operation. Additional subscriptions, detailed in Section 9.1, “Configuring Node Host Entitlements”, are optional and only required based on your planned usage of OpenShift Enterprise. For example, locate the pool ID for the "JBoss Enterprise Application Platform for OpenShift Enterprise" subscription if you plan to install the JBoss EAP premium xPaaS cartridge.
  3. Attach the desired subscription(s). Replace pool-id in the following command with your relevant Pool Id value(s) from the previous step: 
    # subscription-manager attach --pool pool-id --pool pool-id
  4. Enable the Red Hat OpenShift Enterprise 2.2 Application Node channel: 
    # subscription-manager repos --enable rhel-6-server-ose-2.2-node-rpms
  5. Verify that the yum repolist command lists the enabled channel(s).

    Example 9.3. Verifying the Enabled Node Channel

    # yum repolist

repo id                           repo name

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

9.1.2. Using Red Hat Network Classic on Node Hosts

You can use Red Hat Network (RHN) Classic as the subscription method for your node host, which allows the system to access the channels and packages required for installation. The following instructions describe the basic RHN Classic configuration steps to prepare an OpenShift Enterprise node host for installation.

Note

While 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 (RHSM) for new installations. For details on how to migrate from RHN Classic to RHSM, see the OpenShift Enterprise Administration Guide.

Procedure 9.2. To Configure Node Host Subscriptions Using Red Hat Network Classic:

  1. Use the rhnreg_ks command to register your Red Hat Enterprise Linux system. Replace username and password in the following command with your Red Hat Network account credentials: 
    # rhnreg_ks --username username --password password
  2. Enable the Red Hat OpenShift Enterprise 2.2 Node channel: 
    # rhn-channel -a -c rhel-x86_64-server-6-ose-2.2-node
  3. Verify that the yum repolist command lists the enabled channel(s).

    Example 9.4. Verifying the Enabled Node Channel

    # yum repolist

repo id                             repo name

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