| *** kornicameister has quit IRC | 00:25 | |
| *** kornicameister has joined #openstack-requirements | 00:26 | |
| *** kornicameister has quit IRC | 00:40 | |
| *** kornicameister has joined #openstack-requirements | 00:45 | |
| prometheanfire | k, ptg registered for and flight booked | 01:13 |
|---|---|---|
| *** kornicameister has quit IRC | 01:30 | |
| *** kornicameister has joined #openstack-requirements | 01:35 | |
| *** kornicameister has quit IRC | 02:29 | |
| *** kornicameister has joined #openstack-requirements | 02:35 | |
| *** udesale has joined #openstack-requirements | 03:40 | |
| *** kornicameister has quit IRC | 03:53 | |
| *** kornicameister has joined #openstack-requirements | 03:54 | |
| openstackgerrit | Tony Breeds proposed openstack/requirements master: [WiP] Tool to find repos that could be a problem when we thaw https://review.openstack.org/492382 | 05:56 |
| tonyb | prometheanfire: ^^^ don't laugh | 05:56 |
| tonyb | prometheanfire: Alos it's about twice as long as I expected but it alos has comments | 05:56 |
| tonyb | prometheanfire: and theer were way more repos that are problems than I expected. | 05:57 |
| tonyb | Dinesh_Bhor: You really shoudl reply to your requirements FFE email | 06:03 |
| Dinesh_Bhor | tonyb: yes, sorry for delay | 06:16 |
| prometheanfire | is git part of our requirements (it doesn't look to be in bindep) | 06:17 |
| prometheanfire | so, import git may not work | 06:17 |
| Dinesh_Bhor | tonyb: we are planning to cut stable/pike. I am contacting PTL Sampath Priyankara (samP) for the same. | 06:25 |
| strigazi | tonyb Hi, in your email [1] you mention that magnum doesn't use the releases repo, what that means? We do releases using the releases repo. [1] http://lists.openstack.org/pipermail/openstack-dev/2017-August/120922.html | 06:37 |
| prometheanfire | I see you are here https://github.com/openstack/releases/blob/master/deliverables/pike/magnum.yaml | 06:41 |
| strigazi | prometheanfire yes. We haven't cut pike yet. | 06:41 |
| prometheanfire | right, which is a problem on it's own, but you are in the repo, at least there | 06:42 |
| strigazi | prometheanfire Is there another problem? That email confused me. | 06:44 |
| prometheanfire | I don't know, I'm hoping he answers :P | 06:45 |
| *** tpatil has joined #openstack-requirements | 06:45 | |
| strigazi | tonyb prometheanfire , magnum is in openstack/releases, follows cycle-with-intermediary, is subscribed in the requirements repo, it is not a branchless repo. But it doesn't have a pike branch. We will fix our pipeline and cut as soon as possible. | 06:49 |
| prometheanfire | strigazi: sgtm | 06:51 |
| *** tpatil has quit IRC | 07:04 | |
| *** prometheanfire has quit IRC | 07:23 | |
| *** aarefiev_afk is now known as aarefiev | 07:29 | |
| *** prometheanfire has joined #openstack-requirements | 07:42 | |
| *** tmorin has joined #openstack-requirements | 07:43 | |
| tmorin | hi tonyb, are you around for a question related to https://review.openstack.org/#/c/492115/ ? | 07:43 |
| tonyb | tmorin: I was not but I am now .... sup? | 09:19 |
| tmorin | hi tonyb | 09:19 |
| tonyb | prometheanfire: probably not like I said it's a WiP that needs work | 09:20 |
| tmorin | tonyb: a bit of context first: networking-bagpipe relies on exabgp, but exabgp 4.0.x branch has had regressions in the recent past | 09:20 |
| tmorin | tonyb: I would like to make sure that openstack requirements upper constraints are not upgraded automatically | 09:21 |
| tmorin | tonyb: how can we ensure that ? | 09:21 |
| tonyb | tmorin: The best we can do is try to remeber to add you as a reviewer on reviews that do that thing | 09:21 |
| tonyb | there isn't an automated process that allows does what you want though | 09:22 |
| tmorin | I was thinking that exabgp<4.0.3 in global-requirements.txt might do that :-/ | 09:23 |
| tonyb | strigazi: [tony@thor releases]$ gti grep openstack/magnum -- deliverables/{_independent,pike}/ | 09:23 |
| tmorin | (as an example) | 09:23 |
| tonyb | didn't show anything so it seems like you haven't done a magnum release during pike | 09:23 |
| tonyb | tmorin: No we don't cap requiremtns like that | 09:23 |
| tonyb | tmorin: we can *try* add you to a review and/or create a no-op chnage in networking-bagpipe to check that it mostly works | 09:24 |
| tmorin | yep, that will surely help | 09:24 |
| tonyb | tmorin: but the advantage of u-c is that it's trivial to revert a chnage that is bad in some way | 09:24 |
| strigazi | tonyb We try to fix the pipeline and cut the branch | 09:24 |
| tonyb | strigazi: Great. That's all we need. a stable/pike branch | 09:25 |
| tmorin | and I guess that in the case where a change would pass and a regression would happen, we can still update upper-constraints.txt again in another change to downgrade | 09:25 |
| tonyb | tmorin: Like i said is a best effort not a firm commitmen, but we do something similar for horizon | 09:26 |
| strigazi | tonyb: ok, tmr max we will cut the branch. The lack of resource on infra killed us :( | 09:26 |
| tmorin | tonyb: ok, understood | 09:26 |
| tonyb | strigazi: okay. will you use new-release from release to make the branch? that'd be best as it sets up the meta-data *and* the branch at the same time :) | 09:27 |
| tmorin | tonyb: might be interesting to have the bot add the core of impacted projects added as reviewers of the change, wouldn't it ? | 09:27 |
| strigazi | tonyb I do it manually usually, i can give it a go and give feedback | 09:28 |
| tonyb | strigazi: Using the tool would be great if you can. | 09:29 |
| tonyb | tmorin: that'd be technically possible but the requirements team doesn't have time to do that in queens or rocky | 09:30 |
| tonyb | tmorin: Also that's potentially a lot of people. Imagine what would happen when we update olso.config for example ;P | 09:30 |
| tmorin | tonyb: yes... | 09:31 |
| tmorin | tonyb: yes, no trivial to define when it's relevant to Cc people and when it's best not to | 09:32 |
| *** sdague has joined #openstack-requirements | 09:50 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints https://review.openstack.org/488373 | 09:52 |
| tonyb | https://etherpad.openstack.org/p/requirements_pike_thaw | 10:03 |
| *** tmorin has quit IRC | 10:29 | |
| *** udesale has quit IRC | 10:36 | |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/requirements master: update constraint for monasca-common to new release 2.3.0 https://review.openstack.org/492521 | 12:37 |
| *** jrist has joined #openstack-requirements | 12:58 | |
| *** sdake_ is now known as sdake | 15:27 | |
| *** aarefiev is now known as aarefiev_afk | 16:00 | |
| *** witek_ has joined #openstack-requirements | 16:25 | |
| *** witek has quit IRC | 16:26 | |
| *** witek_ has quit IRC | 16:37 | |
| *** samP_ has joined #openstack-requirements | 16:48 | |
| *** samP_ has quit IRC | 16:49 | |
| *** samP_ has joined #openstack-requirements | 17:06 | |
| samP_ | tonyb: Hi | 17:11 |
| samP_ | tonyb: I am the current maintainer for maskari, masakari-monitors, and python-masakariclient | 17:13 |
| samP_ | tonyb: I would like to discuss about release dates of those projects. | 17:14 |
| samP_ | tonyb: This is related to your mail http://lists.openstack.org/pipermail/openstack-dev/2017-August/120922.html | 17:15 |
| prometheanfire | samP_: what is your release process? | 17:16 |
| samP_ | prometheanfire: we originally planed to release after 8/15 meeting | 17:17 |
| samP_ | prometheanfire: I mean cut the stable/pike | 17:17 |
| prometheanfire | is there anything preventing you from doing it earlier? | 17:17 |
| samP_ | prometheanfire: for masakari-monitrs and python-masakariclient, I can do it 8/11 | 17:18 |
| prometheanfire | if so, can you block requirements updates til you branch (if we do unfreeze) | 17:18 |
| samP_ | prometheanfire: However, for masakari, I would like to land few changes before cut stable/pike | 17:19 |
| prometheanfire | ok | 17:19 |
| samP_ | prometheanfire: block requirements update = do not merge the updates from requrements? | 17:20 |
| prometheanfire | ya, -2 them | 17:20 |
| samP_ | prometheanfire: sure, that can be done. | 17:20 |
| prometheanfire | cool, I think that's the plan we are putting forward | 17:21 |
| samP_ | prometheanfire: great, then I will replay to ML with our plan. | 17:21 |
| samP_ | prometheanfire: thank you very much | 17:21 |
| prometheanfire | cool | 17:22 |
| prometheanfire | np | 17:22 |
| *** samP_ has quit IRC | 18:00 | |
| *** openstackgerrit has quit IRC | 19:03 | |
| *** jrist has quit IRC | 19:48 | |
| *** amotoki has quit IRC | 20:24 | |
| *** sdake is now known as k2so | 20:37 | |
| tonyb | prometheanfire: the point was to determine if masakari needs an FFE. If they're going to cut pike then it's easier to give them and FFE (and have the accept the g-r update) than to go through the backporting issue. Ho Hum we'll see if they've done anything. | 22:28 |
| prometheanfire | did I miss that ffe? | 22:32 |
| prometheanfire | I'm almost caught up, promise | 22:33 |
| prometheanfire | I did update the etherpad for OSA | 22:48 |
| *** sdague has quit IRC | 23:47 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!