How do I install OpenShift Enterprise?
Environment
- OpenShift Enterprise (OSE)
- 1.x
- 2.0
- 2.1
Issue
- How do I subscribe to the proper OpenShift Enterprise channels/repositories?
- How do I install OpenShift Enterprise?
- What software channels/repositories should be enabled on broker and node?
- Getting issue when installing Openshift Enterprise with below error resulting in aborting installation:
+ echo 'OpenShift: Command failed: yum install mongodb-server mongodb'
OpenShift: Command failed: yum install mongodb-server mongodb
+ echo 'OpenShift: Please ensure relevant repos/subscriptions are configured.'
Resolution
- Ensure that proper repositories or channels are added on the hosts. OpenShift Enterprise can be deployed in various configurations using either of Red Hat's subscription models:
Red Hat Subscription Management [RHSM]
Red Hat Network Classic
-
As a convenience to assist during installation, Red Hat provides a bash script and a kickstart file that can be configured to help you register and install the components relevant to your deployment. See the Installation Guide for links to the latest scripts.
- In addition to the kickstart or bash script openshift also provide an install utility, documented in the Install Guide, that is the preferred way to install OpenShift Enterprise.
-
Red Hat also provides an OpenShift Enterprise reference architecture which shows how to deploy the product in a distributed fashion and details some recommended practices.
Root Cause
- For OpenShift Enterprise (OSE) deployments prior to version 1.2, the following repositories are needed on the OpenShift Enterprise broker hosts and node hosts in addition to the Red Hat Enterprise Linux base channel:
OSE 1.0/1.1 broker hosts
Red Hat OpenShift Enterprise Infrastructure
Red Hat OpenShift Enterprise Client Tools (optional)
OSE 1.0/1.1 node hosts
Red Hat OpenShift Enterprise Node
Red Hat OpenShift Enterprise Client Tools (optional)
- Starting with OpenShift Enterprise 1.2, the channel names include the version number as well:
OSE 1.2 broker hosts
Red Hat OpenShift Enterprise 1.2 Infrastructure
Red Hat OpenShift Enterprise 1.2 Client Tools (optional)
OSE 1.2 node hosts
Red Hat OpenShift Enterprise 1.2 Node
Red Hat OpenShift Enterprise 1.2 Client Tools (optional)
OSE 2.0 broker hosts :
Red Hat OpenShift Enterprise 2.0 Infrastructure
Red Hat OpenShift Enterprise 2.0 Client Tools
Red Hat Software Collections 1
OSE 2.0 node hosts :
Red Hat OpenShift Enterprise 2.0 Application Node (for RHSM), or
Red Hat OpenShift Enterprise 2.0 Node (for RHN Classic)
Red Hat Software Collections 1
Optionals :
Red Hat OpenShift Enterprise 2.0 JBoss EAP add-on
JBoss Enterprise Application Platform
JBoss Enterprise Web Server 2
Red Hat OpenShift Enterprise Client Tools 2.0
OSE 2.1 broker hosts :
Red Hat OpenShift Enterprise 2.1 Infrastructure
Red Hat OpenShift Enterprise 2.1 Client Tools
Red Hat Software Collections 1
OSE 2.1 node hosts :
Red Hat OpenShift Enterprise 2.1 Application Node (for RHSM), or
Red Hat OpenShift Enterprise 2.1 Node (for RHN Classic)
Red Hat Software Collections 1
Optionals :
Red Hat OpenShift Enterprise 2.1 JBoss EAP add-on
JBoss Enterprise Application Platform
JBoss Enterprise Web Server 2
OSE 2.2 broker hosts :
Red Hat OpenShift Enterprise 2.2 Infrastructure
Red Hat OpenShift Enterprise 2.2 Client Tools
Red Hat Software Collections 1
OSE 2.2 node hosts :
Red Hat OpenShift Enterprise 2.2 Application Node (for RHSM), or
Red Hat OpenShift Enterprise 2.2 Node (for RHN Classic)
Red Hat Software Collections 1
Optionals :
Red Hat OpenShift Enterprise 2.2 JBoss EAP add-on
JBoss Enterprise Application Platform
JBoss Enterprise Web Server 2
- For new deployments, it is recommended to install the latest available version. For a more comprehensive list of available channels, see the following sections of the OpenShift Enterprise Deployment Guide:
Diagnostic Steps
- Make sure the system is registered to either Red Hat Subscription Management(RHSM) or Red Hat Network Classic(RHN).
- ssh passwordless login from the broker hosts to the node hosts. Refer link
- Ruby must be installed on both broker and node before initiating the script.
yum install ruby
- Static ip's are preferred for the hosts.
- If Dynamic IP are used you must ensure that when the IP changes the host name entry for the Server also changed in DNS.
- Check with oo-admin-yum-validator tool to configure yum and prepare your host to install the broker components. This tool reports a set of problems, provides recommendations, and halts by default so that you can review each set of proposed changes. For more information refer link
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
