- Mail original -
> De: "Thierry Carrez"
> À: openstack-dev@lists.openstack.org
> Envoyé: Lundi 22 Mai 2017 11:02:21
> Objet: Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master
>
> Mike Bayer wrote:
> > On 05/18/2017 06:13 PM,
On Thu, Jun 1, 2017 at 3:46 PM, Andrey Grebennikov <
agrebenni...@mirantis.com> wrote:
> We had a very similar conversation multiple times with Keystone cores
> (multi-site Keystone).
>
Geo-rep Galera was suggested first and it was immediately declined (one of
> the reasons was the case of complet
We had a very similar conversation multiple times with Keystone cores
(multi-site Keystone).
Geo-rep Galera was suggested first and it was immediately declined (one of
the reasons was the case of complete corruption of Keystone DB everywhere
in case of accidental table corrupt in one site) by me as
On 05/31/2017 11:06 PM, Mike Bayer wrote:
I'd also throw in, there's lots of versions of Galera with different
bugfixes / improvements as we go along, not to mention configuration
settings if Jay observes it working great on a distributed cluster
and Clint observes it working terribly, it c
On 05/30/2017 09:06 PM, Jay Pipes wrote:
On 05/30/2017 05:07 PM, Clint Byrum wrote:
Excerpts from Jay Pipes's message of 2017-05-30 14:52:01 -0400:
Sorry for the delay in getting back on this... comments inline.
On 05/18/2017 06:13 PM, Adrian Turjak wrote:
Hello fellow OpenStackers,
For th
> -Original Message-
> From: Jay Pipes [mailto:jaypi...@gmail.com]
> Sent: Wednesday, May 31, 2017 12:00 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Multi-master
>
> On 05/31/2017 02:14 AM, Clint By
On 05/31/2017 02:14 AM, Clint Byrum wrote:
Either way, it should be much simpler to manage slave lag than to deal
with a Galera cluster that won't accept any writes at all because it
can't get quorum.
Would CockroachDB be any better at achieving quorum?
Genuinely curious. :)
Best,
-jay
___
Excerpts from Jay Pipes's message of 2017-05-30 21:06:59 -0400:
> On 05/30/2017 05:07 PM, Clint Byrum wrote:
> > Excerpts from Jay Pipes's message of 2017-05-30 14:52:01 -0400:
> >> Sorry for the delay in getting back on this... comments inline.
> >>
> >> On 05/18/2017 06:13 PM, Adrian Turjak wrote
On 05/30/2017 05:07 PM, Clint Byrum wrote:
Excerpts from Jay Pipes's message of 2017-05-30 14:52:01 -0400:
Sorry for the delay in getting back on this... comments inline.
On 05/18/2017 06:13 PM, Adrian Turjak wrote:
Hello fellow OpenStackers,
For the last while I've been looking at options fo
Excerpts from Jay Pipes's message of 2017-05-30 14:52:01 -0400:
> Sorry for the delay in getting back on this... comments inline.
>
> On 05/18/2017 06:13 PM, Adrian Turjak wrote:
> > Hello fellow OpenStackers,
> >
> > For the last while I've been looking at options for multi-region
> > multi-mast
Sorry for the delay in getting back on this... comments inline.
On 05/18/2017 06:13 PM, Adrian Turjak wrote:
Hello fellow OpenStackers,
For the last while I've been looking at options for multi-region
multi-master Keystone, as well as multi-master for other services I've
been developing and one
On 05/22/2017 05:02 AM, Thierry Carrez wrote:
Mike Bayer wrote:
On 05/18/2017 06:13 PM, Adrian Turjak wrote:
So, specifically in the realm of Keystone, since we are using sqlalchemy
we already have Postgresql support, and since Cockroachdb does talk
Postgres it shouldn't be too hard to back
Mike Bayer wrote:
> On 05/18/2017 06:13 PM, Adrian Turjak wrote:
>>
>> So, specifically in the realm of Keystone, since we are using sqlalchemy
>> we already have Postgresql support, and since Cockroachdb does talk
>> Postgres it shouldn't be too hard to back Keystone with it. At that
>> stage you
On 20/05/17 09:31, Mike Bayer wrote:
>
> On 05/18/2017 06:13 PM, Adrian Turjak wrote:
>>
>> So, specifically in the realm of Keystone, since we are using sqlalchemy
>> we already have Postgresql support, and since Cockroachdb does talk
>> Postgres it shouldn't be too hard to back Keystone with it.
- Mail original -
> De: "Curtis"
> À: "OpenStack Development Mailing List (not for usage questions)"
>
> Cc: openst...@lists.openstack.org
> Envoyé: Vendredi 19 Mai 2017 01:43:39
> Objet: Re: [openstack-dev] [Keystone] Cockroachdb for Keystone Mul
On 05/18/2017 06:13 PM, Adrian Turjak wrote:
So, specifically in the realm of Keystone, since we are using sqlalchemy
we already have Postgresql support, and since Cockroachdb does talk
Postgres it shouldn't be too hard to back Keystone with it. At that
stage you have a Keystone DB that could
On Thu, May 18, 2017 at 6:43 PM, Curtis wrote:
> On Thu, May 18, 2017 at 4:13 PM, Adrian Turjak
> wrote:
> > Hello fellow OpenStackers,
> >
> > For the last while I've been looking at options for multi-region
> > multi-master Keystone, as well as multi-master for other services I've
> > been dev
On Fri, 19 May 2017, Adrian Turjak wrote:
On 19 May 2017 11:43 am, Curtis wrote:
I had thought that the OpenStack community was deprecating Postgres
support though, so that could make things a bit harder here (I might
be wrong about this).
I really hope not, because that will
On 19 May 2017 11:43 am, Curtis wrote:On Thu, May 18, 2017 at 4:13 PM, Adrian Turjak wrote:
> Hello fellow OpenStackers,
>
> For the last while I've been looking at options for multi-region
> multi-master Keystone, as well as multi-master for other services I've
> been developing and one thing th
On Thu, May 18, 2017 at 4:13 PM, Adrian Turjak wrote:
> Hello fellow OpenStackers,
>
> For the last while I've been looking at options for multi-region
> multi-master Keystone, as well as multi-master for other services I've
> been developing and one thing that always came up was there aren't many
Hello fellow OpenStackers,
For the last while I've been looking at options for multi-region
multi-master Keystone, as well as multi-master for other services I've
been developing and one thing that always came up was there aren't many
truly good options for a true multi-master backend. Recently I'
21 matches
Mail list logo