Bug 1472096

Summary: [RFE] zone anti affinity for MongoDB replica sets
Product: Red Hat Software Collections Reporter: Jaspreet Kaur <jkaur>
Component: rh-mongodb34-containerAssignee: Patrik Novotný <panovotn>
Status: CLOSED WONTFIX QA Contact: Lukáš Zachar <lzachar>
Severity: medium Docs Contact: Lenka Špačková <lkuprova>
Priority: medium    
Version: rh-mongodb34CC: aos-bugs, bparees, hhorak, jokerman, mmccomas, simon.gunzenreiner, sreber
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-04 09:04:04 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 Jaspreet Kaur 2017-07-18 05:45:21 UTC 
1. Proposed title of this feature request

 zone anti affinity for MongoDB replica sets


3. What is the nature and description of the request?

This request is for extending the provided template to take this into account. 
 https://docs.openshift.com/container-platform/3.5/using_images/db_images/mongodb.html#creating-the-final-replication-set
mentions that (in tech preview) we can create a replica set.
It seems to us that this approach is ignoring an important aspect of reality


 4. Why does the customer need this? (List the business requirements here)

 In most multi data center environments, replica sets should be provisioned to a 2nd/3rd DC site / Availability Zone (to compensate for the loss of an AZ).
Comment 2 Ben Parees 2017-07-18 16:45:11 UTC 
Fixing this entails making a change to the mongo templates that reside here:
https://github.com/openshift/origin/tree/master/examples/db-templates