Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

For people who have been following this topic, a reminder that later today there will be a TC meeting dedicated to discussing this issues captured by this thread[1], the related thread on active or passive database approaches[2] and the two reviews about "what to do about postgreSQL" [3][4]. It

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

Thanks. It’s more of a question of not leaving people high and dry when they have made a reasonable choice in the past based on the choices supported at the time. Tim On 23.05.17, 21:14, "Sean Dague" wrote: On 05/23/2017 02:35 PM, Tim Bell wrote: > Is there a proposal

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

On 05/23/2017 02:35 PM, Tim Bell wrote: > Is there a proposal where deployments who chose Postgres on good faith can > find migration path to a MySQL based solution? Yes, a migration tool exploration is action #2 in the current proposal. Also, to be clear, we're not at the stage of removing

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

Is there a proposal where deployments who chose Postgres on good faith can find migration path to a MySQL based solution? Tim On 23.05.17, 18:35, "Octave J. Orgeron" wrote: As OpenStack has evolved and grown, we are ending up with more and more MySQL-isms

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

As OpenStack has evolved and grown, we are ending up with more and more MySQL-isms in the code. I'd love to see OpenStack support every database out there, but that is becoming more and more difficult. I've tried to get OpenStack to work with other databases like Oracle DB, MongoDB, TimesTen,

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

On 05/22/2017 11:26 PM, Matt Riedemann wrote: > On 5/22/2017 10:58 AM, Sean Dague wrote: >> I think these are actually compatible concerns. The current proposal to >> me actually tries to address A1 & B1, with a hint about why A2 is >> valuable and we would want to do that. >> >> It feels like

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

On Mon, 22 May 2017, Sean Dague wrote: This feels like what a Tier 2 support looks like. A basic SQLA and pray so that if you live behind SQLA you are probably fine (though not tested), and then test and advanced feature roll out on a single platform. Any of that work might port to other

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

On 5/22/2017 10:58 AM, Sean Dague wrote: I think these are actually compatible concerns. The current proposal to me actually tries to address A1 & B1, with a hint about why A2 is valuable and we would want to do that. It feels like there would be a valuable follow on in which A2 & B2 were

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

On 05/15/2017 07:16 AM, Sean Dague wrote: > We had a forum session in Boston on Postgresql and out of that agreed to > the following steps forward: > > 1. explicitly warn in operator facing documentation that Postgresql is > less supported than MySQL. This was deemed better than just removing >

[openstack-dev] [tc] revised Postgresql deprecation patch for governance

We had a forum session in Boston on Postgresql and out of that agreed to the following steps forward: 1. explicitly warn in operator facing documentation that Postgresql is less supported than MySQL. This was deemed better than just removing documentation, because when people see Postgresql files