Tuesday, 2019-05-14

*** dklyle has quit IRC00:11
*** zbr_ has joined #openstack-nova00:13
*** zbr has quit IRC00:14
*** itlinux has joined #openstack-nova00:15
*** itlinux has quit IRC00:22
*** itlinux has joined #openstack-nova00:23
*** itlinux has quit IRC00:25
*** itlinux has joined #openstack-nova00:26
*** bbowen has quit IRC00:39
*** itlinux has quit IRC00:41
*** itlinux has joined #openstack-nova00:44
*** itlinux has quit IRC00:47
*** psyton has joined #openstack-nova00:49
*** psyton has quit IRC00:50
*** macza has joined #openstack-nova01:00
*** psyton has joined #openstack-nova01:01
openstackgerritMerged openstack/nova master: Add functional confirm_migration_error test  https://review.opendev.org/65787001:02
*** macza has quit IRC01:04
*** bbowen has joined #openstack-nova01:05
*** brinzhang has joined #openstack-nova01:09
*** ttsiouts has joined #openstack-nova01:22
*** guozijn has joined #openstack-nova01:24
*** bhagyashris has joined #openstack-nova01:25
*** ileixe has joined #openstack-nova01:30
*** dklyle has joined #openstack-nova01:37
*** guozijn has quit IRC01:39
*** guozijn has joined #openstack-nova01:40
*** hongbin has joined #openstack-nova01:49
*** ttsiouts has quit IRC01:54
*** dklyle has quit IRC01:54
*** nicolasbock has quit IRC01:55
*** bbowen has quit IRC02:14
*** BjoernT has joined #openstack-nova02:32
*** BjoernT has quit IRC02:33
*** BjoernT has joined #openstack-nova02:34
*** BjoernT has quit IRC02:37
*** mvkr has quit IRC02:41
*** macza has joined #openstack-nova02:48
*** BjoernT has joined #openstack-nova02:51
*** macza has quit IRC02:52
*** mvkr has joined #openstack-nova02:55
*** whoami-rajat has joined #openstack-nova02:59
*** ttsiouts has joined #openstack-nova03:03
*** sean-k-mooney has quit IRC03:09
*** sean-k-mooney has joined #openstack-nova03:11
*** imacdonn has quit IRC03:24
*** ttsiouts has quit IRC03:35
*** imacdonn has joined #openstack-nova03:39
*** igordc has quit IRC03:44
*** sapd1_x has joined #openstack-nova03:46
*** udesale has joined #openstack-nova03:52
*** ricolin has joined #openstack-nova03:58
*** mvkr has quit IRC04:03
*** ivve has quit IRC04:10
*** macza has joined #openstack-nova04:11
*** macza has quit IRC04:16
*** pcaruana|afk| has joined #openstack-nova04:25
*** hongbin has quit IRC04:29
*** pcaruana|afk| has quit IRC04:35
*** BjoernT has quit IRC04:48
*** BjoernT has joined #openstack-nova04:48
*** janki has joined #openstack-nova05:01
*** ratailor has joined #openstack-nova05:05
*** ivve has joined #openstack-nova05:13
*** dpawlik has joined #openstack-nova05:28
*** ttsiouts has joined #openstack-nova05:33
*** guozijn has quit IRC05:38
*** udesale has quit IRC05:43
*** udesale has joined #openstack-nova05:43
*** BjoernT has quit IRC05:47
*** Luzi has joined #openstack-nova06:02
*** maciejjozefczyk has joined #openstack-nova06:02
*** ttsiouts has quit IRC06:06
*** amodi has quit IRC06:31
*** xek has joined #openstack-nova06:35
*** belmoreira has joined #openstack-nova06:41
*** slaweq has joined #openstack-nova06:52
*** udesale has quit IRC06:52
*** udesale has joined #openstack-nova06:52
*** dpawlik has quit IRC06:57
*** slaweq has quit IRC07:03
*** awalende has joined #openstack-nova07:03
*** tesseract has joined #openstack-nova07:05
*** rcernin has quit IRC07:06
*** pcaruana has joined #openstack-nova07:12
*** helenafm has joined #openstack-nova07:25
*** tssurya has joined #openstack-nova07:25
*** dpawlik has joined #openstack-nova07:28
*** ttsiouts has joined #openstack-nova07:31
*** rpittau|afk is now known as rpittau07:32
openstackgerritBoxiang Zhu proposed openstack/nova master: Fix failure to boot instances with qcow2 format images  https://review.opendev.org/64027107:33
*** jangutter has joined #openstack-nova07:50
*** dtantsur|afk is now known as dtantsur07:54
*** sridharg has joined #openstack-nova07:55
*** ralonsoh has joined #openstack-nova07:58
*** belmoreira has quit IRC07:59
*** tkajinam has quit IRC08:14
*** luksky has joined #openstack-nova08:24
*** jaosorior has quit IRC08:25
*** ttsiouts has quit IRC08:34
*** derekh has joined #openstack-nova08:37
awalendeWhere in the db is stored the volumes that are attached to a specific instance?08:39
*** belmoreira has joined #openstack-nova08:39
awalendeI have a failing instance which can't boot because it tries to attach a non existing volume.08:39
*** priteau has joined #openstack-nova08:41
brinzhangawalende: You can look down the 'block_device_mapping' table.08:46
brinzhangawalende: There may be information about the disk you need with the instance.08:48
awalendeThanks! I found the entry08:51
awalendenow to find out which field to manipulate in order to detach it08:52
awalendeor is it safe to delete the rows with the non existing volume?08:52
*** davidsha has joined #openstack-nova09:02
*** ttsiouts has joined #openstack-nova09:10
*** ratailor_ has joined #openstack-nova09:14
*** ricolin has quit IRC09:14
*** ratailor has quit IRC09:16
openstackgerritBoxiang Zhu proposed openstack/nova master: Add host and hypervisor_hostname flag to create server  https://review.opendev.org/64552009:20
*** bhagyashris has quit IRC09:35
openstackgerritSurya Seetharaman proposed openstack/python-novaclient master: [Docs] Update client docs to add reason and locked options  https://review.opendev.org/65900009:37
*** tssurya has quit IRC09:41
*** jaosorior has joined #openstack-nova09:41
*** tssurya has joined #openstack-nova09:41
*** ttsiouts has quit IRC09:44
*** boxiang has quit IRC09:48
*** belmoreira has quit IRC09:50
*** gibi is now known as gibi_off10:02
*** baderbuddy has joined #openstack-nova10:05
*** ratailor__ has joined #openstack-nova10:06
*** ratailor_ has quit IRC10:09
*** baderbuddy has quit IRC10:13
*** jaosorior has quit IRC10:24
*** shilpasd has joined #openstack-nova10:31
*** tbachman has quit IRC10:43
openstackgerritHamdy Khader proposed openstack/nova master: [WIP] OVS DPDK port representors support  https://review.opendev.org/65878510:50
*** bbowen has joined #openstack-nova10:51
*** bbowen has quit IRC10:56
*** belmoreira has joined #openstack-nova10:56
*** jangutter has quit IRC10:56
*** jaosorior has joined #openstack-nova11:03
*** udesale has quit IRC11:12
*** jangutter has joined #openstack-nova11:31
*** ratailor_ has joined #openstack-nova11:46
*** ratailor__ has quit IRC11:48
*** nicolasbock has joined #openstack-nova11:48
*** slaweq has joined #openstack-nova11:54
*** tbachman has joined #openstack-nova11:54
*** vabada_ is now known as dabadaba11:58
*** dabadaba has quit IRC12:02
openstackgerritHamdy Khader proposed openstack/os-vif master: [WIP] OVS DPDK port representors support  https://review.opendev.org/65878612:05
*** tetsuro has joined #openstack-nova12:09
*** luksky has quit IRC12:10
*** tetsuro has quit IRC12:11
*** udesale has joined #openstack-nova12:14
*** aarents has joined #openstack-nova12:15
*** bbowen has joined #openstack-nova12:16
*** lpetrut has joined #openstack-nova12:19
*** slaweq has quit IRC12:21
*** priteau has quit IRC12:22
*** lpetrut has joined #openstack-nova12:23
*** sridharg has quit IRC12:23
*** derekh has quit IRC12:25
openstackgerritAlexandre arents proposed openstack/nova master: Fix live-migration when glance image deleted  https://review.opendev.org/65905412:29
*** janki has quit IRC12:30
*** sridharg has joined #openstack-nova12:36
*** mchlumsky has joined #openstack-nova12:41
*** davidsha has quit IRC12:44
kashyapalex_xu: Hi, I have abandoned this spec (the `cpu_model_list` thing) after further discussions w/ the QEMU & libvirt folks: https://review.opendev.org/#/c/642030/12:45
*** mchlumsky has quit IRC12:46
*** ratailor_ has quit IRC12:48
*** mriedem has joined #openstack-nova12:49
*** mchlumsky has joined #openstack-nova12:50
*** luksky has joined #openstack-nova12:52
alex_xukashyap: ok, got it12:57
*** jistr is now known as jistr|call12:59
*** ttsiouts has joined #openstack-nova13:02
*** belmoreira has quit IRC13:02
*** brinzhang has quit IRC13:06
*** ttsiouts has quit IRC13:07
*** k4bi has joined #openstack-nova13:12
*** udesale has quit IRC13:14
*** udesale has joined #openstack-nova13:14
*** derekh has joined #openstack-nova13:15
*** lbragstad has joined #openstack-nova13:15
*** ttsiouts has joined #openstack-nova13:26
*** jistr|call is now known as jistr13:30
*** abhishekk has joined #openstack-nova13:30
*** ttsiouts has quit IRC13:30
*** BjoernT has joined #openstack-nova13:34
*** BjoernT has quit IRC13:36
*** BjoernT_ has joined #openstack-nova13:36
*** BjoernT has joined #openstack-nova13:37
*** BjoernT_ has quit IRC13:40
mdboothbauzas: I also thought we might have other bugs like https://review.opendev.org/#/c/658845/, so I posted to the ML earlier13:45
bauzasmdbooth: yup that's why I left a comment13:45
mdboothbauzas: ack13:46
bauzaswe have this bug, so we can fix it, but maybe we should also look at other methods13:46
mdboothbauzas: Indeed13:46
mdboothbauzas: And be generally stricter about not modifying argument data. It causes a bunch of issues, but I think this is the subtlist I've encountered.13:47
mdboothIncidentally, this specific issue breaks the '1 task at a time' guard in n-api for all operations which use task state, which is nearly all of them.13:48
mdbooths/all operations/all instance operations/13:49
openstackgerritSurya Seetharaman proposed openstack/nova master: [Trivial doc change] Admin can overwrite the locked_reason of an owner  https://review.opendev.org/65906713:51
*** jamesdenton has joined #openstack-nova13:52
*** awalende has quit IRC13:53
*** awalende has joined #openstack-nova13:53
kashyapaspiers: You okay with the "plan" at the end here: https://review.opendev.org/#/c/655193/13:56
*** kaisers1 has quit IRC13:56
kashyapalex_xu: If later we decide that we "really need it", we can always restore it.13:57
*** awalende has quit IRC13:58
*** k4bi has quit IRC13:58
*** belmoreira has joined #openstack-nova13:58
*** awalende has joined #openstack-nova13:59
kashyapefried: When you're about, bike-shedding, for the file name in 'os-traits': how about the x86.py --> x86-common.py?  (Or is it "implied"?)14:01
*** awalende has quit IRC14:03
efriedkashyap: We can't change x86.py at this point. And yes, I think common is implied. I would just make an x86 subdirectory with intel.py and amd.py14:03
*** mlavalle has joined #openstack-nova14:03
kashyap(Oh, right.)14:03
kashyapI keep forgetting that "can't ever change" aspect.14:03
kashyapThx.14:03
efriedkashyap: I'm actually not 100% sure of the mechanics. I think you may have to remove x86.py and move the contents to x86/__init__.py14:04
efriedIt's the strings that get produced that aren't allowed to change.14:04
kashyapRight, I'm not sure either.  I'll duke around a bit.  This is my first time tipping toes into this repo14:05
kashyap(Trying not to boil any lakes as "first steps" :D)14:05
sean-k-mooneywhy woudl you move them to __init__.py14:07
sean-k-mooneyjust to not have to type x8614:07
kashyapsean-k-mooney: I don't know, having x86.py file and x86/ directory in the _same_ directory feels "clumsy".14:08
sean-k-mooneyfrom a general style point of view is strongly dislike haveing __init__.py contain any content ever14:08
kashyapsean-k-mooney: I can live with it; but open to any approach that lets us avoid it14:08
sean-k-mooneywe dont currently have an x86 direcotry correct14:09
sean-k-mooneyhttps://github.com/openstack/os-traits/tree/master/os_traits/hw/cpu14:09
sean-k-mooneywe just have the x86.py14:09
sean-k-mooneywhy are you creating a directory14:09
kashyapsean-k-mooney: See the discussion on the change here: https://review.opendev.org/#/c/655193/14:10
kashyapsean-k-mooney: Specifically this remark from Eric on PS2:14:11
kashyap    hw/cpu/x86.py (common to both Intel and AMD)14:11
kashyap    hw/cpu/x86/amd.py (AMD-specific) <== new (but see below)14:11
kashyap    hw/cpu/x86/intel.py (Intel-specific) <== new14:11
efriedsean-k-mooney: os-traits has a precedent for having attributes in __init__.py14:11
sean-k-mooneyim looking but or you do hw/cpu/intel.py hw/cpu/amd.py and hw/cpu/x86.py14:12
sean-k-mooney* or you could do hw/cpu/intel.py hw/cpu/amd.py and hw/cpu/x86.py14:12
efriedsean-k-mooney: Point is, both intel and amd are x8614:12
sean-k-mooneyyes14:12
efriedbut have divergent attributes14:12
efriedlike for this spectre/meltdown stuff14:13
*** abhishekk has quit IRC14:13
sean-k-mooneywell they really should not14:13
*** dklyle has joined #openstack-nova14:13
efriedheh14:13
*** tbachman has quit IRC14:13
sean-k-mooneyat the traits point of view14:13
efriedsean-k-mooney: I mentioned that14:13
efriedbut kashyap shot me down14:13
sean-k-mooneywe shoudl have a common trait where posible14:13
efriedyup, read discussion in that patch.14:13
*** lpetrut has quit IRC14:14
sean-k-mooneykashyap: what was the outcome fo the discussion with openstack security on exposeing thes as traits14:14
kashyapsean-k-mooney: I didn't write to the 'openstack-security' folks.14:14
sean-k-mooneyso before we decided on this chagne we shoudl have that disucssion14:14
kashyapsean-k-mooney: Note: at 'traits point of view", it is impossibel to have "divergent attributes".  See my last comment14:15
kashyapI carefully discussed it with DanPB yesterday, and posted my discussion14:15
*** rpittau is now known as rpittau|afk14:15
*** ratailor has joined #openstack-nova14:16
sean-k-mooneysure but just because danpb sates an opion does not mean we will alway follow it but im reading the comments now :)14:16
efriedpoint is, we need HW_CPU_X86_INTEL_FOO and HW_CPU_X86_AMD_BAR as well as HW_CPU_X86_BAZ. I'm just not sure whether that happens with14:17
efriedhw/cpu/x86/intel.py: FOO14:17
efriedhw/cpu/x86/amd.py: BAR14:17
efriedhw/cpu/x86.py: BAZ14:17
efriedor14:17
efriedhw/cpu/x86/intel.py: FOO14:17
efriedhw/cpu/x86/amd.py: BAR14:17
efriedhw/cpu/x86/__init__.py: BAZ14:17
efriedor we could even leave the existing structure and do14:17
efriedhw/cpu/x86.py: INTEL_FOO14:17
efriedhw/cpu/x86.py: AMD_BAR14:17
efriedhw/cpu/x86.py: BAZ14:17
*** dpawlik has quit IRC14:17
efriededleafe: Do you have an opinion on this?14:17
edleafeThey all come out to the same trait string, right?14:18
sean-k-mooneyyou can do it with all of the above14:18
kashyapsean-k-mooney: No, you misunderstood me.  It's not "because" DanPB said.14:18
kashyapsean-k-mooney: See these two points:14:18
aspiersI'm with sean-k-mooney in that I don't like putting stuff in __init__.py14:18
kashyap  * The benefit of HW_CPU_HAS_SPECTRE_CURE is that it glosses over the14:18
kashyap    difference between the AMD and Intel flag names for the fix ('IBRS' vs14:18
*** Luzi has quit IRC14:18
kashyap    'IBPB').  However, we  likely going to want feature- based traits for14:18
kashyap    other things: AES, PCID, etc.14:18
kashyap  * The HW_CPU_HAS_SPECTRE_CURE is ill-defined :-( since there are many14:18
kashyap    Spectre-related bugs.14:18
kashyapsean-k-mooney: Frankly, we're over-thinking on the generic "traits" thing.14:19
kashyapI want to tackle that separately.  And first get the granular traits in, without discussing this to the ends of the worlds.14:19
sean-k-mooneykashyap: so traits shoudl not may to qemu feature flags directly14:19
mdboothstephenfin: I know you called it a nit, but given that I suspect it's a bug it wasn't caught by flake8 I'm going to respin anyway. Thanks for looking!14:19
sean-k-mooneythere is no reas an IBRS trait cant map to the IBPB feature  on amd and IBRS on intel14:20
kashyapsean-k-mooney: I disagree.14:20
*** tbachman has joined #openstack-nova14:20
stephenfinmdbooth: Go for it. fwiw, I do have a series to update the hacking version we use but I've WIP'd that til the removal of cells v1 is complete14:20
sean-k-mooneypart of os-tratis is to provide a vendor independ set of common traits that can be normalised14:20
edleafeefried: if we're going to be having _INTEL_* and _AMD_* traits, it would make more sense to have them in their own modules14:20
stephenfinThere's enough merge conflicts as it is14:20
sean-k-mooneyand them mapped to plathform specific thing in the virt dirvers14:20
kashyapefried: Yeah, I'd like to know the answer to your earlier question14:21
kashyap(On the structure)14:21
sean-k-mooneyedleafe: we dont really want to add tratis to the __init__.py file in general but we do allow it14:21
kashyapWhy we "don't really want"?14:22
kashyapIf efried says there's a precedence14:22
edleafesean-k-mooney: yeah, that's messier, but it does work14:22
edleafeSeparate modules is cleaner14:22
efriedsean-k-mooney: That's happening all over os-traits. In typical projects I agree it may be best avoided, but when in rome...14:22
sean-k-mooneykashyap: because its condiered an anti pattern in python14:22
kashyapHm14:22
efriedof nine __init__.pyZ in os-traits, five have content.14:23
sean-k-mooneyefried: yes i know14:23
kashyapsean-k-mooney: Also, look at: compute/__init__.py14:23
sean-k-mooneyalthough when i suggested adding namespaces in os-traits intially i was hoping to not use __init__.py14:24
edleafeIf you're creating a directory hierarchy, and need directory-level traits, the only way to do that is in __init__.py14:24
sean-k-mooneyedleafe: yes which is why we use it14:24
openstackgerritMatthew Booth proposed openstack/nova master: Fix retry of instance_update_and_get_original  https://review.opendev.org/65884514:25
efriededleafe: you can't have x86.py and x86/ ?14:25
sean-k-mooneybut do we need hw/cpu/x86/intel.py or just hw/cpu/intel.py14:25
sean-k-mooneyif its an intel specific trait why add x8614:25
efriededleafe: that seems horrible to me because you wouldn't know where to look for your stuff, but is it even legal python?14:25
mdboothbauzas stephenfin: ^^^ Only change is whitespace for stephenfin's nit.14:25
kashyapefried: edleafe: So, does this structure make sense:14:25
kashyap    hw/cpu/x86/amd.py (AMD-specific)14:25
kashyap    hw/cpu/x86/intel.py (Intel-specific)14:25
kashyap    hw/cpu/x86/__init__.py (Common for both AMD and Intel)14:25
kashyap    ---14:25
kashyap    hw/cpu/amd.py (Deprecate it with a comment)14:25
efriedkashyap: Yes, I think that's the right way to go.14:26
sean-k-mooneyi think the opisite14:26
edleafeefried: that would create HW_CPU_X86_X86_FOO, no?14:26
kashyapsean-k-mooney: Also note that there are other vulns. _besides_ Spectre/Meltdown: E.g. "L1TF".14:26
efriedkashyap: And remove x86.py. Current contents go to x86/__init__.py14:26
sean-k-mooneyi would prefer to add an intel.py beside the amd.py14:26
edleafeefried: oh, you mean at the level above?14:26
stephenfinThis feels like a lot of ado about nothing. What's wrong with keeping everything in x86.py again?14:26
kashyapefried: Right (on removing x86.py)14:26
edleafeefried: yeah, that could work14:26
sean-k-mooneyi mean just add an intel.py here https://github.com/openstack/os-traits/tree/master/os_traits/hw/cpu14:26
edleafeBut it's unnecesary14:27
efriededleafe: I meant, is it legal to have: hw/cpu/x86.py and hw/cpu/x86/__init__.py14:27
aspiersstephenfin: stop trying to spoil the bike-shedding fun ;-)14:27
stephenfin:)14:27
kashyapstephenfin: "Nothing"?  It's because traits are "baked in forever", we're having this discussion.  Otherwise, none would bother belaboring.14:27
edleafeefried: yep14:27
kashyapaspiers: Yeah, stephenfin is only aggravating :D14:27
aspierskashyap is right about that, traits much need more care than most stuff14:27
efriedstephenfin: because there are traits that exist only on amd and only on intel.14:27
sean-k-mooneystephenfin: well until openstack security ways in on the security question my current stance is we should add none of these tratis14:28
efriedFrom now on we shall require everyone to read all comments on this patch and pass a quiz before being allowed to participate in the conversation.14:28
kashyapstephenfin: I know you have more than 10 minutes of attention span: have fun reading: https://review.opendev.org/#/c/655193/414:28
aspiersefried: I guess stephenfin's point was about which file they go in, not so much how they're namespaced14:28
aspiersefried: haha good idea!14:28
stephenfinkashyap: Not really. I mean, they're still for x86 architectures, only those from specific companies14:29
stephenfinThrowing everything in x86.py sounds a lot easier than trying to categorize each flag, IMO :)14:29
sean-k-mooneystephenfin: i agree14:29
kashyapsean-k-mooney: I think your stance there is invalid, recall what we discussed before:14:29
kashyap  < efried> kashyap, sean-k-mooney: I'm going to say it's fine to add the traits to os-traits regardless; the vulnerability occurs when we expose them via compute14:29
kashyapstephenfin: Did you read the discussion here: https://review.opendev.org/#/c/655193/ ?14:30
stephenfinI mean, we're not going to have an amd_intel.py file if a flag is only supported by AMD and Intel and not whoever else has an x86 license14:30
kashyap(If not, there's more nuance than just following the IRC discussion here)14:30
stephenfinkashyap: I did and held my tongue because I wan't sure14:30
kashyapHeh14:30
efriedwe have to categorize the intel- and amd-specific ones anyway. The strings that come out in the end are already figured. It's a question of whether to have INTEL_FOO and AMD_BAR in x86.py or have separate namespace dirs.14:30
sean-k-mooneykashyap: my full stance on this is we should not do it peiord but if we must add these i would prefer them to be generic not vender specific and only as a last resouce expose vendor specific tratits14:30
stephenfinbut now that I've seen this, I've decided my first impression made some sense at least14:31
stephenfinsean-k-mooney: Aye, agreed on the latter part of that at least. Not sure about the basis for the former so can't comment14:31
stephenfinefried: Do we? Why?14:32
stephenfin(just for context)14:32
kashyapsean-k-mooney: You seem to be too hung up on 'generic'.  It _doesn't_ fully make sense in this case.14:32
efriedI'll go out on a limb and say that anything x86 that's supported by both AMD and Intel should go into the x86 namespace, and random manufacturer that owns 0.0000001% of the x86 market who doesn't support that feature can just not turn it on.14:32
sean-k-mooneykashyap: i think this is a missue use of traits and im pushing back becasue i dont think you have mad the case of why we should be exposing this in a non generic way14:33
efriedstephenfin: Because some of them are mutually exclusive.14:33
kashyapsean-k-mooney: The case is the vulnerabilities cannot be trivially mapped into 'generic' traits>14:33
sean-k-mooneytraits are ment to be an abstration over hardware and are not intened to enable specifric feature flags in the emulated cpu14:33
efriedwell now I can get behind that ^14:33
kashyapsean-k-mooney: And some people may want to run _without_ "L1TF" (which is Intel-only)14:33
stephenfinefried: OK. How would that manifest itself in a way we care about?14:34
sean-k-mooneykashyap: sure but why do this need to be in placement14:34
sean-k-mooneyas a trait14:34
stephenfin(again, just so I know. Genuine question)14:34
sean-k-mooneykashyap: my concern is that you appear to be trying to use tratis to carry vm configuration in fomation by making the vendor specific when we should be able to provide an abstration here14:35
efriedstephenfin: Apparently there's "has a flag you can turn on to mitigate X vulnerability" with variants of "do it on the CPU" and "do it in virt" and then there's "is manufactured without the vulnerability in the first place so no flags needed". And different variants of those exist depending on amd vs intel.14:35
kashyapsean-k-mooney: No, you're assuming far too much.  This whole discussion "exploded" when I simply noticed a few weeks ago some missing CPU traits.14:36
efriedstephenfin: I had already questioned whether we really cared about those distinctions, as opposed to "vulnerable or not".14:36
efriedapparently we do.14:36
sean-k-mooneyefried: right but the request to turn on the flag shoudl either be in the nova.conf or as a flavor extra spec or as an image proerty14:36
kashyapAnd digigng more, I then thought: "If you have generic CPU flags listed, what about those that provide mitigation for security flaws.)14:36
sean-k-mooneythat flag should not be enabled by addign a required tratit to the flavor or image14:37
efriedsean-k-mooney: Right, but how do you schedule (or avoid scheduling to) a system that is or is not able to enable those flags?14:37
*** tbachman has quit IRC14:37
stephenfinefried: OK, I wasn't aware of that. Thanks14:37
sean-k-mooneywe normalise the vendor diference in the virt dirver to a standard trait that is vendor independed14:37
kashyapstephenfin: Your earlier question is answered in the commit message: "Notes on the "SSB"/"SSBD" confusion"14:38
kashyap(Here: https://review.opendev.org/#/c/655193/)14:38
kashyap(It notes how Intel and AMD addressed the same issue differently.)14:39
dansmithkashyap: are you suggesting traits for flaws, not just traits for cpu flags?14:39
kashyapdansmith: On "traits for flaws", I'm not sure if it makes sense.  For now, all I care about is: all the required CPU flags are captured as traits14:40
kashyapErr, s/required/missing/14:40
sean-k-mooneykashyap: efried suggested generic  HW_CPU_HAS_MELTDOWN_CURE, HW_CPU_HAS_SPECTRE_CURE style traits in teh review14:41
kashyapsean-k-mooney: And did you see my response that I already pasted here?14:41
dansmith:(14:41
sean-k-mooneypersonally i think that is a better solution then what you are suggesting14:41
artomMELTDOWN_CURE sounds like a thing all parents of toddlers need14:41
*** tbachman has joined #openstack-nova14:41
kashyapsean-k-mooney: Huh, you haven't read the response, that I posted, have you:14:42
kashyap  * The benefit of HW_CPU_HAS_SPECTRE_CURE is that it glosses over the14:42
kashyap    difference between the AMD and Intel flag names for the fix ('IBRS' vs14:42
sean-k-mooneyalthoght i woudl personally go with hw_CPU_VULNERABLITY_SPECTER14:42
kashyap    'IBPB').  However, we  likely going to want feature-based traits for14:42
kashyap    other things: AES, PCID, etc.14:42
kashyapGiven the above it doesn't make sense the "generic roll-up traits".14:42
kashyap  * The HW_CPU_HAS_SPECTRE_CURE is ill-defined :-( since there are many14:42
kashyap    Spectre-related bugs.14:42
kashyaps/"sense the"/"sense to have"/14:43
sean-k-mooneyyes i did see that comment14:43
kashyapsean-k-mooney: If you have a _clear_ proposal, please write it as a (not too long) comment in the change, I'd appreciate it.14:43
kashyapFor now, I'll go with the structure I discussed with efried earlier.14:43
sean-k-mooneyok i will. but to be clear adding a required trait should have 0 impact on the xml generation and should not enable a cpu feature flag in the libvirt xml for that cpu feature14:44
sean-k-mooneyif the host is configed in the nova.conf to enable that feature that is fine but reporting/requireing a trait should not change the behavior of the vm form another that was schduled to that host without requiring the traits14:45
dansmithfwiw, I *hate* the "has the cure" trait14:46
kashyapdansmith: Hehe, that's not going to happen :-)14:46
sean-k-mooneydansmith: well what about the other fomulation of hw_cpu_vulnerablity_XYZ14:46
kashyapdansmith: It was a thinking-out-loud point from Eric.14:47
edleafedansmith: it's as bad as "doesn't have the vulnerability" trait14:47
dansmithsean-k-mooney: I don't like that either14:47
sean-k-mooneywhich the cpu feature flags are in another vail14:47
dansmith"is broken" or "was broken" or "has a software fix" are terrible traits to me14:47
sean-k-mooneydansmith: ya i dont like tracking vulnerablity in placement period14:48
dansmithsean-k-mooney: agreen14:48
dansmith*agreed14:48
dansmithI also don't think that tracking cpu flags in placement for non-feature flags makes sense14:48
dansmithAVX2, yes... flags that just imply that a microcode fix has been applied, not so much14:48
sean-k-mooneyi stil am concerned that adding any of the security realted flag give me a vector to upload an image with a require/forbidn trait and target a vulnerable host14:49
*** lpetrut has joined #openstack-nova14:49
dansmithsean-k-mooney: for serious14:49
kashyapdansmith: How about this idea (that I discussed here on PS:4 as "Another Idea" - https://review.opendev.org/#/c/655193/):14:49
kashyapMake Nova check the 'sysfs' (/sys/devices/system/cpu/vulnerabilities) directory for vulnerabilities.  And e.g. if it reports "Vulnerable" (instead of "Mitigation") for Meltdown (or other flaws), print a warning that the host is vulnerable, and on next release refuse to start the VMs14:49
sean-k-mooneydansmith: :)14:49
dansmithkashyap: I have a hard time understanding why this is a nova thing at all.. configs to turn on compatibility as needed makes sense, since we are controlling the definition of the VMs,14:50
sean-k-mooneykashyap: i dont think its novas place to do that14:50
dansmithbut the management of the host-level patching is not our deal, IMHO14:50
dansmithwhat sean-k-mooney said14:50
kashyapdansmith: Nah, we don't _patch_ it.  But isn't it fair game for Nova to tell that: "hey, your host is vulnerable to critical flaws, launching VMs there is dangerous?"14:51
dansmithsame reason we don't refuse to boot instances because we're concerned that our cpu fans are spinning too slowly14:51
dansmithkashyap: not IMHO14:51
kashyapI see.14:51
kashyapJust wondering out loud.  My umbilical cord isn't tied to that idea :-)14:51
sean-k-mooneykashyap: depending on your enviornment (a air gapped secure datacenter) you ligitamately may want to have a vulnerable system for the performace improvments. i agree with dansmith that it should not be novas role to dictate your securety and threat model14:52
kashyapOne would think it's reasonable for Nova to prompt admins to secure their hypervisors.14:53
dansmithsean-k-mooney: yeah, definitely agree.. I have unpatched systems for reasons :)14:53
kashyapsean-k-mooney: Yeah, I've considered that point -- on someone _intentionally_ wanting to run unpatched14:53
kashyap... precisely for the perf reasons.14:53
sean-k-mooneykashyap: you could make the same argument for libvirt if you go that route or qemu14:53
dansmithor fan speed, or cpu temperature, or firmware patch levels, or os patch levels, or ....14:54
kashyapWell, that doesn't make sense in the _common_ case for those components.  Not everyone is sitting there with "air-gapped secure datacenters".14:54
sean-k-mooneythe kernel warns the user and i think that is where the warning should be14:54
kashyapsean-k-mooney: Are you referring to the 'sysfs' directory as "kernel warns"?14:56
sean-k-mooneykashyap: well i ment the message in dmesg form the early boot but sysfs can be used later at runtime14:57
sean-k-mooneyits also show in thing like lscpu14:57
sean-k-mooneyactully its not in lscpu but is in /proc/cpuinfo in the bugs line "bugs  : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf"15:01
kashyapsean-k-mooney: Yeah, it's _not_ in `lscpu`15:01
*** ratailor has quit IRC15:02
sean-k-mooneyya it would be a nice enhancement to add it15:02
kashyapRight, it's in /proc/cpuinfo.  And of course, 'sysfs' is a better place.15:02
sean-k-mooneyyep and you allso get entires in dmesg as the are detected on kenel boot with the mitigations that are applied15:04
sean-k-mooneylike this15:04
sean-k-mooney 0.033797] Spectre V2 : Mitigation: Full generic retpoline15:04
sean-k-mooney[    0.033797] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch15:04
sean-k-mooney[    0.033798] Spectre V2 : Spectre v2 mitigation: Enabling Indirect Branch Prediction Barrier15:04
sean-k-mooney[    0.033798] Spectre V2 : Enabling Restricted Speculation for firmware calls15:04
sean-k-mooney[    0.033799] Spectre V2 : Spectre v2 cross-process SMT mitigation: Enabling STIBP15:04
sean-k-mooney[    0.033800] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp15:04
sean-k-mooneywhich is the same info that gets stroed in cat /sys/devices/system/cpu/vulnerabilities/*15:05
openstackgerritGorka Eguileor proposed openstack/nova master: Use os-brick locking for volume attach and detach  https://review.opendev.org/61419015:05
mriedembauzas: dansmith: can one of you hit this stable/stein test-only backport to keep things moving? https://review.opendev.org/#/c/658929/15:13
*** mchlumsky has quit IRC15:13
*** mchlumsky has joined #openstack-nova15:15
*** wwriverrat has quit IRC15:18
openstackgerritStephen Finucane proposed openstack/nova master: Remove 'instance_update_from_api'  https://review.opendev.org/65130215:20
openstackgerritStephen Finucane proposed openstack/nova master: Stop handling 'update_cells' on 'BandwidthUsage.create'  https://review.opendev.org/65130315:20
openstackgerritStephen Finucane proposed openstack/nova master: Stop handling cells v1 for instance naming  https://review.opendev.org/65130415:20
openstackgerritStephen Finucane proposed openstack/nova master: Remove cells code  https://review.opendev.org/65130615:20
openstackgerritStephen Finucane proposed openstack/nova master: Remove conductor_api and _last_host_check from manager.py  https://review.opendev.org/65105915:20
*** tbachman has quit IRC15:21
*** wwriverrat has joined #openstack-nova15:24
*** tbachman has joined #openstack-nova15:26
*** ttsiouts has joined #openstack-nova15:27
*** wwriverrat has quit IRC15:28
*** mchlumsky has quit IRC15:28
*** mchlumsky has joined #openstack-nova15:30
*** helenafm has quit IRC15:30
openstackgerritAdrian Chiris proposed openstack/nova master: [FUP] Follow-up patch for SR-IOV live migration  https://review.opendev.org/65910115:30
*** sridharg has quit IRC15:35
*** hemna has joined #openstack-nova15:41
*** lpetrut has quit IRC15:45
*** belmoreira has quit IRC15:48
*** dklyle has quit IRC15:50
*** sridharg has joined #openstack-nova15:51
openstackgerritStephen Finucane proposed openstack/nova master: Modify PciDevice.uuid generation code  https://review.opendev.org/53048715:51
openstackgerritStephen Finucane proposed openstack/nova master: Add an online migration for PciDevice.uuid  https://review.opendev.org/53090515:51
*** dklyle has joined #openstack-nova15:52
*** hamzy has quit IRC15:52
stephenfindansmith: If you have any free time today, could you take a look at those two patches again? ^ They're the sixth and seventh oldest ones I have, respectively :)15:52
*** awalende has joined #openstack-nova15:54
*** openstackgerrit has quit IRC15:54
dansmithstephenfin: is there something that is going to need this?15:56
dansmithnot that it's a bad thing to have proper uuids, but... just wondering15:56
stephenfinWe have a chunk of legacy code that is present only because we can't be sure we don't have UUIDs. I'd like to remove that15:56
stephenfinSo it's tech debt15:56
dansmithokay15:58
*** igordc has joined #openstack-nova15:59
*** awalende has quit IRC15:59
mriedemstephenfin: the bottom one is so obviously copied from the bdm code it still mentions bdms in it16:00
*** cfriesen has joined #openstack-nova16:00
stephenfinmriedem: Yuuup (though the reference is obv a mistake)16:00
*** ttsiouts has quit IRC16:01
*** imacdonn has quit IRC16:01
*** macza has joined #openstack-nova16:01
stephenfin mdbooth and I discussed dragging it out into something standardized a long time back, but we figured it would be better wait for at least one more user before proceeding down the generic util path16:01
*** gyee has joined #openstack-nova16:01
*** igordc has quit IRC16:03
*** openstackgerrit has joined #openstack-nova16:04
openstackgerritMerged openstack/python-novaclient master: [Docs] Update client docs to add reason and locked options  https://review.opendev.org/65900016:04
openstackgerritMatthew Booth proposed openstack/nova master: Add code comment to _instance_update  https://review.opendev.org/65911216:10
*** dklyle has quit IRC16:11
*** imacdonn has joined #openstack-nova16:15
*** dklyle has joined #openstack-nova16:16
*** mgoddard has quit IRC16:20
*** dklyle has quit IRC16:21
*** tbachman has quit IRC16:21
*** mgoddard has joined #openstack-nova16:21
*** k4bi has joined #openstack-nova16:22
*** dklyle has joined #openstack-nova16:23
openstackgerritAdrian Chiris proposed openstack/nova master: [FUP] Follow-up patch for SR-IOV live migration  https://review.opendev.org/65910116:28
*** mgoddard has quit IRC16:30
*** maciejjozefczyk has quit IRC16:31
*** mgoddard has joined #openstack-nova16:32
*** partlycloudy has left #openstack-nova16:33
logan-hello, in OSA we've got a failure bumping our nova testing SHA (https://review.opendev.org/#/c/658208/) due to an api_db sync failure:16:36
logan-http://logs.openstack.org/08/658208/3/check/openstack-ansible-deploy-aio_metal-ubuntu-bionic/6c21b9f/logs/ara-report/result/2b065096-d2f5-497b-a29b-2833502c0459/16:36
logan-"AttributeError: 'module' object has no attribute 'COMPUTE_IMAGE_TYPE_AKI'"16:36
openstackgerritStephen Finucane proposed openstack/nova-specs master: Add 'flavor-extra-spec-image-property-validation-extended' spec  https://review.opendev.org/63873416:36
mriedemlogan-: which version of os-traits?16:36
mriedemyou need os-traits>=0.12.016:37
logan-checking16:37
logan-ok thanks16:37
dtantsurhey folks, we see this one rocky in ironic: http://logs.openstack.org/71/658771/4/check/ipa-tempest-dsvm-partition-bios-ipmi-iscsi-tinyipa-src/fb9d0bb/logs/screen-n-cpu.txt.gz?level=INFO16:38
dtantsurcan it be https://github.com/openstack/nova/commit/35bda4ec385e4c2b3d4cee07467f5077b13b1dd9 ?16:38
mriedemdtantsur: which thing? the StrictVersion? yes.16:38
mriedemer wait16:38
mriedemthe StrictVersion thing has been around awhile https://bugs.launchpad.net/nova/+bug/179376616:39
openstackLaunchpad bug 1793766 in OpenStack Compute (nova) "An unknown error has occurred when trying to get the list of nodes from the Ironic inventory. Error: StrictVersion instance has no attribute 'version'" [Low,Confirmed]16:39
mriedembut maybe it's hitting more now because of ^16:39
dtantsurI'm not sure if it's on nova or ironicclient side tbh16:39
logan-thanks for the tip mriedem, it looks like we're pulling in 0.11.0 somehow. http://logs.openstack.org/08/658208/3/check/openstack-ansible-deploy-aio_metal-ubuntu-bionic/6c21b9f/logs/ara-report/result/7f027c76-34d4-4dfa-a06a-d91722043b58/16:40
dtantsurmriedem: then we end up with http://logs.openstack.org/71/658771/4/check/ipa-tempest-dsvm-partition-bios-ipmi-iscsi-tinyipa-src/fb9d0bb/logs/screen-n-cpu.txt.gz#_May_14_12_21_18_27173316:40
dtantsurI'm not sure if the StrictVersion thingy is the cause, but looks so16:40
logan-oh we need to bump our requirements sha16:40
logan-heh16:40
mriedemlogan-: stale upper-constraints?16:41
mriedemoh ok16:41
logan-yup, that should fix it up. thanks!16:41
stephenfinsean-k-mooney: If you're around for a while longer, you might fancy looking at https://review.opendev.org/638734 again. Think I've addressed most of your concerns (by focussing solely on flavor extra specs)16:41
* stephenfin -> 🏡16:42
*** tbachman has joined #openstack-nova16:43
*** udesale has quit IRC16:46
sean-k-mooneyoh the validation spec sure ill take a look16:46
openstackgerritMerged openstack/nova stable/stein: Add functional confirm_migration_error test  https://review.opendev.org/65892916:47
*** mgoddard has quit IRC16:48
*** mgoddard has joined #openstack-nova16:48
*** dtantsur is now known as dtantsur|afk16:51
tssuryamriedem: could you have a look when you have time ? https://review.opendev.org/#/c/658110/ - thanks in advance16:53
*** luksky has quit IRC16:54
*** dklyle has quit IRC16:59
*** derekh has quit IRC17:00
*** dklyle has joined #openstack-nova17:01
*** mgoddard has quit IRC17:02
*** mgoddard has joined #openstack-nova17:03
*** tssurya has quit IRC17:06
*** slaweq has joined #openstack-nova17:06
sean-k-mooneystephenfin: adrianc i left some comments on https://review.opendev.org/#/c/659101/2 but this actully intduces more nits then it fixes at least from my view point17:11
*** slaweq has quit IRC17:14
*** mgoddard has quit IRC17:20
*** mgoddard has joined #openstack-nova17:22
*** ralonsoh has quit IRC17:25
*** _erlon_ has joined #openstack-nova17:32
*** sridharg has quit IRC17:36
*** itlinux has joined #openstack-nova17:42
*** aarents has quit IRC17:45
*** hamzy has joined #openstack-nova17:48
*** itlinux has quit IRC17:48
*** dklyle has quit IRC17:52
sean-k-mooneystephenfin: done. i think i have a better solution that i more generic then what you proposed but still support a yaml file for operators to customise17:54
*** itlinux has joined #openstack-nova17:54
*** tjgresha has quit IRC17:54
sean-k-mooneyall standard extra specs however would be validated in python and we woudl have a stevedor entry point so that cyborg, rmd,os-traits extra specs could also be validated17:55
*** tjgresha has joined #openstack-nova17:57
*** ttsiouts has joined #openstack-nova17:58
*** mvkr has joined #openstack-nova17:58
*** hongbin has joined #openstack-nova18:04
*** luksky has joined #openstack-nova18:15
*** betherly has joined #openstack-nova18:19
*** BjoernT has quit IRC18:22
*** betherly has quit IRC18:24
*** ivve has quit IRC18:29
*** ttsiouts has quit IRC18:31
*** lpetrut has joined #openstack-nova18:42
*** BjoernT has joined #openstack-nova18:44
*** lpetrut has quit IRC18:46
adriancsean-k-mooney: Thanks, ill take a look tommorow ?18:48
adriancwithout the ? :)18:49
sean-k-mooneyadrianc: they are reltivly minor18:49
sean-k-mooneyand one comment is a presonl preference/nit18:49
*** jdillaman has quit IRC18:49
adriancyah i gave it a quick look, thanks for providing inputs. BTW do we really need to bother ourselves with the cyborg integration on the is_sriov_port propery ?18:51
adrianci mean its A. a future issue , B. ive just moved the "mess" to one place18:51
sean-k-mooneyam proably not i just wanted to highlight it18:51
adriancack18:51
sean-k-mooneyi mean we can always fix it when we integrate cyborg rather then now18:51
openstackgerritRodrigo Barbieri proposed openstack/nova stable/rocky: Add functional confirm_migration_error test  https://review.opendev.org/65883418:59
*** betherly has joined #openstack-nova19:00
openstackgerritEric Fried proposed openstack/nova master: [Trivial doc change] Admin can overwrite the locked_reason of an owner  https://review.opendev.org/65906719:04
*** betherly has quit IRC19:04
*** itlinux has quit IRC19:16
*** dklyle has joined #openstack-nova19:16
*** dklyle has quit IRC19:19
*** david-lyle has joined #openstack-nova19:19
*** pcaruana has quit IRC19:19
*** slaweq has joined #openstack-nova19:21
*** awalende has joined #openstack-nova19:25
*** david-lyle has quit IRC19:42
mriedemdansmith: so i just realized that our 2.33 change for listing hypervisors which added limit and marker support for paging changed the previous behavior where we'd just return everything - we now default to CONF.api.max_limit if you don't specify a limit, and i can't tell if that's good or not - i suppose in terms of api load it's good to limit server-side19:46
mriedemforces the client to page though19:46
dansmithmriedem: you mean before that we would return all of them regardless of the amount?19:46
mriedemright19:46
dansmithlike, 50000000000 of them?19:46
mriedem10K, 14K, whatever cern has yeah19:47
dansmithclamping to max_limit does not seem like a regression to me :)19:47
mriedemheh19:47
mriedemyeah i'm just learning some watcher code where they build their data model for hypervisors and it's super inefficient, and lossy because of this limit thing i realize19:47
mriedemtl;dr they (1) list all hypervisors with details (well, up to 1K), (2) for each hypervisor, get it's servers (3) for each hypervisor, get it's details (again)19:48
mriedemall of that can be done in a single GET with 2.5319:48
dansmithyoza19:49
dansmith*yowza19:49
mriedemand i *think* this is on ever audit request19:49
mriedemrather than like build on startup, then modify as notifications come in19:49
mriedem*every19:49
dansmithsweet19:52
mriedemoy, and for every compute node, get all of its instances in separate GETs19:59
NewBrucehey sean-k-mooney / mriedem20:03
NewBrucesaw the code updates and call for review - will get onto it asap - sorry bout that - got caught up in a couple other bug chasing efforts…..20:04
NewBrucethanks for the work on it though :)20:04
*** jmlowe has joined #openstack-nova20:06
*** tesseract has quit IRC20:06
*** awalende has quit IRC20:19
*** awalende has joined #openstack-nova20:20
*** awalende has quit IRC20:24
*** bbowen_ has joined #openstack-nova20:26
*** itlinux has joined #openstack-nova20:27
*** jdillaman has joined #openstack-nova20:27
*** ttsiouts has joined #openstack-nova20:28
*** bbowen has quit IRC20:28
*** bbowen_ has quit IRC20:36
*** cdent has joined #openstack-nova20:36
*** ivve has joined #openstack-nova20:36
*** JamesBenson has joined #openstack-nova20:40
*** hamzy has quit IRC20:41
*** slaweq has quit IRC20:44
*** JamesBenson has quit IRC20:54
*** cdent has quit IRC20:58
*** JamesBenson has joined #openstack-nova20:59
*** JamesBenson has quit IRC20:59
mriedemnp20:59
*** ttsiouts has quit IRC21:01
*** itlinux has quit IRC21:07
*** BjoernT has quit IRC21:14
mriedemefried: comments on surya's fix here https://review.opendev.org/#/c/658110/ - if you're in agreement i'll just make the changes quick21:15
efriedmriedem: wfm. You want to fix or would you feel better if I did?21:18
mriedemi'll do it, already got the test done21:18
openstackgerritMatt Riedemann proposed openstack/nova master: Disable limit if affinity(anti)/same(different)host is requested  https://review.opendev.org/65811021:21
*** dklyle has joined #openstack-nova21:27
mriedemefried: so i addressed my nits on ^ you and alex were +2, want to just fast approve?21:30
efriedmriedem: gimme a sec. I'll mark up and then fast approve.21:32
efriedmriedem: Comments added. If you are okay with those things, say so and I'll approve.21:36
efriedor quick respin to address would be better :)21:36
mriedemoh hmm21:38
mriedemmultiple hints aye21:38
mriedemcouldn't i just throw a fake hint in there?21:38
mriedemi.e. are you ok with this?21:39
mriedem        fake_spec = objects.RequestSpec(21:39
mriedem            flavor=flavor, scheduler_hints={hint: [uuids.fake],21:39
mriedem                                            'some-fake-hint': ['fake-value']})21:39
efriedThat would be good too, but I'd like to see >1 of the hints we're conditioning on.21:40
efriedmriedem: If it were me, I would nix ddt, put the guts of the test in a _helper, and loop over it with various permutations of hints constructed in a loop from components.21:41
efriedmriedem: if you tire of this, I can take a crack at it.21:42
mriedemddt is nice in that the test names have the ddt values in the test name in case one of them blows up21:43
mriedemanyway i've got a thing21:43
mriedemthis didn't come up in the review comments on the patch before this so i figured it was fine - unless that came up in irc21:44
*** dklyle has quit IRC21:44
*** dklyle has joined #openstack-nova21:44
*** amodi has joined #openstack-nova21:44
mriedemi'm not going to mention something about nested providers in the commit message b/c this is going back to queens21:46
mriedemwhere those weren't supported21:46
mriedemis that ok?21:46
efriedYeah, ignore that one, just thought to point it out.21:46
*** mchlumsky has quit IRC21:47
openstackgerritMatt Riedemann proposed openstack/nova master: Disable limit if affinity(anti)/same(different)host is requested  https://review.opendev.org/65811021:47
*** betherly has joined #openstack-nova21:48
*** bbowen has joined #openstack-nova21:48
efriedmriedem: +A21:49
mriedemwhew21:49
efriedI know, try to do a nice thing...21:50
*** dklyle has quit IRC21:50
*** ivve has quit IRC21:50
*** betherly has quit IRC21:53
* mriedem makes a note to complain to my tc liaison about the nova core team21:59
*** rcernin has joined #openstack-nova22:00
*** luksky has quit IRC22:01
*** betherly has joined #openstack-nova22:08
*** betherly has quit IRC22:13
*** tbachman has quit IRC22:15
*** tbachman has joined #openstack-nova22:17
*** whoami-rajat has quit IRC22:18
*** BjoernT has joined #openstack-nova22:35
*** tbachman_ has joined #openstack-nova22:36
*** tbachman has quit IRC22:37
*** tbachman_ is now known as tbachman22:37
*** BjoernT has quit IRC22:39
*** BjoernT has joined #openstack-nova22:40
openstackgerritEric Fried proposed openstack/nova master: WIP: TC Vision Reflection  https://review.opendev.org/65893222:48
efriedA little more every day22:48
efriedmaybe by meeting time I'll have enough for folks to start ripping apart22:49
*** tkajinam has joined #openstack-nova22:52
*** _erlon_ has quit IRC22:52
*** ttsiouts has joined #openstack-nova22:58
*** hemna has quit IRC23:11
*** hongbin has quit IRC23:20
*** betherly has joined #openstack-nova23:31
*** ttsiouts has quit IRC23:32
*** macza has quit IRC23:33
*** mlavalle has quit IRC23:34
*** betherly has quit IRC23:36
*** BjoernT has quit IRC23:42
*** irclogbot_0 has quit IRC23:45
*** lbragstad has quit IRC23:47
*** irclogbot_0 has joined #openstack-nova23:48
*** itlinux has joined #openstack-nova23:49
*** betherly has joined #openstack-nova23:51
*** betherly has quit IRC23:56

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