Tuesday, 2018-07-17

openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in libvirt/test_driver.py (5)  https://review.openstack.org/57084200:00
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in libvirt/test_driver.py (6)  https://review.openstack.org/57133000:02
openstackgerritMerged openstack/nova master: z/VM Driver: add power actions  https://review.openstack.org/54334000:35
openstackgerritMerged openstack/nova master: z/VM Driver: add get console output  https://review.openstack.org/54334400:46
openstackgerritMerged openstack/nova master: Adjust log style and remove ocata support  https://review.openstack.org/57646200:46
openstackgerritMerged openstack/nova master: fix cellv2 delete_host  https://review.openstack.org/58217100:46
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in libvirt/test_driver.py (7)  https://review.openstack.org/57199200:54
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in libvirt/test_driver.py (8)  https://review.openstack.org/57199300:55
*** mriedem has quit IRC01:36
*** lei-zh has joined #openstack-placement02:01
*** takashin has joined #openstack-placement02:04
*** tetsuro has joined #openstack-placement02:12
openstackgerritTakashi NATSUME proposed openstack/nova master: Transform volume.usage notification  https://review.openstack.org/58034502:15
openstackgerritTakashi NATSUME proposed openstack/nova master: Transform libvirt.error notification  https://review.openstack.org/48485102:36
*** lei-zh has quit IRC02:57
*** lei-zh has joined #openstack-placement02:57
openstackgerritTakashi NATSUME proposed openstack/nova master: Add the guideline to write API reference  https://review.openstack.org/56905803:01
openstackgerritGhanshyam Mann proposed openstack/nova master: Remove "DEPRECATED" tag from Obsolete APIs  https://review.openstack.org/58309203:20
*** lei-zh has quit IRC03:23
*** lei-zh has joined #openstack-placement03:23
openstackgerritMultipleCrashes proposed openstack/nova master: Retry decorator fix for instances which go into ERROR state during bulk delete  https://review.openstack.org/56341804:40
openstackgerritGhanshyam Mann proposed openstack/nova master: Remove "DEPRECATED" tag from Obsolete APIs  https://review.openstack.org/58309204:40
openstackgerritGhanshyam Mann proposed openstack/nova master: Remove "DEPRECATED" tag from Obsolete APIs  https://review.openstack.org/58309204:42
*** lei-zh has quit IRC04:48
*** lei-zh has joined #openstack-placement05:06
*** e0ne has joined #openstack-placement05:18
*** tetsuro has quit IRC05:19
*** e0ne has quit IRC05:20
*** tetsuro has joined #openstack-placement05:22
*** lei-zh has quit IRC05:33
*** lei-zh has joined #openstack-placement05:35
*** lei-zh1 has joined #openstack-placement05:57
*** lei-zh has quit IRC05:58
*** alex_xu has quit IRC05:59
*** alex_xu has joined #openstack-placement06:02
*** lei-zh- has joined #openstack-placement06:05
*** lei-zh1 has quit IRC06:06
openstackgerritMerged openstack/nova master: Address nits in server group policy series  https://review.openstack.org/58161606:23
openstackgerritjichenjc proposed openstack/nova master: Enhance doc to guide user to use nova user  https://review.openstack.org/58311506:31
*** alex_xu has quit IRC06:36
*** alex_xu has joined #openstack-placement06:36
*** lei-zh- has quit IRC06:38
*** lei-zh has joined #openstack-placement06:42
*** lei-zh has quit IRC06:53
*** lei-zh has joined #openstack-placement06:53
*** ttsiouts has joined #openstack-placement06:55
*** lei-zh has quit IRC07:01
*** lei-zh has joined #openstack-placement07:01
*** peereb has joined #openstack-placement07:04
*** ttsiouts has quit IRC07:20
*** ttsiouts has joined #openstack-placement07:59
*** e0ne has joined #openstack-placement08:05
*** ttsiouts has quit IRC08:16
*** ttsiouts has joined #openstack-placement08:19
*** takashin has left #openstack-placement08:31
*** tssurya has joined #openstack-placement08:35
*** alex_xu has quit IRC08:45
*** alex_xu has joined #openstack-placement08:46
*** cdent has joined #openstack-placement08:47
*** ttsiouts has quit IRC08:56
*** ttsiouts has joined #openstack-placement08:57
*** sean-k-mooney has joined #openstack-placement09:20
openstackgerritGhanshyam Mann proposed openstack/nova master: Merge server create for scheduler hint extension  https://review.openstack.org/57906709:40
openstackgerritGhanshyam Mann proposed openstack/nova master: Merge server create for multiple-create extension  https://review.openstack.org/58001709:41
openstackgerritGhanshyam Mann proposed openstack/nova master: Merge server create for scheduler hint extension  https://review.openstack.org/57906709:48
openstackgerritStephen Finucane proposed openstack/nova master: scheduler: Start utilizing RequestSpec.network_metadata  https://review.openstack.org/56445209:51
openstackgerritStephen Finucane proposed openstack/nova master: Assorted cleanups from numa-aware-vswitches series  https://review.openstack.org/58265109:51
*** lei-zh has quit IRC10:08
*** ttsiouts has quit IRC10:16
cdentbbs10:21
openstackgerritGhanshyam Mann proposed openstack/nova master: Merge server create for multiple-create extension  https://review.openstack.org/58001710:53
*** tetsuro has quit IRC11:01
*** ttsiouts has joined #openstack-placement11:16
openstackgerritGhanshyam Mann proposed openstack/nova master: Merge server create for keypair extension  https://review.openstack.org/58320311:19
openstackgerritBalazs Gibizer proposed openstack/nova master: Escalate UUID validation warning to error in test  https://review.openstack.org/54038611:26
openstackgerritBalazs Gibizer proposed openstack/nova master: Fix a newly introduced UUID warning in the unit test  https://review.openstack.org/58320511:26
openstackgerritZhenyu Zheng proposed openstack/nova master: Address nit in 79dac41fee178dabb547f4d7bc10609630767131  https://review.openstack.org/58321211:40
*** edmondsw has joined #openstack-placement12:06
*** ttsiouts has quit IRC12:09
*** ttsiouts has joined #openstack-placement12:20
cdentjaypipes, efried found the bug I was experiencing, left a comment about it on https://review.openstack.org/#/c/582383/12:30
jaypipeslooking12:47
jaypipescdent: see line 4010 on my original submission: https://review.openstack.org/#/c/582383/1/nova/api/openstack/placement/objects/resource_provider.py12:49
efriedGood one Chris.12:50
efriedjaypipes: 4010?12:50
jaypipesefried: note that was addressed in my original12:51
jaypipescdent, efried: sorry, 410112:51
jaypipesdyslexia sets in12:51
efriedthat makes more sense.12:51
jaypipesefried: you'd mentioned that wouldn't be necessary if we did the two-step in your revision.12:52
jaypipesefried: but maybe it's still needed?12:52
efriedjaypipes: I didn't say that, but yes, I agree something like it is still needed.12:52
efriedcdent, jaypipes: So we could stuff that same loop into the new function. But it's not quite that simple - we also need to *check* the rp generations in the allocations at some point before we just overwrite them.12:53
efriedSo like maybe we start off before we do anything else and make sure they match each other12:53
efriedi.e. for each rp found in both the inventories side and the allocations side, make sure the generations are the same; if not, that's like a 400 I think.12:54
efriedOnce that check is out of the way, then yes, we can make sure the same rp objs are used in both the alloc and inv sides.12:54
efriedand in fact, all of that should arguably be done from the handler.12:55
efriedBecause it's the handler that's responsible for converting the incoming dicts to objects.12:55
jaypipesefried: why do we need to check them?12:55
efriedjaypipes: To make sure they're the same. If I pass an RP with gen 1 on the allocs side and the same RP with gen 2 on the inv side, I done f'ed up.12:55
jaypipesefried: just use the resource provider objects that were used in the first step. if they then come back as concurrent update detected, that's a *good* thing, right?12:56
*** peereb has quit IRC12:56
jaypipesefried: it means we prevented overwriting when someone made a change we didn't know about.12:56
efriedjaypipes: In that scenario it would be a bad thing if they didn't raise concurrent update; but that doesn't mean it's always a good thing if they do.12:57
jaypipesefried: if we use the actual objects that were used in the first part of the operation (like my code did originally), we can trust nobody else messed with those object generations, right? and that means if we submit the final replace_all() and get back a concurrent update detected, that means the generation increment failed which is the correct protection we wanted (a *different* thread updated those records from our own).12:58
jaypipesefried: ok, walk me through what you're thinking w.r.t. the "good thing".12:58
efriedjaypipes: I think we're saying the same thing. Reusing objects. Walking...12:58
jaypipesah, ok12:58
efried1) The handler first makes sure that, in the *dict* representations, the caller passed the same generations for a given RP that shows up in both the inv and alloc sides. This is a sanity check. The payload is simply invalid, bogus, garbled, nonsense if this constraint is not met.12:59
efried2) The handler keeps a cache of rp objs it sees as it populates the inv object, and then reuses those as it populates the allocs object.12:59
efried3) The db side method remains unchanged.13:00
jaypipesefried: isn't that basically what cdent's PSOT /reshaper code is already doing? https://review.openstack.org/#/c/576927/8/nova/api/openstack/placement/handlers/reshaper.py13:02
jaypipesefried: except instead of "keeping a cache of rps", it's just sending the Inventory objects that contain the providers that it already generation-checked.13:02
jaypipesefried: obviously, cdent's code doesn't "reuse those as it populates the allocs object", but that's basically what my original line 4101 code did in the reshape() function, so we could just re-use that, right? and keep that logic out of hte handler.13:05
jaypipeswhich I'm sure cdent would like ;)13:05
jaypipes(keeping code out of the handler)13:05
efriedstand by, let me make sure I'm going to mean what I'm about to say...13:06
cdentcdent loves it when code is not in the handler13:07
* cdent is catching up, was hanging laundry13:07
jaypipescdent: like a good Brit. well done.13:08
cdentalso like a good brit, it should start raining on it any minute13:08
jaypipesheh13:09
*** jaypipes is now known as was13:09
*** was is now known as jaypipes13:10
*** e0ne has quit IRC13:11
cdentpresumably as a first step, changing the test to not reuse objects is one way to "look like the real world" and then fixing things so the tests passes moves us along13:12
efriedPutting aside the question of where the code will live (handler or db side) for now:13:13
efried1) We still need the sanity check to make sure the RP gens on the inventory side are consistent with those on the allocs side.  That is not happening anywhere now, in old code or new.13:13
efried2) We can either a) reuse rp objects built while creating the InventoryList as we populate the AllocationList; or b) replace the rp objects in the AllocationList after the fact like 4101.13:13
efriedFor 2a we would need to change some method signatures (like passing a dict of already-retrieved rp objects into create_allocation_list).13:13
efried2b seems a bit ugly and inefficient, because we already went through the work of creating rp objects that we're now going to throw away.13:13
efriedIn any case, the goal being that:13:13
efried3) By the time the existing db-side code runs, the inv and alloc objects are sharing rp objects.13:13
cdentI would _very_ much prefer that the sharing only be inside the obj.rp.reshape method and that we not require it by the caller13:16
jaypipescdent: ++13:16
efriedAs for the question of handler or db side, today it seems like the handler side is responsible for converting payload dicts into objects; and the db side is responsible for using those objects to effect db changes. So if we go with 2a, it makes sense for it to live on the handler side fo sho, because it's part of *constructing* the objects...13:16
jaypipesefried: let us free cdent of this worry.13:16
efried...so since both of you agree the sharing needs to be enforced on the db side, I guess that means 2b.13:16
jaypipesefried: I'm not entirely sure I agree it's important to check the alloc gens vs. the inv gens.13:17
efried...which I still think *could* have been done on the handler side; but I get y'all's point, and it's a good reason to do it in the db side.13:17
efriedjaypipes: Really? Then which would you go with?13:17
cdentefried: the allocations don't come with gens when sent as data. they only get them by loading them13:18
cdentso if we treat the inv gens as authoritative, then we get the protection you want13:18
jaypipesefried: I would go with 2b. I'm just saying I don't think we need a separate step that looks at the data sent in the allocations block's generations and makes sure those rp gens are identical to the rp gens used in the inventories block.13:18
jaypipescdent: precisely.13:18
efriedoh? hold...13:18
openstackgerritBalazs Gibizer proposed openstack/nova master: Transform missing delete notifications  https://review.openstack.org/41029713:18
openstackgerritBalazs Gibizer proposed openstack/nova master: Send soft_delete from context manager  https://review.openstack.org/47645913:18
efriedThe allocs do come with rp gens.13:19
efriedoh, shit13:19
efriedI hope the docs are wrong for POST /allocations13:20
jaypipesthey are not.13:20
efriedGET /allocations/{c} has the rp gen.13:20
jaypipesyes.13:20
efriedAnd PUT /allocations/{c} includes it, but (at least according to the docs) ignores it. If we didn't change that in 1.28 to *not* ignore, we were supposed to.13:21
cdentno we were not13:21
cdentrp generations are not something we want to watch during allocations13:21
cdentthat we don't is why we created consumer generations13:22
cdentwe discussed this in dublin and it was quite clear that rp gens would not help (and would in fact hinder)13:22
efriedokay okay, I'm remembering now - and was indeed confusing rp gens with consumer gens.13:23
cdentwhen we write an allocation we are _not_ validating that our view of inventory hasn't change13:23
jaypipesright.13:23
cdentwe don't want to do that because allocations happen often13:23
jaypipesright, and all we want to ensure is that capacity isn't exceeded, not that nothing has changed about the provider at all.13:23
efriedthen... why do we increment provider gens when we change allocs?13:23
jaypipesefried: to indicate there has been a change.13:24
efriedyou just said two opposite things.13:24
cdentno, we didn't13:24
jaypipesno I didn't :)13:24
cdentbrb13:24
cdentthe difference is in who the observer is13:26
efriedHere's my confusion: it seems like we should either be using rp gens when we do alloc operations, or not. It sounds like we're incrementing, but not validating, which seems inconsistent and wrong.13:26
cdenta thing making allocations is not the same observer as the thing changing rps and inventories13:27
cdentplus, we need them for the compare and swap13:27
cdentgens provide two purposes13:27
cdentone for the remote callers consistency of view etc13:27
cdentthe other for (to quote jay) http://www.joinfu.com/2015/01/understanding-reservations-concurrency-locking-in-nova/13:28
cdent(please correct me if I just got all that wrong jaypipes )13:28
openstackgerritVladyslav Drok proposed openstack/nova master: ironic: Report resources as reserved when needed  https://review.openstack.org/51792113:28
openstackgerritMerged openstack/nova master: objects: Add NUMACell.network_metadata  https://review.openstack.org/56443913:30
jaypipescdent: no, that's correct.13:31
jaypipesefried: shall I hack on this patch and add back the line 4101 thing? and add tests for this as cdent has asked for?13:32
efriedjaypipes: Sounds like a plan, man.13:33
jaypipesefried: k, will do.13:33
cdentyay, a plan13:34
jaypipescdent: I am *only* pulling the db trx patch, not anything above it. ok with you?13:34
jaypipes(i.e. I'm not going to rebase the entire series013:34
cdentyes13:34
jaypipesk13:34
jaypipesjust checking.13:34
cdentyeah, wise, it's bound to cause some confusion13:35
jaypipescdent: FYI, I have a patch series that breaks up resource_provider.py into multiple files. waiting to push it until we're done with this surgery, but you should like it when it finally does get pushed.13:36
cdenthuzzah13:36
*** mriedem has joined #openstack-placement13:51
openstackgerritMatt Riedemann proposed openstack/nova master: Add unshelve instance error info to fault table  https://review.openstack.org/57974713:51
openstackgerritsahid proposed openstack/nova master: libvirt: remove unused attribute driver for LibvirtConfigNodeDevice  https://review.openstack.org/58324613:59
openstackgerritsahid proposed openstack/nova master: libvirt: add format_dom for ConfigNodeDevicePciSubFunctionCap  https://review.openstack.org/58324713:59
openstackgerritsahid proposed openstack/nova master: libvirt: add missing type for LibvirtConfigNodeDevicePciCap  https://review.openstack.org/58324813:59
openstackgerritsahid proposed openstack/nova master: libvirt: add format_dom() for config LibvirtConfigNodeDevicePciCap  https://review.openstack.org/58324913:59
openstackgerritsahid proposed openstack/nova master: libvirt: add format_dom() method for LibvirtConfigNodeDevice  https://review.openstack.org/58325013:59
openstackgerritsahid proposed openstack/nova master: libvirt: add generater of fake pci devices capabilities  https://review.openstack.org/58325113:59
openstackgerritMatt Riedemann proposed openstack/nova master: Call generate_image_url only for legacy notification  https://review.openstack.org/56452814:01
openstackgerritMerged openstack/nova master: Replace support matrix ext with common library  https://review.openstack.org/48130414:25
openstackgerritJay Pipes proposed openstack/nova master: perform reshaper operations in single transaction  https://review.openstack.org/58238314:27
jaypipescdent, efried: ^14:28
* cdent looks14:28
openstackgerritChris Dent proposed openstack/nova master: WIP: [placement] Add /reshaper handler for POST  https://review.openstack.org/57692714:30
cdentjaypipes: fixes the issue I was seeing14:31
cdentI have successfully reshaped.14:32
cdentI'll carry on, and add some more tests a bit later in the day14:32
jaypipescdent: cool. obviously, I can't do gabbit tests for reshape in that patch (since the handler code builds on top of that patch)14:33
* cdent nods14:33
openstackgerritMatt Riedemann proposed openstack/nova master: Fix "XLibvirt KVM (ppc64)" typo in feature support matrix docs  https://review.openstack.org/58326714:37
gibicdent, efried: FYI I slowly but making progress locally to change the report client to use 1.28 for allocations. I hope I will have something to push this week15:02
*** mriedem has left #openstack-placement15:04
*** mriedem has joined #openstack-placement15:05
jaypipesis it Friday yet?15:06
gibijaypipes: that would be soo nice, but unfortunately not.15:07
openstackgerritEric Fried proposed openstack/nova master: Fix "XLibvirt KVM (ppc64)" typo in feature support matrix docs  https://review.openstack.org/58326715:08
cdentgibi++15:09
*** ttsiouts has quit IRC15:09
efriedgibi: Sweet dude.15:11
openstackgerritMatt Riedemann proposed openstack/nova master: Transform metrics.update notification  https://review.openstack.org/58056715:24
openstackgerritStephen Finucane proposed openstack/nova master: WIP: Add functional tests for numa-aware-vswitches  https://review.openstack.org/58328815:28
*** ttsiouts has joined #openstack-placement15:48
*** ttsiouts has quit IRC15:48
*** ttsiouts has joined #openstack-placement15:49
*** ttsiouts has quit IRC15:54
jaypipesefried: I can haz factor out those common LOC in a followup patch plz?16:05
efriedjaypipes: sho. Are we looking to merge this right away, or wait until more of the series has matured so we can flush out more bugs?16:05
jaypipesefried: up to you and cdent.16:06
cdentjaypipes: fup fine with me16:11
cdentI reckon we should hold off merging the bottom until we've had a successful reshape from the resource client?16:11
jaypipescdent: that's fine with me, sure16:13
cdents/resource/report/16:14
cdentall words are the same in my mind16:14
efriedSo at this point, jaypipes if you're done messing with the bottom, have you had a chance to look at the client patch yet?16:14
jaypipesefried: I have not, no. Is there a patch up for that?16:14
efriedIt's still needing tests, but I want to make sure the broad strokes of the algo are good with y'all before sinking a bunch of time into that.16:14
efriedjaypipes: https://review.openstack.org/#/c/576236/16:15
* cdent enqueue16:15
*** tssurya has quit IRC16:19
*** e0ne has joined #openstack-placement16:31
openstackgerritMatt Riedemann proposed openstack/nova master: Remove support for /os-floating-ip-dns REST API  https://review.openstack.org/58294316:35
openstackgerritMatt Riedemann proposed openstack/nova master: Remove "DEPRECATED" tag from Obsolete APIs  https://review.openstack.org/58309216:35
openstackgerritMerged openstack/nova master: Fix a newly introduced UUID warning in the unit test  https://review.openstack.org/58320517:14
*** e0ne has quit IRC17:15
*** e0ne has joined #openstack-placement17:21
*** diga has joined #openstack-placement17:25
digaHello guys17:37
openstackgerritMerged openstack/nova master: Escalate UUID validation warning to error in test  https://review.openstack.org/54038617:38
efrieddiga: Howdy.  What's up?17:39
digacdent: efried : want to start work on placement, can you give me to get started ?17:39
digaefried: Hey17:39
digaefried: Do you have some work item for me ?17:40
* efried looks for bugs...17:40
digaokay17:41
efrieddiga: Here's the open placement bugs: https://bugs.launchpad.net/nova/+bugs?field.tag=placement&orderby=-id17:42
efrieddiga: Make sure you pick one that doesn't already have an owner.17:42
digaefried: sure17:42
efrieddiga: Let me know if you want help/guidance.17:42
digaefried: yup17:43
efrieddiga: You can also review open patches.17:43
digaefried: okay17:43
digaefried: can you post link here ?17:44
digawill review it17:44
efrieddiga: The easiest way to find reviews is to follow the placement update that gets sent out to the dev mailing list weekly.17:44
digayeah17:45
efriedIt may get a bit stale over the course of the week, but it ought to be a good starting point.17:45
efrieddiga: Here's the latest one: http://lists.openstack.org/pipermail/openstack-dev/2018-July/132252.html17:45
digaI have that mail, will pick it up from there17:45
digaefried: okay17:45
efriedGreat.  We really appreciate the help!17:45
digaefried: :) I will try my best friend17:48
*** diga has quit IRC17:52
openstackgerritEric Fried proposed openstack/nova master: WIP: Compute: Handle reshaped provider trees  https://review.openstack.org/57623618:00
efriedcdent: Wanted to rebase to get test results, but it looks like the microversion patch is in merge conflict. May I fix it?18:01
efriedjaypipes: ...by rebasing the whole series?18:01
jaypipesefried: please go ahead18:03
jaypipesefried: if cool with cdent18:03
efriedready to push on your nod cdent18:05
*** e0ne has quit IRC18:15
cdentgo for it efried, was dining18:32
openstackgerritEric Fried proposed openstack/nova master: perform reshaper operations in single transaction  https://review.openstack.org/58238318:32
openstackgerritEric Fried proposed openstack/nova master: WIP: [placement] Add /reshaper handler for POST  https://review.openstack.org/57692718:32
openstackgerritEric Fried proposed openstack/nova master: WIP: Compute: Handle reshaped provider trees  https://review.openstack.org/57623618:32
efrieddone ^18:32
efrieddidn't want to eff with any local edits you had cdent18:32
cdentefried: I think I'm hands off until tomorrow morning, so if you need to do it again, feel free18:33
efriedrgr18:33
*** cdent has quit IRC18:42
openstackgerritsean mooney proposed openstack/nova master: update tox venv env to install all requirements  https://review.openstack.org/58333618:48
*** e0ne has joined #openstack-placement18:49
openstackgerritMatt Riedemann proposed openstack/nova master: WIP: Add regression test for bug 1781710  https://review.openstack.org/58333918:53
openstackbug 1781710 in OpenStack Compute (nova) "ServersOnMultiNodesTest.test_create_server_with_scheduler_hint_group_anti_affinity failing with "Servers are on the same host"" [High,Fix released] https://launchpad.net/bugs/1781710 - Assigned to Matt Riedemann (mriedem)18:53
*** efried has quit IRC19:14
*** efried has joined #openstack-placement19:14
openstackgerritMerged openstack/nova master: Merge server create for scheduler hint extension  https://review.openstack.org/57906719:35
openstackgerritMerged openstack/nova master: Fix "XLibvirt KVM (ppc64)" typo in feature support matrix docs  https://review.openstack.org/58326719:35
*** e0ne has quit IRC19:41
openstackgerritsean mooney proposed openstack/nova master: random hacking for bug 1781710  https://review.openstack.org/58334719:55
openstackbug 1781710 in OpenStack Compute (nova) "ServersOnMultiNodesTest.test_create_server_with_scheduler_hint_group_anti_affinity failing with "Servers are on the same host"" [High,Fix released] https://launchpad.net/bugs/1781710 - Assigned to Matt Riedemann (mriedem)19:55
openstackgerritMerged openstack/nova master: Add unshelve instance error info to fault table  https://review.openstack.org/57974719:59
*** tssurya has joined #openstack-placement20:04
openstackgerritMatt Riedemann proposed openstack/nova master: Additional/alternative fix for bug 1781710  https://review.openstack.org/58335120:20
openstackbug 1781710 in OpenStack Compute (nova) "ServersOnMultiNodesTest.test_create_server_with_scheduler_hint_group_anti_affinity failing with "Servers are on the same host"" [High,Fix released] https://launchpad.net/bugs/1781710 - Assigned to Matt Riedemann (mriedem)20:20
*** tssurya has quit IRC20:23
efriedjaypipes: When we do yaml-based generic device passthrough, I anticipate there being a config file at the conductor (which can specify device types at the level of vendor/product ID) whose entries can be superseded by a file per compute (which can specify the same, but can also get down to specific devices by address etc. if needed).20:56
efriedjaypipes: Are you okay if we strawman that conf file name as /etc/nova/passthrough.yaml ?20:56
efriedThe one on the compute can/will be virt type-specific, but no reason for it to have a different name, is there?20:57
jaypipesefried: /etc/nova/devices.yaml or /etc/nova/inventory.yaml would be my preference.21:26
jaypipes /etc/nova/inventory.yaml being what I had originally proposed I believe...21:26
efriedjaypipes: inventory.yaml is pretty generic; but maybe that's your intent.21:26
jaypipesefried: ack, yeah it was my intent to be generic.21:26
efriedi.e. can potentially encompass things like VCPU...21:26
efriedwhich may be how NUMA topology gets specified, or something, dunno.21:27
efriedanyway, dig.21:27
openstackgerritMerged openstack/nova master: Call generate_image_url only for legacy notification  https://review.openstack.org/56452821:29
efriedjaypipes: Have you thought about how to reconcile generic content vs. virt-specific content in such a file?21:30
*** edmondsw has quit IRC21:36
*** edmondsw_ has joined #openstack-placement21:45
*** edmondsw_ has quit IRC21:49
openstackgerritMatt Riedemann proposed openstack/nova master: Update RequestSpec.instance_uuid during scheduling  https://review.openstack.org/58334721:58
jaypipesefried: to me it's all about the node's inventory and traits...22:13
jaypipesefried: could have all that information in a single YAML file IMHO.22:13
jaypipesefried: but I need to run off for the day now...22:13
efriedight, later.22:13
jaypipestalk to you tomorrow.22:13
jaypipes:)22:13
openstackgerritEric Fried proposed openstack/nova master: WIP: Compute: Handle reshaped provider trees  https://review.openstack.org/57623622:38

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