Este conteúdo não está disponível no idioma selecionado.
6.3. Configuring a Complete Environment
The following is an example configuration for a complete OpenShift Enterprise deployment consisting of:
- One host with the
nameserverrole. - Two hosts with the
brokerrole. - Two hosts with the
msgserverrole. - Three hosts with the
datastorerole. - Multiple hosts with the
noderole.
This example uses a common set of variables to ensure that parameters between different roles match up properly. This example is also appropriate for deploying on Infrastructure-as-a-Service (IaaS) environments where public and private routing is in use; applications are made available via their public IP addresses by making use of the
ec2_public_ipv4 fact.
Recommended Order of Deployment:
- Name server host.
- Message server hosts.
- Datastore hosts, ensuring the primary host is fully deployed before adding additional nodes to your replica set.
- Broker hosts.
- Node hosts.
Common Variables for This Example
Example 6.10. Name Server Configuration
Example 6.11. Message Server Configuration (ActiveMQ)
Example 6.12. Datastore Configuration
This assumes that you are naming your primary
datastore node ose-mongo01.example.com.
Example 6.13. Node Configuration
You must have one set of configuration options per district. This registers the
node_ip_address using the public IP address so that all applications on these gears are publicly accessible.
Example 6.14. Broker Configuration