GitHub user NuxRo added a comment to the discussion: Additional Zone vs Region - US East and West
Regions are a bit useless and I would ignore the concept. There is nothing shared between them. Depending on your requirements either could work: 1 - deploy a new zone under existing CloudStack; also deploy a new mgmt server and a DB slave, but keep the mgmt server stopped - the latency is too high between the 2 sites to make this work without problems. In the event of DR you can start the management server and have it talk to the local DB slave (which you will turn into a master) so you can manage the local zone. 2 - even "simpler", just deploy a new CloudStack, completely independent. This will make things a little bit complicated if you want to have the same users, offerings, templates etc, you'll need to think of a way to sync these between the two. SAML or LDAP could be employed here for the users part. The upside here is that an outage in one will not affect you in any way in the other, hence more robustness. My 2 cents. GitHub link: https://github.com/apache/cloudstack/discussions/12115#discussioncomment-15061053 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
