[openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

Rui Chen chenrui.momo at gmail.com
Tue Feb 7 13:09:10 UTC 2017

Actually, some users used postgresql in production deployment(8%), the
following photo extract from user survey report of April 2016.
And our (Huawei) customers had deployed postgresql AFAIK, so I hope we can
support both mysql and postgresql,
let users free to choose anyone.

[image: 内嵌图片 1]

2017-02-03 20:05 GMT+08:00 Matthew Booth <mbooth at redhat.com>:

> On Thu, Feb 2, 2017 at 4:42 PM, Sean Dague <sean at dague.net> 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 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 with MySQL in mind.
>> >> Postgres and MySQL have different trade offs, different things each are
>> >> good at and different places in which each has weakness. By attempting
>> >> to support Postgres AND MySQL, we prevent ourselves from focusing
>> >> adequate attention on making sure that our support for one of them is
>> >> top-notch and in keeping with best practices for that database.
>> >>
>> >> So let me state my opinion slightly differently. I think we should
>> >> support one and only one RDBMS backend for OpenStack, and we should
>> open
>> >> ourselves up to use advanced techniques for that backend. I don't
>> >> actually care whether that DB is MySQL or Postgres - but the corpus of
>> >> existing deployments on MySQL and the existing gate jobs I think make
>> >> the choice one way or the other simple.
>> >
>> >
>> > 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 expect to run database-related unit tests.   Targeting just one
>> > database is very handy but if you really want to use the features
>> > without roadblocks, you need to go all the way.
>> 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 because of the ways we use
>> sqlite.
> I wrote a patch series to optionally run all our unit tests using MySQL
> instead of sqlite a couple of years ago, and it wasn't that hard at the
> time. The biggest issue I recall was fixing up tests which assumed
> sub-second timestamp granularity which MySQL did not support at the time
> (but may now).
> IIRC the series died because we killed the fixture I was using in oslo.db
> without replacement before my series finished landing. Fundamentally wasn't
> that hard, though.
> Matt
> --
> Matthew Booth
> Red Hat Engineering, Virtualisation Team
> Phone: +442070094448 <+44%2020%207009%204448> (UK)
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170207/79ba8cf2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 107103 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170207/79ba8cf2/attachment.png>

More information about the OpenStack-dev mailing list