Open Stack

We do it with some of our databases (horizon, designate, and keystone) and
we run a arbitrator process (garbd) in a 3rd DC. We have lots of low
latency bandwidth which you have to be careful with. My recommendation
would be that you need to know your network well and have good monitoring
in place.

On Tue, May 5, 2015 at 9:33 AM, Curtis <serverascode at gmail.com> wrote:

> Do people have any comments or strategies on dealing with Galera
> replication across the WAN using regions? Seems like something to try
> to avoid if possible, though might not be possible. Any thoughts on
> that?
>
> Thanks,
> Curtis.
>
> On Mon, May 4, 2015 at 3:11 PM, Jesse Keating <jlk at bluebox.net> wrote:
> > I agree with Subbu. You'll want that to be a region so that the control
> > plane is mostly contained. Only Keystone (and swift if you have that)
> would
> > be doing lots of site to site communication to keep databases in sync.
> >
> > http://docs.openstack.org/arch-design/content/multi_site.html is a good
> read
> > on the topic.
> >
> >
> > - jlk
> >
> > On Mon, May 4, 2015 at 1:58 PM, Allamaraju, Subbu <subbu at subbu.org>
> wrote:
> >>
> >> 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
> >>
> >>
> >> _______________________________________________
> >> OpenStack-operators mailing list
> >> OpenStack-operators at lists.openstack.org
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
> >
> >
> > _______________________________________________
> > OpenStack-operators mailing list
> > OpenStack-operators at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >
>
>
>
> --
> Twitter: @serverascode
> Blog: serverascode.com
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150505/307c80d7/attachment.html>