Wednesday, 2019-05-08

*** ttsiouts has quit IRC00:06
*** takashin has joined #openstack-placement00:07
openstackgerritChris Dent proposed openstack/placement master: WIP: Remove null root provider protections  https://review.opendev.org/65771601:39
*** cdent has quit IRC01:40
*** tssurya has quit IRC02:16
*** ttsiouts has joined #openstack-placement02:39
*** ttsiouts has quit IRC02:44
*** cdent has joined #openstack-placement04:34
*** cdent has quit IRC05:09
*** dims has quit IRC05:32
*** dims has joined #openstack-placement05:33
*** dims has quit IRC06:16
*** ttsiouts has joined #openstack-placement06:34
*** dims has joined #openstack-placement06:42
*** dims has quit IRC06:49
*** dims has joined #openstack-placement06:54
*** ttsiouts has quit IRC07:33
*** takashin has left #openstack-placement08:00
*** helenafm has joined #openstack-placement09:06
*** ttsiouts has joined #openstack-placement09:06
*** ttsiouts has quit IRC09:11
*** ttsiouts has joined #openstack-placement10:46
*** ttsiouts has quit IRC10:50
*** belmoreira has joined #openstack-placement11:02
*** tssurya has joined #openstack-placement11:02
*** sean-k-mooney has joined #openstack-placement11:18
*** belmoreira has quit IRC11:36
*** belmoreira has joined #openstack-placement11:39
*** helenafm has quit IRC12:05
*** ttsiouts has joined #openstack-placement12:32
*** alex_xu has quit IRC12:43
*** alex_xu has joined #openstack-placement12:48
*** ttsiouts has quit IRC12:53
*** alex_xu has quit IRC13:01
efried_ptostephenfin: Can you suss why https://review.opendev.org/#/c/655665/1 is failing the docs job?13:12
*** efried_pto is now known as efried13:12
stephenfinefried: looks like os-resource-classes haven't specifically stated that python3 be used to build docs http://logs.openstack.org/65/655665/1/check/openstack-tox-docs/9ed3570/job-output.txt.gz#_2019-05-08_12_57_27_56347613:13
stephenfini.e. 'basepython = python3'13:13
stephenfinin tox.ini13:13
efriedstephenfin: Okay, so does it depend which CI node it lands on for the job or did something change since Monday?13:14
efriedBecause https://review.opendev.org/#/c/657464/ passed13:14
stephenfinefried: I'm guessing something changed under the hood, though what I don't know13:15
efriedI can propose a patch on tox.ini I guess...13:16
stephenfinbecause Sphinx 2.0 is Python 3 only so that shouldn't ever work with Python 2.713:16
efriedyah13:16
openstackgerritEric Fried proposed openstack/os-resource-classes master: Use py3 for docs build  https://review.opendev.org/65780013:17
efriedstephenfin: ^13:17
openstackgerritEric Fried proposed openstack/os-resource-classes master: Add MEM_ENCRYPTION_CONTEXT resource class  https://review.opendev.org/65566513:17
efriedthanks stephenfin, will see how this shakes out.13:18
efriedstephenfin: Yeah, https://review.opendev.org/#/c/657464/ failed today, so something must have changed somewhere since Monday night.13:30
openstackgerritEric Fried proposed openstack/os-resource-classes master: Propose standard ACCELERATOR_FPGA resource class  https://review.opendev.org/65746413:30
*** ttsiouts has joined #openstack-placement13:30
efriedstephenfin, gibi: Would y'all mind approving orc gate fix https://review.opendev.org/#/c/657800/ please13:32
stephenfinefried: Before we do, do you want to fix all the other targets? Everything should be using python3 now13:35
stephenfinefried: i.e. put it in '[testenv]' and set the ignore_basepython_conflict option in '[tox]'13:35
efriedstephenfin: Except for the py27 env. That one will ignore the testenv setting, yah?13:37
stephenfinefried: If you set ignore_basepython_conflict, yeah13:37
stephenfinOtherwise tox will complain13:37
*** helenafm has joined #openstack-placement13:38
openstackgerritEric Fried proposed openstack/os-resource-classes master: Use py3 for all* tox targets  https://review.opendev.org/65780013:39
efriedstephenfin: Like that ^13:39
stephenfinyup13:41
*** jaypipes has joined #openstack-placement13:43
*** aspiers has joined #openstack-placement13:46
aspierso/13:46
aspiersI still don't get that sphinx failure13:51
aspiersWhen I run tox -e docs on os-resource-classes locally, it installs Sphinx 1.8.513:51
*** mriedem has joined #openstack-placement13:52
aspierswhich works fine with Python 2.713:52
aspiersWhereas http://logs.openstack.org/65/655665/1/gate/openstack-tox-docs/6da0012/job-output.txt.gz installed 2.0.1 which failed with 2.7.1513:52
*** artom has joined #openstack-placement13:52
aspiersdoc/requirements.txt has sphinx!=1.6.6,!=1.6.7,>=1.6.2 # BSD13:52
aspiersso is this just pip being non-deterministic?13:53
aspiersstephenfin, efried: ^^^13:53
stephenfinaspiers: You tried 'tox -e docs --recreate' ?13:54
aspiersI nuked .tox/docs first13:54
aspierswhich is basically the same thing IIUC13:54
aspiersI guess pip is too stupid to pick the right Sphinx version based on the Python version, but that still doesn't explain why it works for me locally13:55
* aspiers tries with --recreate just to be sure13:56
aspiersyup, still works13:56
aspiersInstalls Sphinx 1.8.513:57
stephenfinaspiers: Yeah, looking at 'openstack/requirements', I see the following:13:57
stephenfin413 | Sphinx===1.8.5;python_version=='2.7'13:57
stephenfin413 | Sphinx===1.8.5;python_version=='2.7'13:57
stephenfin414 | Sphinx===2.0.1;python_version=='3.4'13:58
aspiersAh, so pip *isn't* that stupid13:58
stephenfinlast two for python_version==('3.5'|'3.6') too13:58
aspiersin which case, why the hell is the CI job installing Sphinx 2.x?13:58
stephenfinnot a clue. That's a weird one13:58
aspiersIs the CI job actually using the requirements repo? I see it being cloned, but not used13:59
stephenfinaspiers: Ah, indeed13:59
stephenfinWe're not using upper-constraints13:59
aspiersit's in tox.ini13:59
aspiersbut overridden in [testenv:docs]14:00
stephenfinfor '[testenv] deps', yes14:00
stephenfinyeah, not for the docs version14:00
aspiersthat's the bug14:00
stephenfinyuuup14:00
aspiersso we shouldn't need to require Python 2.714:00
aspiersbut fix this instead14:00
aspierssorry14:00
aspierss/2.7/3/14:00
stephenfinIndeed. Nice spot14:00
aspiersWell, you gave me the right hint by mentioning openstack/requirements ;-)14:01
stephenfinWe still should switch to Python3 but this is the main issue14:01
aspiersRight14:01
aspiersI can submit the fix14:01
stephenfinwanna propose the fix?14:01
aspiers:)14:01
stephenfinjinx14:01
stephenfingot for it14:01
aspiersOK, I guess just by duplicating the upper-constraints line into testenv:docs?14:02
stephenfinyup14:02
stephenfininterestingly, nova is also broken in this way14:02
aspiersooohh14:02
stephenfinactually, no, it's not14:02
aspiers:)14:02
stephenfinbecause we override install_command there instead14:02
aspiersos-traits is correct14:03
stephenfinthough mordred said there's some reason not to do that. idk why14:03
aspiersstephenfin: It still doesn't explain why the CI job chose Sphinx 2.x but my local tox/pip didn't14:05
aspiersso I can't reproduce the issue locally :-/14:06
aspiersah well, I'll submit anyway14:06
stephenfinI wonder if they're using the a different Python version of the tox package itself14:06
aspiersYeah, or pip14:06
stephenfins/the //14:06
stephenfinyup14:06
stephenfinI'd rather it did fail everywhere, tbh. At least that way we'd spot the breakages14:07
aspiersRight :)14:07
*** belmoreira has quit IRC14:08
openstackgerritAdam Spiers proposed openstack/os-resource-classes master: Add missing upper-constraints.txt to deps in docs testenv  https://review.opendev.org/65781514:13
aspiersstephenfin: ^^^14:13
aspiersOK, back in ~1514:13
aspiersefried: ^^^14:13
efriedaspiers: +A14:25
openstackgerritEric Fried proposed openstack/os-resource-classes master: Add MEM_ENCRYPTION_CONTEXT resource class  https://review.opendev.org/65566514:26
efriedmriedem: Mind pushing https://review.opendev.org/#/c/657800/ please?14:27
mriedemlooking14:29
mriedemdone14:31
openstackgerritMerged openstack/os-resource-classes master: Add missing upper-constraints.txt to deps in docs testenv  https://review.opendev.org/65781514:37
aspiers\o/14:37
openstackgerritMerged openstack/os-resource-classes master: Use py3 for all* tox targets  https://review.opendev.org/65780014:41
openstackgerritMerged openstack/os-resource-classes master: Add MEM_ENCRYPTION_CONTEXT resource class  https://review.opendev.org/65566514:47
*** belmoreira has joined #openstack-placement14:49
*** artom has quit IRC14:50
*** artom has joined #openstack-placement14:51
openstackgerritEric Fried proposed openstack/os-resource-classes master: Propose standard ACCELERATOR_FPGA resource class  https://review.opendev.org/65746414:52
*** belmoreira has quit IRC15:07
*** ttsiouts has quit IRC15:07
*** ttsiouts has joined #openstack-placement15:12
*** Sundar has joined #openstack-placement15:19
*** altlogbot_0 has quit IRC15:21
*** irclogbot_2 has quit IRC15:22
*** altlogbot_0 has joined #openstack-placement15:22
*** irclogbot_0 has joined #openstack-placement15:24
*** altlogbot_0 has quit IRC15:27
*** altlogbot_0 has joined #openstack-placement15:28
*** irclogbot_0 has quit IRC15:28
*** irclogbot_2 has joined #openstack-placement15:30
*** cdent has joined #openstack-placement15:36
*** e0ne has joined #openstack-placement15:50
*** e0ne has quit IRC15:53
cdentmriedem: do you have any more info than what's currently on https://review.opendev.org/#/c/656448/ about what's up with watcher?16:06
mriedemnot yet no16:08
mriedemand i don't know enough about the watcher internals yet to be able to identify things they are doing with nova that could be replaced with placement16:08
mriedemmy guess is they could use GET /a_c as a pre-check to validate a set of nodes before asking nova to migrate somewhere16:09
mriedemit's also not clear to me how watcher gathers metrics for inventory and allocation data it uses to make decisions16:10
mriedemi mean, i know they have gnocchi/ceilometer/monasca data sources so i'm guessing they rely on those things listening for that info from nova, and then based on that make their decisions16:10
*** e0ne has joined #openstack-placement16:11
*** artom has quit IRC16:18
mriedemi've just been told that we need to use watcher (or write our own - which i'm trying to really avoid) but we need to make sure it scales for a public cloud16:19
mriedemso i'm kind of fumbling in the dark, like a 6th grader at a lock in16:19
*** david-lyle has quit IRC16:19
*** dklyle has joined #openstack-placement16:20
cdentmriedem: that sounds like great type ii fun16:24
*** helenafm has quit IRC16:24
*** e0ne has quit IRC16:26
mriedemi have a decent story about a 6th grade lock in where i was trying to woo a girl and ended the night hunched over a toilet in the gym locker room16:26
mriedemahhh youth16:26
aspiersXD16:27
aspiersSounds about as successful as some of my early attempts16:27
mriedemoh i still "dated" angie for awhile after that night, my powers of charisma could not be stopped - until some time later when i'm sure i was broken up with via one of her friends telling me, or a note or something16:29
aspierslife is harsh16:31
edleafemriedem: The problem Watcher has (or at least *had* when I was working with them) was that even if they knew that a target host had sufficient resources, they had no visibility into the restrictions that were in scheduler filters17:00
edleafeE.g., affinity/anti17:00
edleafeThat was why their ask has been for a way to run potential candidates through the scheduler to get a filtered set that passes whatever restrictions are in place17:01
*** ttsiouts has quit IRC17:10
*** e0ne has joined #openstack-placement17:10
*** e0ne has quit IRC17:12
*** e0ne has joined #openstack-placement17:18
mriedemyeah i thought about that, plus any qualitative things now like traits, and we have these pre-filters for aggregates and such17:18
*** ttsiouts has joined #openstack-placement17:19
*** e0ne has quit IRC17:21
edleafemriedem: Since the placement API is accessible to them, they could handle those queries. The Nova scheduler, though, has no external access17:21
*** ttsiouts has quit IRC17:54
*** e0ne has joined #openstack-placement17:59
*** e0ne has quit IRC18:07
*** ttsiouts has joined #openstack-placement18:09
*** artom has joined #openstack-placement18:10
*** ttsiouts has quit IRC18:14
*** ttsiouts has joined #openstack-placement18:42
*** cdent has quit IRC19:20
*** ttsiouts has quit IRC19:44
*** ttsiouts has joined #openstack-placement19:59
*** cdent has joined #openstack-placement20:03
*** ttsiouts has quit IRC20:04
*** david-lyle has joined #openstack-placement20:12
*** dklyle has quit IRC20:15
*** edleafe has quit IRC20:15
*** evrardjp has quit IRC20:15
*** dansmith has quit IRC20:15
*** edleafe has joined #openstack-placement20:16
*** evrardjp has joined #openstack-placement20:16
*** purplerbot has quit IRC20:17
*** dansmith has joined #openstack-placement20:20
*** ttsiouts has joined #openstack-placement20:37
*** purplerbot has joined #openstack-placement20:40
*** tssurya has quit IRC20:41
*** ttsiouts has quit IRC20:42
*** artom has quit IRC20:44
*** artom has joined #openstack-placement20:45
*** artom has quit IRC20:45
*** cdent has quit IRC20:55
*** cdent has joined #openstack-placement21:00
*** cdent has quit IRC21:08
*** cdent has joined #openstack-placement21:33
openstackgerritEric Fried proposed openstack/os-traits master: Introduce traits for NUMA and NIC subtree affinity  https://review.opendev.org/65789822:09
efriedcdent: Created a Task for ^, not sure if we care to make tasks that granular or not...22:10
efrieduhh, I guess I should have created the Task under os-traits?22:10
efriedNot sure how that works.22:10
cdentif it helps get things done, that's great22:10
cdentwhen you can have tasks in other projects under a story that is in project A22:10
efriedokay, I was able to change the project for that task.22:11
cdentbtw, I create a worklist with nested magic tasks on it: https://storyboard.openstack.org/#!/worklist/62722:11
* efried looks to see if new task magically ended up in same...22:11
efriedyup, did it end up there because you put it there or did it happen automatically cdent?22:11
cdentautomatically22:11
efriedneat22:12
efriedso, let the bikeshedding begin.22:12
cdentthose are "active tasks on story ####"22:12
cdentwhich was far harder to suss out than it should have been22:12
cdentthe deal on those traits is that every numa node and every nic would get them?22:14
cdenti guess automating that is why we have computesr22:14
* cdent gack. i am so tired.22:14
efriedyeah, that's what I'm thinking22:20
efriedit seems like a reasonable use of a trait, to me.22:20
efriedagain, where "trait" means "trait", in the sense of "characteristic", not necessarily "capability".22:21
* cdent nods22:22
*** cdent has quit IRC23:15
openstackgerritEric Fried proposed openstack/placement master: Add NUMANetworkFixture for gabbits  https://review.opendev.org/65746323:19
*** e0ne has joined #openstack-placement23:35
*** ttsiouts has joined #openstack-placement23:41
*** cdent has joined #openstack-placement23:44
*** e0ne has quit IRC23:52

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