PostgreSQL driver has been removed from DevStack
Just a heads up that the PostgreSQL DB driver has been removed from DevStack as of today [1]. This was deprecated in Pike due to lack of maintenance and has been on the chopping block since then. If you have jobs that relied on this, it would be advisable to drop these jobs now. I don't think the DevStack team have the resources to maintain this so if someone *really* needed to keep it around, they should probably put together a plugin and consume it that way.
Stephen
On 10/17/2019 12:12 PM, Stephen Finucane wrote:
Just a heads up that the PostgreSQL DB driver has been removed from DevStack as of today [1]. This was deprecated in Pike due to lack of maintenance and has been on the chopping block since then. If you have jobs that relied on this, it would be advisable to drop these jobs now. I don't think the DevStack team have the resources to maintain this so if someone*really* needed to keep it around, they should probably put together a plugin and consume it that way.
Stephen
This would have been useful information before actually merging the change to drop this code. We have at least a few postgres jobs (the grenade one is relatively new) because we have postgres support in a few places, like placement.
What maintenance burden did people actually have when the pg jobs didn't break?
On 17/10/2019 20.00, Matt Riedemann wrote:
On 10/17/2019 12:12 PM, Stephen Finucane wrote:
Just a heads up that the PostgreSQL DB driver has been removed from DevStack as of today [1]. This was deprecated in Pike due to lack of maintenance and has been on the chopping block since then. If you have jobs that relied on this, it would be advisable to drop these jobs now. I don't think the DevStack team have the resources to maintain this so if someone*really* needed to keep it around, they should probably put together a plugin and consume it that way.
Stephen
This would have been useful information before actually merging the change to drop this code. We have at least a few postgres jobs (the grenade one is relatively new) because we have postgres support in a few places, like placement.
FYI: http://zuul.opendev.org/t/openstack/jobs allows searching for jobs, just add "postgres" in the search box and see which ones are used,
Andreas
On 10/17/2019 1:41 PM, Andreas Jaeger wrote:
FYI: http://zuul.opendev.org/t/openstack/jobs allows searching for jobs, just add "postgres" in the search box and see which ones are used,
Yeah so I count about 56 jobs between -postgres and -pg in the name.
On 10/17/2019 1:00 PM, Matt Riedemann wrote:
This would have been useful information before actually merging the change to drop this code. We have at least a few postgres jobs (the grenade one is relatively new) because we have postgres support in a few places, like placement.
What maintenance burden did people actually have when the pg jobs didn't break?
I've proposed a revert:
https://review.opendev.org/#/c/689250/
On 19-10-17 14:42:58, Matt Riedemann wrote:
On 10/17/2019 1:00 PM, Matt Riedemann wrote:
This would have been useful information before actually merging the change to drop this code. We have at least a few postgres jobs (the grenade one is relatively new) because we have postgres support in a few places, like placement.
What maintenance burden did people actually have when the pg jobs didn't break?
I've proposed a revert:
Thanks, some of us are still using postgres (think it was installed grizzly / folsom time frame). I understand the desire for removal but doesn't make me any less sad.
participants (4)
-
Andreas Jaeger
-
Matt Riedemann
-
Matthew Thode
-
Stephen Finucane