will probably be much easier to go from no cells
to cells v2 than cells v1 to v2.
Mike
From: Joseph Bajin
Date: Wednesday, May 6, 2015 at 8:06 AM
Cc: OpenStack Operators
Subject: Re: [Openstack-operators] expanding to 2nd location
Just to add in my $0.02, we run in multiple sites as well. We
Just to add in my $0.02, we run in multiple sites as well. We are using
regions to do this. Cells at this point have a lot going for it, but we
thought it wasn't there yet. We also don't have the necessary resources to
make our own changes to it like a few other places do.
With that, we said th
On Tue, May 5, 2015 at 11:33 AM, Curtis 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?
>
We're doing this with good luc
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.
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 wrote:
> I agree with Sub
On Mon, May 4, 2015 at 9:42 PM, Tom Fifield wrote:
> Do you need users to be able to see it as one cloud, with a single API
> endpoint?
Define need :)
As many of you know my cloud is a University system and researchers
are nothing if not lazy, in the best possible sense of course :) So
having
Second installation, IMHO. Everything else would make it less robust.
On 05/04/2015 11:40 PM, Jonathan Proulx 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
CERN runs two data centres in Geneva (3.5MW) and Budapest (2.7MW), around
1,200 KMs . We have two 100Gb/s links between the two sites and latency of
around 22ms.
We run this as a single cloud with 13 cells. Each cell is only in one data
centre.
We wanted a single API endpoint from the user pers
On 05/05/15 04:40, Jonathan Proulx 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)? A
Hi Jon,
We're about to expand our OpenStack Cloud to a second datacenter.
>
Congratulations! :)
> Anyone one have opinions they'd like to share as to what I would and
> should be worrying about or how to structure this?
What services will be shared between the two locations? Keystone with db
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
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 wrote:
>
> Hi All,
>
> We're about to expand
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
13 matches
Mail list logo
