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 just argue that we
>> should pick one and then actually design our database interactions based
>> on how that one works.
>>
>> I don't actually expect us to decide to do that, of course. Why would we
>> ever say no to more places for people to express their desire for
>> difference? But I strongly believe it would be in the best interests of
>> OpenStack if we did.
>
> all for a slimmer openstack.
>
> so Julien's initial query regarding postgresql. if we only do test one
> and only one, i don't think it's safe to say we support anything other
> than that and we should probably be more consistent with this messaging?
> right now postgresql is not just gated on in places, but can just as
> easily be configured in dev environments, and is mentioned as supported
> in our docs[1]. we'd probably have consider all the existing deployments
> that leverage postgresql and what response to give them on either
> migrating or some other alternative.
>
> [1]
> http://docs.openstack.org/newton/install-guide-rdo/environment-sql-database.html
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 upstream.
-Sean
--
Sean Dague
http://dague.net
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
