Re: [openstack-dev] [tc] [all] TC Report 18-07
On 2018-02-13 11:31 AM, gordon chung wrote: > > > was there a resolution for this? iiuc, pgsql is not supported by glance > based on: > https://github.com/openstack/glance/commit/f268df1cbc3c356c472ace04bd4f2d4b3da6c026 > err... nevermind. it seems https://github.com/openstack/glance/commit/106de18f326247e8d3f715452665b96dade6d2bc fixes it... or it seems i can run devstack. carry on :) -- gord __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tc] [all] TC Report 18-07
On 2/13/2018 10:31 AM, gordon chung wrote: was there a resolution for this? iiuc, pgsql is not supported by glance based on: https://github.com/openstack/glance/commit/f268df1cbc3c356c472ace04bd4f2d4b3da6c026 i don't know if it was a bad commit but it seems to break any case that tries to use pgsql (except if the db has all migrations applied already). not making an opinion here, just asking as i have a patch[1] to remove pgsql gate from one of the telemetry projects that was affected and wondering if i should proceed. [1]https://review.openstack.org/#/c/542240/ Wow, not even a release note on that glance change. As I commented in the review, if you're using postgresql, it doesn't matter if you don't care about rolling upgrade support for glance, you literally just can't upgrade *at all* to queens for glance now. Surely there must be some kind of way we can put in logic like, "if engine == postgresql: log a warning and do the offline schema migration" ? -- Thanks, Matt __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [tc] [all] TC Report 18-07
On 2018-02-13 10:08 AM, Chris Dent wrote: > > # PostgreSQL and Triggers > > Later in the [same > day](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-02-07.log.html#t2018-02-07T17:18:56) > > > there was some discussion about the state of PostgreSQL support and > the merit of using triggers to manage migrations. There were some > pretty strong (and supported) assertions that triggers are not a good > choice. was there a resolution for this? iiuc, pgsql is not supported by glance based on: https://github.com/openstack/glance/commit/f268df1cbc3c356c472ace04bd4f2d4b3da6c026 i don't know if it was a bad commit but it seems to break any case that tries to use pgsql (except if the db has all migrations applied already). not making an opinion here, just asking as i have a patch[1] to remove pgsql gate from one of the telemetry projects that was affected and wondering if i should proceed. [1] https://review.openstack.org/#/c/542240/ cheers, -- gord __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [tc] [all] TC Report 18-07
HTML: https://anticdent.org/tc-report-18-07.html A few things to report from the past week of TC interaction. Not much in the way of opportunities to opine or editorialize. # Goals Still more on the topic of OpenStack wide goals. There was some robust [discussion](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-02-07.log.html#t2018-02-07T12:56:13) about the [mox goal](https://governance.openstack.org/tc/goals/rocky/mox_removal.html) (eventually leading to accepting the goal, despite some reservations). That discussion somehow meandered into where gerrit is on the "least bad" to "most good" scale. # PostgreSQL and Triggers Later in the [same day](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-02-07.log.html#t2018-02-07T17:18:56) there was some discussion about the state of PostgreSQL support and the merit of using triggers to manage migrations. There were some pretty strong (and supported) assertions that triggers are not a good choice. # PowerStackers and Driver Projects [Discussion](http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2018-02-08.log.html#t2018-02-08T15:43:44) about having a [PowerStackers](https://review.openstack.org/#/c/540165/) project evolved into a review of the current thinking on dealing with projects that require access to special drivers or hardware. This is a common discussion in OpenStack because so much of the point of OpenStack is to provide an abstraction over _stuff_. # Prepping the PTG There's a growing [etherpad](https://etherpad.openstack.org/p/PTG-Dublin-TC-topics) of topics to be discussed with the TC Friday morning at the PTG. You should feel free to add topics and show up and keep the TC in check. The room the meeting will be in [is glorious](https://crokepark.ie/meetings-events/spaces/space-listing/coiste-bainisti) in its criminal-mastermind-wonderfulness. -- Chris Dent (⊙＿⊙') https://anticdent.org/ freenode: cdent tw: @anticdent__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
