Monday, 2018-03-26

*** odyssey4me has quit IRC00:35
*** odyssey4me has joined #openstack-requirements00:35
*** hongbin has joined #openstack-requirements01:12
*** hongbin has quit IRC03:45
*** udesale has joined #openstack-requirements04:35
openstackgerritgaryk proposed openstack/requirements master: Use the correct version for vmware-nsxlib  https://review.openstack.org/55617505:22
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/55599806:18
*** toabctl has joined #openstack-requirements06:32
*** andreas_s has joined #openstack-requirements06:50
*** ralonsoh has joined #openstack-requirements07:26
*** markmcclain has quit IRC07:40
*** dhellmann has quit IRC07:41
openstackgerritMerged openstack/requirements master: Update G-R for oslo.concurrency>=3.26.0  https://review.openstack.org/55598007:51
*** jpich has joined #openstack-requirements07:58
*** finucannot is now known as stephenfin09:03
*** udesale_ has joined #openstack-requirements09:10
*** udesale has quit IRC09:10
*** udesale_ has quit IRC09:15
*** udesale has joined #openstack-requirements09:16
*** dhellmann has joined #openstack-requirements09:31
*** markmcclain has joined #openstack-requirements09:32
*** jpich has quit IRC10:03
*** jpich has joined #openstack-requirements10:08
*** jpich has joined #openstack-requirements10:10
*** jpich has quit IRC10:11
*** jpich has joined #openstack-requirements10:15
*** jpich has quit IRC10:16
*** jpich has joined #openstack-requirements10:17
*** jpich has quit IRC10:21
*** jpich has joined #openstack-requirements10:21
*** jpich has quit IRC10:22
*** jpich has joined #openstack-requirements10:30
*** jpich has quit IRC10:31
*** andreas_s_ has joined #openstack-requirements11:33
*** andreas_s has quit IRC11:35
openstackgerritMerged openstack/requirements master: Bump minimum Django version to 1.11  https://review.openstack.org/55604711:48
*** andreas_s_ has quit IRC12:08
*** andreas_s has joined #openstack-requirements12:09
*** andreas_s has quit IRC12:09
*** andreas_s has joined #openstack-requirements12:09
*** andreas_s_ has joined #openstack-requirements12:12
*** edmondsw has joined #openstack-requirements12:13
*** andreas_s has quit IRC12:15
*** snapiri has quit IRC12:16
*** jpich has joined #openstack-requirements12:18
*** andreas_s has joined #openstack-requirements12:34
*** andreas_s_ has quit IRC12:37
*** odyssey4me has quit IRC12:47
*** odyssey4me has joined #openstack-requirements12:47
*** udesale has quit IRC13:53
*** udesale has joined #openstack-requirements13:55
*** cjloader has joined #openstack-requirements14:24
*** jpich has quit IRC14:58
*** jpich has joined #openstack-requirements15:08
*** jpich has quit IRC15:12
*** jpich has joined #openstack-requirements15:13
*** jpich has quit IRC15:14
*** jpich has joined #openstack-requirements15:15
*** jpich has quit IRC15:15
*** jpich has joined #openstack-requirements15:16
*** jpich has quit IRC15:17
*** jpich has joined #openstack-requirements15:19
*** jpich has quit IRC15:19
*** jpich has joined #openstack-requirements15:25
openstackgerritMatthew Thode proposed openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/55599815:28
*** jpich has quit IRC15:38
*** andreas_s has quit IRC15:39
*** andreas_s has joined #openstack-requirements15:40
*** jpich has joined #openstack-requirements15:48
*** jpich has quit IRC15:48
*** andreas_s has quit IRC15:48
*** jpich has joined #openstack-requirements15:50
*** jpich has quit IRC15:50
*** AJaeger has joined #openstack-requirements15:50
AJaegerrequirements team, please review https://review.openstack.org/555426 - are you fine removing the requirements sync also for stable releases?15:50
AJaegerprometheanfire: ^15:50
*** jpich has joined #openstack-requirements15:51
*** jpich has quit IRC15:52
*** jpich has joined #openstack-requirements15:52
*** andreas_s has joined #openstack-requirements15:54
*** pabelanger has quit IRC15:56
prometheanfirenot for stable15:56
prometheanfireiirc it was only the plan going forward15:56
AJaegerprometheanfire: then -1 please15:59
*** pabelanger has joined #openstack-requirements16:00
*** udesale has quit IRC16:17
*** udesale has joined #openstack-requirements16:17
*** andreas_s has quit IRC16:18
*** andreas_s has joined #openstack-requirements16:22
*** jpich has quit IRC16:32
*** udesale has quit IRC16:35
*** andreas_s has quit IRC16:36
*** andreas_s has joined #openstack-requirements16:55
openstackgerritOpenStack Proposal Bot proposed openstack/requirements master: update constraint for os-brick to new release 2.4.0  https://review.openstack.org/55659017:02
prometheanfiredhellmann: dirk tonyb smcginnis - think it's time to retire newton? https://review.openstack.org/55580217:07
*** ralonsoh has quit IRC17:08
*** andreas_s has quit IRC17:09
*** andreas_s has joined #openstack-requirements17:14
smcginnisprometheanfire: I think it has been retired for most projects, so probably.17:41
smcginnisprometheanfire: tonyb probably has a better handle on where things are on that.17:42
smcginnisBut we said our extended maintenance would start with Ocata, so I think it's probably a good time for newton to go away.17:42
*** andreas_s has quit IRC17:47
prometheanfireyep, agreed17:49
dhellmann++17:49
openstackgerritMerged openstack/requirements master: Use the correct version for vmware-nsxlib  https://review.openstack.org/55617517:57
*** snapiri has joined #openstack-requirements18:58
*** snapiri has quit IRC19:15
*** EmilienM has quit IRC19:57
*** EmilienM has joined #openstack-requirements19:58
*** edmondsw has quit IRC20:21
openstackgerritMerged openstack/requirements master: Updated from generate-constraints  https://review.openstack.org/55599820:25
dhellmannprometheanfire : let me know if/when you have time to talk about https://review.openstack.org/#/c/555426/2 and stable branches20:40
prometheanfiredhellmann: yo, now's good20:41
dhellmannhey20:41
prometheanfiremay even catch both tonyb and dirk20:41
dhellmannhow often do we change the lower bounds of dependencies on stable branches?20:41
prometheanfirelower bounds, never, but we do add exclusions sometimes20:42
* prometheanfire thinks libvirt-python-4.1.0 should be backported to queens/pike20:42
dhellmannhow big of a deal is it to not sync those? because they end up applying to the constraints list either way, right?20:43
prometheanfireit's probably fine, maybe I'm just stuck in my ways20:44
prometheanfireI would like an ack from dirk/tony though20:44
dhellmannoh, yes, we should all agree, definitely20:45
dhellmannand maybe I'm missing an important case20:45
dhellmannit just seems like those should be pretty, well, stable :-)20:45
dhellmannI would be OK with leaving the tools around and just turning off the job20:46
prometheanfirethey are20:46
dhellmannthat way we could do a sync by hand if we have to20:46
prometheanfirehmm, https://review.openstack.org/556642 didn't show up20:46
prometheanfiremaybe I forgot to remove the change-id?20:46
prometheanfiresure20:47
dirkI'll likely be back tomorrow20:47
openstackgerritMerged openstack/requirements master: Drop ordereddict from g-r  https://review.openstack.org/55073220:47
*** edmondsw has joined #openstack-requirements20:47
dirkI haven't had a chance to be concentrated enough to read reviews that are beyond trivial20:48
dhellmannok20:48
dhellmannthe thing I want to avoid is having a bunch of teams with lower-constraints jobs that pass and bot proposed patches that only change requirements lists and not lower-constraints.txt20:48
prometheanfirethat's a good point too20:49
dhellmannin part because I think pip's resolver allows a constraint to be outside of the range (so I need to fix up the patch in the requirements repo)20:51
dhellmannI'll try and do that tomorrow morning20:51
prometheanfireya, uc overrides ALL20:51
dhellmannso we need the check-requirements job to look at the l-c value and ensure it is in the required range20:52
dhellmannI thought pip did that, so didn't implement that change myself20:52
dirkdhellmann: yeah, that's what's confusing me as well. All the validate checks on the g-r.txt need to be repeated now on the projects repo, right?20:53
dhellmannwell, not quite all of them20:53
dirkE.g. only one lower bound, no exclusion below lower bound and so on20:53
dhellmannwe're comparing the local requirements against the g-r list20:53
dhellmannso that will take care of most of the checks, right?20:53
dirkAre we comparing that the r. Lower bound is equal to lc?20:54
dhellmannif I say set B has to be a subset of set A, then you can't have things in B that are not in A20:54
dhellmannno, that's the 1 thing I realize now I need to add20:54
dirkAnd are we checking that all that is in r is also in lc?20:54
dhellmannanything in the local requirements file that is also in the lower constraint list has to have the lower bound match the lower constraint if there is a lower bound20:54
dirkRight, but there isn't a check for that?20:55
dhellmannthere is not today, no20:55
dhellmannthat's what I'm going to do tomorrow20:55
dhellmannand I can add the check that all r are in lc20:55
dirkAlso, the requirements check currently only triggers when certain files are touched20:55
dhellmannthat should still be ok, right?20:56
dhellmannI'm not sure all requirements need to be in lower constraints20:56
dirkIt needs to cover l-c as well, right?20:56
dirkImho they should be20:56
dhellmannall of the things in requirements.txt do, but that job tests all of the various requirements files right now20:56
dhellmannthe doc/requirements.txt items don't need to be20:56
dhellmannoh, I see what you mean about the check job20:57
dirkWhy?20:57
dhellmannyes, I can update it to trigger on the lower-constraints.txt file20:57
dhellmannwhy are the doc settings tested against the g-r list?20:57
dirkBecause we want docs to be buildable with coinstallable deps?20:58
dirkNot sure, wasn't involved in that20:58
dhellmannI guess I can see the benefit of that.20:58
dhellmannthe lower-constraints list isn't meant to be a set of co-installable things, though20:59
dhellmannso we don't need to test the doc settings against the l-c list20:59
dirkAlso, last question from the trivial kind: what if we want to remove an exclude from g-r? We need to manually update all consumers?20:59
dhellmannunder the rules so far, yes, we would have to do that20:59
dhellmannthat's the same as what we have today, right?21:00
dhellmannwell, except that a bot would do it21:00
dhellmannlike I said, we can keep the tools around to automate that, if you want21:00
dirkYes, which is a big work saver21:00
dhellmannwell, ideally we wouldn't need to update all of those projects in the first place21:01
dhellmannwe would update g-r and u-c and that would be it21:01
dirkI didn't quite understand the reason for the lc.txt in the projects yet21:01
dhellmannand then to undo it we can just change those lists again21:01
dhellmannthe l-c file in the project is to test that the project has accurate lower bounds in its requirements files21:01
dirkThat's the other thought I had: what ensures that at the time of a release the git tag being consistent and coinstallable?21:02
dhellmannfor now we're only using unit tests, although projects are free to add functional test jobs, too21:02
dhellmannwhat ensures that today?21:02
dirkAssuming they have mergd the last bot update, the bot update21:02
dhellmanna dsvm gate job, right?21:02
dhellmannno, the bot update does not actually have anything to do with co-installability21:03
dhellmannthe u-c list is the co-installability list21:03
dhellmannthe constraints completely override any range settings from within the projects21:03
dirkSure21:03
dirkBit for users (I heard they exist) only the pip requirements matter21:04
dirkSo those need to be consistent with the constraints and coinstallable with a sensible set of other projects at the time of a release of a module21:04
dhellmannwe want to make those lists as accurate as possible, but we document that the u-c list is our list of things we actually test with21:04
dirkCurrently this is only ensured by freeze periods21:05
*** edmondsw has quit IRC21:05
dhellmannideally this will mean fewer changes to the requirements files within projects21:05
dhellmannand so we should actually stay coinstallable more of the time21:05
dhellmannwe're still going to have a feeze period21:05
dirkAnyway, sorry for speaking up while half being faded out already. I am hopeful to have a look at this when I am back in the office tomorrow21:07
dhellmannyeah, please do. and if you have more detailed questions like this about the process please post on the thread on the mailing list instead of one of the reviews, since it's easier to discuss there21:08
dirkSo the lc.txt in the project are not synced across projects21:08
dhellmannI think I understand your concerns, but I think some are about things we don't promise today and some are things that aren't going to change21:08
dhellmannthat's right. each project has its own lc.txt file21:08
*** edmondsw has joined #openstack-requirements21:08
tonybprometheanfire: No, we can't returen newton.  We did that with mitaka and broke stuff :(21:12
prometheanfiretonyb: I mean just stop accepting changes, not remove the branch21:13
tonybprometheanfire: Oh yeah stable/newton pretty much means auto-abandon21:14
* tonyb is readyign scrollback for the stop syncing on stable discussion21:14
dhellmanntonyb : I'm around for a little while longer if you have comments/questions21:22
tonybdhellmann: I dropped my opinion on the chnage which is "drop the job leave the code"21:22
dhellmannok21:23
dhellmannwfm21:23
tonybdhellmann: so that if we need to we can reasonably easily run an update21:23
dhellmannI will abandon the patches to delete the code21:23
dhellmannsure21:23
tonybdhellmann: it *shouldn't* happen but it probably will :/21:23
tonybdhellmann: Thanks.21:23
openstackgerritDoug Hellmann proposed openstack/requirements master: make the --reqs arg to project-requirements-change.py useful  https://review.openstack.org/55540321:25
dhellmannrebased that fix to keep that one21:25
dirkdhellmann: I appreciate you finally getting a serious dent at working on this, we have not done this for far too long :-/21:26
dhellmannI'm glad I finally have a little time to spend on it21:26
*** edmondsw has quit IRC21:26
dhellmannI'd like to be done by the first milestone21:26
* dhellmann crosses his fingers21:26
dirkdhellmann: yeah, you're correct to say that we didn't guarantee any of that but the bot updates were usually nagging enough so that people merged them21:27
dirkWhich avoided many of the corner cases that we open up to now21:27
dhellmannbut the bot updates didn't actually control whether the projects were coinstallable21:27
dhellmannthey had no effect at all on that21:28
dhellmannok; I'm going to drop offline for the evening. tomorrow morning I will work on the changes to the check job that dirk and I discussed21:28
dirkWell, they ensured that a coinstallable set of versions/deps were within declared deps21:29
dirkdhellmann: thanks, have a nice evening.21:30
*** cjloader has quit IRC22:00
*** cjloader has joined #openstack-requirements22:00
*** cjloader has quit IRC22:04
*** pabelanger has quit IRC23:01
*** pabelanger has joined #openstack-requirements23:01
*** andreas_s has joined #openstack-requirements23:50
*** andreas_s has quit IRC23:54

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