6.3. Using the Sample Deployment Steps

The installation scripts provided in Section 6.2, “Using the Installation Scripts” are also detailed as manual, sample deployment steps for hosts identified in this guide as the following:
Host 1
The broker host detailed in Chapter 7, Manually Installing and Configuring a Broker Host.
Host 2
The node host detailed in Chapter 9, Manually Installing and Configuring Node Hosts.
The sample deployment steps are useful for understanding the various actions of the installation scripts, which enables administrators to further customize their deployments to their specifications.
Packages that are installed from third-party repositories and products such as EPEL or Puppet can adversely affect OpenShift Enterprise installations. This can result in issues that require additional time to troubleshoot. Therefore, Red Hat recommends that you only use packages from Red Hat Enterprise Linux Server 6 to install the base operating system and additional repositories when preparing OpenShift Enterprise hosts, and disable any third-party yum repositories during installation, including the unsupported Red Hat Enterprise Linux Server Optional channel. Proper yum configurations for OpenShift Enterprise installations are covered in Section 7.2, “Configuring Yum on Broker Hosts” and Section 9.2, “Configuring Yum on Node Hosts”.
The sample deployment steps assume that Host 1 and Host 2 are configured with a Red Hat Enterprise Linux Server entitlement and have Red Hat Enterprise Linux Server 6.6 or later installed with all base packages fully updated. Most importantly, you must have the latest version of the selinux-policy package installed on each host, as it is necessary for the correct operation of OpenShift Enterprise. Use the yum update command to update all packages before installing OpenShift Enterprise.

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.

6.3.1. Service Parameters

In the sample deployment steps, the broker host (Host 1) and node host (Host 2) are configured with the following parameters:
Service domain example.com
Broker IP address DHCP
Broker host name broker.example.com
Node 0 IP address DHCP
Node 0 host name node.example.com
Datastore service MongoDB
Authentication service Basic Authentication using httpd mod_auth_basic
DNS service BIND, configured as follows:
  • IP address: dynamic
  • Zone: example.com (same as Service Domain)
  • Domain suffix: example.com (same as Service Domain)
Messaging service MCollective using ActiveMQ
All of these parameters are customizable to suit your requirements. As detailed in the instructions, the domain and host names can be modified by editing the appropriate configuration files. The messaging, authentication, and DNS services are each implemented as plug-ins to the broker.

Important

DHCP is supported, and use thereof is assumed in this guide. However, dynamic reassignment of IP addresses is not supported and can cause problems.