GitHub user justinestruch created a discussion: Additional Zone vs Region - US East and West
Hi All. I have a question on architecture for our Cloudstack setup. Currently we are setup in a datacenter on the US East Coast in NYC. We are starting to setup a new environment on the US West Coast in LA. There is about 70 ms of latency between US East and West. My goal is to be able to manage the entire cloud from one Management Console GUI. I'm trying to avoid having separate consoles for US East and US West but I am worried about the latency slowing things down between the 2 DCs. <img width="1508" height="746" alt="regions" src="https://github.com/user-attachments/assets/3f70cefc-3831-474f-89ae-97ae1c0a8af8"; /> Which option from below would you recommend or think is best practice for us? 1. Deploy a new management server and Region. I think when doing this, cloudstack can see all resources in both regions? As described here https://docs.cloudstack.apache.org/en/4.22.0.0/installguide/configuration.html#adding-regions-optional 2. Deploy a new Zone and deploy a secondary management server in that new zone. This will give us redundancy if the primary mgmt server goes down as described here https://docs.cloudstack.apache.org/en/4.22.0.0/conceptsandterminology/choosing_deployment_architecture.html#multi-site-deployment 3. Just deploy a new zone. Don't deploy a secondary management server. 4. Other better option? GitHub link: https://github.com/apache/cloudstack/discussions/12115 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
