Managing mongoDB containers having multiple DNS names through automation agent
We got mongoDB running on openshift pods across 2 separate openshift clusters and it runs perfectly fine but we are now facing issue with doing mongoDB restore, and that has led to us now wanting to use automation agent to control the mongod process on the containers.
The major challenge we are facing is that we run into issues when automation agent runs rs.initiate() and as part of the process tries to gather the hostname of the pod by running hostname -f command. The trouble is we have to deal with separate openshift clusters and have got mongod replica set members split across separate openshift clusters so we use a global DNS name so that the hostnames are resolved at the DNS level and allows for communication to flow through across seperate openshift clusters.
We want to have a feature which would allow us to choose what hostnames the automation agent should use in order to create the replica set. We also feel, this would be a huge asset for anyone trying to control the mongod containers from the ops manager and would give mongoDB an edge when it comes to running databases on containers.
We are also happy to provide any assistance in this regard and want this feature to be considered on a high priority as it is a BLOCKER for us.