このコンテンツは選択した言語では利用できません。

6.2. Using the Installation Scripts


You can deploy OpenShift Enterprise using the installation scripts, which include configurable parameters to help automate the installation of OpenShift Enterprise components on a Red Hat Enterprise Linux 6.6 system. By supplying the scripts with parameters relevant to your deployment requirements, you can get an environment running quickly without having to manually configure all of the required services.
For kickstarts, the openshift.ks kickstart script is available at:

Example 6.1. Downloading the openshift.ks Kickstart Script

$ curl -O https://raw.githubusercontent.com/openshift/openshift-extras/enterprise-2.2/enterprise/install-scripts/openshift.ks
Copy to Clipboard Toggle word wrap
For pre-installed Red Hat Enterprise Linux 6.6 systems, the openshift.sh bash script is the extracted %post section of the openshift.ks script and is available at:

Example 6.2. Downloading the openshift.sh Bash Script

$ curl -O https://raw.githubusercontent.com/openshift/openshift-extras/enterprise-2.2/enterprise/install-scripts/generic/openshift.sh
Copy to Clipboard Toggle word wrap
The actions and parameters related to the installation and configuration of OpenShift Enterprise are the same between the two scripts. The commented notes in the header of the scripts provide extensive information on their usage and parameters.

Important

The sample deployment steps detailed later in this guide describe the various actions of the installation scripts. However, these deployment methods are independent of each other; this means that you can install and configure a complete broker or node host by either following the steps manually, or by running the scripts. The corresponding functions of the scripts are identified in the respective sample deployment steps.
Supplying Parameters to the Scripts

When using the openshift.ks script, you can supply parameters as kernel parameters during the kickstart process. When using the openshift.sh script, you can similarly supply parameters as command-line arguments. See the commented notes in the header of the scripts for alternative methods of supplying parameters using the openshift.sh script.

The installation scripts are highly customizable, and as such can be used for a variety of deployment scenarios using many different configurations. The following sections highlight some important parameters, show basic script usage, and provide examples on installing and configuring sample hosts for a simple deployment.

Note

For the purposes of this guide, the following examples use the openshift.sh script by supplying parameters as command-line arguments. The same parameters can be supplied as kernel parameters for kickstarts using the openshift.ks script.

6.2.1. Selecting Components to Install

If you do not supply any parameters, the scripts install all OpenShift Enterprise components on a single host with the default configuration. Using the install_components parameter, the scripts can be configured to install one or more of the following components on a single host:
Expand
Table 6.1. Options for the install_components Parameter
Options Description
broker Installs the broker application and tools.
named Supporting service. Installs a BIND DNS server.
activemq Supporting service. Installs the messaging bus.
datastore Supporting service. Installs the MongoDB datastore.
node Installs node functionality, including cartridges.

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.
You can install any combination of components on a host, as long as broker and node components are installed on separate hosts. Any component can also be installed as a standalone host.
For example, the following command runs the openshift.sh script and installs the broker, named, activemq, and datastore components on a single host, using default values for all unspecified parameters:

Example 6.3. Installing the broker, named, activemq, and datastore Components Using openshift.sh

$ sudo sh openshift.sh install_components=broker,named,activemq,datastoresudo sh openshift.sh install_components=broker,named,activemq,datastoresudo sh openshift.sh install_components=broker,named,activemq,datastore
Copy to Clipboard Toggle word wrap
For another example, the following command runs the openshift.sh script and installs only the node component on a single host, using default values for all unspecified parameters:

Example 6.4. Installing the node Component Using openshift.sh

$ sudo sh openshift.sh install_components=nodesudo sh openshift.sh install_components=nodesudo sh openshift.sh install_components=node
Copy to Clipboard Toggle word wrap
トップに戻る
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2025 Red Hat