Friday, 2018-10-05

« Thursday, 2018-10-04 Index Saturday, 2018-10-06 »
*** hamzy_ has joined #openstack-nova00:01
*** hamzy_ is now known as hamzy00:02
*** Swami has quit IRC00:04
*** slagle has quit IRC00:15
*** slagle has joined #openstack-nova00:15
*** pooja_jadhav has quit IRC00:17
openstackgerritMerged openstack/nova master: Fix logging parameter in _populate_pci_mac_address  https://review.openstack.org/60762800:22
*** rcernin has quit IRC00:27
*** rcernin has joined #openstack-nova00:29
*** pooja_jadhav has joined #openstack-nova00:29
*** hshiina has joined #openstack-nova00:35
openstackgerritMerged openstack/nova master: Not set instance to ERROR if set_admin_password failed  https://review.openstack.org/55516000:45
*** med_ has quit IRC01:01
*** mrsoul has joined #openstack-nova01:17
*** med_ has joined #openstack-nova01:18
*** Dinesh_Bhor has joined #openstack-nova01:23
*** edmondsw has joined #openstack-nova01:26
*** moshele has joined #openstack-nova01:39
*** Dinesh_Bhor has quit IRC01:41
*** moshele has quit IRC01:48
*** Dinesh_Bhor has joined #openstack-nova01:49
*** hongbin has joined #openstack-nova01:57
*** gyee has quit IRC02:01
*** mhen has quit IRC02:02
*** mhen has joined #openstack-nova02:03
*** tiendc has joined #openstack-nova02:05
*** itlinux has joined #openstack-nova02:05
*** jiaopengju has joined #openstack-nova02:21
*** dosaboy has quit IRC02:35
*** bhagyashris has joined #openstack-nova02:36
*** vivsoni has quit IRC02:56
*** annp has joined #openstack-nova03:01
*** sapd1 has quit IRC03:10
*** sapd1 has joined #openstack-nova03:10
openstackgerritMerged openstack/nova master: Handle missing marker during online data migration  https://review.openstack.org/60516403:14
openstackgerritMerged openstack/nova master: Placement: Remove usage of get_legacy_facade()  https://review.openstack.org/60733603:26
*** hongbin has quit IRC03:42
*** udesale has joined #openstack-nova03:49
*** Dinesh_Bhor has quit IRC03:57
*** med_ has quit IRC04:16
*** hoangcx has quit IRC04:38
*** rcernin has quit IRC04:42
*** rcernin has joined #openstack-nova04:46
*** kukacz has quit IRC04:52
*** openstackgerrit has quit IRC04:52
*** mgoddard has quit IRC04:52
*** kevinbenton has quit IRC04:52
*** kukacz has joined #openstack-nova04:57
*** openstackgerrit has joined #openstack-nova04:57
*** mgoddard has joined #openstack-nova04:57
*** kevinbenton has joined #openstack-nova04:57
*** Bhujay has joined #openstack-nova04:59
*** Bhujay has quit IRC05:00
*** Bhujay has joined #openstack-nova05:00
*** ratailor has joined #openstack-nova05:18
*** bhagyashris has quit IRC05:38
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove an unnecessary duplicate flag  https://review.openstack.org/60816206:05
*** bhagyashris has joined #openstack-nova06:09
openstackgerritVlad Gusev proposed openstack/nova stable/rocky: Not set instance to ERROR if set_admin_password failed  https://review.openstack.org/60816506:34
*** tiendc has quit IRC06:35
*** udesale has quit IRC06:39
*** markvoelker has joined #openstack-nova06:40
*** gibi is now known as giblet06:42
giblethappy Friday nova06:42
*** markvoelker has quit IRC06:45
*** Bhujay has quit IRC06:46
*** sahid has joined #openstack-nova06:47
*** udesale has joined #openstack-nova06:53
*** pcaruana has joined #openstack-nova06:57
*** bhagyashris has quit IRC07:02
*** rcernin has quit IRC07:04
*** maciejjozefczyk has joined #openstack-nova07:05
*** rtjure has quit IRC07:09
*** jpena|off is now known as jpena07:10
*** rtjure has joined #openstack-nova07:12
*** helenafm has joined #openstack-nova07:15
*** ralonsoh has joined #openstack-nova07:21
*** Luzi has joined #openstack-nova07:26
mrch_.07:33
*** dosaboy has joined #openstack-nova07:38
*** bauzas is now known as PapaOurs07:39
PapaOursgood Friday novaers07:39
*** mrch_ has quit IRC07:47
*** mrch has joined #openstack-nova07:48
*** mrch has quit IRC07:50
*** mrch has joined #openstack-nova07:52
*** lpetrut has joined #openstack-nova07:54
*** hshiina has quit IRC07:54
*** ttsiouts has joined #openstack-nova07:59
*** tssurya has joined #openstack-nova07:59
*** takashin has left #openstack-nova08:00
*** ttsiouts has quit IRC08:02
*** ttsiouts has joined #openstack-nova08:03
*** alexchadin has joined #openstack-nova08:05
*** ttsiouts has quit IRC08:07
openstackgerritVlad Gusev proposed openstack/nova stable/queens: Not set instance to ERROR if set_admin_password failed  https://review.openstack.org/60817908:08
openstackgerritVlad Gusev proposed openstack/nova stable/pike: Not set instance to ERROR if set_admin_password failed  https://review.openstack.org/60818008:09
*** ttsiouts has joined #openstack-nova08:15
*** cfriesen has quit IRC08:21
*** priteau has joined #openstack-nova08:26
openstackgerritMerged openstack/nova master: Refactor allocation checking in functional tests  https://review.openstack.org/60728708:26
*** derekh has joined #openstack-nova08:35
*** moshele has joined #openstack-nova08:40
*** panda|off is now known as panda08:40
*** markvoelker has joined #openstack-nova08:41
*** cdent has joined #openstack-nova08:45
*** moshele has quit IRC08:45
*** tetsuro_ has quit IRC08:45
openstackgerritLee Yarwood proposed openstack/nova stable/queens: libvirt: Remove reference to transient domain when detaching devices  https://review.openstack.org/60818609:01
openstackgerritSylvain Bauza proposed openstack/nova master: libvirt: implement reshaper for vgpu  https://review.openstack.org/59920809:02
*** janki has joined #openstack-nova09:05
PapaOursgiblet: off the discussions we had, I just rebased ^09:13
*** markvoelker has quit IRC09:15
*** efried has quit IRC09:17
*** efried1 has joined #openstack-nova09:17
gibletPapaOurs: ack09:18
*** efried1 is now known as efried09:19
*** bhagyashris has joined #openstack-nova09:28
*** stephenfin is now known as finucannot09:35
*** bhagyashris has quit IRC09:43
*** alexchadin has quit IRC09:51
openstackgerritMerged openstack/nova stable/queens: libvirt: Use os.stat and os.path.getsize for RAW disk inspection  https://review.openstack.org/60429510:03
*** sheel has joined #openstack-nova10:05
*** markvoelker has joined #openstack-nova10:12
*** udesale has quit IRC10:18
*** erlon_ has joined #openstack-nova10:21
*** ttsiouts has quit IRC10:22
*** itlinux has quit IRC10:24
*** tbachman has quit IRC10:41
*** markvoelker has quit IRC10:44
*** tetsuro has quit IRC10:48
*** annp has quit IRC10:53
*** jchhatbar has joined #openstack-nova10:59
*** janki has quit IRC11:00
*** jchhatbar has quit IRC11:01
*** jchhatbar has joined #openstack-nova11:02
*** moshele has joined #openstack-nova11:02
*** jpena is now known as jpena|lunch11:04
*** s10 has joined #openstack-nova11:06
*** jchhatba_ has joined #openstack-nova11:06
*** jchhatbar has quit IRC11:09
*** dtantsur|afk is now known as dtantsur11:09
*** rpittau_ has quit IRC11:17
*** moshele has quit IRC11:20
*** helenafm has quit IRC11:21
*** moshele has joined #openstack-nova11:21
*** alexchadin has joined #openstack-nova11:35
*** ttsiouts has joined #openstack-nova11:40
*** markvoelker has joined #openstack-nova11:41
openstackgerritSurya Seetharaman proposed openstack/nova master: Modify get_by_cell_and_project() to get_not_deleted_by_cell_and_project()  https://review.openstack.org/60766312:01
openstackgerritSurya Seetharaman proposed openstack/nova master: Return a minimal construct for nova list when a cell is down  https://review.openstack.org/56778512:01
openstackgerritSurya Seetharaman proposed openstack/nova master: [WIP] Refactor scatter-gather utility to return exception objects  https://review.openstack.org/60793412:01
openstackgerritSurya Seetharaman proposed openstack/nova master: Return a minimal construct for nova show when a cell is down  https://review.openstack.org/59165812:01
openstackgerritSurya Seetharaman proposed openstack/nova master: Return a minimal construct for nova service-list when a cell is down  https://review.openstack.org/58482912:01
openstackgerritSurya Seetharaman proposed openstack/nova master: API microversion bump for handling-down-cell  https://review.openstack.org/59165712:01
*** med_ has joined #openstack-nova12:03
*** tbachman has joined #openstack-nova12:04
*** tbachman_ has joined #openstack-nova12:06
*** jpena|lunch is now known as jpena12:06
*** ratailor has quit IRC12:08
*** tbachman has quit IRC12:09
*** tbachman_ is now known as tbachman12:09
*** helenafm has joined #openstack-nova12:11
*** udesale has joined #openstack-nova12:12
*** jaypipes is now known as leakypipes12:12
*** markvoelker has quit IRC12:15
*** mdbooth has quit IRC12:17
*** mdbooth has joined #openstack-nova12:18
*** mdbooth has quit IRC12:19
*** mdbooth has joined #openstack-nova12:20
leakypipescdent, efried, sean-k-mooney: morning sunshines. so, quick question... where should we put the HPET trait in os-traits namespace hierarchy? I was thinking either COMPUTE_HPET or HW_HPET but could also see a case for a new namespace... something like HW_TIME_HPET or just TIME_HPET. Thoughts?12:20
*** mdbooth has quit IRC12:20
leakypipesfor the record, the COMPUTE_ namespace prefix is where we put the virt driver capabilities.12:20
leakypipesand HW_ namespace is where hardware-specific things go.12:21
*** mdbooth has joined #openstack-nova12:21
leakypipeswith sub-namespaces like HW_CPU_ and HW_GPU_ etc12:21
*** mdbooth has quit IRC12:22
*** mdbooth has joined #openstack-nova12:23
sean-k-mooneyleakypipes: i would be fine with HW_HPET or HW_TIME_HPET12:23
*** mdbooth has quit IRC12:23
cdentleakypipes: are we wanting to mean "this host provides an HPET"? If so I'd go HW_HPET or HW_TIME_HPET (in case we ever want a HW_TIME_PIT or some such)12:24
*** mdbooth has joined #openstack-nova12:24
*** mdbooth has quit IRC12:24
sean-k-mooneyleakypipes: the spec was suggesting HW_GUEST_HPET_CAPABLE i think12:25
*** mdbooth has joined #openstack-nova12:25
sean-k-mooneyactully it was HPET_GUEST_CAPABLE.. im not sure to be honest. when  i see HW_HPET i assume that means the host has a HPET available and eneabled12:26
leakypipessean-k-mooney: well, to continue my point about traits being capabilities... the _CAPABLE is redundant.12:27
*** mdbooth has quit IRC12:27
leakypipessean-k-mooney: and again, the trait decorates the provider (the host) not the guest.12:27
sean-k-mooneyso maybe we want 2 traits HW_GUEST_HPET(enable guest HPET) and HW_HPET(find host with hardware hpet)12:27
*** dtantsur is now known as dtantsur|brb12:27
leakypipessean-k-mooney: no....12:28
leakypipes:)12:28
leakypipessean-k-mooney:  that is UNACCEPTABLE!12:28
* leakypipes dons cloak of stubbornness12:28
sean-k-mooneyhehe ok so what does HW_HPET mean12:28
sean-k-mooney"host has a hpet or is capable of emulating one" or "host has a hpet" or "host is capable of providing a hpet to a guest"12:29
leakypipesleakypipes: it would mean that the host supports HPET. and the virt driver would see the trait:HW_HPET=require trait in the image metadata and configure the libvirt XML to enable HPET for the guest.12:29
* artom is afraid it will get misunderstood as placement supporting pets12:30
leakypipesleakypipes: I propose keeping it simple with the trait and just having one trait called HW_HPET (or HW_TIME_HPET). then, if the guest configuration really does need to get more complex in the future, we can always add a separate hw:hpet_policy extra spec.12:30
leakypipesartom: :)12:30
leakypipesartom: that ship has already sailed, my friend :P12:30
cdentindeed12:31
cdentsad12:31
cdentbigly sad12:31
leakypipesartom: we support all KINDS of pets.12:31
sean-k-mooneyleakypipes: so its virt driver specific then. e.g. ironic it means this host has a hpet and libvirt it means this host can provide a hpet. but in either case the guest will see a hpet12:31
artomAround the world and back, with spices and native prisoners onboard.12:31
artomAlso, pet in french means fart, so I'm just giggling like a 13 year old.12:32
leakypipessean-k-mooney: remember at the end of the discussion last night, we said "we will go with option 2 (which is "just use a trait and have the virt driver look at the traits list for simple configurations") and IFF there is a need for more complex non-binary configuration pieces, then we can add a complementary extra spec that the virt driver can consult for that more specific configuration"12:32
leakypipesartom: :)12:33
sean-k-mooneyleakypipes: ya im fine with the hw:hpet_policy for extra config12:33
leakypipescdent: you have a preference on the trait name?12:33
cdentleakypipes: [t 39lC]12:34
purplerbot<cdent> leakypipes: are we wanting to mean "this host provides an HPET"? If so I'd go HW_HPET or HW_TIME_HPET (in case we ever want a HW_TIME_PIT or some such) [2018-10-05 12:24:14.244038] [n 39lC]12:34
*** sheel has quit IRC12:34
artomAre we bikeshedding? Because HPET is High Precision Event Timer, right?12:34
leakypipescdent: oh, shit, sorry mate. totally missed that.12:34
artomSo please don't be redundant by putting TIME in the trait name12:34
leakypipesartom: yessir12:34
sean-k-mooneyleakypipes: i belive this is the first time however that a HW_* trait is being used to dicribe a capablity of the hyperviror rather then a capablity of the hardware teh hypervior is running on which is the only thing i find a little confusing12:35
cdentartom: except that we have namespaces in the traits, sort of12:35
*** dosaboy has quit IRC12:35
leakypipessean-k-mooney: we have the COMPUTE_ namespace for virt driver capabilities.12:35
artomcdent, is TIME (eith as _TIME or TIME_) a namespace?12:36
*** dosaboy has joined #openstack-nova12:36
leakypipessean-k-mooney: but I was under the impression that an HPET was something the host either had or didn't...12:36
leakypipesartom: it was intended as a namespace, yes.12:36
sean-k-mooneyleakypipes: right in that case COMPUTE_HPET woudl seam better12:36
*** dosaboy has quit IRC12:36
artomleakypipes, ah, in that case never mind me :)12:36
leakypipesartom: to future proof if we need to add traits to describe other timer-related thingamabobs.12:36
sean-k-mooneyleakypipes: qemu can emulate a hpet with a monotonic clock or other time source12:36
sean-k-mooneyso the host does not need to have one for the guest to have one12:36
cdentI think I'm going to write a worm to add CUSTOM_UNACCEPTABLE trait to all clouds it can find12:37
leakypipesheh12:37
artomcdent, or CUSTOM_PWNED12:37
sean-k-mooneyleakypipes: so my two cents would be COMPUTE_HPET is compute is capable of providing hpet and HW_HPET is host has a HPET but im not too pushed either way12:38
leakypipessean-k-mooney: do you see a need for a _TIME subnamespace?12:39
leakypipessean-k-mooney: feel free to say no... honestly I'm asking you guys since you're closest to the hw vendors.12:39
sean-k-mooneyleakypipes: ya i think that is a good idea. cybog are adding a time related feature this cycle12:40
leakypipessean-k-mooney: ack. to both HW_ and to COMPUTE_, yeah?12:40
sean-k-mooneyya proably. this is the cybog one https://review.openstack.org/#/c/586994/12:40
sean-k-mooneyAdd HPTS driver, (HPTS: High Precision Time Synhronization cards)12:41
sean-k-mooneynot really sure what they are or why you need them but apparednt zte cares about them12:41
leakypipessean-k-mooney: the Edge! NFV! 5G! Unicorns!12:43
*** alexchadin has quit IRC12:43
sean-k-mooneyleakypipes: i was thinking more cern/scientif compute but its prably finacal serverces/high frequence trading stuff12:44
leakypipessean-k-mooney: though, after looking through that HPTS patch, it looks more like HPTS devices are VFs and thus are resources, not traits (i.e. the host would have an inventory of something like an HPTS resource class)12:44
jrollleakypipes: don't bring my life into this12:44
jroll>.>12:44
leakypipeshehe12:45
leakypipesjroll: weren't you supposed to be busy passing through a GPU or something... now leave us!12:45
sean-k-mooneyya i would have assumed the pf provide would be taged with a trait or something but maybe they will just use a resouce class12:48
leakypipessean-k-mooney: well, it seems that the PF has a limited number of VFs for doing the high-precision timing in guests, which is why I think it's probably an inventory/resource class12:49
sean-k-mooneyby the way should i review https://review.openstack.org/#/c/514713/ and https://review.openstack.org/#/c/514712/3/ for secure boot and tp-m traits or leave it to cfressen and co?12:49
openstackgerritMerged openstack/nova stable/ocata: Add check for invalid allocation amounts  https://review.openstack.org/60732012:50
openstackgerritMerged openstack/nova stable/ocata: Add check for invalid inventory amounts  https://review.openstack.org/60732112:50
openstackgerritMerged openstack/nova stable/ocata: Don't delete neutron port when attach failed  https://review.openstack.org/60761412:50
sean-k-mooneyleakypipes: while i think of it. i spent 4 hours this morning getting that netdevsim module to compile and load...12:51
sean-k-mooneyleakypipes: its support vfs :) they dont have pci enpoint or show up in libvirt :( but the PF does12:51
leakypipesjroll: you know I kid, right? :) we love you here in compute land.12:52
leakypipessean-k-mooney: lovely.12:52
sean-k-mooneyleakypipes: i dont know if the pfs it create will be enough to do testing but its alot less usfull then i was hoping. that said i tested it with an older version so maybe a newer version will support more things12:53
sean-k-mooneyim going to park it for a few days but if we can use it to do even a little testign in the gate that would be still an improvement12:53
sean-k-mooneyim alot less optimistic now however whcih is a shame. it would be nice to have better sriov/passthough testing.12:54
leakypipessean-k-mooney: "newer version" <-- does that mean something like "release two nights ago as a ZIP file"?12:54
sean-k-mooneyhaha no im building form the sorce rpms form fedora 28 but i used the 3.16 kernel it install with in stead of the 3.17.x kernel that is in the package manager. the gate should be using the latest kernel in the package manger12:55
*** dosaboy has joined #openstack-nova12:56
openstackgerritSurya Seetharaman proposed openstack/nova master: Cleanup comp_node, res_prov, services, aggregate_hosts during cell deletion  https://review.openstack.org/54666012:56
*** dims_ has quit IRC12:58
sean-k-mooneycrap, when i said 3.x replace that with 4.x ... but same difference. install iso ships with much older kernel then cloud image that the gate uses12:58
leakypipessean-k-mooney: 3.17.x kernel!? well, at least it's 4 years old.12:58
leakypipesalright, phew...12:58
*** mriedem has joined #openstack-nova12:59
*** mchlumsky has joined #openstack-nova13:03
*** Luzi has quit IRC13:04
*** moshele has quit IRC13:13
*** efried is now known as fried_rice13:14
*** moshele has joined #openstack-nova13:14
*** dave-mccowan has joined #openstack-nova13:15
jrollleakypipes: of course :)13:16
*** tbachman has quit IRC13:17
openstackgerritJay Pipes proposed openstack/os-traits master: Add COMPUTE_TIME_HPET trait  https://review.openstack.org/60825813:18
leakypipessean-k-mooney: ^13:19
*** dave-mccowan has quit IRC13:21
*** tbachman has joined #openstack-nova13:21
*** moshele has quit IRC13:22
*** mdbooth has joined #openstack-nova13:23
fried_riceleakypipes, sean-k-mooney: I'm late to the naming party, but I want it noted that NO significance should be attached to the name I chucked into the spec draft. I was just a placeholder.13:26
fried_riceI dig the name (and reasoning) leakypipes put into ---^13:27
fried_ricejust a teeny paperwork issue with that patch and I'm +213:27
sean-k-mooneyfried_rice: cool13:27
leakypipesfried_rice: coo, thx13:28
finucannotlyarwood: Fancy hitting https://review.openstack.org/#/c/588570/2 today before you head off on your holliers13:30
lyarwood*clicks*13:30
*** panda is now known as panda|off13:31
*** med_ has quit IRC13:31
lyarwoodfinucannot: cool thanks for doing that, it LGTM now.13:32
finucannotlyarwood: ta13:33
*** tbachman_ has joined #openstack-nova13:34
openstackgerritStephen Finucane proposed openstack/nova master: conf: Improve documentation for defer_iptables_apply  https://review.openstack.org/44543613:34
openstackgerritStephen Finucane proposed openstack/nova master: conf: Undeprecate the 'dhcp_domain' option  https://review.openstack.org/48061613:34
sean-k-mooneyleakypipes: actuly just reading your comment regarding a harware htpe and resouce class i dont think that is how it works13:35
sean-k-mooneyleakypipes: you dont actully pass the hardware hpet to the guest13:36
*** tbachman has quit IRC13:36
*** tbachman_ is now known as tbachman13:36
sean-k-mooneyleakypipes: qemu just can use it as its time source for the guest hpet or it can use another timesoucre13:36
leakypipessean-k-mooney: oh? I thought you said that only a single guest could use the hardware HPET on a host at a time?13:37
sean-k-mooneyleakypipes: no that was for the TPM13:37
leakypipesahhhhhhhhh13:37
* cdent misses his vic-2013:37
leakypipessorry, yeah, I was confused. I'll fix the HPET patch ASAP.13:37
openstackgerritStephen Finucane proposed openstack/nova master: Modify PciDevice.uuid generation code  https://review.openstack.org/53048713:38
openstackgerritStephen Finucane proposed openstack/nova master: Add an online migration for PciDevice.uuid  https://review.openstack.org/53090513:38
finucannotfried_rice: Could you take a look at https://review.openstack.org/#/c/530924/ before it ends up in merge conflict again? :)13:38
* fried_rice clicks13:39
*** ttsiouts has quit IRC13:39
mdboothmriedem: So this one is looking good: https://review.openstack.org/#/c/578846/. I got a clean (of relevant failures) run against your evacuate ci test.13:39
openstackgerritStephen Finucane proposed openstack/nova master: objects: Remove legacy '_from_dict' functions  https://review.openstack.org/53741413:40
fried_ricefinucannot: Cool feature. Reviewing...13:41
finucannotta13:41
*** s10_ has joined #openstack-nova13:42
*** mdbooth has quit IRC13:42
*** s10 has quit IRC13:42
*** mdbooth has joined #openstack-nova13:43
fried_ricefinucannot: Not having looked too deep yet: The ones you skipped, you skipped on purpose?13:43
finucannotfried_rice: For example?13:44
fried_ricefinucannot: https://review.openstack.org/#/c/530924/7/nova/conf/libvirt.py@10713:44
*** jangutter has quit IRC13:44
fried_riceI guess because there was no description in the docstring13:44
*** awaugama has joined #openstack-nova13:45
finucannotLess that and more it being near-zero value13:45
finucannotIt is possible that I missed a few others though so do keep your eyes peeled. It's been through a few rounds13:45
fried_ricefinucannot: Okay, I'll mark all the missed ones just for reference. But looking at them, I think I agree there's no value for now.13:46
finucannotack. Sounds good13:46
fried_ricefinucannot: I need to see how they show up in the docs. Wondering if it would be good future-proofing to turn choices=['foo', 'bar'] into choices=[('foo', ''), ('bar', '')] for those...13:47
finucannotOh, that's a good point, actually. Here's the rendering code13:47
finucannothttps://github.com/openstack/oslo.config/blob/master/oslo_config/sphinxext.py#L161-L17113:48
fried_ricefinucannot: Ahem13:48
fried_ricehttp://logs.openstack.org/24/530924/7/check/openstack-tox-docs/a4e127f/html/configuration/config.html#api.auth_strategy13:48
fried_riceit appears to be broken, at least for that first un13:48
*** mdbooth has quit IRC13:48
fried_riceshit, ignore13:48
finucannotI was going to say...13:48
*** dtantsur|brb is now known as dtantsur13:48
fried_riceI thought I was going to skip coffee this morning. Clearly that is not going to be possible.13:48
*** mdbooth has joined #openstack-nova13:49
fried_ricefinucannot: So yeah, quick experiment to make sure ('foo', '') shows up like I think it will. That could be done separately, of course.13:49
*** mdbooth has quit IRC13:49
*** mdbooth has joined #openstack-nova13:50
*** mlavalle has joined #openstack-nova13:56
*** _pewp_ has quit IRC13:57
*** erlon_ has quit IRC13:57
melwitt.13:57
*** erlon has joined #openstack-nova13:57
*** _hemna has quit IRC13:58
*** jangutter has joined #openstack-nova14:00
*** ttsiouts has joined #openstack-nova14:00
*** munimeha1 has joined #openstack-nova14:01
*** eharney has joined #openstack-nova14:02
*** tbachman has quit IRC14:04
*** tbachman_ has joined #openstack-nova14:04
fried_ricefinucannot: tox -e docs is giving me14:14
fried_riceImportError: bad magic number in 'nova.notifications.objects.libvirt': b'\x03\xf3\r\n'14:14
fried_ricewhich looks familiar but I can't remember wtf14:14
finucannotLet me build locally. This is unrelated, right?14:15
fried_ricetotally14:15
fried_ricewell, I was trying to build locally to experiment with the above14:15
fried_ricefinucannot: removing *.pyc fixed it.14:15
fried_ricecall off the doggs14:16
finucannotack14:16
fried_ricefinucannot: We did something recently to stop doing that find -delete14:16
fried_riceI guess it was there for a reason :(14:16
fried_ricefinucannot: Interesting data point: http://paste.openstack.org/show/731591/ results in no change to the output. I was actually expecting it to turn it into a bolded one-item-per-line list with no descriptions, but it doesn't - it still looks just like https://docs.openstack.org/nova/latest/configuration/config.html#libvirt.virt_type14:19
*** dansmith is now known as SteelyDan14:20
finucannotfried_rice: That's because I defensively coded against that. Oops https://github.com/openstack/oslo.config/blob/master/oslo_config/sphinxext.py#L163-L16414:20
finucannotiirc, that was in place to prevent us emitting the 'Possible values' section twice for something like nova14:21
fried_ricefinucannot: Does '' convert to None somewhere along the line?14:21
* fried_rice hacks up something else quick...14:21
finucannotHmm, it shouldn't but lemme check14:21
fried_rice(I promise I will eventually get back to reviewing your actual patch - hopefully before another rebase is required :)14:22
finucannotSo it shouldn't, based on this https://github.com/openstack/oslo.config/blob/bc9b7f5d2fb4c552254263bb0843fb766a9978a0/oslo_config/types.py#L118-L12114:23
finucannotThough, personally, given that we have the 'Valid values' line already, I think emitting the 'Possible values' section too probably isn't necessary https://github.com/openstack/oslo.config/blob/master/oslo_config/sphinxext.py#L11714:24
fried_ricefinucannot: Sorry, I still haven't gotten that coffee. It didn't dtrt, it printed the normal14:24
fried_riceValid Values:kvm, lxc, qemu, uml, xen, parallels14:24
fried_ricebut then also did the paragraph thing with <No description provided> for each, which is ugly.14:24
finucannotYeah, so drop back to choices=['foo', 'bar']14:25
fried_riceyeah.14:25
finucannotYou'll keep the 'Valid Values' line but won't get those ugly lines14:25
finucannotCool14:25
fried_ricefinucannot: So yeah, the ones you changed are now showing up double, once in Valid Values on the third line, and then the new "Possible values" section.14:25
fried_riceBut that's going to be a change in oslo, if you want to dedup, not in consuming code.14:26
finucannotYup. That was on purpose. We we previously doing that in nova14:26
finucannotOnly by hand14:26
finucannotI should probably just change the 'Possible values' title to something more meaningful, like 'Valid values description' or the likes14:27
*** ttsiouts has quit IRC14:31
*** ttsiouts has joined #openstack-nova14:31
openstackgerritMartin Midolesov proposed openstack/nova master: vmware:PropertyCollector for caching instance properties  https://review.openstack.org/60827814:32
openstackgerritStephen Finucane proposed openstack/nova master: Remove get_config_vhostuser  https://review.openstack.org/56547114:33
openstackgerritStephen Finucane proposed openstack/nova master: Make 'plugin' a required argument for '_get_vif_instance'  https://review.openstack.org/60827914:33
*** mrch has quit IRC14:35
*** ttsiouts has quit IRC14:36
*** panda|off has quit IRC14:36
openstackgerritStephen Finucane proposed openstack/nova master: Remove get_config_vhostuser  https://review.openstack.org/56547114:37
openstackgerritStephen Finucane proposed openstack/nova master: Make 'plugin' a required argument for '_get_vif_instance'  https://review.openstack.org/60827914:37
*** panda has joined #openstack-nova14:37
*** udesale has quit IRC14:38
finucannotfried_rice: Also, we still have the line to remove 'pyc' files14:38
finucannotIf that's not getting called, it's because the target isn't calling {[testenv]commands}14:38
fried_ricehm, why didn't it hit when I did tox -e or tox -re?14:38
fried_rice...with the docs target. /me looks...14:38
finucannotYeah, we don't call it there14:39
fried_riceokay. Should we?14:39
finucannotIf we do anything we code (which we do) then yeah, we should14:40
finucannotOnce we depend on tox 3.0.0, we can remove that line in favour of PYTHONDONTWRITEBYTECODE14:41
finucannothttps://github.com/tox-dev/tox/commit/336f4f6bd8b53223f940fc5cfc43b1bbd78d469914:41
fried_riceI'm gonna go review your actual patch now, mkay?14:45
*** rloo has joined #openstack-nova14:47
openstackgerritJay Pipes proposed openstack/os-traits master: Add COMPUTE_TIME_HPET trait  https://review.openstack.org/60825814:48
leakypipesfried_rice: ^14:48
leakypipessean-k-mooney: ^^14:48
fried_riceleakypipes: +214:49
*** rloo is now known as waterloo14:51
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Cross-cell resize  https://review.openstack.org/60393014:52
melwittgood review for friday: trivial bug fix https://review.openstack.org/60804014:53
*** _pewp_ has joined #openstack-nova14:53
waterloohi, is there a list of diff between nova CLI and openstack CLI wrt parity? In particular, I would like a --property for 'openstack server rebuild'. Should i open a story about it and make the change or was there a reason not to support that?14:53
melwittthere are differences, we don't have an official list. there might be an etherpad out there somewhere that describes the parity discrepancies14:55
melwittI don't know what --property is, so I need to look at the docs to see what it is14:55
waterloomelwitt: should i assume it was just missed (it is --meta in 'nova server-rebuild')14:55
PapaOursmriedem: now that nova supports nested a-c, could you drop your -2 on https://review.openstack.org/#/c/599208/ ?14:55
waterloomelwitt: err, 'nova rebuild'14:56
* waterloo will be glad to only have one CLI to remember...14:56
melwittwaterloo: yeah, if there's anything you can do in novaclient that you can't do in osc, it's not intentional14:56
waterloomelwitt: great or not great ;) I'll submit a story about it cuz i love stories! :D14:57
melwittwe talked about the general problem of the lack of parity at the PTG14:57
*** _hemna has joined #openstack-nova14:57
melwittand IIRC, we talked about the possibility of moving our CLI to be an OSC plugin (which we've talked about in the past, but not too seriously) but then I think dtroyer said OSC is in the process of moving to openstacksdk so that should be completed first14:58
mriedemwaterloo: https://etherpad.openstack.org/p/compute-api-microversion-gap-in-osc14:58
*** helenafm has quit IRC14:58
melwittcool, I thought mriedem might have an etherpad14:59
waterloomelwitt: i did it for ironic awhile ago, somewhat painful to go through and compare/address but done! you too, can do it, just need to find a guinea pig, err volunteer.14:59
waterloothx mriedem!14:59
mriedemanything else thats missing unrelated to microversions is just a new parity story against OSC in SB14:59
*** tbachman_ is now known as tbachman15:04
waterloomriedem: would you mind if i opened a story (in python-openstackclient) wrt nova CLI feature parity and just link this etherpad? although maybe that won't help, not sure i would have looked for that15:05
mriedemsure...there are already several osc stories created and linked *from* the etherpad since that's how the work was being tracked. doesn't matter much to me if there is an epic or something in SB though.15:06
mriedemneeds a project manager to create a board and all that15:07
mriedemand people to test/review the changes15:07
*** mdbooth has quit IRC15:07
waterloomriedem: good luck with that...15:08
mriedemwell if it were a community goal in T...15:08
*** mdbooth has joined #openstack-nova15:08
mriedemthen someone could maybe justify to their employer dedicating a lot of time to this15:08
*** mdbooth has quit IRC15:08
*** med_ has joined #openstack-nova15:09
waterloomriedem: I'm sure lots of folks would support that!15:09
waterloo(dunno about companies but who knows...)15:09
*** mdbooth has joined #openstack-nova15:09
sean-k-mooneywaterloo: are ye talking about nova/osc feature partity?15:10
waterloosean-k-mooney: yeah, are you working on it? (i can only hope)15:10
sean-k-mooneywaterloo: finucannot:  and i said we were interested in looking at it if we had time15:11
*** _pewp_ has quit IRC15:11
mriedemmelwitt: i don't think we need to care about getting these CI job changes into ocata-em https://review.openstack.org/#/q/I41b03a34795efe139d5911c605cdbd3c47a2f059 - given that, everything else is merged for ocata and we could do the final release and tag the branch15:11
*** mdbooth has quit IRC15:11
sean-k-mooneywaterloo: that assume i get my feature dev done early in S e.g. m1/m2 so that i have tiem to look at it later in the cycle15:11
*** _pewp_ has joined #openstack-nova15:11
*** mdbooth has joined #openstack-nova15:12
waterloosean-k-mooney: sweet, thx, I can hope then :)15:12
*** _hemna has quit IRC15:12
melwittmriedem: makes sense. I added a new [as of yesterday] bug to the ocata-em etherpad, but the more I think about it, it's super latent so probably not worth holding up for15:13
*** _hemna has joined #openstack-nova15:14
mriedemyeah i saw, and commented15:14
mriedemin the etherpad. i don't think we need to hold up EM forever15:14
melwittI wasn't thinking of it as forever, just someone ran into the problem and the fix fixed it for them. and it's a 5 line change15:15
melwittand I wasn't sure if there was anything else in the works or what date the rest of the community was targeting for EM, so I just thought I'd ask15:16
melwittif everything and everyone else is ready to go, then we can just go ahead15:17
mriedemEM means the branch stays open so people can backport fixes and pull from stable/ocata,15:17
mriedemwhich is good enough IMO15:17
melwittyeah. again, I didn't know when the rest of the community was targeting EM so I didn't know if there was time anyway. if everyone's ready to go now, then that's fine, let's go ahead15:19
*** macza has joined #openstack-nova15:20
*** ttsiouts has joined #openstack-nova15:21
mriedemi doubt anyone else is ready to go15:21
*** munimeha1 has quit IRC15:22
mriedemor is working on this15:22
mriedemlots of projects probably just want to eol ocata15:22
mriedemlike heat15:22
waterloosean-k-mooney, mriedem: fyi, I added that as a story, only to try to get eyes on it and to mention the etherpad: https://storyboard.openstack.org/#!/story/200398015:22
*** mdbooth has joined #openstack-nova15:22
*** gyee has joined #openstack-nova15:24
*** bnemec is now known as beekneemech15:27
cdentIs there some way to boot a server such that you force the host and the scheduler doesn't get involved? I know that's possible with migrations, but is it with boot?15:28
*** munimeha1 has joined #openstack-nova15:28
sean-k-mooneycdent: yes and its kindo fo a bug15:28
mriedem--availability-zone nova:<host>15:28
sean-k-mooneyyep that ^15:29
mriedemhttps://docs.openstack.org/nova/latest/admin/availability-zones.html15:29
*** ttsiouts has quit IRC15:29
mriedemmelwitt: so i'm going to propose rocky/queens/pike/ocata releases and then the ocata-em tag on top of that15:29
melwittmriedem: ack15:29
*** ttsiouts has joined #openstack-nova15:30
sean-k-mooneymriedem: what effect does the em tag actully have? we are not going to backport anything ourselves anymroe right but in therory others can?15:30
mriedemwe?15:31
cdentsean-k-mooney, mriedem: interesting, thanks. The reason for this is to be able to move a vm from cloud A to cloud B in magical ways. When some form of it gets B, want to be able to skip the scheduler15:31
mriedemanyone that cares about stable can backport stuff as before15:31
mriedemas for what it means, read https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html15:32
sean-k-mooneypeople working on nova bugfixs. normally they would be backported to stable branches subject to policy but would that still happen for em branches15:32
* sean-k-mooney clicks15:32
mriedemtl;dr we don't release it, VMT can ignore it, and we can let it rot if no one cares about it15:33
sean-k-mooneymriedem: sure but since we dont delete that branch and convert it to just at tag if a disto or a large customer is still using it and wants to backport fixes they still could15:34
*** ttsiouts has quit IRC15:34
*** pcaruana has quit IRC15:39
openstackgerritBalazs Gibizer proposed openstack/nova master: Handle allocations consuming only from the child RPs  https://review.openstack.org/60829815:42
*** spatel has joined #openstack-nova15:46
spatelsean-k-mooney: morning15:46
spatelhad one general question if you available Ping me! no rush15:47
fried_ricefinucannot: https://review.openstack.org/#/c/530924/ is +A, but there's some fup work whenever you feel like it :)15:52
finucannotfried_rice: Ack, I'll tackle those now15:56
*** mrjk_ has quit IRC15:56
*** mchlumsky has quit IRC15:57
*** mrjk_ has joined #openstack-nova15:57
*** mrjk_ has quit IRC15:58
*** mrjk_ has joined #openstack-nova15:58
*** lpetrut has quit IRC15:59
sean-k-mooneyspatel: hi15:59
leakypipesfried_rice: you pushing an updated revision on https://review.openstack.org/#/c/607989/?15:59
sean-k-mooneyspatel: am i will be around for a littel bit but did not sleep very weel last night16:00
fried_riceleakypipes: Nope, cfriesen/jackding are taking over.16:00
*** mrjk_ has quit IRC16:00
spatelsean-k-mooney: hey! so my SR-IOV working great now i am working in availability zone and this is how my server layout work in racks https://ibb.co/j9kgUK16:00
*** jchhatba_ has quit IRC16:00
fried_riceleakypipes: My interest in the issue was purely in wearing you down on the whole using-traits-for-config thing. So my work here is done.16:00
spatelsean-k-mooney: sorry to hear that!!16:00
spatelits long weekend get some sleep :)16:01
spatelBase on that diagram how should plan my availability zone?  and how does openstack spread instance between two AZ ?16:02
spatelif i tell openstack create 10 instance then how does it get divided between AZ ?16:02
PapaOursspatel: there was an excellent talk about AZs in a previous Summit16:03
PapaOursspatel: lemme help you by giving you the session link16:03
spatelPapaOurs: great they must have video in youtube then16:04
PapaOursspatel: https://www.openstack.org/videos/vancouver-2018/curse-your-bones-availability-zones-116:04
spatelsweet!!16:04
leakypipesfried_rice: :)16:04
spateltrying to understand mechanic behind AZ and scheduler, how drive logic to spread machine out between two zone?16:05
spatelis that scheduler job ?16:05
PapaOursspatel: that's a filter16:06
PapaOursbut see the video, it explains it :)16:06
spateli am watching it..16:06
spatelPapaOurs: thanks16:06
*** helenafm has joined #openstack-nova16:06
PapaOurs6pm here, time for opening a beer16:08
PapaOurshave a nice week-end folks16:08
PapaOurs\o16:08
*** PapaOurs is now known as bauzas16:08
sean-k-mooneyspatel: sorry just looking at teh diagram now16:09
*** mriedem has quit IRC16:09
spatelno worry! take your time16:10
spatelSR-IOV doesn't support bonding so i can't create bond between two TOR switches16:10
spatelSR-IOV does support bonding but inside VM (i think i am not ready for that)16:11
sean-k-mooneyso availablity zones are a user facing grouping mechaniums. from the schduler point of view they are just a metadata tag on a host aggaragte16:11
*** jpena is now known as jpena|off16:12
sean-k-mooneyso if you requst a vm in zone A the scudler will only look at host that are in a host aggragte with avaiablity_zone=a set16:12
*** itlinux has joined #openstack-nova16:12
*** s10_ has quit IRC16:12
sean-k-mooneyit then allpies the rest of the filters to reduce the set of host. e.g. ram, cpus, disk or in your case pci deivces for sriov16:13
spatelbut that would be hardwire right?16:13
sean-k-mooneythat is a bit of a simplicfation  as there is another service called placement that is also invoved.16:13
sean-k-mooneyso yes and no16:13
spatelcurrently we are using AWS with terraform and we tell tf to create instance between A and B zone and it does it job16:14
sean-k-mooneythe operator e.g. you in this case has to decalre what hosts are in the A avaliablity zone16:14
sean-k-mooneyspatel: AWS availablity zones ar enot the same as openstacks16:14
spatelunderstand but is there way i can get functionality close to AWS16:15
sean-k-mooneyin AWS an availablity zone is a seperate falut domain so if you have an ouate in zone A zone by is still fine16:15
spatelLet's in openstack i create two AZ  (a, b)  and i want to tell openstack go build 10 vm then does openstack spread machine out between two AZ ? or this is not possible?16:16
sean-k-mooneyspatel: yes unfortunetely we leave that as an exerciest to the operator to configure cooreltys.  1.) you can actully map your AZ  to seprate falut domains 2.) you can use cells + availahity zone or 3.) you can use regions16:16
spatelif not possible then i have to specify AZ by hand16:16
sean-k-mooneyspatel: if they are different requires e.g. 10 vm requires they can be spread. if you use the multi create api im not certine if it will spread or scdule them all to the same AZ16:17
spatelcurrently i have TOR level AZ (i am not much worried about power failure)16:18
spateljust want to make sure if i loose TOR it won't knock out all my customer server16:18
spatelso trying to spread out VM between two tor16:19
sean-k-mooneyok the other thing that you are sharing with openstack AZ are your controler service. e.g. your db and api seriveces16:19
*** derekh has quit IRC16:19
spatelhmm??16:19
*** ralonsoh has quit IRC16:20
sean-k-mooneyso in a standard openstack deployment you have contoler nodes that run the api services, schduler and databases16:20
spatelYes i have 3 controller node16:21
sean-k-mooneythoes contoll plane nodes manage the compute nodes that reside in AZs16:21
spatelyup16:22
sean-k-mooneyyes so in your 2 AZ config as long as the compute node can sitll acess one of the 3 controllers and you can also acess the same controler then you will be able to manage that host16:22
sean-k-mooneyif you have a network partition that breaks that link then the guests workload running on the compute nodes may still work fine but you will lose the ablity to manage them16:23
spateli am totally fine if i loose management access!! as far as application serving my customer16:23
sean-k-mooneyin aws the api/dataables/storage and networking uplinks are deployed per AZ so the failrue more for openstack is slightly different as the contolplane is not per aZ16:24
spatelreplacing TOR switch will take may be 1 hour or so!!16:24
spatelas far as i meet my customer SLA we are fine with that16:24
sean-k-mooneyok :) many people coming form AWS expect openstacks availablity zone to map exactly to the same concept as AWS. you seam to have done more reasearch or given it more taught then most16:25
spatelIn my design if you see i break total server between two TOR switch and if either one down i will loose 50% machine16:25
spatelI totally get that point AWS != openstack in AZ context :)16:26
sean-k-mooneyspatel: so looking at https://ibb.co/j9kgUK can you discibe your intient16:26
*** sahid has quit IRC16:26
sean-k-mooneyyou have 2 tors16:26
spatelyes16:26
sean-k-mooneyand 2 AZs one per tor16:27
spatelyes16:27
sean-k-mooneyhalf of your servers use TOR-1 for there SRIOV dataplane and TOR-2 for managmente16:27
spatelyup! that is correct16:27
sean-k-mooneythe other half swap which TOR is used form management and data16:28
spatelyup!16:28
sean-k-mooneyso if TOR-1's PSU explodes half the servers will loose data conenctivity and the other half will loose manament capablity16:29
spatelyes! that is right16:29
sean-k-mooneyam is that what you want?16:29
spatelyes in PSU failure still my 50% instance will be live and providing service but openstack will loose management function16:30
sean-k-mooneyi assume you do not have the option to seperate management and data traffic16:30
*** cdent has left #openstack-nova16:30
spatelI don't have option because i have to purchase NIC to install on compute node also SR-IOV doesn't do bonding so i am going to loose some customer if TOR switch blowup16:31
sean-k-mooneyspatel: do you intend to pass the PF or VF to the vms running your voip applications?16:31
spatelyes my VF is attach to instance16:32
spateli don't have any kind of bonding anywhere at present because of limitation of SR-IOV16:32
spatelhttp://paste.openstack.org/show/731595/16:33
spatelThis is what my compute look, i am running 2 instance with dual NIC on two different VLAN16:33
sean-k-mooneyright so what i was goint to suggest is that you could either reserve a VF or use the pf of your sriov nic as a bond pair for your manament network.16:34
spateloh!! wait is that possible?16:35
sean-k-mooneyso in your case you can create a bound between eno1 and eno2 for managment traffic and then openstack can use just the vfs16:35
sean-k-mooneyspatel: yes16:36
spateli thought if you configure NIC for sr-iov then you can't bond them16:36
sean-k-mooneyit depends on the nic16:36
spatelI have tried that and found my loop in my switch16:36
spatelmay be it was config issue..16:36
spateli have all Cisco nexus switch running vPC (active+active bonding mode=4)16:37
spateli have Qlogic NIC16:37
sean-k-mooneywell it defintely depens on how you create the bond (e.g. just mac loadbalcing with out swich supprot or lacp with it)16:37
spateldid you every run that kind of test?16:38
*** mdbooth has quit IRC16:38
spateli would like to know if you did and what config you configure16:38
spatelI will run same experiment on my LAB and try come combination16:39
spatelthat was great if it work16:39
sean-k-mooneyi have never used Qlogic NIC but i have created bonds with intel nics in active failover mode16:39
spatels/was/would be/16:39
spateldid you configure with SR-IOV ?16:40
spateli meant SR-IOV + Mgmt (in bonding)16:40
spatelI think i understand what you trying to explain.. i will give it a try..16:40
spateli wish if you can create bonding between two VF :)16:41
sean-k-mooneythat is a good questiong the host had both sriov and a manament bound but i cant remeber if the manament bound was using the pf that had the sriov vf allocated from it16:41
spateli remember last time when i try to did that i got interface error (BPDU guard disable my nic)16:42
sean-k-mooneyi think i had 10G nic for tenat data/vfs  1 1G nic and a second 10G nic bonded for manament and ceph traffic16:42
spateloh!! you have PF level isolation16:42
*** pcaruana has joined #openstack-nova16:42
spatelI have plan in future to install 1G nic for Mgmt traffic but not this year16:42
sean-k-mooneyspatel: yes i did in that case but im tring to remeber if i tried to create a bound with the pf used for the VFs16:43
spatelhmm! worth running some test :)16:44
sean-k-mooneyspatel: see the thng was will i had vm using VFs allocated form the PF named eth1 i also added eth1 to ovs16:44
spatelhmm!!16:44
sean-k-mooneyso i think that is why i did not add it to the storage/manament bond16:44
sean-k-mooneye.g. ovs was using the PF16:44
spateli will try if i can setup bonding with PF then it would be great16:45
spateli can protect mgmt traffic but still i will loose dataplan16:45
sean-k-mooneyanyway my 1st concern with https://ibb.co/j9kgUK would be that while the datapane woudl remain up on half the node that same half would no lonbger be manageable16:46
*** dims has joined #openstack-nova16:46
sean-k-mooneypersonally if i could not have a ha manament plane i would put the manament and datapane for my hosts to the same TOR16:47
spatelhmm! ok that also make sense16:48
sean-k-mooneyprovide you deploy your app to both TORs you will still have half your applications service coustomers but you wil be able to also mange those hosts16:48
spateldata + mgmt on same TOR16:48
spatelIf we loose mgmt for few hour i don't think its going to be a big deal..16:49
*** helenafm has quit IRC16:49
spatelthese compute nodes are going to run only 1 or 2 instance ( because they are CPU hungry )16:49
sean-k-mooneywell it depens on your useage model. with the split deployemnt you were goning tohave that anyway right since you did not have manamnet ha16:50
spatelHere i am just trying to minimize failure (50%)16:50
*** pcaruana has quit IRC16:50
spateli have good remote hand in datacenter and they will replace TOR within 1 hour :)16:51
openstackgerritStephen Finucane proposed openstack/nova master: Fix nits in choices documentation  https://review.openstack.org/60831016:51
finucannotfried_rice: ^16:52
spatelmy main question was if i split server between two AZ then how i can automate instance build so they spread our between A16:52
spatelAZ16:52
sean-k-mooney:) well just one other note. if you do end up with ovs-dpdk instead of sriov in that case you would be better just bonding eno1 and eno2 and then using ovs to deivde up the bandwith betwwen manament and teant use.16:52
sean-k-mooneyam waht you are asking for is how can i express an antiafinity policy16:53
spatelcurrently i have script which i manually specify vm-1 go to AZ-1 and vm-2 go to AZ-2 (I am doing by hand )16:53
sean-k-mooneySteelyDan: ^ we do not have a way to do AZ anti afinity with server groups correct16:54
spatelDPDK is next month todo list :)16:54
SteelyDansean-k-mooney: I don't even understand those words16:54
spatelI am reading this line from one of openstack doc: The Nova scheduler provides filters that you can use to ensure that OpenStack instances are automatically placed on the same host (affinity) or separate hosts (anti-affinity).16:55
sean-k-mooneySteelyDan:  spatel is trying to desing a layout that will allow https://ibb.co/j9kgUK one of the two tors to fail and have openstack loadbalnce vms across them16:55
SteelyDanspatel: that sentence means you can say "put this instance on the same host as this other instance"16:55
spatele.g - if i tell openstack build 50 instance then it will load 25 on TOR1 server and 25 in TOR2 server16:56
SteelyDanspatel: the doc line you quoted above is purely about affinity between instances, not about affinity or load balancing between two hosts16:57
SteelyDanI don't think we have any way to do that with the existing set of filters, no.16:57
spateloh!16:57
sean-k-mooneySteelyDan: we had been discussing using AZ to model the network falut domain(TOR)16:57
sean-k-mooneyspatel: you might be able to do this with heat. on top of nova16:58
sean-k-mooneyspatel: there is one other way to do it which is to use neutron physnets16:59
SteelyDansean-k-mooney: if nova can't represent this, I'm not sure how you could get heat to do it for you16:59
spatelhmm! i think time to exploration16:59
sean-k-mooneySteelyDan: i was specalting that you may be able to tell heat to spit this request between AZ a and AZ b16:59
SteelyDanobviously if you want to hardcode alternating boxes in the rack to two different AZs and then boot your instances into AZs with your own spread then you can do this17:00
SteelyDanwhich is all heat could do17:00
SteelyDanbut what I mean is, I don't see a way to specify this generically to nova with existing stuff17:00
spatelwe can do that by script also right? script will take count and divide them by number of AZ and feed them to nova boot17:01
SteelyDansure17:01
sean-k-mooneyspatel: yep17:01
sean-k-mooneythe othere way to model this is via neutron physnets17:01
spatelor write more smart script will will collect data from AZ and then compare which AZ has more room to handle more instance17:01
sean-k-mooneyon all the hosts connected to tor1 lable the physnet as top117:02
sean-k-mooneyand on the others tor217:02
spatelcan you explain about neutron physnets?17:02
spateloh!! i know what you saying17:02
sean-k-mooneywhen using VLAN or Flat netwroks in neutron they are assocated with a physica network or physnet in neutron17:03
spatelhmm!17:03
sean-k-mooneyso if you have 2 networks and 2 physnets you can have one AZ and then booth half your vms with network 1 and half with network 217:03
sean-k-mooneyspatel: that wouls more expcltly model what your actuly doing17:04
spatelnever thought about that but look like need to explore, i will try to run some test and see how it work out17:04
sean-k-mooneyspatel: it has littel other advanates however over using AZs and still would require your script17:04
spateli think short term hack is script17:05
spatelbut i will go dipper17:05
spatelI think this was really good discussion, let me explore all option and find best fit.17:05
spatelsean-k-mooney: SteelyDan thank you so much for your input..!17:06
sean-k-mooneyspatel: sure thing. am fyi while i have ran some devclouds and worked on openstack for quite a while there are also some oepratros in irc that can share there expreicnes17:06
spateli will find them out soon :)17:07
sean-k-mooneyspatel: maybe  reach out to mnaser too im sure he can share his experices17:07
spatelthis is just beginning i have more to learn17:07
*** dave-mccowan has joined #openstack-nova17:08
spatellet me write down his name :)17:08
spateldid you work on Octivia LB ?17:08
sean-k-mooneyspatel: well if you havent check it out before there is a lot of greate matial on the openstack foundation youtube channel. but if i can help you know where to find me17:08
sean-k-mooneyspatel: Octivia no unfortunetly not.17:09
spateli think i know where to go for any kind of help... (find sean-k-mooney)17:09
spatelno worry i may soon need ELB for cloud17:09
spatelwe have lots of F5 but i need ELB so i don't need to worry about capacity17:09
spatelBRB my lunch is ready..17:10
*** dave-mccowan has quit IRC17:14
*** sean-k-mooney has quit IRC17:16
openstackgerritMohammed Naser proposed openstack/nova master: DNM: test GPU jobs  https://review.openstack.org/60831517:16
*** dtantsur is now known as dtantsur|afk17:18
*** sean-k-mooney has joined #openstack-nova17:24
openstackgerritMohammed Naser proposed openstack/nova master: DNM: test GPU jobs  https://review.openstack.org/60831517:25
*** jangutter has quit IRC17:31
*** eharney has quit IRC17:34
openstackgerritSurya Seetharaman proposed openstack/nova master: Refactor scatter-gather utility to return exception objects  https://review.openstack.org/60793417:37
openstackgerritSurya Seetharaman proposed openstack/nova master: Return a minimal construct for nova show when a cell is down  https://review.openstack.org/59165817:37
openstackgerritSurya Seetharaman proposed openstack/nova master: Return a minimal construct for nova service-list when a cell is down  https://review.openstack.org/58482917:37
openstackgerritSurya Seetharaman proposed openstack/nova master: API microversion bump for handling-down-cell  https://review.openstack.org/59165717:37
*** tssurya has quit IRC17:44
*** moshele has joined #openstack-nova17:44
*** med_ has quit IRC17:46
*** eharney has joined #openstack-nova17:49
openstackgerritMohammed Naser proposed openstack/nova master: DNM: test GPU jobs  https://review.openstack.org/60831517:56
*** sridharg has joined #openstack-nova18:01
*** moshele has quit IRC18:02
*** sridharg has quit IRC18:04
*** Blotis_ has joined #openstack-nova18:13
Blotis_Test18:13
*** tssurya has joined #openstack-nova18:19
Blotis_Is it possible from withing the CLI to figure out which VM's are currently using a particular group?18:21
*** imacdonn has quit IRC18:22
*** imacdonn has joined #openstack-nova18:22
Blotis_if I want to remove a security group that is currently being used by a vm, I have to remove that security group from that instance first...what if I have too many instances? is there a quick solution?18:22
*** tbachman has quit IRC18:32
openstackgerritMerged openstack/nova master: De-dupe subnet IDs when calling neutron /subnets API  https://review.openstack.org/60804018:32
openstackgerritMerged openstack/nova master: conf: Use new-style choice values  https://review.openstack.org/53092418:32
*** Swami has joined #openstack-nova18:36
*** slaweq has quit IRC18:37
*** slaweq has joined #openstack-nova18:38
*** eharney has quit IRC18:40
openstackgerritmelanie witt proposed openstack/nova stable/rocky: De-dupe subnet IDs when calling neutron /subnets API  https://review.openstack.org/60833618:46
openstackgerritMerged openstack/nova master: Remove an unnecessary duplicate flag  https://review.openstack.org/60816218:55
*** tbachman has joined #openstack-nova18:56
*** moshele has joined #openstack-nova19:20
*** dave-mccowan has joined #openstack-nova19:23
*** erlon has quit IRC19:27
*** tbachman has quit IRC19:34
*** slagle has quit IRC19:35
*** eharney has joined #openstack-nova19:46
openstackgerritEric Fried proposed openstack/nova master: Fix nits in choices documentation  https://review.openstack.org/60831020:07
fried_ricefinucannot: Fixed one typo and +2d ^20:14
*** spatel has quit IRC20:47
*** munimeha1 has quit IRC20:52
*** rtjure has quit IRC21:07
*** med_ has joined #openstack-nova21:10
*** med_ has quit IRC21:20
openstackgerritMerged openstack/nova master: Run ServerMovingTests with nested resources  https://review.openstack.org/60408421:27
*** tbachman has joined #openstack-nova21:32
*** priteau has quit IRC21:46
*** itlinux has quit IRC21:50
*** moshele has quit IRC21:55
*** slagle has joined #openstack-nova22:00
*** itlinux has joined #openstack-nova22:19
*** itlinux has quit IRC22:22
*** spatel has joined #openstack-nova22:34
*** spatel has quit IRC22:39
*** cfriesen has joined #openstack-nova22:44
*** tssurya has quit IRC22:53
*** artom has quit IRC22:54
*** Blotis_ has quit IRC22:55
*** jmlowe has quit IRC23:00
*** jmlowe has joined #openstack-nova23:03
*** Swami has quit IRC23:04
*** macza has quit IRC23:06
*** tssurya has joined #openstack-nova23:26
*** gyee has quit IRC23:31
« Thursday, 2018-10-04 Index Saturday, 2018-10-06 »

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