Open Stack

Excerpts from witold.bedyk at est.fujitsu.com's message of 2017-08-03 16:07:45 +0000:
> > -----Original Message-----
> > From: Doug Hellmann [mailto:doug at doughellmann.com]
> > Sent: Donnerstag, 3. August 2017 15:45
> > To: openstack-dev <openstack-dev at lists.openstack.org>
> > Subject: Re: [openstack-dev]
> > [ffe][requirements][monasca][heat][watcher][congress] FFE for python-
> > monascaclient minimum version in g-r
> > 
> > Excerpts from witold.bedyk at est.fujitsu.com's message of 2017-08-03
> > 11:39:47 +0000:
> > > Hello everyone,
> > >
> > > I would like to ask for the FFE for python-monascaclient version in global
> > requirements.
> > >
> > > The current version in Pike (1.7.0) is not fully backward compatible. The
> > monasca exception classes were replaced with keystoneauth exceptions,
> > which affects heat and watcher projects if they use current upper
> > constraints. The fixes for these projects have been submitted [1, 2].
> > >
> > > Also, monasca projects (monasca-agent, monasca-ui, monasca-api) rely on
> > python-monascaclient 1.7.0 and don't work with older versions.
> > >
> > > The change for bumping the minimum version of python-monascaclient is
> > here:
> > >
> > > https://review.openstack.org/489173
> > >
> > >
> > > Best greetings
> > > Witek Bedyk
> > >
> > >
> > > [1] https://review.openstack.org/490016
> > > [2] https://review.openstack.org/490018
> > >
> > 
> > It is rather late to be raising the minimum allowed version of a library due to
> > backwards incompatibilities. Can you provide more details about which
> > projects will be impacted (both by updating, and by not updating)?
> 
> 
> Hi Doug,
> 
> I know it's very unfortunate to raise it so late. We haven't paid enough attention when merging the osc-lib integration to monascaclient. I'm sorry for that.
> 
> If we update g-r impacted projects are:
> * Congress
> * Heat
> * Watcher
> For Heat and Watcher we have provided above referenced changes. Congress should work with both, old and new versions, from what we've checked.
> Rally and Freezer-dr do not follow g-r. Fix for Rally has already been merged [1]. Freezer-dr should not be impacted.
> 
> If we don't update g-r the impacted projects are again:
> * Heat
> * Watcher
> The teams don't want to merge compatibility fixes until requirements are raised. Please refer to the reviews from the first message. Without these fixes monascaclient from upper-constraints does not work for them.
> 
> The change in g-r does not alter u-c.
> 
> 
> [1] https://review.openstack.org/486015
> 
> > 
> > How can it be that the Monasca services already rely on the features of this
> > version? Are they not following the constraints process, so they use the
> > same versions of the libraries all of the other projects use?
> > 
> > Doug
> 
> 
> I'm not sure if I know what you mean. We do use upper-constraints for installation and testing. The new version is in u-c.

OK, I think the thing that I misunderstood was that this
backwards-incompatible release is already out. The version number 1.7.0
doesn't follow the SemVer policies if it is incompatible. It should have
been 2.0.0.

> 
> Could you please advise how to proceed?

A good start would be to get all of the PTLs for the projects you listed
to express their opinion here on this thread. Part of the point of
freezing is to force coordination when we do need to make exceptions.

Doug

> 
> 
> Thanks
> Witek
>