___
> From: Logan Barfield
> Sent: Wednesday, January 07, 2015 2:00 PM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: Multi-Datacenter Deployment
>
> A followup here: You can't have secondary storage that
another.
- Si
From: Logan Barfield
Sent: Wednesday, January 07, 2015 2:00 PM
To: [email protected]
Cc: [email protected]
Subject: Re: Multi-Datacenter Deployment
A followup here: You can't have secondary storage that spans regions (e.g,
te
Jan 7, 2015 at 12:57 PM, Simon Weller wrote:
> See inline.
>
> From: Logan Barfield
> Sent: Wednesday, January 07, 2015 11:43 AM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: Multi-Datacenter De
See inline.
From: Logan Barfield
Sent: Wednesday, January 07, 2015 11:43 AM
To: [email protected]
Cc: [email protected]
Subject: Re: Multi-Datacenter Deployment
I appreciate the explanation. That seems to confirm what I was thinking
n right now, short of
> setting up a completely separate CS instances per DC.
>
> Hope this helps a little.
>
> - Si
>
>
> From: Logan Barfield
> Sent: Tuesday, January 06, 2015 1:45 PM
> To: [email protected]; [email protected]
&g
udstack.apache.org; [email protected]
Subject: Multi-Datacenter Deployment
We are currently running a single location CloudStack deployment:
- 1 Hardware firewall
- 1 Mangement/Database Server
- 1 NFS staging store (for S3 secondary storage)
- Ceph RBD for primary storage
- 4 Hypervisors
Hi Logan,
The biggest issue to deal with in a multi-datacenter deployment is the
database, specifically latency between database nodes and between the
CloudStack management servers and the database. Hosts in remote zones quite
happily talk back to remote management servers over WAN links
We are currently running a single location CloudStack deployment:
- 1 Hardware firewall
- 1 Mangement/Database Server
- 1 NFS staging store (for S3 secondary storage)
- Ceph RBD for primary storage
- 4 Hypervisors
- 1 Zone/Pod/Cluster
We are looking to expand our deployment to other datacenters, a
