The Trove weekly meeting time has been changed from 1800UTC on Wednesdays to
1500UTC on Wednesdays[1]. Thanks to Trevor for following up on this action
item from the discussions we had in the summit in Boston.
This change has been made to accommodate some new participants to the
community from
Hi all!
As the discussion around PostgreSQL has progressed, it has come clear to
me that there is a decently deep philosophical question on which we do
not currently share either definition or agreement. I believe that the
lack of clarity on this point is one of the things that makes the
On 05/19/2017 05:10 PM, Matt Riedemann wrote:
On 5/19/2017 3:35 PM, Monty Taylor wrote:
Heck - while I'm on floating ips ... if you have some pre-existing
floating ips and you want to boot servers on them and you want to do
that in parallel, you can't. You can boot a server with a floating ip
On Fri, May 19, 2017 at 02:04:05PM -0400, Sean Dague wrote:
You end up replicating the Ceilometer issue where there was a break down
in getting needs expressed / implemented, and the result was a service
doing heavy polling of other APIs (because that's the only way it could
get the data it
On 05/18/2017 02:49 PM, Sean Dague wrote:
On 05/18/2017 01:02 PM, Mike Bayer wrote:
On 05/17/2017 02:38 PM, Sean Dague wrote:
Some of the concerns/feedback has been "please describe things that are
harder by this being an abstraction", so examples are provided.
so let's go through this
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
On 05/20/2017 12:04 PM, Julien Danjou wrote:
On Fri, May 19 2017, Mike Bayer wrote:
IMO that's a bug for them.
Of course it's a bug. IIRC Mehdi tried to fix it without much success.
I'm inspired to see that Keystone, Nova etc. are
able to move between and eventlet backend and a mod_wsgi
On 05/21/2017 03:51 PM, Monty Taylor wrote:
So I don't see the problem of "consistent utf8 support" having much to
do with whether or not we support Posgtresql - you of course need your
"CREATE DATABASE" to include the utf8 charset like we do on MySQL, but
that's it.
That's where we stand
On 05/21/2017 03:38 PM, Monty Taylor wrote:
documentation on the sequence of steps the operator should take.
In the "active" approach, we still document expectations, but we also
validate them. If they are not what we expect but can be changed at
runtime, we change them overriding
