[openstack-dev] [oslo] Can we stop global requirements update?

2017-04-19 Thread Julien Danjou
Hoy, So Gnocchi gate is all broken (agan) because it depends on "pbr" and some new release of oslo.* depends on pbr!=2.1.0. Neither Gnocchi nor Oslo cares about whatever bug there is in pbr 2.1.0 that got in banished by requirements Gods. It does not prevent it to be used e.g. to install the

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-19 Thread Clark Boylan
On Wed, Apr 19, 2017, at 05:54 AM, Julien Danjou wrote: > Hoy, > > So Gnocchi gate is all broken (agan) because it depends on "pbr" and > some new release of oslo.* depends on pbr!=2.1.0. > > Neither Gnocchi nor Oslo cares about whatever bug there is in pbr 2.1.0 > that got in banished by req

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-19 Thread Julien Danjou
On Wed, Apr 19 2017, Clark Boylan wrote: > I think we know from experience that just stopping (eg reverting to the > situation we had before requirements and constraints) would lead to > sadness. Installations would frequently be impossible due to some > unresolvable error in dependency resolution

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-19 Thread Doug Hellmann
Excerpts from Clark Boylan's message of 2017-04-19 08:10:43 -0700: > On Wed, Apr 19, 2017, at 05:54 AM, Julien Danjou wrote: > > Hoy, > > > > So Gnocchi gate is all broken (agan) because it depends on "pbr" and > > some new release of oslo.* depends on pbr!=2.1.0. > > > > Neither Gnocchi nor

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-19 Thread Matthew Oliver
We have started this work. I've been working on: https://review.openstack.org/#/c/444718/ Which will do requirement checks, as specified in the Pike PTG ehterpad for Tuesday morning: https://etherpad.openstack.org/p/relmgt-stable-requirements-ptg-pike (line 40+). Once done, Tony and I were going

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-19 Thread Joshua Harlow
Doug Hellmann wrote: Excerpts from Clark Boylan's message of 2017-04-19 08:10:43 -0700: On Wed, Apr 19, 2017, at 05:54 AM, Julien Danjou wrote: Hoy, So Gnocchi gate is all broken (agan) because it depends on "pbr" and some new release of oslo.* depends on pbr!=2.1.0. Neither Gnocchi nor

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-20 Thread Doug Hellmann
Excerpts from Matthew Oliver's message of 2017-04-20 14:41:38 +1000: > We have started this work. I've been working on: > https://review.openstack.org/#/c/444718/ Wonderful! I'm sorry I didn't realize you were working on it. Thank you! > Which will do requirement checks, as specified in the Pike

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-20 Thread gordon chung
On 20/04/17 01:32 AM, Joshua Harlow wrote: > Wasn't there also some decision made in austin (?) about how we as a > group stated something along the line of co-installability isn't as > important as it once was (and may not even be practical or what people > care about anymore anyway)? > > With k

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-20 Thread Doug Hellmann
Excerpts from gordon chung's message of 2017-04-20 17:12:26 +: > > On 20/04/17 01:32 AM, Joshua Harlow wrote: > > Wasn't there also some decision made in austin (?) about how we as a > > group stated something along the line of co-installability isn't as > > important as it once was (and may n

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-20 Thread Joshua Harlow
Doug Hellmann wrote: Excerpts from gordon chung's message of 2017-04-20 17:12:26 +: On 20/04/17 01:32 AM, Joshua Harlow wrote: Wasn't there also some decision made in austin (?) about how we as a group stated something along the line of co-installability isn't as important as it once was (a

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-21 Thread ChangBo Guo
2017-04-19 23:10 GMT+08:00 Clark Boylan : > On Wed, Apr 19, 2017, at 05:54 AM, Julien Danjou wrote: > > Hoy, > > > > So Gnocchi gate is all broken (agan) because it depends on "pbr" and > > some new release of oslo.* depends on pbr!=2.1.0. > > > > Neither Gnocchi nor Oslo cares about whatever

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-21 Thread Doug Hellmann
Excerpts from Joshua Harlow's message of 2017-04-20 22:31:19 -0700: > Doug Hellmann wrote: > > Excerpts from gordon chung's message of 2017-04-20 17:12:26 +: > >> On 20/04/17 01:32 AM, Joshua Harlow wrote: > >>> Wasn't there also some decision made in austin (?) about how we as a > >>> group st

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-04-22 Thread Julien Danjou
On Fri, Apr 21 2017, Doug Hellmann wrote: > My memory of the outcome of that session was that we needed to maintain > co-installability; that we could continue to keep an eye on the > container space as an alternative; and that a new team of maintainers > would take over the requirements list (whi

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-16 Thread Julien Danjou
On Wed, Apr 19 2017, Julien Danjou wrote: > So Gnocchi gate is all broken (agan) because it depends on "pbr" and > some new release of oslo.* depends on pbr!=2.1.0. Same things happened today with Babel. As far as Gnocchi is concerned, we're going to take the easiest route and remove all our

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-16 Thread Andreas Jaeger
On 2017-05-16 11:42, Julien Danjou wrote: > On Wed, Apr 19 2017, Julien Danjou wrote: > >> So Gnocchi gate is all broken (agan) because it depends on "pbr" and >> some new release of oslo.* depends on pbr!=2.1.0. > > Same things happened today with Babel. As far as Gnocchi is concerned, > we'

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-16 Thread Julien Danjou
On Tue, May 16 2017, Andreas Jaeger wrote: > what exactly happened with Babel? > > I see in global-requirements the following: > Babel>=2.3.4,!=2.4.0 # BSD > > that shouldn't case a problem - or does it? Or what's the problem? Damn, at the moment I pressed the `Sent' button I thought "You just c

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-16 Thread Andreas Jaeger
On 2017-05-16 12:10, Julien Danjou wrote: > On Tue, May 16 2017, Andreas Jaeger wrote: > >> what exactly happened with Babel? >> >> I see in global-requirements the following: >> Babel>=2.3.4,!=2.4.0 # BSD >> >> that shouldn't case a problem - or does it? Or what's the problem? > > Damn, at the

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-16 Thread Julien Danjou
On Tue, May 16 2017, Andreas Jaeger wrote: > It is needed to generate the translations, but can't we move it for > oslo-i18n into test-requirements? I've pushed this and it seems to work, pretty sure it's safe. https://review.openstack.org/#/c/465014/ If we can merge this today and then relea

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-18 Thread Mike Bayer
On 05/16/2017 05:42 AM, Julien Danjou wrote: On Wed, Apr 19 2017, Julien Danjou wrote: So Gnocchi gate is all broken (agan) because it depends on "pbr" and some new release of oslo.* depends on pbr!=2.1.0. Same things happened today with Babel. As far as Gnocchi is concerned, we're goin

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-18 Thread Julien Danjou
On Thu, May 18 2017, Mike Bayer wrote: > I'm not understanding this? do you mean this? In the long run, yes. Unfortunately, we're not happy with the way Oslo libraries are managed and too OpenStack centric. I've tried for the last couple of years to move things on, but it's barely possible to de

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-18 Thread Mike Bayer
On 05/18/2017 02:37 PM, Julien Danjou wrote: On Thu, May 18 2017, Mike Bayer wrote: I'm not understanding this? do you mean this? In the long run, yes. Unfortunately, we're not happy with the way Oslo libraries are managed and too OpenStack centric. I've tried for the last couple of years

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-18 Thread Julien Danjou
On Thu, May 18 2017, Mike Bayer wrote: > replaces oslo.service with a multiprocessing approach that doesn't use > eventlet. great! any openstack service that rides on oslo.service would like > to be able to transparently switch from eventlet to multiprocessing the same > way they can more or les

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-19 Thread Mehdi Abaakouk
On Thu, May 18, 2017 at 03:16:20PM -0400, Mike Bayer wrote: On 05/18/2017 02:37 PM, Julien Danjou wrote: On Thu, May 18 2017, Mike Bayer wrote: I'm not understanding this? do you mean this? In the long run, yes. Unfortunately, we're not happy with the way Oslo libraries are managed and to

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-19 Thread Julien Danjou
On Fri, May 19 2017, Mehdi Abaakouk wrote: > Not really, I just put some comments on reviews and discus this on IRC. > Since nobody except Telemetry have expressed/try to get rid of eventlet. TBH Keystone get rid of it too. But they only provide WSGI servers. They don't build any daemon so they d

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-19 Thread Doug Hellmann
Excerpts from Mehdi Abaakouk's message of 2017-05-19 10:23:09 +0200: > On Thu, May 18, 2017 at 03:16:20PM -0400, Mike Bayer wrote: > > > > > >On 05/18/2017 02:37 PM, Julien Danjou wrote: > >>On Thu, May 18 2017, Mike Bayer wrote: > >> > >>>I'm not understanding this? do you mean this? > >> > >>In

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-19 Thread Joshua Harlow
Mehdi Abaakouk wrote: Not really, I just put some comments on reviews and discus this on IRC. Since nobody except Telemetry have expressed/try to get rid of eventlet. Octavia is using cotyledon and they have gotten rid of eventlet. Didn't seem like it was that hard either to do it (of course t

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-19 Thread Mike Bayer
On 05/19/2017 04:23 AM, Mehdi Abaakouk wrote: And some applications rely on implicit internal contract/behavior/assumption. IMO that's a bug for them.I'm inspired to see that Keystone, Nova etc. are able to move between and eventlet backend and a mod_wsgi backend.IMO eventlet is

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-20 Thread Julien Danjou
On Fri, May 19 2017, Mike Bayer wrote: > IMO that's a bug for them. Of course it's a bug. IIRC Mehdi tried to fix it without much success. > I'm inspired to see that Keystone, Nova etc. are > able to move between and eventlet backend and a mod_wsgi backend.IMO > eventlet is really not needed

Re: [openstack-dev] [oslo] Can we stop global requirements update?

2017-05-21 Thread Mike Bayer
On 05/20/2017 12:04 PM, Julien Danjou wrote: On Fri, May 19 2017, Mike Bayer wrote: IMO that's a bug for them. Of course it's a bug. IIRC Mehdi tried to fix it without much success. I'm inspired to see that Keystone, Nova etc. are able to move between and eventlet backend and a mod_wsgi b