Description of problem:
For nodes classified between regions, there must be a limit to how far the regions can be. e.g. Can we have an OpenShift deployment that has nodes in Australia as well as US?
Also, can we have an HA broker setup such that one set of brokers run on one geo and set in a far-away geo? How far?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Need the numbers in terms of RTT latency.
e.g. OpenShift will not operate well if the broker instance and the mongodb instance are more than 300ms apart (round trip time).
e.g. OpenShift will not work reliably if the broker instance and a region of nodes are more than 400ms apart.
e.g. OpenShift broker and activemq instances cannot be more than 200ms apart.
I would start with a local two node + one broker setup. And put some network simulator to insert a fake latency.
If latency is introduced to all incoming traffic on the nodes (not the broker), then it is good enough to see where the product experience breaks down.
Regarding the network simulator, this is a good tool - http://www.linuxfoundation.org/collaborate/workgroups/networking/netem
It will be a qualitative measurement mostly - at what latency does one declare OpenShift is not good enough? Maybe a chart of latency number vs time it takes to create an app (or add-cart/scale-up etc), and customers can figure what is acceptable and what is not.
Closing this BZ.
The focus of the documentation team is going to shift from OpenShift v2 to v3, and only the remaining v2 doc BZs that feature actual errors in the docs will be worked on.
If there are any oppositions for any specific BZs, please contact me or the docs team.