___
> From: Logan Barfield
> Sent: Wednesday, January 07, 2015 2:00 PM
> To: d...@cloudstack.apache.org
> Cc: users@cloudstack.apache.org
> 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: d...@cloudstack.apache.org
Cc: users@cloudstack.apache.org
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: d...@cloudstack.apache.org
> Cc: users@cloudstack.apache.org
> Subject: Re: Multi-Datacenter De
See inline.
From: Logan Barfield
Sent: Wednesday, January 07, 2015 11:43 AM
To: d...@cloudstack.apache.org
Cc: users@cloudstack.apache.org
Subject: Re: Multi-Datacenter Deployment
I appreciate the explanation. That seems to confirm what I was thinking
I appreciate the explanation. That seems to confirm what I was thinking,
that until regions are working 100% we'll just have to make sure the
DC-to-DC links are as stable/redundant as possible to prevent HA issues.
If we increase the HA delay it shouldn't be a major issue, and it will
still be bet
Logan,
We currently run CS in multiple geographically separate DCs, and may be able to
give you a little insight into things.
We run KVM in advanced networking mode, with CLVM clusters backed onto Dell
Compellent SANs. We currently have different DCs running different zones per
DC, in a single
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.
Cur
