[openstack-dev] [oslo] [telemetry] [requirements] [FFE] Oslo.db 4.13.2

Doug Hellmann doug at doughellmann.com
Wed Sep 7 19:23:17 UTC 2016


Excerpts from Mike Bayer's message of 2016-09-07 14:09:06 -0400:
> 
> On 09/07/2016 01:29 PM, Doug Hellmann wrote:
> > Excerpts from Matthew Thode's message of 2016-09-07 09:11:58 -0500:
> >> On 09/07/2016 08:58 AM, Doug Hellmann wrote:
> >>> Excerpts from Matthew Thode's message of 2016-09-07 08:21:50 -0500:
> >>>> https://review.openstack.org/366298
> >>>>
> >>>> This is just a bump to upper-constraints so is more minor to get testing
> >>>> working and fix the bug that occurred in Gnocchi (and possibly others).
> >>>>
> >>>> We are able to mask the 'bad' versions of oslo.db and unmask pymysql
> >>>> 0.7.7 after the freeze (and backport them to stable/newton) so this is
> >>>> easier to merge.
> >>>>
> >>>
> >>> If we have a known-bad version of the library, maybe it would be better
> >>> to incorporate that info into the global-requirements list before we
> >>> branch the requirements repository? I'm not sure what we've done in
> >>> this case for past cycles.
> >>>
> >>> Doug
> >>>
> >>> __________________________________________________________________________
> >>> 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
> >>>
> >> Are you fine with the knock on effects that a gr update would cause?
> >
> > What do we have that uses oslo.db and is itself a library that would
> > need to be re-released?
> 
> I would assume Gnocchi which acts as a backend for Ceilometer.

Gnocchi is a service. It's not in the pip requirements list for
ceilometer, so releasing a new version of oslo.db and having that
trigger a new release of gnocchi won't also trigger a new release
of ceilometer to update its dependency list.

The service projects are not yet at their RC1 point, so haven't been
branched. Neither has the requirements list. If blocking the "bad"
version of oslo.db doesn't trigger a cascade of new library releases, we
should do it before we tag RC1 and branch the requirements list so that
we don't have to try to backport the block into newton.

Doug



More information about the OpenStack-dev mailing list