On 02/07/2017 07:09 AM, Rui Chen wrote:
Actually, some users used postgresql in production deployment(8%), the following
photo extract from user survey report of April 2016.
Technically the 8% includes both production (4%) as well as dev/QA (3%), and
proof-of-concept (1%).
Chris
On Thu, Feb 2, 2017 at 4:42 PM, Sean Dague wrote:
> On 02/02/2017 10:33 AM, Mike Bayer wrote:
> >
> >
> > On 02/01/2017 10:22 AM, Monty Taylor wrote:
> >>
> >> I personally continue to be of the opinion that without an explicit
> >> vocal and well-staffed champion, supporting
On 02/02/2017 11:42 AM, Sean Dague wrote:
That's all fine and good, we just need to rewrite about 100,000 unit
tests to do that. I'm totally cool with someone taking that task on, but
making a decision about postgresql shouldn't be filibustered on
rewriting all the unit tests in OpenStack
On 02/02/2017 11:48 AM, Julien Danjou wrote:
> On Wed, Feb 01 2017, Julien Danjou wrote:
>
>> My questions are simple and can be organized in a tree:
>>
>>Does Nova want to support PostgreSQL?
>> / \
>>Yes No
On Wed, Feb 01 2017, Julien Danjou wrote:
> My questions are simple and can be organized in a tree:
>
>Does Nova want to support PostgreSQL?
> / \
>Yes No
>/ \
>Why
On 02/02/2017 10:33 AM, Mike Bayer wrote:
>
>
> On 02/01/2017 10:22 AM, Monty Taylor wrote:
>>
>> I personally continue to be of the opinion that without an explicit
>> vocal and well-staffed champion, supporting postgres is more trouble
>> than it is worth. The vast majority of OpenStack
On 02/02/2017 10:59 AM, Monty Taylor wrote:
On 02/02/2017 09:33 AM, Mike Bayer wrote:
On 02/01/2017 10:22 AM, Monty Taylor wrote:
I personally continue to be of the opinion that without an explicit
vocal and well-staffed champion, supporting postgres is more trouble
than it is worth. The
On 02/02/2017 09:33 AM, Mike Bayer wrote:
>
>
> On 02/01/2017 10:22 AM, Monty Taylor wrote:
>>
>> I personally continue to be of the opinion that without an explicit
>> vocal and well-staffed champion, supporting postgres is more trouble
>> than it is worth. The vast majority of OpenStack
On Thu, Feb 2, 2017 at 10:33 AM, Mike Bayer wrote:
>
>
> well, let me blow your mind and agree, but noting that this means, *we
> drop SQLite also*. IMO every openstack developer should have
> MySQL/MariaDB running on their machine and that is part of what runs if you
>
On 02/01/2017 10:22 AM, Monty Taylor wrote:
I personally continue to be of the opinion that without an explicit
vocal and well-staffed champion, supporting postgres is more trouble
than it is worth. The vast majority of OpenStack deployments are on
MySQL - and what's more, the code is written
On 02/01/2017 12:24 PM, gordon chung wrote:
>
>
> On 01/02/17 12:15 PM, Sean Dague wrote:
>> What were you thinking about the messaging? TC resolution for
>> deprecation of postgresql as a first class backend?
>>
>> If setup tools want to support things, that's fine, just they do need to
>>
On 01/02/17 12:15 PM, Sean Dague wrote:
> What were you thinking about the messaging? TC resolution for
> deprecation of postgresql as a first class backend?
>
> If setup tools want to support things, that's fine, just they do need to
> realize they are owning that support its not coming from
On 02/01/2017 12:21 PM, Julien Danjou wrote:
> On Wed, Feb 01 2017, Sean Dague wrote:
>
>> If setup tools want to support things, that's fine, just they do need to
>> realize they are owning that support its not coming from upstream.
>
> The problem as I see it right now is that upstream is
On Wed, Feb 01 2017, Sean Dague wrote:
> If setup tools want to support things, that's fine, just they do need to
> realize they are owning that support its not coming from upstream.
The problem as I see it right now is that upstream is schizophrenic: it
seems it does not want to support nor
On 02/01/2017 12:12 PM, gordon chung wrote:
>
>
> On 01/02/17 11:42 AM, Monty Taylor wrote:
>> As I mentioned before, I don't think it matters which of the two we pick
>> - although I know _way_ more about MySQL personally and it has a much
>> more proven track record at absurdly large scale - I
On 01/02/17 11:42 AM, Monty Taylor wrote:
> As I mentioned before, I don't think it matters which of the two we pick
> - although I know _way_ more about MySQL personally and it has a much
> more proven track record at absurdly large scale - I just argue that we
> should pick one and then
On 02/01/2017 10:06 AM, gordon chung wrote:
>
>
> On 01/02/17 10:22 AM, Monty Taylor wrote:
>>
>> I personally continue to be of the opinion that without an explicit
>> vocal and well-staffed champion, supporting postgres is more trouble
>> than it is worth. The vast majority of OpenStack
On 01/02/17 10:22 AM, Monty Taylor wrote:
>
> I personally continue to be of the opinion that without an explicit
> vocal and well-staffed champion, supporting postgres is more trouble
> than it is worth. The vast majority of OpenStack deployments are on
> MySQL - and what's more, the code is
On 02/01/2017 09:18 AM, Sean Dague wrote:
On 02/01/2017 10:12 AM, Matt Riedemann wrote:
On 2/1/2017 8:07 AM, Julien Danjou wrote:
It's not just Nova, it's the entire set of integrated-gate jobs which
dropped the postgresql job. There is a bit more history there, it's in
the ML somewhere, but
On 02/01/2017 09:12 AM, Matt Riedemann wrote:
> On 2/1/2017 8:07 AM, Julien Danjou wrote:
>> Hi there,
>>
>> So the Ceilometer gate has been broken again by Nova today because of a
>> SQL bug in the placement API with PostgreSQL. This is the second time
>> that something like that happened: last
On 02/01/2017 10:12 AM, Matt Riedemann wrote:
> On 2/1/2017 8:07 AM, Julien Danjou wrote:
> It's not just Nova, it's the entire set of integrated-gate jobs which
> dropped the postgresql job. There is a bit more history there, it's in
> the ML somewhere, but it's not just like Nova decided to stop
On 2/1/2017 8:07 AM, Julien Danjou wrote:
Hi there,
So the Ceilometer gate has been broken again by Nova today because of a
SQL bug in the placement API with PostgreSQL. This is the second time
that something like that happened: last November¹, we also reported a
bug in Nova wrt PostgreSQL.
Hi there,
So the Ceilometer gate has been broken again by Nova today because of a
SQL bug in the placement API with PostgreSQL. This is the second time
that something like that happened: last November¹, we also reported a
bug in Nova wrt PostgreSQL.
Fortunately, Mehdi investigated and sent a
23 matches
Mail list logo