Friday, 2019-07-19

*** igordc has quit IRC00:05
openstackgerritmelanie witt proposed openstack/nova master: Avoid logging traceback when detach device not found  https://review.opendev.org/67164000:05
*** mlavalle has quit IRC00:24
*** igordc has joined #openstack-nova00:24
*** igordc has quit IRC00:30
*** brinzhang has joined #openstack-nova00:30
*** tetsuro has joined #openstack-nova00:30
*** brinzhang_ has joined #openstack-nova00:32
*** sapd1 has joined #openstack-nova00:32
*** dakshina-ilangov has quit IRC00:34
*** TxGirlGeek has joined #openstack-nova00:56
*** BjoernT has joined #openstack-nova00:57
*** BjoernT has quit IRC00:58
*** gyee has quit IRC01:00
*** ricolin_ is now known as ricolin01:04
*** brinzhang_ has quit IRC01:06
*** brinzhang has quit IRC01:06
*** brinzhang has joined #openstack-nova01:07
alex_xukashyap: I replied you on the maillist, looks like ceilometer still using the perf meters, include some of meter isn't just about cmt.01:07
*** imacdonn has quit IRC01:16
*** BjoernT has joined #openstack-nova01:17
*** imacdonn has joined #openstack-nova01:17
*** BjoernT has quit IRC01:24
*** whoami-rajat has joined #openstack-nova01:34
*** JamesBenson has joined #openstack-nova01:55
*** JamesBenson has quit IRC01:59
*** bhagyashris has joined #openstack-nova01:59
*** TxGirlGeek has quit IRC02:05
*** tkajinam has quit IRC02:21
*** tkajinam has joined #openstack-nova02:21
*** tetsuro has quit IRC02:34
openstackgerritTakashi NATSUME proposed openstack/nova master: Fix cleaning up console tokens  https://review.opendev.org/63771602:38
openstackgerritGhanshyam Mann proposed openstack/nova master: Replace "integrated-gate-py3" template with new "integrated-gate-compute"  https://review.opendev.org/67155103:09
*** tbachman has joined #openstack-nova03:09
*** tbachman has quit IRC03:17
*** brinzhang_ has joined #openstack-nova03:18
*** brinzhang has quit IRC03:22
*** psachin has joined #openstack-nova03:37
*** ricolin_ has joined #openstack-nova03:40
*** ricolin has quit IRC03:42
*** rpittau|afk is now known as rpittau03:44
*** udesale has joined #openstack-nova04:04
*** _erlon_ has quit IRC04:12
*** pcaruana has joined #openstack-nova04:37
*** rpittau is now known as rpittau|Imonapla04:38
*** rpittau|Imonapla is now known as rpittau|flying04:38
*** ratailor has joined #openstack-nova04:39
*** dpawlik has joined #openstack-nova04:51
*** abhishekk has joined #openstack-nova04:56
*** Luzi has joined #openstack-nova04:57
*** tkajinam has quit IRC05:01
*** TxGirlGeek has joined #openstack-nova05:21
*** TxGirlGeek has quit IRC05:23
openstackgerritAlex Xu proposed openstack/nova-specs master: Use PCPU and VCPU in one instance  https://review.opendev.org/66865605:29
openstackgerritAlex Xu proposed openstack/nova-specs master: Use PCPU and VCPU in one instance  https://review.opendev.org/66865605:37
*** udesale has quit IRC05:42
*** udesale has joined #openstack-nova05:42
*** mrjk_ has joined #openstack-nova05:46
*** mmethot_ has joined #openstack-nova05:46
*** mchlumsky_ has joined #openstack-nova05:47
*** jistr has quit IRC05:47
*** kaisers has quit IRC05:47
*** mgoddard has quit IRC05:48
*** kaisers has joined #openstack-nova05:48
*** jistr has joined #openstack-nova05:48
*** mmethot has quit IRC05:49
*** mrjk has quit IRC05:49
*** artom has quit IRC05:49
*** mchlumsky has quit IRC05:49
*** mgoddard has joined #openstack-nova05:51
*** gibi has quit IRC05:55
*** tkajinam has joined #openstack-nova05:55
*** rcernin has quit IRC06:02
*** udesale has quit IRC06:12
*** udesale has joined #openstack-nova06:17
*** belmoreira has joined #openstack-nova06:21
*** gibi has joined #openstack-nova06:24
*** maciejjozefczyk has joined #openstack-nova06:39
*** hoonetorg has quit IRC06:39
*** hoonetorg has joined #openstack-nova06:56
*** damien_r has joined #openstack-nova06:58
*** belmoreira has quit IRC07:03
*** belmoreira has joined #openstack-nova07:04
*** belmoreira has quit IRC07:05
*** slaweq has joined #openstack-nova07:09
*** tssurya has joined #openstack-nova07:10
*** zbr has quit IRC07:15
*** zbr has joined #openstack-nova07:16
*** helenafm has joined #openstack-nova07:18
*** ttsiouts has joined #openstack-nova07:26
*** ttsiouts has quit IRC07:36
*** ivve has joined #openstack-nova07:44
*** luksky11 has joined #openstack-nova07:46
*** cdent has joined #openstack-nova07:50
kashyapalex_xu: Will check; thank you07:58
*** ralonsoh has joined #openstack-nova08:00
alex_xukashyap: not sure how ceilometer enable those meters https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/virt/libvirt/inspector.py#L218, since nova doesn't pass those parameter to libvirt08:01
kashyapYeah, was wondering the same; thanks for the code pointer08:01
cdentalex_xu, kashyap : I seem to recall that at some point ceilometer made their own compute node agent rather than listening to nova, because nova didn't want to give all the information that ceilo wanted to get08:04
*** ccamacho has joined #openstack-nova08:04
cdentI may be remembering wrong though. Also I have zero context here so I may be butting in with info that you've already got.08:04
* cdent remembers somewhat fondly the simple days of being a ceilometer core, all those years ago08:04
kashyapcdent: No, I didn't know what you said; that's useful to know08:04
cdentkashyap: you'll definitely want to check me on that. It's a vague memory08:05
kashyapcdent: The context is this patch: https://review.opendev.org/#/c/669129/08:05
kashyapcdent: Linux kernel has removed the underlying infrastructure for Intel "CMT"08:05
cdentseems like it's a done deal then, yeah?08:06
kashyapRight08:06
kashyapWe already today warn if any anyone specifies the "CMT" 'performance' events via Nova's config attributes08:06
cdentkill it! kill it with fire!08:06
kashyapHehe, yeah.08:06
kashyapHowever there are *other* 'perf' events besides the CMT variants.  So I asked on the mailing list if anyone is using them at all.08:07
kashyap[While bearing in mind -discuss list audience does not represent all users ever :D]08:07
*** derekh has joined #openstack-nova08:08
*** ttsiouts has joined #openstack-nova08:08
* cdent has often wondered where the users hang out08:08
*** rpittau|flying is now known as rpittau08:13
alex_xukashyap: we can write other event than cmt https://github.com/openstack/nova/blob/master/nova/conf/libvirt.py#L78508:13
kashyapalex_xu: Right, I wrote that documentation :-)08:14
kashyapI was merely wondering if there are real-world users who are using these other events at all08:14
alex_xukashyap: I missed understand that conf only can can fill cmt, mbm..etc08:15
kashyapNo, not really -- any of the allowable `perf` events by libvirt08:15
alex_xukashyap: yes, that is always a question hard to answer08:15
kashyapHence my question on the list about *non-CMT* events08:15
kashyapRight08:15
alex_xuoops08:17
kashyapalex_xu: Sorry if I didn't phrase it clearly.08:19
*** cdent has quit IRC08:21
*** brinzhang has joined #openstack-nova08:25
*** brinzhang_ has quit IRC08:28
*** yaawang has quit IRC08:47
*** panda is now known as panda|drappt08:50
*** yaawang has joined #openstack-nova08:51
*** tetsuro has joined #openstack-nova08:56
*** ricolin_ is now known as ricolin08:59
*** ag-47 has joined #openstack-nova09:03
*** tkajinam has quit IRC09:05
*** derekh has quit IRC09:09
*** derekh has joined #openstack-nova09:19
*** xek has joined #openstack-nova09:20
openstackgerritzhangyangyang proposed openstack/nova master: Bump the openstackdocstheme extension to 1.20  https://review.opendev.org/67169409:29
*** cdent has joined #openstack-nova09:31
*** takashin has left #openstack-nova09:33
*** tetsuro has quit IRC09:43
*** ttsiouts has quit IRC09:45
*** ttsiouts has joined #openstack-nova09:46
*** artom has joined #openstack-nova09:47
*** artom has quit IRC09:47
*** artom has joined #openstack-nova09:47
*** ttsiouts has quit IRC09:50
*** ttsiouts has joined #openstack-nova09:55
*** bhagyashris has quit IRC10:01
*** udesale has quit IRC10:05
*** udesale has joined #openstack-nova10:06
*** panda|drappt is now known as panda10:14
*** ttsiouts has quit IRC10:23
*** ttsiouts has joined #openstack-nova10:24
*** brault has joined #openstack-nova10:26
*** ttsiouts has quit IRC10:28
*** luksky11 has quit IRC10:28
*** brinzhang has quit IRC10:29
openstackgerritzhangyangyang proposed openstack/nova master: Bump the openstackdocstheme extension to 1.20  https://review.opendev.org/67169410:32
*** brault has quit IRC10:32
*** cdent has quit IRC10:32
*** priteau has joined #openstack-nova10:32
*** priteau has quit IRC10:35
*** priteau has joined #openstack-nova10:37
*** udesale has quit IRC10:44
*** udesale has joined #openstack-nova10:45
*** priteau has quit IRC10:47
*** udesale has quit IRC10:54
*** udesale has joined #openstack-nova10:55
*** abhishekk has quit IRC10:56
*** luksky11 has joined #openstack-nova10:56
*** udesale has quit IRC11:02
*** ag-47 has quit IRC11:02
*** cdent has joined #openstack-nova11:08
*** ttsiouts has joined #openstack-nova11:09
*** tesseract has joined #openstack-nova11:33
artomalex_xu, still around? I figure we can talk here rather than on gerrit, about vpmem and NUMA LM11:35
*** panda is now known as panda|lunch11:42
*** xek has quit IRC11:43
*** xek has joined #openstack-nova11:43
artomSo the current flow is driver.cclm_dest -> rpc.cclm_source -> claim -> driver.numa_config11:44
artomThe claim has to happen before driver.numa_config, and presumably before driver.vpmem_config or whatever you'd call it11:45
artomAnd rpc.cclm_source has to happen before the claim, because the source will tell the destination if it's trying to perform a NUMA live migration11:45
artom(We can't just check instance.numa_topology because the source might be an old compute)11:46
artom(But that could change in a later release)11:46
artomSo really the question is, can rpc.cclm_source happen before driver.cclm_dest11:46
* artom checks that cclm_source needs11:47
artom*what11:47
artomAh, it's passed the dest_check_data11:48
artomSo it doesn't look like we can change the order11:51
artomI'll put all that ^^ in gerrit :)11:51
*** spatel has joined #openstack-nova11:52
*** _erlon_ has joined #openstack-nova12:05
*** spatel has quit IRC12:08
*** belmoreira has joined #openstack-nova12:10
*** udesale has joined #openstack-nova12:21
*** ag-47 has joined #openstack-nova12:30
*** belmoreira has quit IRC12:32
*** belmoreira has joined #openstack-nova12:34
*** panda|lunch is now known as panda12:36
*** spatel has joined #openstack-nova12:36
*** spatel has quit IRC12:42
*** bbowen has joined #openstack-nova12:44
*** udesale has quit IRC12:49
*** belmoreira has quit IRC12:51
*** tssurya has quit IRC12:52
*** ratailor has quit IRC12:52
*** belmoreira has joined #openstack-nova12:52
*** udesale has joined #openstack-nova12:53
*** cdent has quit IRC12:53
*** belmoreira has quit IRC12:56
*** jdillaman has joined #openstack-nova13:00
*** bbowen has quit IRC13:02
*** bbowen has joined #openstack-nova13:02
*** xek has quit IRC13:17
*** eharney has joined #openstack-nova13:21
efriedstephenfin: there's this spec https://review.opendev.org/#/c/668656 about mixing VCPU/PCPU in one instance.13:22
efriedI see you looked at it a few patch sets ago13:22
stephenfinYup. I really don't want that to happen this cycle13:23
efriedoh13:23
efriedwhyzat?13:23
stephenfinI've been working on cpu-resources, which that relies on, all this week and a good bit of last week13:23
efriedyes, obviously that's a hard dep13:23
stephenfinThe upgrade scenario is tricky af13:23
stephenfinbut it's being made easier by some assumptions I can make through a VM being all one kind of CPU13:24
efriedyou mean reshaping allocations?13:24
stephenfinAmong other things, yeah13:24
efriedHm13:24
stephenfinThe reason we dragged that out in the first place was because cpu-resources was horribly complex13:25
efriedyeah, I get that.13:25
efriedcan a VM today have pinned and shared?13:25
stephenfinNot today, no13:25
efriedoh, I see. Yeah, that makes a difference.13:25
stephenfinExcept for emulator threads13:25
stephenfinBut that's not the same thing at all13:25
stephenfinAnyway, I'm not sure why dragging that complexity back in would be something we'd ever want to do13:26
efriedwell13:26
stephenfinThis cycle, that is13:26
efriedthere's a strong customer use case13:26
stephenfinNext cycle, I'm all over that13:26
efriedtbc, the ask on you would be review, not code13:26
stephenfinI figured there might be, aye :)13:26
efriedjust not sure why we would want to say "next cycle" rather than "once cpu-resources is done"13:27
stephenfinTell you what, let's wait til I have code up13:27
stephenfinHa, jinx13:27
efriedwhich may wind up being the same thing, but ... yeah13:27
efriedexcept that spec freeze is next week13:28
stephenfinYeah, I'd like to wait to see how cpu-resources goes before committing to anything13:28
stephenfinI wanted to have that up this week but unit test coupling is killing me13:28
stephenfinand I haven't even started on the reshape13:28
efriedas you well know, approving a spec for this release doesn't "commit" us to getting it in this release.13:28
stephenfinTechnically, no, but it does send the wrong message to people that aren't as involved in nova as we are13:29
stephenfin(PMs)13:29
*** belmoreira has joined #openstack-nova13:29
efriedIt would be a better story for Alex et al if they could go back and tell their downstream "approved, but considerable risk due to deps" than "no chance in Train".13:29
efriedyeah, Alex and I can manage PM expectations :)13:29
stephenfinSuggesting we think this can land when I, for example, have very little confidence that it will13:29
stephenfinOh, I'm worried about my PM :P13:29
efriedokay. Alex and I can't manage your PM.13:30
stephenfinNot sure anyone can, heh13:30
stephenfinAnyway, not really the point13:30
stephenfinAs above, I'm not confident about landing that feature, but if the ask is to just review the spec, I can do that13:31
stephenfinThough not today. I want to keep chipping away at these unit tests and hopefully get the first few patches pushed13:31
efriedI think it would be a good step if we can get you & sean-k-mooney agreeing to the design itself, before spec freeze.13:32
stephenfinYeah, that makes sense13:33
efriedThen we can armwrestle over whether it makes sense to merge it for Train with the caveat of high risk, or merge it in backlog/13:33
stephenfinOkay, I can set aside time to do that early next week, maybe in person with sean-k-mooney13:33
efriedthank you sir13:33
efriedand with alex_xu13:33
sean-k-mooneysorry was away form my laptop what was the context?13:34
stephenfinIn person might be tough there, but sure :)13:34
efriedeasier for you than for me.13:34
sean-k-mooneyefried: i think he ment alex13:34
efriedsean-k-mooney: we're talking about the mixed PCPU/VCPU spec13:34
sean-k-mooneyoh ok13:34
efriedTLDR, stephenfin and I both agree it would be quite high risk for Train, and need to decide whether we want to merge it with that caveat or take a hard line and explicitly punt it. But in either case, I would like to see the design sorted before spec freeze, so we merge it either to train/ or backlog/.13:35
sean-k-mooneyfor what its worth i think we could do that but im concerned with the scope. e.g. if we had completed teh rest fo the cpu stuff by m2 i would have been fine with it13:35
sean-k-mooneyefried: ok13:36
sean-k-mooneyill look at it again13:36
efriedthanks13:36
sean-k-mooneyi think at most we only need 1 extraspec13:36
sean-k-mooneynot the two that are proposed. and i would prefer it to be a new one rather then messing with hw:cpu_policy13:37
sean-k-mooneyspec freeze is wednesday right?13:37
sean-k-mooneyor thrusday? next week in either case13:37
stephenfinI'd rather we used 'resources:VCPU' and 'resources:PCPU' but I don't recall why that wasn't chosen again13:38
stephenfinI need to look at it again13:38
stephenfinnext week though!13:38
sean-k-mooneystephenfin: because we never want people ot use resocues: driectly and that does not provide a way to say which cpus are the pinned ones13:38
stephenfinThat's the one13:39
stephenfinjaypipes will be turning over in his OpenStack grave though13:39
efriedFWIW at every turn I'm finding I prefer using non-Placement-isms in the flavor, that get translated internally to Placement-isms.13:41
efriedparticularly since we have the request_filter framework now.13:42
*** ttsiouts has quit IRC13:42
sean-k-mooneythe main disadvandate to useing the placment stuff direcly is if the modeling in placment chagnes you have to chagne your flavors13:42
efriedthat too13:42
efriedanother big one is that you sometimes don't know enough at flavor time to construct all the proper placement-isms.13:43
sean-k-mooneyright13:43
efriedThis will become more and more true as we start splitting out NUMA, devices, bandwidth, etc.13:43
sean-k-mooneythe image can enable pinning or numa13:43
efriedyup13:43
efriedwe have pieces coming together from several places and there will need to be placement syntax tying them together (e.g. affinity)13:44
efriedbut you can't know that until schedule time when all the pieces are assembled.13:44
efriedgibi: you still around?13:44
*** cdent has joined #openstack-nova13:47
*** mchlumsky_ has quit IRC13:47
*** TheJulia is now known as needssleep13:48
*** mchlumsky has joined #openstack-nova13:49
sean-k-mooneyneedssleep: i like the name :) i woke up today thinking it was thursday so i can agree with that statement13:50
gibiefried: yes13:51
efriedgibi: o/13:51
efriedWhat further is needed to secure your +2 on the providers.yaml spec https://review.opendev.org/#/c/612497/ ?13:51
*** igordc has joined #openstack-nova13:52
*** mlavalle has joined #openstack-nova13:52
gibiefried: the '$COMPUTE_NODE' templating seems too much. If we simply allow to identify an RP by name then we can spare the complexity of the templating13:53
sean-k-mooneygibi: personally i would be fine with suppport both uuid and name13:53
gibiefried: if the rest of the team feels ok with the templating I won't stop it13:53
sean-k-mooneyyou would usee uuid if you want to reference non root providers, or create them in the future and name to reference the root provider or any other named one13:54
efriedgibi: I added `name` back to the `identification`13:54
sean-k-mooneyim not oppsed to the templating by the way just my 2cents13:55
* sean-k-mooney time for coffee before meeting13:55
efriedgibi: and `$COMPUTE_NODE` allows us to hit ironic nodes, which (as dansmith convinced me yesterday) you wouldn't want to try to identify by hostname because the nodes managed by this compute can change when the hashring reshuffles.13:55
gibiefried: sorry I stuck with PS12. reading PS 12 now13:55
gibiI mean 1313:56
efriedcool, thanks.13:56
openstackgerrit**** proposed openstack/nova master: Nova: node should be deleted when last service is deleted  https://review.opendev.org/67173113:56
sean-k-mooneyam ^13:57
sean-k-mooneyno ...?13:57
dansmithlol13:57
sean-k-mooneyapperently there is a bluepirnt but the link does not work13:58
gibiefried: so we have more than one node  under a compute service. the admin wants to configure some node specific thing via the yaml file. It works for a while but then the node is moved under another compute service where the yaml file has different config. How this allows the admin to specify config for a single ironic node properly?13:58
efriedgibi: If they want to have a config for "one specific ironic node no matter which compute service it's under" they could deploy the same config (a single file, that identifies that ironic node explicitly) to all compute hosts.13:59
dansmithgibi: yep, if the admin has different files on different nodes, then a rebalance will change inventory, regardless of if they use $COMPUTE_NODE or not.. that'll need to be a ..node: warning probably regardless13:59
sean-k-mooneydansmith: oh its just a bad commit title14:00
dansmithsean-k-mooney: apparently the submitter is a secret agent14:00
dansmithwho cannot reveal their identity14:00
gibiso the templating only helps if the config in the yaml file is not node specific but compute service specific14:00
sean-k-mooneyapparently so14:00
sean-k-mooneytoo bad they didnt update there commit email or username14:01
dansmithgibi: specific to all the nodes managed by that compute, but you have a good point:14:01
gibibut _all_ node changes so it is not well defined14:01
dansmithgibi: some people with different ironic node types would want to have a different selector but still apply one definition to multiple things14:01
efriedgibi: Yes. Or if you know you want all of your ironic nodes in your deployment to have some common characteristic, like a trait. You could effect that by deploying one section with $COMPUTE_NODE to each host instead of all N to each compute host.14:01
dansmiththe identification section presumably offers us the ability to identify nodes by means other than $COMPUTE_NODE or uuid,14:02
efrieddansmith: as of PS13 it allows you to identify by name14:02
efriedearlier revs had a whole panoply of identification mechanisms, but we trimmed it down to the bare bones.14:03
dansmithso that we can say things like "any node managed by this service with inventory of CUSTOM_IRONIC_GOLD would be matched14:03
dansmithefried: name isn't super helpful in this case, but ... yeah14:03
dansmithand that's good for early revs I think14:03
gibiOK, I think I see the use case of the templating now.14:03
efriedbut yes, you make a good case for future expansion of the identification section.14:03
dansmithI'm saying that's a good reason for having identification be a section and not a key14:03
dansmithright14:03
*** belmoreira has quit IRC14:04
gibiwe might need a warning for ironic admins about using the yaml for node specific config14:04
dansmithlike I said, a ..note: somewhere for sure14:04
gibiOK14:04
gibilet me read PS13 through, but I think I'm +2 on the spec14:05
*** Luzi has quit IRC14:05
efriedThanks gibi14:05
*** luksky11 has quit IRC14:06
*** JamesBenson has joined #openstack-nova14:08
*** damien_r has quit IRC14:09
artomdansmith, dunno if you saw efried's adding of yourself to https://review.opendev.org/#/c/671471/, could I pester you some more for it?14:10
gibiefried: does changing 'ensure' to 'additional' keeps the intended behavior idepmotent? I mean if I restart a compute serivce it won't try to re-create the inventory if already exists14:11
dansmithartom: I did not14:11
dansmithgibi: it's still idempotent language to me14:11
efriedgibi: yes, it's just a bikeshed of the word being used. I think I explained the rationale in the comment on PS1214:11
efriedgibi: it's more than just "restart a compute service" -- this thing runs on every periodic14:12
gibidansmith: I more after the behavior. if that is idepmontent then I'm happy14:12
gibiefried: OK. then I'm happy :)14:12
dansmithgibi: same behavior, more descriptive (IMHO) wording14:12
*** JamesBenson has quit IRC14:12
efriedIt makes me happy to make you happy, gibi14:12
gibidansmith: OK. I accept the language change blindly as I'm not a native speakre14:13
dansmithheh14:13
gibi... and try to learn in the process14:13
efrieddon't try to learn too much from s/ensure/additional/14:13
efriedthat way lies madness14:13
dansmithefried: stop mocking me14:14
efriedyou can learn things about Dan, but not about English14:14
efriedjinx14:14
* dansmith scowls14:14
efriedkisses14:14
gibi:)14:14
*** spatel has joined #openstack-nova14:15
gibiI'm +2 on the provider config spec14:19
*** igordc has quit IRC14:20
gibiand I guess it is good time to inform you that I will disappeare for two weeks of vacation starting in an hour14:20
efriedphew, then I'm glad I nabbed you for that +2.  Have a great vacation gibi!14:22
gibiefried: thanks!14:23
cdentenjoy your time off gibi14:28
gibicdent: thanks14:28
dansmithartom: you have to fix your many typos anyway, so I think you should move the code to a single check to LOG.warning on startup and then I'd be +2 if not for needing some diversity on it14:31
artomdansmith, in _init_host?14:32
dansmiththat'd be startup yeah :)14:32
artomYeah, that'd make sense14:32
sean-k-mooneyif you put it in _init_host i would perfonally make it stop the agent booting14:32
dansmithno14:32
artomIt wouldn't stop it14:33
artomBut... it might take a long time14:33
dansmiththis should be a LOG.warning14:33
sean-k-mooneyim fine with it just being a warning to14:33
artomNot sure if that's acceptable14:33
dansmithartom: also a reno, just in case anyone is relying on this to do their homework for them14:33
dansmithartom: how long does this take? I'm not sure why it'd be slow really14:34
artomThe bug's env has > 1000 nics, they timed it to over 2 minutes14:34
*** dpawlik has quit IRC14:34
artom    ==========14:34
artom    $ time python -c "import nova.compute.utils; nova.compute.utils.get_machine_ips()"14:34
artom    real    2m32.642s14:34
artom    user    0m4.358s14:34
artom    sys     2m27.918s14:34
artom    ==========14:34
efriedwow14:34
dansmithwhich thing takes long? listing the nics themselves?14:35
dansmithbecause that really shouldn't take that long14:35
efriedyeah, is there not a quicker way to find out if my IP is on the system?14:35
efriedifconfig -a | grep ??14:35
artomefried, could be that "dumb", yeah. Would we be cool with this?14:35
dansmithif it's the list, then not much can be done, but if it's our processing, we could limit to 100 nics and bail after, or something14:36
artomifconfig isn't on every system nowadays, but `ip` is14:36
efriedconsidering what we're shooting for here, I would be totally fine with something that "dumb".14:36
dansmithno, don't do ip|grep14:36
efriedif we were relying on this for real functionality that would be one thing14:36
dansmiththis  has been in place for four years and one person has complained,14:36
efriedbut this is a best-effort sanity check14:36
dansmithso I think once at startup which is way less impactful should be fine14:36
artomdansmith, well, thousands of nics aren't exactly common :)14:36
dansmithright14:36
dansmithwhich is why it's not a problem to do this for the 99.999% I think14:37
efriedand as dansmith noted in the original, it's possible for it to fail and everything still be alright.14:37
artomI'm just worried there might be something that implicitly relies on compute service starting up in less than a few seconds14:37
dansmithartom: we have tons of things that are long-running in compute startup,14:37
dansmithso that's not a concern14:37
dansmithwe block compute startup until we can talk to conductor in both directions, we clean up failed migrations, do disk IO, etc, etc14:37
artomdansmith, ack, sounds like we have a way forward with moving the warning to _init_host then14:38
artom(dansmith, btw, I suspect it's https://github.com/openstack/nova/blob/master/nova/compute/utils.py#L977 that's the time sink, not https://github.com/openstack/nova/blob/master/nova/compute/utils.py#L975, but that's moot, and unless we ask the reporter we'll never know)14:42
dansmithartom: yeah I just don't know _why_ it'd be slow, unless it's trying to reverse lookup all the addresses too14:42
artomYeah, good question...14:43
openstackgerritEric Fried proposed openstack/nova-specs master: Followup for provider config file spec  https://review.opendev.org/67174914:43
artomIf it was doing reverse lookups I think it'd be slower, because a single loopkup takes forever to timeout14:43
efrieddansmith: Put the ironic NOTE in a fup so as not to lose gibi's +2 ^14:43
dansmithartom: that call is implemented in C even14:44
*** dpawlik has joined #openstack-nova14:46
*** luksky11 has joined #openstack-nova14:46
*** belmoreira has joined #openstack-nova14:46
alex_xustephenfin: sean-k-mooney thanks in person14:47
alex_xusean-k-mooney: buyin your proposal about 1 extraspec and mask14:47
*** dpawlik has quit IRC14:51
alex_xuartom: ah...claim depends on migrate_data, just aware that, I need to dig into your patch more14:52
artomalex_xu, hey, if you find a way to make it work, I'm all for it :)14:52
alex_xuat least understand the dependence...and I pretty sure people will hate that I added a interface call get_vpmems :)14:53
artomalex_xu, yeah, that'd make 2 libvirt-specific interfaces that no other driver uses14:55
alex_xuyea14:55
artomMaybe consolidate them into something like "get_driver_specific_migrate_data"?14:56
artomNot super happy with that either14:56
efriedfwiw, I think we need *something* like this ^14:57
efriedalthough... I thought we already *had* driver-specific migrate data14:58
artomExactly14:58
artomIt's more like... claims-dependant driver-specific14:58
artomWhich is a mouthful14:58
artomOr... post-claim migrate_data14:59
artomWould that work?14:59
openstackgerritStephen Finucane proposed openstack/nova master: Use a less chipper title for release notes  https://review.opendev.org/67175215:00
*** JamesBenson has joined #openstack-nova15:02
artomdriver.migrate_data_from_claim(context, instance, claim)15:02
artomefried, alex_xu ^^ how does that sound?15:02
*** ricolin_ has joined #openstack-nova15:03
*** belmoreira has quit IRC15:03
efriedartom: What are these LiveMigrateData subclasses for, if not for this?15:03
dansmithI'm not following this,15:04
*** ricolin has quit IRC15:04
dansmithbut we do have per-driver migrate data for exactly this reason15:04
artomefried, it's a sequencing problem15:04
dansmithand that's what those subclasses are15:04
artomSee https://review.opendev.org/#/c/634606/44/nova/compute/manager.py@648215:04
artomIt's not a migrate_data class problem, it's "we need to call the driver twice, once for check_can_live_migrate_destination, and once after we've done claims"15:04
artomIn my patch, that second call is very use-case specific "get_dst_numa_config"15:05
sean-k-mooneyfor what its woth we do something similar for sriov15:05
artomalex_xu will need to solve the same problem, so rather than adding "get_vpmem_config" or whatever to the driver interface, we're trying to come up with a more generic single method for that second call to driver15:05
alex_xuI'm trying to figure out why you need the migration_data for the claim15:06
artomOther way around, we need to claim to update the migrate data15:06
artomBecause we get the NUMA topology on the dest host from the claim15:06
*** gibi is now known as gibi_off15:07
alex_xuartom: looks like you only want to know whether instance has numa topo https://review.opendev.org/#/c/634606/44/nova/compute/manager.py@647015:09
sean-k-mooneyfor sriov migration we added https://review.opendev.org/#/c/620115/35/nova/compute/resource_tracker.py which we callin in https://review.opendev.org/#/c/620115/35/nova/conductor/tasks/live_migrate.py15:10
sean-k-mooney* in check_can_live_migrate_destination15:10
*** belmoreira has joined #openstack-nova15:11
artomalex_xu, in my case, yeah15:11
alex_xuartom: I don't understand this https://review.opendev.org/#/c/634606/44/nova/virt/libvirt/driver.py@746315:12
artomalex_xu, it's to handle the N/N-1 problem15:13
alex_xuwhat different with we check instance.numa_topology at dest host compute manager15:13
alex_xuoh, upgrade issue15:13
artomExactly15:13
sean-k-mooney alex_xu old host wont populate that field15:13
artomBut you're right, once we get to U or V or whenever, that's no longer needed15:13
openstackgerrit**** proposed openstack/nova master: Nova: node should be deleted when last service is deleted  https://review.opendev.org/67173115:13
sean-k-mooneywell actuly ignore that15:13
sean-k-mooneythey wont populate it but we need it for other reasons15:14
alex_xudo we need that LM to be fixed in the middle of S to T upgrade15:14
alex_xuif not, then we can just enable the numa LM by the rpc version15:15
artomAre you asking whether we need to support S -> T NUMA LM?15:15
alex_xuwe can only support that LM when all the nodes upgrade to T15:15
sean-k-mooneyalex_xu: we need to assume that not all nodes will be upgrade at teh same time15:15
artomWe do, it's apparently a big thing during upgrades, operators migrate workloads off compute nodes being upgraded15:15
sean-k-mooneyalex_xu: that was discussed at lenght in the spec15:16
artomOr if you're asking "why not check min service version" to determine whether we can NUMA LM...15:16
sean-k-mooneyalex_xu: https://specs.openstack.org/openstack/nova-specs/specs/train/approved/numa-aware-live-migration.html#upgrade-impact15:16
artomYeah, we could do that, and at point it's what was done in the code, but I think dansmith came up with this way, which personally I find more elegant15:16
alex_xuthe min service version is also require all the nodes upgrade to T, right?15:17
artomYeah15:17
artomAlthough perhaps, in the interest of not adding driver interface methods, we could go back to checking min service version, and then we could do the claim before driver.check_can_live_migrate_at_destinaton15:18
artom(I think)15:18
sean-k-mooneywe should not do the claim before that15:18
sean-k-mooneydriver.check_can_live_migrate_at_destinaton is where the claim should be done15:19
alex_xuthat check means, only the source node is new version, then we can do LM?15:19
sean-k-mooneyalex_xu: we can live migrate but we wont update the guest xml15:19
sean-k-mooneyso it will be jsut as broken as before15:20
sean-k-mooneybut it will live migrate succesfully15:20
alex_xusean-k-mooney: so in upgrade, we need to LM from the old to new, then LM from new back to old15:21
sean-k-mooneyyou dont need too15:21
sean-k-mooneywe just wont break that15:21
sean-k-mooneythe sriov migration feature is coded such that it falls back to the old behavior if the info is not available to use teh new flow15:22
sean-k-mooneythe new flow is basically only used when both are new enough but its explained in the table in the spec15:22
alex_xubut I still can't migrate the instance from old to new...that break the first step of upgrade15:23
sean-k-mooneyyou can15:23
alex_xuyou said the xml won't update15:23
sean-k-mooneycorrect15:24
sean-k-mooneyit use the old live migration workflow15:24
artomIt's impossible to update the XML unless both source and dest support it15:24
artomSo we do best effort and revert to previous half-broken behaviour15:24
alex_xuthe instance won't be break?15:24
artomIt might :)15:24
artomThat's why it's currently half-broken15:25
sean-k-mooneythey havent been broken for the last 10 releases15:25
alex_xuhah15:25
sean-k-mooneywhat might happen is two vms get pinned to the same cores15:25
sean-k-mooneybut that could happen before.15:25
artomIt might actually break if it's pinned to CPUs that don't exist on the dest15:25
sean-k-mooneyif the cores do not exist or there is not enough hugepages libvirt fails the migrtion due to the qemu error15:26
alex_xuyea, so...we should ask the user to do that15:26
sean-k-mooneyand it auto reverts15:26
alex_xus/should/shouldn't/15:26
sean-k-mooneythat is the same behavior as today15:26
alex_xuI remember we have a patch stop that LM api call by checking the instance has numa15:27
sean-k-mooneyyep we merged that15:27
artomYeah, it's now disabled by default15:27
sean-k-mooneyso to live migrarte form S->T they need to re enabeld it15:28
sean-k-mooneyalthough i think artom is removing that option in T?15:28
sean-k-mooneyor is that puhsed to U15:28
alex_xuso...we will tell the user, now you can LM your instance again when you upgrade from S to T, but you instance may gone based on lucky :)15:28
artomsean-k-mooney, it's being deprecated but not removed, because of the upgrade impact15:28
artomWe don't want to turn it on by default unless we're sure the whole cloud supports it15:28
sean-k-mooneyalex_xu: the important thing is we do not regres or change any live migration behavior with artom code15:29
alex_xusean-k-mooney: I agree with that...but doesn't mean we should encourge the user to do that15:30
*** zbr is now known as zbr|out15:30
alex_xuspecial for danger thing15:30
sean-k-mooneywe are not encuragin people to do it15:30
sean-k-mooneyif you have numa instance you should cold migrate them or do an inplace upgrade15:30
sean-k-mooneythat is what we will be telling customers15:30
*** luksky11 has quit IRC15:30
alex_xuyes, so we needn't to support src to dest numa instance LM :)15:31
alex_xufor s to t15:31
sean-k-mooneyalex_xu: orginally we didnt15:31
sean-k-mooneybut both i belive dansmith and mriderman wanted the spec changed to the current form15:32
artom(Oh man, M. Riderman)15:32
artomI am lolling right now15:32
* alex_xu not dare to question on dansmith and mriderman :)15:33
sean-k-mooneyactully it look like dansmith didnt review that spec but i know we spoke to him about it15:34
sean-k-mooneyanyway for sriov live migration since it never worked before we have a hard check in the conductor15:35
sean-k-mooneyand fail if both nodes are not knew enough15:35
sean-k-mooneysince live migration wiht hugepages is a thing we support for ovs-dpdk we did not want to break it by blocking it15:36
openstackgerritMerged openstack/nova master: Bump the openstackdocstheme extension to 1.20  https://review.opendev.org/67169415:36
alex_xuI guess the only reason, the user know they have same type machine, and the instances won't break with pinning to same pcpu15:37
sean-k-mooneyalex_xu: uncontidionally blocking old to new migration would be a regression.15:37
alex_xuah..15:38
sean-k-mooneywell if the instance is not pinned but just has hugepages we dont want to break that15:38
alex_xuI see the reason now15:38
artomalex_xu, yeah, I think that's explicitly called out somewhere: NUMA LM is only "guaranteed" to work if you're migrating to an "empty" identical machine, identically configured,15:38
alex_xugot it15:39
sean-k-mooneyin the hugepage case if there are not enoguht free spawning the qemu instace fail on the dest and we abort the migration before we even pause the vm on the source15:40
sean-k-mooneythe same is true if the cores dont exist on the dest15:41
sean-k-mooneyso the only issue that is not caght by that is two vms being pinned to the same host15:41
sean-k-mooney* core15:41
alex_xucan we check the src and dst service version in the conductor?15:41
openstackgerritArtom Lifshitz proposed openstack/nova master: libvirt: move checking CONF.my_ip to init_host()  https://review.opendev.org/67147115:42
sean-k-mooneywe can but why would we15:42
alex_xuemm...I guess we need another param for the rpc15:42
artomalex_xu, that's what I had at some point, Dan talked me out of it15:42
sean-k-mooneywe need the data that is pass back from can live migrate on dest15:42
artomdansmith, efried ^^ (the CONF.my_ip to init_host() thing)15:42
sean-k-mooneyto be able to generate the updated xml15:43
efriedsean-k-mooney: Is https://review.opendev.org/#/c/638680/ still waiting on https://review.opendev.org/#/c/670189/ ?15:43
*** JamesBenson has quit IRC15:43
sean-k-mooneykind of. im not changeing the public interface of the function it calls15:43
sean-k-mooneybut i suspect that if i chekcout that patch locally it will still expode15:44
sean-k-mooneyi can check that quickly.15:44
efriedartom: would you mind adding a teeny unit test that asserts _check_my_ip is called during init_host?15:46
*** JamesBenson has joined #openstack-nova15:48
artomefried, ack, makes sense15:48
efriedartom: I recognize that a unit test for init_host as a whole is missing, and would be an appropriate add, but unrelated...15:49
*** pcaruana has quit IRC15:49
artomefried, hrmm, yeah, went looking, didn't find anything15:49
efriedyeah15:50
artomSo, maybe as a separate fup patch on top?15:50
*** rpittau is now known as rpittau|afk15:50
artomThe full unit test, I mean15:50
efriedsure, that would be great, though I would also just not notice if it never happened15:50
efriedThere are lots of gaps in unit test in libvirt/test_driver15:50
efriedlots15:50
artomMy thinking it, given how much I'll have to mock to just assert this one thing being called, might as well do the full thing15:51
artom*is15:51
sean-k-mooneyefried: its not failing because my kernel does not support sev. so https://review.opendev.org/#/c/638680/27/nova/virt/libvirt/host.py@1066 prevent the call to get_domain_capablities15:51
efriedartom: There are other tests that call init_host but don't mock a zillion things. I didn't look too deeply into how they're doing that, but...15:52
efriedprobably because of FakeLibvirtDriver15:53
artomAh, indeed15:53
efriednaw, even the ones that use real LibvirtDriver with FakeVirtAPI15:53
efriedso, it should be possible to do it without too much mocking.15:53
sean-k-mooneyif i comment out the if i get this trace back15:54
sean-k-mooneyhttp://paste.openstack.org/show/754594/15:54
efriedthough that leads me to wonder how you're getting away with not mocking netifaces.interfaces() and .ifaddresses()15:55
artomget_machines_ips gets mocked out entirely15:55
efriedartom: Is your test actually running netifaces.interfaces() on whatever system you're invoking it on??15:55
efriedyeah, I mean all the other tests that invoke init_host() :)15:55
*** jangutter has quit IRC15:55
artomOh, hah15:56
artomI guess they do?15:56
efriedthat's... not great15:56
efriedunpredictable results on linux, sure failure on other platforms, nah?15:56
artomIt's supposed to be cross-platform15:56
artomBut yeah15:56
efriedNot that I would really expect test_driver to work on another platform anyway, but...15:56
sean-k-mooneyartom: it should not be actully calling it however15:57
efriedso perhaps you need to fixture out get_machine_ips (or netifaces.interfaces) at a higher level15:57
*** helenafm has quit IRC15:57
sean-k-mooneyyou shoudl be able to set up a mock in the setup function once15:57
artomYep15:57
artom;_:15:57
artomAnd here I was thinking I'd get to do a pure removal patch :(15:58
efriedsorry artom. Your karma ran over your dogma.15:58
*** gyee has joined #openstack-nova15:58
artomIs that like my kar running over my dog, just with my ma involved?15:58
efriedjust so16:00
*** ag-47 has quit IRC16:02
efriedsean-k-mooney: I may need some help, or you should bring in a SME, reviewing that get_dowain_capabilities patch. kashyap?16:03
sean-k-mooneysure. i could harden it more then i did but that at least fixes the orignial issue16:05
sean-k-mooneyim still not catching the libvirt exection if we ligitetly misconfigur the config16:05
sean-k-mooneybut we wont explode any more with the defaults16:07
*** belmoreira has quit IRC16:07
sean-k-mooneyefried: do you know if aspires is still working on openstack?16:07
sean-k-mooneyi have not seen them involded in the sev work lately16:08
efriedI haven't seen him in quite a while, but I hope so.16:08
efriedyeah16:08
openstackgerritArtom Lifshitz proposed openstack/nova master: libvirt: move checking CONF.my_ip to init_host()  https://review.opendev.org/67147116:08
sean-k-mooneymaybe i should add Boris Bobrov to the review too since they seam to have taken over the sev stuff16:08
*** bnemec is now known as beekneemech16:09
*** kmalloc is now known as needscoffee16:11
efriedartom: That rev wfm. Just one other thing: do functional tests have the possibility of hitting netifaces now?16:11
artomOK, this isn't a rabbit whole anywhere, it's the pit of hell16:12
artom*hole16:12
artomefried, but yeah, they do, good thought16:12
artomMaybe right up in nova/test.py?16:12
efriedartom: do any func tests use the real libvirt driver?16:13
efriedif they use fake, this is n/a16:13
efriedno, I don't want a libvirt-specific fixture in nova/test.py16:13
artomThey use the fake libvirt API, but real driver IIRC, no?16:13
efried(don't tell me if there are already libvirt-isms dirtying up the base class)16:13
efriedartom: I don't know, I'm still pretty green on all this libvirt stuff.16:14
sean-k-mooneyartom: i dont think so16:14
sean-k-mooneythe unit test in generall dont use the drivers at all16:14
sean-k-mooneythe functional test defualt to the fake dirver16:14
sean-k-mooneyexecpt the function test under the libvirt folder16:14
sean-k-mooneywhich do as you said16:15
sean-k-mooneye.g. fake libvirt api + real libvirt driver16:15
sean-k-mooneyyou could add a test in here somewhare https://github.com/openstack/nova/tree/master/nova/tests/functional/libvirt16:16
artomefried, well, wait a second, we had that before, no?16:16
efriedhad what before?16:16
artomAny migration test that didn't mock out get_host_ip_addr16:16
artomIt ended up calling down to netifaces eventually16:16
efriedseems likely, yeah16:16
sean-k-mooneywe only have 2 migration tests i think16:16
artomSame for functional tests16:16
sean-k-mooneyhttps://github.com/openstack/nova/blob/master/nova/tests/functional/compute/test_live_migration.py16:17
artomI don't think live migration hit that16:18
efriedlet's settle this...16:18
efriedI'm going to write a DNM with a poison fixture that will blow up any test that hits netifaces.interfaces()16:18
efriedand let the gate tell me which tests are affected.16:18
efriedwhich is almost, but not quite, unrelated to your patch.16:19
*** ricolin_ has quit IRC16:19
efriedsince you've expanded the number of code paths in which it could be getting called16:19
artomI'd be OK waiting for that to report before proceeding16:19
artomEven rebasing on top16:19
efriedWell16:19
efriedI'm not sure I want to *keep* the poison fixture16:19
efriedalthough I guess that wouldn't be an awful thing.16:20
artomWell, we're either OK with listing the host interfaces, or we're not :)16:20
artomIf we're not, which seems the case, don't even bother DNM'ing it16:20
efriedyeah, that's a fair point.16:20
efriedokay, stand by16:20
* artom uses this pause to get lunch16:22
*** jmlowe has quit IRC16:24
*** _hemna has joined #openstack-nova16:27
*** beekneemech has quit IRC16:30
*** cdent has quit IRC16:30
*** bnemec has joined #openstack-nova16:35
*** mdbooth_ has joined #openstack-nova16:36
openstackgerritEric Fried proposed openstack/nova master: Poison netifaces.interfaces() in tests  https://review.opendev.org/67177316:38
efriedartom: ^16:38
*** mdbooth has quit IRC16:39
openstackgerritEric Fried proposed openstack/nova master: libvirt: move checking CONF.my_ip to init_host()  https://review.opendev.org/67147116:40
efriedartom: rebased yours on top ^16:40
efriedwe'll see if either/both explode :)16:40
openstackgerritsean mooney proposed openstack/nova master: Libvirt: add support for vPMU configuration.  https://review.opendev.org/67133816:40
sean-k-mooneygibi_off: ill fix the failing tests in ^ on monday so you can ignore it for now16:41
sean-k-mooneyGenericPoisonFixture i like the name :)16:43
artomericyoung, ack, thanks. Don't we already have a DB poison fixture somewhere? If you're making a generic one, should it gobble that up?16:46
artomWhoops, efried ^^16:46
efriedartom: There are two other poison fixtures that I could conceivably roll into this one, but their messages are much more specific and they do more specific things, so I left them alone for now.16:46
artom*snerk* I understand you mean method16:49
artomBut... maybe not have the name of a hard drug in our code? ;)16:49
efriedartom: Heh, yeah, I just didn't want to shadow variable names. It makes my IDE mildly upset, and confuses me.16:52
artomfunc16:53
artom?16:53
efriedI should point out http://eavesdrop.openstack.org/irclogs/%23openstack-nova/%23openstack-nova.2019-07-15.log.html#t2019-07-15T20:49:0816:53
efried(You thought nobody was listening)16:54
artomefried, what I looking at? 1836595?16:54
artomOh, yeah, thank you zhufl ^_^16:54
*** belmoreira has joined #openstack-nova16:55
efrieddansmith: will you be able to get back to (and hopefully close) https://review.opendev.org/612497 (providers.yaml) today?16:56
dansmithhopefully16:56
*** mdbooth_ has quit IRC16:58
*** belmoreira has quit IRC16:58
*** _hemna has quit IRC16:59
*** dustinc_OSCON is now known as dustinc17:06
*** derekh has quit IRC17:10
*** igordc has joined #openstack-nova17:10
*** tbachman has joined #openstack-nova17:22
*** tesseract has quit IRC17:24
*** jmlowe has joined #openstack-nova17:32
*** maciejjozefczyk has quit IRC17:33
*** ralonsoh has quit IRC17:34
*** whoami-rajat has quit IRC17:43
*** udesale has quit IRC17:48
dansmithefried: you wanna fix at least my typo nit and I'll +2+W? No long test run required for these, so a quick bump for a typo seems fine17:51
efrieddansmith: okay, you want me to smash in the fup while I'm at it?17:52
dansmithoh I didn't see the fup, yeah might as well and gibi is +2 there, so ... easy17:54
efrieddansmith: Do you want me to say "exactly one" identification mechanism, or is "at least one" good?17:55
dansmithefried: the point of my comment is "exactly one" is important.. if you say "at least one" you need to define what happens if they put name and uuid and they don't match17:56
efriedright, that would be an error.17:56
efried"exactly one" would restrict us in the future if we wanted to do some kind of pattern matching17:57
efriedname_matches: /pattern/17:57
efriedhas_trait: CUSTOM_FOO17:57
efriedkind of thing17:57
*** xXraphXx has joined #openstack-nova17:57
efriedbut I'm fine either way.17:57
dansmithsure, but as it is today, I would think "exactly one" gets you a crisper definition.. then when you add a match you can say "zero or one of name/uuid and one or more filters" or something like that.. but I don't care whether you go loose or tight, just define the edges if you go loose17:58
dansmithif you want to put this in your fup for bikeshedding I can just +W the bottom one17:59
efrieddansmith: so tbc you're okay if I leave it defined as is but add "error if you specify both and they don't match"?17:59
dansmithI think "at least one" is better than "either" because I'm not sure whether either means "one but not both", but yes, if you want "at least one" and define the edges, that's fine18:00
dansmithbut, what happens if I do $COMPUTE_NODE and name and there's no match? Is that an error because I won't ever do anything, or is that a 'well no match but that's what you asked for' ?18:01
dansmithand, that might be right at startup, but not after a reshuffle,18:02
dansmithand in the zero hour case with ironic, the compute starts up with no nodes at first18:02
dansmithnot trying to complicate this, which is why I thought "exactly one" makes this easier for the moment :)18:02
efriedokay okay18:02
*** bnemec is now known as beekneemech18:04
openstackgerritEric Fried proposed openstack/nova-specs master: Spec: Provider config YAML file  https://review.opendev.org/61249718:04
efrieddansmith: smashed and done ^18:05
* dansmith dusts hands18:06
efried\o/18:06
efriedthanks dansmith18:06
openstackgerritStephen Finucane proposed openstack/nova master: objects: Remove legacy '_from_dict' functions  https://review.opendev.org/53741418:17
openstackgerritStephen Finucane proposed openstack/nova master: objects: Rename 'nova.objects.instance_numa_topology'  https://review.opendev.org/67178918:17
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Remove unnecessary try-catch around 'getCPUMap'  https://review.opendev.org/67179018:17
openstackgerritStephen Finucane proposed openstack/nova master: claims: Remove useless caching  https://review.opendev.org/67179118:17
openstackgerritStephen Finucane proposed openstack/nova master: Add '[compute] cpu_dedicated_set' option  https://review.opendev.org/67179218:17
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Start reporting PCPU inventory to placement  https://review.opendev.org/67179318:17
openstackgerritStephen Finucane proposed openstack/nova master: libvirt: Start reporting 'pcpus' to the resource tracker  https://review.opendev.org/67179418:17
openstackgerritStephen Finucane proposed openstack/nova master: trivial: Rename exception argument  https://review.opendev.org/67179518:17
openstackgerritStephen Finucane proposed openstack/nova master: trivial: Remove unused function parameter  https://review.opendev.org/67179618:17
openstackgerritStephen Finucane proposed openstack/nova master: Remove 'hardware.get_host_numa_usage_from_instance'  https://review.opendev.org/67179718:17
openstackgerritStephen Finucane proposed openstack/nova master: Remove 'hardware.host_topology_and_format_from_host'  https://review.opendev.org/67179818:17
openstackgerritStephen Finucane proposed openstack/nova master: Remove 'hardware.instance_topology_from_instance'  https://review.opendev.org/67179918:17
openstackgerritStephen Finucane proposed openstack/nova master: WIP: hardware: Differentiate between shared and dedicated CPUs  https://review.opendev.org/67180018:17
openstackgerritStephen Finucane proposed openstack/nova master: Add support translating CPU policy extra specs, image meta  https://review.opendev.org/67180118:17
stephenfinefried: FYI ^18:17
efriednice. alex_xu ^18:18
stephenfinThe second to last patch needs a lot more work to handle upgrades properly (tests are failing too) and I still need to do the reshape, but that's where my head's at18:18
* stephenfin -> 🍻18:19
*** bbowen has quit IRC18:24
efrieddansmith: Not sure if you're still following oslo.service SIGHUP, but you may be able to tell whether it's doing the right thing based on the logs I just posted https://review.opendev.org/#/c/641907/18:24
*** factor has joined #openstack-nova18:27
efriedartom: the results are in. So far your patch is going to wind up needing to undo the changes I'm making to the tests as a result. It may end up being more prudent to put the poison patch on top of yours, once yours finishes tests and we find out what *it* will have to change.18:30
artomefried, I don't mind handling any conflicts that come up18:33
artomefried, to put it bluntly, you handle yours, I'll handle mine :P18:34
openstackgerritMerged openstack/nova-specs master: Spec: Provider config YAML file  https://review.opendev.org/61249718:34
efriedThere are only three failures: one func, two unit. All three will be n/a afaict under your patch.18:34
efriedmaybe I should just wait until yours comes back.18:34
efrieddustinc: ----^18:35
artomn/a afaict18:35
artom?18:35
efriedlmk when you want to start talking impl18:35
dustincoh good!18:35
dustincI am back in office today and want to get my freshly failing tests fixed on other, let's start Monday morning?18:36
efriedartom: I mean all three of them come from invoking driver.get_host_ip_addr18:36
efrieddustinc: sure18:36
artomefried, honestly, if it makes your life easier, drop my patch entirely18:36
dustincefried: great, ttyt18:36
efriedartom: I'm not looking for an easy life. I want danger. I want thrills.18:36
artomHave you tried insulting Putin?18:37
artomIt's just... I won't know for sure what needs fixing until I have your full patch in front of me18:38
efriedartom: Here's yours:18:38
efriedhttp://logs.openstack.org/71/671471/5/check/openstack-tox-py27/0282bb0/testr_results.html.gz18:38
efriedhttp://logs.openstack.org/71/671471/5/check/nova-tox-functional/318a334/testr_results.html.gz18:38
artomI dunno, your call18:39
efriedthe only overlap is the functional one, test_cold_migrate_with_physnet, which fails in yours because of init_host and in mine because of get_ip. The fix there might actually be the same.18:39
efriedso18:39
efriedlet's do this18:39
artomGiven that this is latent, we could indeed merge my fix first18:39
efriedfix yours til it passes on top of mine18:39
efriedthen we'll swap them18:39
efriedwhich should actually make mine pass.18:39
efrieddig?18:40
*** luksky11 has joined #openstack-nova18:41
artomefried, right, I think I get you18:41
efriedIt's not exactly latent when your patch goes from 3 netifaces calls to 44 :)18:41
artomYours breaks because of driver.get_host_ip_addr()18:41
artomMine will fix that ^^18:41
efriedcorrect18:41
artomBut it will break others things in the process18:41
efriedcorrect18:41
efrieduntil it doesn't.18:41
artomYes, which is why I'm paid the big bucks, apparently18:42
efriedgotta do something to afford your meth habit18:42
artom"Meth. Why?" is indeed a good anti-drugs slogan18:43
*** jmlowe has quit IRC18:46
*** _hemna has joined #openstack-nova18:55
*** eharney has quit IRC18:57
*** psachin has quit IRC19:20
openstackgerritArtom Lifshitz proposed openstack/nova master: libvirt: move checking CONF.my_ip to init_host()  https://review.opendev.org/67147119:23
openstackgerritArtom Lifshitz proposed openstack/nova master: Poison netifaces.interfaces() in tests  https://review.opendev.org/67177319:23
artomefried, let's wait for Zuul, but I think I got them all19:24
efriedartom: cool. did you reverse them as well?19:24
artomAye19:24
efriedokay. Thanks for sticking with this.19:24
artomNp :)19:24
redkrieghello all, I'm trying to use rescue mode to install windows, but the official iso (which works in a computer when burned) says no bootable device found in rescue mode.  an ubuntu iso works fine on the same host.  has anyone else ever hit this issue?19:27
*** _hemna has quit IRC19:29
*** efried1 has joined #openstack-nova19:33
*** efried has quit IRC19:33
*** efried1 is now known as efried19:33
*** jmlowe has joined #openstack-nova19:36
efriedredkrieg: That's... not exactly a nova issue, is it?19:38
redkriegI don't know if it's something specific to rescue mode's way of mounting isos.  I've been able to use the iso with libvirt in the past.  it's fine, I'll find a more appropriate venue19:40
efriedredkrieg: Sorry, yeah, #openstack is more appropriate for support. This channel is for dev.19:41
*** eharney has joined #openstack-nova19:42
redkriegthanks, I'll ask there19:42
artomefried, hrmm, one thing I forgot to consider was the backport situation19:44
artomThat poison patch isn't going back19:45
efriedartom: that's fine, then, because you switched em.19:45
efriedYou don't rely on the poison patch19:45
efriedand your swizzle of the mocks is appropriate to backport.19:45
artomOh yeah19:45
efriedand I'm not too worried about whether stable branches have other violations we'll be missing.19:45
efriedthough we can always backport the poison patch to find out, then abandon it.19:46
efriedbut it seems pretty unlikely.19:46
artomYeah19:46
artomThanks for your help in all this, btw :)19:46
efriedfor sure19:47
*** betherly has joined #openstack-nova20:00
*** betherly has quit IRC20:05
*** bbowen has joined #openstack-nova20:11
*** ociuhandu has joined #openstack-nova20:28
*** brault has joined #openstack-nova20:33
*** ociuhandu has quit IRC20:50
*** ociuhandu has joined #openstack-nova20:51
*** ociuhandu has quit IRC20:53
*** ociuhandu_ has joined #openstack-nova20:53
*** ociuhandu_ has quit IRC20:54
*** ociuhandu has joined #openstack-nova20:54
*** ociuhandu has quit IRC20:55
*** ociuhandu has joined #openstack-nova20:55
*** ociuhandu has quit IRC20:56
*** ociuhandu_ has joined #openstack-nova20:56
*** betherly has joined #openstack-nova21:00
*** ociuhandu_ has quit IRC21:01
efriedartom: +221:02
artomefried, \o/21:03
efrieddansmith: we got this one all ready for you https://review.opendev.org/#/c/671471/21:04
*** betherly has quit IRC21:05
openstackgerritEric Fried proposed openstack/nova master: Remove @safe_connect from _delete_provider  https://review.opendev.org/67186621:23
*** luksky11 has quit IRC21:23
*** _hemna has joined #openstack-nova21:25
*** _erlon_ has quit IRC21:30
*** betherly has joined #openstack-nova21:31
*** betherly has quit IRC21:35
*** _hemna has quit IRC21:39
openstackgerritEric Fried proposed openstack/nova master: Remove @safe_connect from _delete_provider  https://review.opendev.org/67186621:41
*** brault has quit IRC21:44
*** JamesBenson has quit IRC22:01
openstackgerritEric Fried proposed openstack/nova master: Disambiguate logs in delete_allocation_for_instance  https://review.opendev.org/67186922:03
efriedo/22:03
*** spatel has quit IRC22:04
*** needssleep is now known as TheJulia22:11
*** eharney has quit IRC22:20
*** betherly has joined #openstack-nova22:22
*** betherly has quit IRC22:27
*** gyee has quit IRC22:34
openstackgerritDustin Cowles proposed openstack/nova master: Use SDK for node.list  https://review.opendev.org/65602722:46
openstackgerritDustin Cowles proposed openstack/nova master: Use SDK for validating instance and node  https://review.opendev.org/65602822:46
openstackgerritDustin Cowles proposed openstack/nova master: Use SDK for setting instance id  https://review.opendev.org/65969022:46
openstackgerritDustin Cowles proposed openstack/nova master: Use SDK for add/remove instance info from node  https://review.opendev.org/65969122:46
openstackgerritDustin Cowles proposed openstack/nova master: Use SDK for getting network metadata from node  https://review.opendev.org/67021322:46
*** betherly has joined #openstack-nova22:53
*** gyee has joined #openstack-nova22:57
*** betherly has quit IRC22:58
*** betherly has joined #openstack-nova23:14
*** betherly has quit IRC23:19
*** takamatsu has quit IRC23:31
*** betherly has joined #openstack-nova23:35
*** betherly has quit IRC23:39
*** mlavalle has quit IRC23:46
*** factor has quit IRC23:46
*** factor has joined #openstack-nova23:47
*** igordc has quit IRC23:48

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