Este conteúdo não está disponível no idioma selecionado.
Chapter 3. Introduction to OpenShift Enterprise Puppet Deployments
Starting with OpenShift Enterprise 2.2, you can deploy a complete, production-capable OpenShift Enterprise environment using a supported Puppet module. While it can be used with or without a Puppet master, this guide covers the use of the module without a Puppet master by applying standalone Puppet manifests locally.
To deploy OpenShift Enterprise using Puppet, you must use the OpenShift Origin Puppet module. The OpenShift Origin Puppet module version 4.1.0 and later is capable of managing both OpenShift Origin and OpenShift Enterprise 2.2 or later. Versions of the Puppet module prior to 4.1.0 have not been tested for use with OpenShift Enterprise.
OpenShift Enterprise support with the Puppet module is enabled by setting the
ose_version
parameter in a host's Puppet manifest to the OpenShift Enterprise release version. For example, the line in the manifest would be:
ose_version => '2.2',
ose_version => '2.2',
You can use the Puppet module to choose from the following roles to be configured on a host:
-
broker
- Installs the broker and Management Console applications.
-
node
- Installs the node component and cartridges.
-
msgserver
- Installs an ActiveMQ message broker.
-
datastore
- Installs MongoDB (not sharded/replicated).
-
nameserver
- Installs a BIND DNS server configured with a TSIG key for dynamic updates.
Note
For more comprehensive information about the architecture of OpenShift Enterprise, including details about each of the above components, see the OpenShift Enterprise Deployment Guide [4].
The following features provided by the OpenShift Origin Puppet module are not supported when using OpenShift Enterprise:
- Collocation of
broker
andnode
roles. - Using
keepalived
and HAProxy for broker high availability (HA) load balancing. - Avahi and Route53 DNS plug-ins.
10gen-mms-agent
,jbossas
, andphpmyadmin
cartridges (not distributed with OpenShift Enterprise).