Thursday, 2019-02-14

*** tetsuro has joined #openstack-placement00:16
*** mriedem has quit IRC00:29
*** bhagyashris has joined #openstack-placement00:57
*** openstackgerrit has joined #openstack-placement01:24
openstackgerritChris Dent proposed openstack/placement master: DNM: Don't use OVO with allocation candidates  https://review.openstack.org/63663101:24
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO for Allocation and AllocationList  https://review.openstack.org/63669401:24
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO for Usage and UsageList  https://review.openstack.org/63669501:24
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in Consumer object  https://review.openstack.org/63680101:24
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in Project object  https://review.openstack.org/63680201:24
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in User object  https://review.openstack.org/63680301:24
openstackgerritChris Dent proposed openstack/placement master: WIP: Don't use OVO in ResourceClass and ResourceClassList  https://review.openstack.org/63680401:24
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in Trait and TraitList objects  https://review.openstack.org/63680501:24
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO for Inventory and InventoryList  https://review.openstack.org/63680601:24
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO with ResourceProvider and ResourceProviderList  https://review.openstack.org/63680701:24
*** cdent has quit IRC01:42
*** tetsuro has quit IRC05:40
nguyenhai_thanks cdent05:48
*** tetsuro has joined #openstack-placement06:03
*** tetsuro has quit IRC06:05
nguyenhai_after reset the apache2, I met this error: apache2 : Depends: apache2-bin (= 2.4.18-2ubuntu3.9) but 2.4.29-1ubuntu4.2 is to be installed06:19
nguyenhai_please help06:19
*** e0ne has joined #openstack-placement06:29
nguyenhai_apache2 : Depends: apache2-bin (= 2.4.18-2ubuntu3.9) but it is not going to be installed06:44
*** e0ne has quit IRC06:46
nguyenhai_I solved it by modifying the sources.list to compatible with the upgrade Ubuntu :) Thanks all07:08
openstackgerritTetsuro Nakamura proposed openstack/placement master: Trivial: return empty set instead of list  https://review.openstack.org/63684607:37
*** e0ne has joined #openstack-placement08:05
*** e0ne has quit IRC08:08
*** e0ne has joined #openstack-placement08:18
*** e0ne has quit IRC08:18
*** e0ne has joined #openstack-placement08:29
*** e0ne has quit IRC08:35
*** helenafm has joined #openstack-placement08:46
*** helenafm has quit IRC08:50
*** tssurya has joined #openstack-placement08:54
*** helenafm has joined #openstack-placement08:58
*** bhagyashris has quit IRC09:42
*** tetsuro has joined #openstack-placement09:50
*** tetsuro has quit IRC09:51
*** cdent has joined #openstack-placement10:13
openstackgerritsahid proposed openstack/osc-placement master: Change python3.5 job to python3.7 job on Stein+  https://review.openstack.org/61007410:21
openstackgerritsahid proposed openstack/os-traits master: Change python3.5 job to python3.7 job on Stein+  https://review.openstack.org/61006510:22
*** helenafm has quit IRC10:38
*** tetsuro has joined #openstack-placement10:41
*** tetsuro has quit IRC10:42
openstackgerritChris Dent proposed openstack/placement master: DNM: Don't use OVO with allocation candidates  https://review.openstack.org/63663110:49
*** helenafm has joined #openstack-placement11:08
*** vdrok_ has quit IRC11:44
*** vdrok has joined #openstack-placement11:48
*** tetsuro has joined #openstack-placement11:51
*** tetsuro has quit IRC12:16
*** tetsuro has joined #openstack-placement12:19
*** tetsuro has quit IRC12:21
*** tetsuro has joined #openstack-placement12:24
cdentsigh, running the placement unit tests takes about 1/100th of the time it takes to do whatever tox and stestr are getting up to12:46
*** tetsuro has quit IRC12:56
openstackgerritChris Dent proposed openstack/placement master: DNM: Don't use OVO with allocation candidates  https://review.openstack.org/63663112:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO for Allocation and AllocationList  https://review.openstack.org/63669412:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO for Usage and UsageList  https://review.openstack.org/63669512:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in Consumer object  https://review.openstack.org/63680112:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in Project object  https://review.openstack.org/63680212:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in User object  https://review.openstack.org/63680312:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in ResourceClass and ResourceClassList  https://review.openstack.org/63680412:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO in Trait and TraitList objects  https://review.openstack.org/63680512:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO for Inventory and InventoryList  https://review.openstack.org/63680612:57
openstackgerritChris Dent proposed openstack/placement master: Don't use OVO with ResourceProvider and ResourceProviderList  https://review.openstack.org/63680712:57
*** mriedem has joined #openstack-placement13:39
*** s10 has joined #openstack-placement13:48
*** cdent has quit IRC14:04
*** cdent has joined #openstack-placement14:15
cdentjaypipes: in addition to other responses on to your message on the evaluation thread, I pointed to some ovo data (with code)14:48
cdentthanks very much for getting on that thread14:48
cdentit's kind of relief when email actually happens14:48
jaypipescdent: thx for writing it! :)14:48
openstackgerritMerged openstack/nova-specs master: Add more detail and fix code block formatting  https://review.openstack.org/62870215:14
*** s10 has quit IRC15:20
efriedcdent: I think we can fix your tox perf woes, at least some of them, by porting https://review.openstack.org/636378 and https://review.openstack.org/582392 to the placement repo (and you installing tox>=3.11 locally). Gimme a few, I'll propose those...15:47
cdentefried: the bytecode makes that much of a difference in the time to start the env? That's very surprising?15:49
efriedcdent: deleting the bytecode could. Though placement is a pretty small repo, so I wouldn't expect it to be so bad. Worth trying.15:50
cdenti had assumed it was combo of installing/verifying the deps plus test discovery15:51
efriedcdent: There was something else that was the main perf killer. I think it was something about ... yes, deps15:51
efriedcdent: I believe there's a workaround where you can touch a file to make it not check the deps15:51
efriedstephenfin: remind me please ^15:51
efriedcdent: for my part, I have some aliases set up that just run stestr directly. Because I got annoyed with all that and couldn't be arsed to keep remembering the workaround.15:52
stephenfinefried: touch nova.egg-info15:52
efriedcdent: There ya go ^15:52
efriedthanks stephenfin15:52
openstackgerritEric Fried proposed openstack/placement master: tox: Don't write byte code (maybe)  https://review.openstack.org/63699515:55
cdentthanks efried and stephenfin15:56
cdentyeah, I often switch over to straight stestr or even unittest (depending on what I'm trying to do)15:56
stephenfinnot that that shouldn't be necessary with the newest tox though, which does that exact thing itself15:56
stephenfin3.1.3, apparently15:57
stephenfin(commit 95f5476e31fd20a93b70027efac1f1864b6ed25c)15:57
cdentbut for the "just run all the things case" I feel obliged to do the defined thing and it gets me all narked that the test time is a tenth of a second but there's a minute of waiting15:57
openstackgerritEric Fried proposed openstack/placement master: Use tox 3.1.1 fixes  https://review.openstack.org/63699715:59
efriedah, neat stephenfin, good to know. Lemme go test that, since I done installed 3.7.0 yesterday...16:00
efriedcdent: functional takes longer than a tenth of a second to run....16:02
cdentefried: sure, but unit does not16:02
efriedclose to 15s on my machine16:02
cdentwhich is still pretty awesome, considering16:02
efriedoh, fo sho compared to e.g. nova, which I don't think I've ever waited around for completion.16:02
efriedcdent: new tox does indeed seem to get past the dep check way quicker.16:03
efried$ time tox16:04
efried<snip>16:04
efried  py27: commands succeeded16:04
efried  py36: commands succeeded16:04
efried  functional: commands succeeded16:04
efried  functional-py36: commands succeeded16:04
efried  pep8: commands succeeded16:04
efried  congratulations :)16:04
efriedreal1m6.563s16:04
efrieduser5m45.549s16:04
efriedsys0m9.873s16:04
cdentyup, definitely speeds up dep check16:05
cdentso now it sits on stestr's discovery (fair enough)16:05
cdentthanks16:06
efriedcdent: I haven't caught up on emails yet, so forgive me if already answered, but have you tested / seen any perf improvements from your nix-OVO efforts?16:11
cdentyeah, there's some converations in that in the thread about evaluating what was good or bad in placement, but the short version of the tale is maybe about 50% improvement16:12
efriednoyce!16:12
cdentof course that's very handwavey imprecise16:12
efriedOkay, but even with a massive margin of error it's an unquestionable improvement.16:12
cdentbut the numbers go from 2.5ish to a bit more than 1.ish16:12
cdentyeah16:12
efriedand we16:13
cdentthere are some definite things to fix16:13
efrieddon't16:13
efriedfin16:13
efriedneed16:13
efriedovo here16:13
cdentbut i'd say it's prolly a goer16:13
cdentI mentioned on one of the patches that it might be useful for someone else to do an iteration on the stack16:13
cdentsimply to get some different brain in there16:13
cdentmy style tends to be "make the critical change and then adapt as tests fail"16:14
cdentwhich means things don't come out super clean (yet)16:14
edleafeSpeed is nice, but removing a bunch of magic is even sweeter16:14
cdentyeah, that part is interesting too16:14
cdentthere's been some implicit casting going on16:15
cdentfrom Decimal() to <other> which without ovo there leads to JSON serialization failures16:15
cdent(which was relatively easy to fix)16:15
cdentbut the stuff that happens is now more clear16:16
cdentone thing that was extra clear while doing this work was that from a grepping standpoint, having the different objects in different files (or at least chunked) would have made this easier16:16
cdent(efried my time tox numbers (on hot venvs) is almost exactly the same)16:17
cdent(using new version)16:17
efriedexcellent16:39
cdentefried: your comments about deepcopy, remind me of a thing from the ovo removal stack. In the last one I specificaly draw your attention to some necessary deepcopy changes.16:55
efriedlooking...16:59
efriedmeanwhile - do you have any freakin idea how this could be happening?16:59
efriedcdent: save me looking through all ten patches, where are said comments?17:00
cdentone mo17:00
cdentefried: end of https://review.openstack.org/#/c/636807/2/placement/objects/resource_provider.py two TODO with your nick17:01
cdentand the commit message17:01
efriedwhy my nick?17:02
efriedbecause I introduced the original deepcopyZ?17:02
*** helenafm has quit IRC17:03
cdentI think so, but I may have blamed wrong17:03
efriedno, that looks like my code.17:03
cdentand by 1:30am last night I was shorthanding quite a bit to not forget stuff17:04
efriedokay, duly noted, will investigate - but later. I'm holding up the bw series rn.17:04
cdentyeah, no rush, just didn't want to forget it17:05
*** dims has quit IRC18:47
*** tssurya has quit IRC19:48
efriedcdent: What are you holding out on before opening up the OVO-nixing series to mergeability?20:15
efriedThe grenade and tempest things put it through live scenarios, right, so we're not just relying on ut/functional to be confident it's "right"?20:18
*** e0ne has joined #openstack-placement20:21
cdentefried: a) consensus that we should do it, b) SETTABLE_FIELDS (on rps) is currently disabled and needs to be reinstated in a slightly different form, c) (lower priority) there's a mess of FIXME throughout which are mostly to do with removing duplicatation and general cruft20:41
cdentbut yes, grenade and tempest are making it do real things, and found a real problem (since fixed)20:42
efriedcdent: ack. Finishing up real review of the bottom one.20:42
cdentkewl20:43
efriedcdent: done20:44
cdentthanks, those make sense, mostly20:46
efriedcdent: added one followon to the usage thing.20:47
* cdent nods20:47
efriedcdent: if a), and b) is later in the series, and c) n/a for the bottom patch (which it will be if you go forward with my comments), can you unblock?20:49
*** takashin has joined #openstack-placement20:52
cdentHow could (a "get consensus") be later in the series. Presumably we either de-OVO or don't, not a hybrid?20:54
cdentb is later in the series.20:54
cdentWhat is your goal in unblocking asap?20:54
cdentefried: responded, but mostly I agree with your comments21:00
efriedcdent: reword: Given that (a) is true (i.e. we have consensus); and (b) happens later in the series; ...21:00
efriedGoal in unblocking fast, nothing really, just would rather it got attention while it's fresh in people's minds. With a -2 people will probably be hesitant to render real votes, and then it'll wind up languishing and not getting finished.21:01
efriedAnd this is something I've been wanting to see done for quite a while, so I'm mainly just excited to see it happen.21:02
cdentreckon so, depends on how quickly there's some constructive review on the later bits of the series. There's some commonality in all the *List classes that could be done from the start, or evolve as we go. I don't really have a preference. Probably just being shy because of nova ptsd.21:02
cdentwhat would be most useful to me, from you, is rather than a close review of each patch in series is a superficial review of the whole thing, first21:03
cdentthen go back for the closer review21:03
cdentbut I agree, yes, it would be good to keep the ball rolling. assuming there's no "omg, no" before my EOD tomorrow I'll make sure the earliest patches are unblocked21:04
efriedcdent: well, my superficial review of the whole thing (as it stood at the time) was what yielded "Huge ++ to this idea, Chris."21:14
efriedAnd my comments on the bottom change's commit message go a bit deeper in support of the thing overall.21:15
cdentefried: sure, but right now, though all tests pass it does not have identical behavior to master, especially since at least two tests are disabled21:15
efriedSo I'm not sure there's value in a less-superficial-but-still-not-thorough review21:15
cdenti'm after things like "I think you should make List super class" and "there needs to be a single _updates method"21:16
efriednoted21:25
-openstackstatus- NOTICE: Jobs are failing due to ssh host key mismatches caused by duplicate IPs in a test cloud region. We are disabling the region and will let you know when jobs can be rechecked.21:32
*** e0ne has quit IRC21:48
cdentnight all21:57
*** cdent has quit IRC21:57
-openstackstatus- NOTICE: The test cloud region using duplicate IPs has been removed from nodepool. Jobs can be rechecked now.22:14
openstackgerritMerged openstack/placement master: Trivial: return empty set instead of list  https://review.openstack.org/63684623:07

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