Wednesday, 2016-05-25

openstackgerritOpenStack Proposal Bot proposed openstack/requirements: Updated from generate-constraints  https://review.openstack.org/32079206:36
coolsvapwe need to have a sync between the proposal bot and dhellmann update constraint bot/patches06:58
*** jpena|off is now known as jpena07:29
jpenanick jpena07:29
openstackgerritJulien Danjou proposed openstack/requirements: Remove tooz from project list  https://review.openstack.org/32082408:13
*** SarathMekala has joined #openstack-requirements08:24
*** SarathMekala has left #openstack-requirements08:24
*** SarathMekala has joined #openstack-requirements08:24
*** SarathMekala has left #openstack-requirements08:24
*** coolsvap is now known as coolsvap_08:30
*** coolsvap_ is now known as coolsvap09:50
*** _amrith_ is now known as amrith10:40
*** openstackgerrit has quit IRC11:18
*** openstackgerrit has joined #openstack-requirements11:18
*** tonyb has left #openstack-requirements11:41
*** tonyb has joined #openstack-requirements11:41
* tonyb doesn't computer good :(11:42
dimsWe are meeting in 3 mins in  #openstack-meeting - Courtesy ping for : amrith coolsvap coreycb david-lyle dhellmann dirk dolphm GheRivero IgorYozhikov jpena jroll markmcclain masayukig mugsie notmorgan number80 prometheanfire sigmavirus24 toabctl tonyb tsufiev ttx11:58
number80o/11:58
amrithhello dims11:58
tonybdims: Thanks11:58
coolsvapdims, ack. Thanks!11:59
tonybdims: I'm on the "town hall" so I'll be distracted but present11:59
dimstonyb : will you be able to run it? :)11:59
dimsah ok11:59
dimsno worries :)11:59
tonybdims: I should be fine to run next week's if that helps you.12:00
jroll\o12:07
* jroll moves to the right room12:07
jrollis the courtesy ping just for everyone in this channel? :)12:08
*** amrith is now known as _amrith_12:30
*** jpena is now known as jpena|lunch12:42
dimsjroll : over some time, we can tune the list :) at the moment just pinging everyone here as the list is small12:56
jrolldims: yeah, just curious :)12:57
dimsjroll : "if you are here, you are interested, if you are interested, we would like you to help us, so we'll ping you" :)12:57
jrollhehe12:58
* coolsvap will be back later in evening12:59
sigmavirus24Sorry for missing the meeting this morning :(13:38
* sigmavirus24 goes to find the logs13:38
*** _amrith_ is now known as amrith13:41
*** amrith is now known as _amrith_13:43
*** _amrith_ is now known as amrith13:44
*** amrith is now known as _amrith_13:45
*** _amrith_ is now known as amrith13:49
*** amrith is now known as _amrith_13:49
*** _amrith_ is now known as amrith13:50
*** jpena|lunch is now known as jpena13:52
openstackgerritMerged openstack/requirements: update constraint for stevedore to new release 1.14.0  https://review.openstack.org/32070414:55
*** amrith is now known as _amrith_15:01
*** _amrith_ is now known as amrith15:04
openstackgerritMerged openstack/requirements: update constraint for tooz to new release 1.37.0  https://review.openstack.org/32070615:04
*** amrith is now known as _amrith_15:05
openstackgerritMerged openstack/requirements: update constraint for taskflow to new release 2.0.0  https://review.openstack.org/32070515:06
*** _amrith_ is now known as amrith15:09
dhellmanndims, tonyb : I'm seeing a lot of conflicts in the constraint updates for the oslo releases. I'm trying to decide whether to squash those into 1 patch, or make it a series. Thoughts?16:02
dimsdhellmann : either one is good16:04
dhellmannsquashing will lead to the changes merging faster16:04
dhellmannI would just approve the bot update, except there's a comment about something in horizon breaking16:05
dhellmannhttps://review.openstack.org/#/c/320792/16:05
openstackgerritMerged openstack/requirements: update constraint for pbr to new release 1.10.0  https://review.openstack.org/32010916:11
dimsdhellmann : unrelated error, please go ahead16:11
openstackgerritDoug Hellmann proposed openstack/requirements: update constraints for oslo releases 24 May 2016  https://review.openstack.org/32070316:25
dhellmanndims, tonyb : squashed ^^16:25
dimsdhellmann : +2 will wait for at least one more +1 before +A'ing it16:42
openstackgerritMerged openstack/requirements: update constraint for oslo.vmware to new release 2.7.0  https://review.openstack.org/32070217:04
*** jpena is now known as jpena|pto17:22
openstackgerritDoug Hellmann proposed openstack/requirements: update constraints for oslo releases 24 May 2016  https://review.openstack.org/32070317:31
dhellmanndims : rebased ^^17:31
openstackgerritDavanum Srinivas (dims) proposed openstack/requirements: Remove unused dcos dependency  https://review.openstack.org/32120319:46
*** amrith is now known as _amrith_20:05
openstackgerritKyle Mestery proposed openstack/requirements: Update neutron-lib to 0.2.0  https://review.openstack.org/32122820:40
dhellmanndims, tonyb : this is the compromise for gnocchiclient in liberty: https://review.openstack.org/#/c/321237/121:08
dimsdhellmann : something else will break and jd__ / telemetry team will be still unhappy. i'd rather they figure out a way to disable constraints for their jobs...21:14
dhellmanndims : ceilometer follows g-r, so it's appropriate for us to constrain their dependencies21:14
dhellmannoh, hmm, maybe they don't21:15
dhellmannI really thought they did21:15
dhellmannI thought only gnocchi wasn't in that list21:15
dimsi see only ceilometermiddleware and python-ceilometerclient in https://github.com/openstack/requirements/blob/stable/liberty/global-requirements.txt21:16
dhellmanndims : ceilometer is in projects.txt for stable/liberty21:17
dhellmannso the problem may come back for other branches, but this at least lets us fix liberty21:18
dimsdhellmann : that's only used by the bot and the bot is switched off21:18
dhellmannright, but the point is that for liberty they were accepting syncs, and that means they can ask for a constraint, and this constraint fixes the issue21:18
dimsdhellmann : they will end up breaking in another way a few days from now21:18
dimshttps://review.openstack.org/#/q/project:openstack/ceilometer+branch:stable/liberty+owner:%22OpenStack+Proposal+Bot%2221:20
dhellmannthat's possible.21:20
dimsthey haven't bothered to work the last bot proposed update21:20
dimsdhellmann : which jobs break? ceilometer?21:22
dhellmannapparently, yes21:22
dhellmannceilometer has a devstack plugin that installs gnocchi, and that fails because it's using an unconstrained gnocchiclient21:22
dhellmannthe version it chooses wants cliff 2.0, which fails the constraint check21:22
dhellmannthat's what led to jd__ raising that constraint. I proposed adding a constraint on gnocchiclient instead.21:23
dimshttps://review.openstack.org/#/q/project:openstack/ceilometer+branch:stable/liberty21:23
dimsthe one from may 23 seems fine21:23
dhellmannok. that's all the information I have, I don't have a link to a log or anything.21:23
*** _amrith_ is now known as amrith21:26
dimsack dhellmann21:26
dimsdhellmann : they can pip install whatever they want in their devstack plugin21:27
dhellmannwell, they can't, because pip is constrained in devstack21:27
dimsdhellmann : then they have to talk to devstack + infra21:27
dimsthat's what they have to work through for master or liberty21:27
dimsthey can't have the safety of constraints w/o bothering to be part of the process21:28
dhellmannthey *are* part of the process for liberty21:28
dimsthey faced this problem already in master21:28
dimsdhellmann : i can't find a log for ceilometer that fails with this cliff problem21:29
dhellmannok, I'll have to get jd__ to provide that info, I took that part on faith21:29
dimsdhellmann : yep. i understand21:29
dimsif it is a project listed in projects.txt for liberty, then let's unblock.21:31
dimsdhellmann : we are trying to make lemonade here with the whole g-r/u-c process. if folks don't like it, they should work with infra and whoever else to run jobs that are not subject to constraints. i am really sad to hear the constant stream of complaints21:37
dimsw/o active participation or alternate proposals21:37
dhellmanndims : understood. I thought in this case it was an easy fix because that version of ceilometer was participating in g-r. I agree that for master we'd leave it up to them to resolve.21:38
tonybdhellmann: Thanks.  I'll take an action item to work with jd__, you, dims and infra to define a reaonable long term compromise. In otehr words work out how to disable constraints in some jobs and what that really means for the gate / this team.22:06
dhellmanntonyb : alternately we could try to convince the telemetry team to start syncing requirements again, but yeah.22:11
dimstonyb : Thanks!22:17
tonybdhellmann: I think there's too much 'bad blood' for that to fly anytime soon.22:18
dimstonyb : we are facing the aftermath, but would like to keep sanity :)22:18
tonybdhellmann: that would be a better solution and one I intend to chat to jd__ about in Barcelona.  Given my lack of history I like to think we can find a way forward.22:19
tonybdims: Yeah.  If we make it optional in the gate there would be an explict "buyer be ware" clause.22:20
tonybAlso moving forward in ocata I have a crazy pants tool in my head (where it's perfect but useless) that will allow us to loosen the coupling between projects but still be co-installable ... basically 3.1222:23
tonybfrom the TODO list.22:24
tonybIt seems like it'd be fun to write :)22:24

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!