Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1042887

Summary: 5.8.4. Configuring Redundancy
Product: OpenShift Container Platform Reporter: Luke Meyer <lmeyer>
Component: DocumentationAssignee: Bilhar <baulakh>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: low Docs Contact:
Priority: unspecified    
Version: 2.0.0CC: adellape, alyoung, jokerman, libra-onpremise-devel, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-09 01:04:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Luke Meyer 2013-12-13 14:56:51 UTC 
https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#sect-Configuring_Redundancy
5.8.4. Configuring Redundancy
---
Alternatively, consider the following options to configure redundancy:
[...]
Install broker on its own host, and combine broker, ActiveMQ, MongoDB, and name server on a single host
==> This doesn't really make sense. Not quite sure what it was meant to be. I suggest the following replacement:
Here are some redundant topologies to consider:
[...]
Install broker and MongoDB together on multiple hosts and ActiveMQ separately on multiple hosts.
===