Open Stack

I suggest building a new AZ (“region” in OpenStack parlance) in the new location. In general I would avoid setting up control plane to operate across multiple facilities unless the cloud is very large.

> On May 4, 2015, at 1:40 PM, Jonathan Proulx <jon at jonproulx.com> wrote:
> 
> Hi All,
> 
> We're about to expand our OpenStack Cloud to a second datacenter.
> Anyone one have opinions they'd like to share as to what I would and
> should be worrying about or how to structure this?  Should I be
> thinking cells or regions (or maybe both)?  Any obvious or not so
> obvious pitfalls I should try to avoid?
> 
> Current scale is about 75 hypervisors.  Running juno on Ubuntu 14.04
> using Ceph for volume storage, ephemeral block devices, and image
> storage (as well as object store).  Bulk data storage for most (but by
> no means all) of our workloads is at the current location (not that
> that matters I suppose).
> 
> Second location is about 150km away and we'll have 10G (at least)
> between sites. The expansion will be approximately the same size as
> the existing cloud maybe slightly larger and given site capacities the
> new location is also more likely to be where any future grown goes.
> 
> Thanks,
> -Jon
> 
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators