Wednesday, 2018-06-27

*** cjloader has joined #openstack-requirements00:28
*** cjloader has quit IRC00:33
*** hongbin has joined #openstack-requirements01:28
*** cjloader has joined #openstack-requirements01:29
*** cjloader has quit IRC01:34
*** hongbin has quit IRC03:11
*** hongbin has joined #openstack-requirements03:37
*** udesale has joined #openstack-requirements03:50
*** hongbin has quit IRC04:24
*** cjloader has joined #openstack-requirements04:27
*** cjloader has quit IRC04:31
*** hwoarang has quit IRC04:40
*** hwoarang has joined #openstack-requirements05:23
*** vpickard has joined #openstack-requirements05:38
*** vpickard_ has quit IRC05:41
*** hwoarang has quit IRC06:06
*** hwoarang has joined #openstack-requirements06:06
*** andreas_s has joined #openstack-requirements06:08
*** ccamacho has joined #openstack-requirements06:22
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/57829106:34
openstackgerritMatthew Thode proposed openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/57829106:38
*** andreas_s has quit IRC06:53
*** udesale has quit IRC06:54
*** udesale has joined #openstack-requirements06:55
*** udesale has quit IRC06:59
*** udesale has joined #openstack-requirements07:00
*** andreas_s has joined #openstack-requirements07:01
*** andreas_s has quit IRC07:07
*** andreas_s has joined #openstack-requirements07:11
*** andreas_s has quit IRC07:18
*** andreas_s has joined #openstack-requirements07:19
*** andreas_s has quit IRC07:21
*** andreas_s has joined #openstack-requirements07:25
*** tosky has joined #openstack-requirements07:40
*** amoralej|off is now known as amoralej07:42
*** andreas_s has quit IRC07:43
*** andreas_s has joined #openstack-requirements07:47
*** andreas_s has quit IRC07:51
*** andreas_s has joined #openstack-requirements07:52
*** andreas_s has quit IRC07:56
*** jpich has joined #openstack-requirements08:02
*** andreas_s_ has joined #openstack-requirements08:15
*** andreas_s_ has quit IRC08:21
*** andreas_s has joined #openstack-requirements08:22
*** dtantsur|afk is now known as dtantsur08:22
*** ccamacho has quit IRC08:27
*** ccamacho has joined #openstack-requirements08:27
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for oslo.config to new release 6.2.2  https://review.openstack.org/57831908:29
*** andreas_s has quit IRC08:30
*** andreas_s has joined #openstack-requirements08:30
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for osprofiler to new release 2.2.0  https://review.openstack.org/57832108:35
*** andreas_s has quit IRC08:36
*** andreas_s has joined #openstack-requirements08:36
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for oslo.log to new release 3.39.0  https://review.openstack.org/57832208:37
*** andreas_s has quit IRC08:40
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for oslo.vmware to new release 2.30.0  https://review.openstack.org/57832308:40
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for oslotest to new release 3.6.0  https://review.openstack.org/57832408:41
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for oslo.versionedobjects to new release 1.33.3  https://review.openstack.org/57832508:41
*** andreas_s has joined #openstack-requirements08:43
*** kevko has joined #openstack-requirements08:53
kevkoprometheanfire: hello Matthew , could I have some questions regarding https://review.openstack.org/#/c/505973/    ( Michal Arbet )08:56
*** udesale has quit IRC11:24
*** amoralej is now known as amoralej|lunch11:37
*** dtantsur is now known as dtantsur|brb12:06
*** ttx has quit IRC12:09
*** ttx has joined #openstack-requirements12:23
*** edmondsw has joined #openstack-requirements12:57
*** edmondsw has quit IRC12:57
*** edmondsw has joined #openstack-requirements12:57
openstackgerritMichal Arbet proposed openstack/requirements master: [DNM] test review of networkx-2.0 for consuming projects to use  https://review.openstack.org/50597313:04
*** amoralej|lunch is now known as amoralej13:18
*** dtantsur|brb is now known as dtantsur13:35
*** udesale has joined #openstack-requirements14:04
prometheanfirekevko: once tests come back :P14:16
kevkoprometheanfire: Hi, you asked me in email that :   Why would you depend on that?   ...but I have to depend on that review because my tests are failing on upper-constraint ( it is installing 1.11 networkx when tests are failing ) ...or ..am I wrong ?14:20
kevkoprometheanfire: btw ...I rebased the review to master14:20
kevkoprometheanfire: this is taskflow fix https://review.openstack.org/#/c/577833/14:22
prometheanfireya, saw the taskflow fix, very happy about it (since it was above me)14:28
kevkoprometheanfire: what about my question ?14:30
prometheanfirekevko: getting to it, just getting started14:31
kevkoprometheanfire: ok , sorry ;-)14:31
prometheanfiremy comment, 'other projects should depend on this change' was meant to say that other projects like taskflow should depend on it14:32
prometheanfireyour taskflow review does depend on it, so we are good there14:33
kevkoprometheanfire: ok, but I don't know why tests are still not appearing ..it is 84 minutes now from last commit14:33
prometheanfirekevko: because the other projects install releases of taskflow, not from git iirc14:34
prometheanfirecross project testing like this can suck14:34
prometheanfirethe cleanest way forward is to get taskflow to work with 1.11 and 2.1 BOTH, make a release of that, then we can update GR/UC to >2.0/2.114:35
prometheanfireit's also the hardest code wise of course14:36
kevkoprometheanfire: i'm not sure if that is possible14:36
kevkoprometheanfire: like ..nice way14:36
prometheanfiredoing a hard switch to support 2.1 without 1.11 support means a break and a forced merge somewhere14:36
prometheanfiredhellmann: tell me if I'm wrong here :D14:37
dhellmannprometheanfire : you're right. We're going to need some way to support both versions at once if we want to be able to test the change to upper constraints.14:55
dhellmannthat may mean testing the version of networkx and defining classes differently, or wrapping the use of networkx in functions that can test the version and do the right thing, or some other approach14:56
edmondswzigo where would I find pkgos-dh?15:04
zigoedmondsw: In openstack-pkg-tools.15:07
*** rpioso|afk is now known as rpioso15:09
*** edmondsw has quit IRC15:33
*** cjloader has joined #openstack-requirements15:48
*** andreas_s has quit IRC16:05
kevkodhellmann: Are u sure you can't first release taskflow ? Because taskflow is fixing all tests from global-requirements project ...16:06
*** edmondsw has joined #openstack-requirements16:09
dhellmannkevko : if taskflow master does not work with both versions of networkx, then we won't be able to update the constraint to use the new version until we also fix all of the rest of the things that are using networkx. And we won't be able to test any service code with the new networkx until we can update the constraint. So we have a problem sequencing the patches to do the update across multiple repositories.16:17
kevkodhellmann: ok, i rewrite taskflow patch16:19
dhellmannkevko : thank you. and I'm sorry this is so hard. I wish more developers took more care with making API changes in libraries.16:19
dhellmannprometheanfire : do you know off the top of your head which requirements jobs still need to be updated to use python 3?16:23
*** tosky has quit IRC16:29
*** tosky has joined #openstack-requirements16:29
*** jpich has quit IRC16:29
prometheanfiredhellmann: not off the top of my head, at lunch now actually :P16:33
*** udesale has quit IRC16:33
*** edmondsw has quit IRC16:43
*** edmondsw has joined #openstack-requirements16:44
*** edmondsw has quit IRC16:44
dhellmannprometheanfire : ok, I'll dig around16:45
*** dtantsur is now known as dtantsur|afk17:04
*** amoralej is now known as amoralej|off17:29
*** edmondsw has joined #openstack-requirements18:01
*** edmondsw has quit IRC18:06
*** edmondsw has joined #openstack-requirements19:50
*** edmondsw has quit IRC19:54
prometheanfire26 min20:04
tonybIt seems I'm double bookd for 0630 this morning.  I'll kmeep an eye on the meeting but I wont be fully present20:24
tonybdhellmann: in terms of requiremenst "owned" jobs all of them that don't specifically have a "pyXX" in the name, so validate* update, linters etc20:26
dhellmanntonyb : ok, thanks20:26
tonybdhellmann: the only ones I worry about are the "bot" jobs everythgin else would be easy to switch, and fix if needed.20:28
dhellmannyeah, we'll just need to take them one at a time I guess20:28
dhellmannhow do you feel about doing that this cycle?20:29
dhellmannor at least starting20:29
prometheanfiresgtm20:30
prometheanfire#startmeeting requirements20:30
tonybdhellmann: +2+W20:30
openstackMeeting started Wed Jun 27 20:30:11 2018 UTC and is due to finish in 60 minutes.  The chair is prometheanfire. Information about MeetBot at http://wiki.debian.org/MeetBot.20:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:30
*** openstack changes topic to " (Meeting topic: requirements)"20:30
openstackThe meeting name has been set to 'requirements'20:30
prometheanfire#topic rollcall20:30
*** openstack changes topic to "rollcall (Meeting topic: requirements)"20:30
prometheanfiretonyb, prometheanfire, number80, dirk, coolsvap, toabctl, smcginnis, dhellmann20:30
prometheanfireo/20:30
dhellmanno/20:30
smcginniso/20:31
prometheanfire#topic Any controversies in the Queue?20:31
*** openstack changes topic to "Any controversies in the Queue? (Meeting topic: requirements)"20:31
smcginnisWe still have issues with networkx and the google API packages.20:32
prometheanfireya, I forget what was with the google-api packages20:32
prometheanfirewhat was breaking from it (do you remember)?20:33
prometheanfirenetworkx, kevko is helping, which is awesome20:33
smcginnisThe google one was something to do with package renames or something along those lines.20:33
prometheanfireI'm in a constant wait state on these pycrypto reviews     https://review.openstack.org/#/c/575199/ https://review.openstack.org/#/c/575163/20:33
smcginnisI think Gorka said he would take a look into it, but I know he's pretty busy.20:33
prometheanfiresmcginnis: oh, that's fun, but if it's just renames it's not so bad20:33
smcginnisWe may just need to keep it capped until we can deprecate and remove that backup driver if no one can step up to maintain it.20:34
smcginnisThere may be more to it than just a rename. I'm not really sure of the specifics.20:34
prometheanfireya20:34
smcginnisBut history is Google paid a consultant to add the driver, then was never seen from again.20:35
dhellmanndriver where?20:35
prometheanfirelol, remove it, if they don't want to maintain it then too bad20:35
smcginnisdhellmann: The only consumer of the Google API package in question that I know of is for a Cinder backup driver.20:35
dhellmannok20:35
prometheanfireya, I thought that was being looked at for review as well20:36
*** tbarron has joined #openstack-requirements20:37
prometheanfirereview meaning possible removal20:37
smcginnisI should poke jungleboyj on that and see what he would like to do.20:37
prometheanfireyarp20:37
smcginnisThe only down side is I think there may be users of that driver, but we are otherwise pretty strict about our other driver types, so backup shouldn't be any different.20:37
prometheanfireanything else?20:37
dhellmannnothing from me20:38
tbarronhi20:38
prometheanfiretbarron: yo20:39
tbarronare you already on open discussion?20:39
* tbarron came in late20:39
prometheanfiredhellmann: smcginnis what do you think should be done about getting reviews for https://review.openstack.org/#/c/575199/ https://review.openstack.org/#/c/575163/ ?20:39
prometheanfiretbarron: soon20:39
* tbarron goes back to fly-on-wall20:40
dhellmannprometheanfire : have you talked to the PTL?20:40
dhellmannI guess I should say, what have you already tried?20:41
smcginnisLast I heard the team was small, so it may just take some time to get reviews.20:41
prometheanfiredhellmann: mainly tried their channel and ML20:41
prometheanfireI could try adding their ptl to the reviews and/or emailing them directly20:41
dhellmannI would try emailing the PTL directly next20:42
prometheanfirek20:42
prometheanfireI'll do that20:42
dhellmannas smcginnis says, it may take some time to get a review, but at least that way you may get a response about what's going on with the team20:42
smcginnis++20:42
prometheanfireyep20:42
prometheanfireok, anything else before open floor?20:43
smcginnisnope20:43
prometheanfire#topic open floor20:43
*** openstack changes topic to "open floor (Meeting topic: requirements)"20:43
tbarronI was recently attempting a stable/pike backport issue in manila and20:43
tbarronhit a devstack issue building libvirt-python20:44
tbarronthere's an incompatability with the libvirt in the version of CentOS that20:44
tbarronis used20:44
tbarronprobably the OS gets updated (with libvirt) after stable requirements are known to work and fixed20:44
tbarronso that then incompatabilities come in20:45
tbarronanyways, raised https://bugs.launchpad.net/manila/+bug/177897120:45
openstackLaunchpad bug 1778971 in OpenStack Global Requirements "stable/pike libvirt / python-libvirt incompatability" [Undecided,New]20:45
tbarronthis is of course more of an issue with long term releases20:45
tbarronimpacting need to maintain stable/* longer20:45
prometheanfiretbarron: yep, we've seen this before iirc20:46
tbarronthat's it20:46
prometheanfiretonyb: do you remember if we've had to update libvirt for stable branches, I think it's come up before and we've updated it20:46
smcginnisThis all seemed very familiar to me too, but couldn't remember any details.20:46
smcginnisrev20:47
smcginnisoops20:47
prometheanfire:D20:47
tbarronwell I dunno if it happened on stable/* but it looks like ubuntu had a similar issue with libvirt and libvirt-python:20:49
prometheanfiretbarron: I think we can update it, especially if it's breaking gate (centos gate in this case iirc).  I'd like to confirm that we've done it before (and think that we have) but I hope to have a final plan by next week/meeting20:49
tbarronhttps://bugs.launchpad.net/devstack/+bug/163656720:49
smcginnisI see other attemptes: https://review.openstack.org/#/q/project:openstack/requirements+message:libvirt20:49
openstackLaunchpad bug 1636567 in openstack-ansible "devstack mitaka installation fails with error "Running setup.py bdist_wheel for libvirt-python: finished with status 'error'" in Ubuntu 16.10" [High,Fix released] - Assigned to Jesse Pretorius (jesse-pretorius)20:49
tbarronprometheanfire: thanks, it's fine with me for upstream requirements to proceed deliberately, i've20:50
smcginnisBut I agree, for a supported stable release on it's tested platform, we should allow raising it since that platform apparently has.20:50
tonybprometheanfire: sorry we've never done this thing to my recollection20:51
tbarronhad to go on and propose the backport downstream to relieve some customer pain but I'm referencing the upstream (-1 workflow) review so that it will all eventually be consistent20:51
smcginnisIt seems past attempts to do this usually ended up with the stables branch no longer being supported.20:51
prometheanfiresmcginnis: heh, that's true20:52
prometheanfirebut now that we are going longer on LTS we don't have that to 'fall back on'20:52
dhellmannwe should only need to update the constraint, right?20:52
prometheanfireyes20:52
dhellmannwhy is that a problem?20:52
prometheanfireI'm sure there's some libvirt sec bug we can use as an excuse to update it if we really want to stay in policy20:52
dhellmannis libvirt special? or are we saying we don't update any constraints other than our own releases?20:53
dhellmannbecause if we're going to encourage extended maintenance branches we're likely going to need to allow constraint updates like this, right?20:53
prometheanfirewe don't update other than our own releases20:53
dhellmannhmm. ok. I thought we didn't update the others automatically. I didn't realize we never updated them at all.20:54
tbarronone somewhat weird thing is that the constraint for stable/queens is libvirt-python>=3.5.0,!=4.1.0 and 3.10.0 (which works) is selected whereas20:54
tbarronfor stable/pike we have 'libvirt-python>=1.2.5' and libvirt-python===3.5.0 is selected20:55
dhellmannI would expect an older version in an older branch20:55
prometheanfiretbarron: it's just what libvirt was frozen at when we cut the release20:55
dhellmannright20:55
tbarronall possible given the constraints, but 3.5.0 would be legal in stable/queens in which case that would break too20:55
prometheanfireI sent the freezer ptl email btw20:56
dhellmannwe don't update the requirements settings, but we should be able to accept changes to the constraints list20:56
prometheanfiretbarron: queens didn't have lower constraint testing (testing the lower-bounds)20:56
tbarronprometheanfire: ack20:56
dhellmanncan someone remind me why we freeze the constraints like that?20:57
tbarroni'm just saying that it's somewhat accidental that stable/queens isn't also broken20:57
prometheanfiredhellmann: ya, we may have to call it out as valid, but with *reasons* we can update20:57
dhellmannprometheanfire : I don't understand why we are so strict in the first place. I understand why we don't take bot changes. I don't understand why we don't take human-proposed changes.20:57
tonybdhellmann: IIRC there is also a need to bump the minimum but I'm hazy on that20:57
prometheanfiredhellmann: history20:58
tonybdhellmann: if it were just the constraint then I don't know that we'd be having this discussion20:58
dhellmannprometheanfire : I think you're following rules that I didn't envision when we set up this team, so I'm just trying to understand what changed between then and now.20:58
prometheanfiretonyb: you may be right, if the min doesn't work we'd need to change the min, if we change the min, that'd have to propigate out and cause knock-on releases20:58
prometheanfiretonyb: dhellmann I'm fine with just the constraint20:59
* prometheanfire thinks we are talking past eachother20:59
dhellmannmaybe20:59
smcginnisI thought the history was newere outside libs could introduce problems, making stable releases not so stable.21:00
tonybdhellmann: constraints are frozen just because lots broke when we updated them we introduce bugs21:00
dhellmannIIRC, we lock the requirements down because changing those implies incompatible updates and propagates requirements that distros update their packages. We do allow changes to the constraints because that's just our list of what we test with.21:00
prometheanfiretonyb: dhellmann our process allows it already https://docs.openstack.org/project-team-guide/dependency-management.html#stable-branch-maintenance21:01
dhellmannWe don't let the *bot* make wholesale constraint changes because we don't want to keep up with that. We should allow people to propose individual (or small sets of) updates to make the CI system keep working.21:01
tonybprometheanfire: Sure I think I'm just confused due to multitasking21:01
dhellmannok21:01
prometheanfiredhellmann: which is the policy21:01
prometheanfirewe all violently agree :P21:01
dhellmannwoo!21:01
tonybdhellmann: Oh yeah if $person wants to bump a constraint on a stable branch hat's fine21:01
smcginnisYeah, this appears totally fine within the rules described by that first bullet.21:01
prometheanfiretbarron: what version did we need? 3.10.0?21:02
dhellmannok, I thought that's what was happening here, so I was confused about why it needed to be discussed. :-)21:02
prometheanfiredhellmann: /me shrugs21:02
tbarronprometheanfire: that's what I see working in stable/queens, just empirical21:02
tbarronprometheanfire: with the same CentOS image and same libvirt package21:02
prometheanfiretbarron: you want to propose that or want us to?  it'd need reasoning in the commit message21:03
tbarronprometheanfire: I'd actually like someone experienced to do it and add me to the review so I can learn21:04
tonybThere was some concern about bumping a major version (or 2) but libvirt doesn't semver so meh21:04
prometheanfiretonyb: indeed21:04
tbarronI'll be happy to help out with such stuff going forwards.21:04
prometheanfireok, I'll propose21:04
prometheanfireanything else before I close this out?21:04
tonybnope21:05
tbarronthanks folks21:05
prometheanfire#endmeeting21:06
*** openstack changes topic to "OpenStack Requirements - IRC meetngs on Wednesdays @ 07:00 UTC in here in #openstack-requirements - See agenda @ http://tinyurl.com/h44ryuw - IRC channel is *LOGGED* @ http://tinyurl.com/j38rk24"21:06
openstackMeeting ended Wed Jun 27 21:06:51 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-06-27-20.30.html21:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-06-27-20.30.txt21:06
openstackgerritMatthew Thode proposed openstack/requirements stable/pike: Update libvirt-python to 3.10.0  https://review.openstack.org/57855821:06
openstackLog:            http://eavesdrop.openstack.org/meetings/requirements/2018/requirements.2018-06-27-20.30.log.html21:06
prometheanfiretbarron: ^21:07
prometheanfirein the middle there21:07
tbarronprometheanfire: got it, ty21:07
smcginnistbarron: Oops, I accidentally added you to the wrong review. Ignore that if you got an email.21:08
smcginnisI wish Gerrit had an undo on there.21:08
tbarronsmcginnis: ty anyways, I just added myself to this one.  Think I see how to do it going forwards.21:09
smcginnistbarron: Yeah, really nothing intimidating once you see it.21:09
*** cjloader has quit IRC21:10
*** cjloader_ has joined #openstack-requirements21:10
*** cjloader_ has quit IRC21:15
*** qwebirc52177 has joined #openstack-requirements21:18
*** qwebirc52177 has quit IRC21:18
openstackgerritTom Barron proposed openstack/requirements stable/pike: Update libvirt-python to 3.10.0  https://review.openstack.org/57855821:27
*** edmondsw has joined #openstack-requirements21:38
*** edmondsw has quit IRC21:43
openstackgerritTony Breeds proposed openstack/requirements stable/pike: Update libvirt-python to 3.10.0  https://review.openstack.org/57855822:01
*** cjloader has joined #openstack-requirements22:35
*** cjloader has quit IRC22:40
*** edmondsw has joined #openstack-requirements23:27
tonybprometheanfire: just for the record, vene though it's your patch can you +1/+2 ^^^23:28
*** edmondsw has quit IRC23:32
prometheanfiretonyb: I know :P23:32
prometheanfireI just wait for tests23:33
tonybprometheanfire: Ahh okay23:33
*** tosky has quit IRC23:35
*** cjloader has joined #openstack-requirements23:36
*** cjloader has quit IRC23:40

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