Monday, 2018-05-14

*** edmondsw has joined #openstack-placement01:07
*** edmondsw has quit IRC01:11
*** edmondsw has joined #openstack-placement01:22
*** edmondsw has quit IRC01:34
*** edmondsw has joined #openstack-placement01:35
*** edmondsw has quit IRC01:37
*** edmondsw has joined #openstack-placement01:37
openstackgerritTetsuro Nakamura proposed openstack/nova master: Return nested providers in get_by_request  https://review.openstack.org/56711301:38
openstackgerritTetsuro Nakamura proposed openstack/nova master: Add traits check in nested provider cadidates  https://review.openstack.org/56715001:38
openstackgerritTetsuro Nakamura proposed openstack/nova master: Support nested alloc cands with sharing providers  https://review.openstack.org/56750801:38
*** edmondsw has quit IRC01:38
*** tetsuro has joined #openstack-placement02:30
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in test_compute_api.py (3)  https://review.openstack.org/56818404:07
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in test_compute_api.py (3)  https://review.openstack.org/56818404:09
openstackgerritcaoyuan proposed openstack/nova master: Update auth_url in install docs  https://review.openstack.org/56800205:49
*** belmoreira has joined #openstack-placement06:08
openstackgerritShilpa Devharakar proposed openstack/nova master: Update docs, API samples for noVNC 1.0.0  https://review.openstack.org/55017306:29
*** tssurya has joined #openstack-placement06:54
*** rubasov has joined #openstack-placement07:03
openstackgerritSurya Seetharaman proposed openstack/nova master: Metadata-API fails to retrieve avz for instances created before Pike  https://review.openstack.org/56787807:14
openstackgerritRadoslav Gerganov proposed openstack/nova stable/queens: Add random sleep between retry calls to placement  https://review.openstack.org/56821807:47
openstackgerritLenny Verkhovsky proposed openstack/nova master: Adding NVMEoF for libvirt driver  https://review.openstack.org/48264007:47
*** belmoreira has quit IRC08:01
*** belmoreira has joined #openstack-placement08:04
*** gibi has quit IRC08:05
*** gibi has joined #openstack-placement08:07
*** gibi is now known as Guest4411808:07
*** alex_xu has quit IRC08:32
*** alex_xu has joined #openstack-placement08:33
*** cdent has joined #openstack-placement08:37
*** Guest44118 is now known as gibi08:44
*** purplerbot has quit IRC09:02
*** purplerbot_ has joined #openstack-placement09:02
*** purplerbot_ is now known as purplerbot__09:02
*** purplerbot__ is now known as purplerbot09:02
openstackgerritsahid proposed openstack/nova master: libvirt: place emulator threads on CONF.cpu_shared_set  https://review.openstack.org/51089709:24
*** avolkov has joined #openstack-placement09:31
*** diga has joined #openstack-placement09:53
openstackgerritTetsuro Nakamura proposed openstack/nova master: Return all resources in provider_summaries  https://review.openstack.org/55804510:04
*** edmondsw has joined #openstack-placement11:03
openstackgerritBalazs Gibizer proposed openstack/nova master: Escalate UUID validation warning to error in test  https://review.openstack.org/54038611:18
openstackgerritBalazs Gibizer proposed openstack/nova master: Suppress UUID warning in map_instance unit tests  https://review.openstack.org/56826311:18
*** diga has quit IRC11:40
*** sean-k-mooney has joined #openstack-placement11:51
sean-k-mooneyo/11:51
sean-k-mooneyanyone familar with how ironic placement custom resouces classes work around?11:54
openstackgerritJulia Kreger proposed openstack/nova master: ironic: add instance_uuid before any other spawn activity  https://review.openstack.org/56372211:58
sean-k-mooneydose placement have a way to assocate a description what a custom resouce class models with the resouce class. e.g. Custom_barmetal_small -> 8 pcpu + 16GB RAM + 2 disk(120GB ssd + 1TB hdd)11:59
openstackgerritSurya Seetharaman proposed openstack/nova master: Make nova service-list use scatter-gather routine  https://review.openstack.org/56827112:02
openstackgerritTetsuro Nakamura proposed openstack/nova master: Return nested providers in get_by_request  https://review.openstack.org/56711312:10
openstackgerritTetsuro Nakamura proposed openstack/nova master: Add traits check in nested provider cadidates  https://review.openstack.org/56715012:10
openstackgerritTetsuro Nakamura proposed openstack/nova master: Support nested alloc cands with sharing providers  https://review.openstack.org/56750812:10
*** cdent has quit IRC12:11
*** tetsuro has left #openstack-placement12:15
openstackgerritNaichuan Sun proposed openstack/nova master: XenAPI: define a new image handler to use vdi streaming  https://review.openstack.org/48647512:16
openstackgerritSurya Seetharaman proposed openstack/nova master: Make nova service-list use scatter-gather routine  https://review.openstack.org/56827112:54
efriedsean-k-mooney: Other than docs, nope.12:58
sean-k-mooneyefried: that is what i was affraid of, i could be captured in flavors but i was hoping for a way to model it in placement nativly12:59
efriedsean-k-mooney: I don't know of any "description" field in placement.  The closest we come is the 'name' field of a resource provider afaik.13:00
sean-k-mooneyefried: one tought i had was to model the resouces as inventories and set the allocation step_size equal to the total but that has other issues13:01
efriedsean-k-mooney: Right, because you have no way to enforce that the flavor consumes all the resources.13:02
sean-k-mooneybasically since its a baremetal node everything from the RP is allocated in one go.13:02
sean-k-mooneyyep13:02
efriedsean-k-mooney: Having said that, if your flavor allocates any one of the resources and the min/step_size are equal to the total, then you would take that node out of the running for other scheduling ops anyway.13:02
efriedum, unless we're talking about allocating a network device or something for post-deploy attach.13:03
sean-k-mooneyya that is why i was thinking of doing it that way but i want to support mixed hypervisor envs e.g. barmetal and vm and i do not want vms to be able to land on the barmetal RP13:04
efriedsean-k-mooney: Presumably you would control that with a trait13:04
sean-k-mooneyefried: i could be we do not have reuired trates for a RP currently13:04
sean-k-mooneye.g. only allocate from this RP if trait X is in allocation request13:05
efriedhuh?  You would put the required trait in the flavor.13:05
sean-k-mooneyi dont think it would be that hard to add but its not there today.13:05
efriedbut the custom resource classes are13:05
sean-k-mooneyyou would have a new table in placement to map required traits to RP and then request the trait in the flavor13:06
edleafesean-k-mooney: a baremetal resource provider has an inventory of 1 CUSTOM_* resource. VMs couldn't land on it.13:06
efriedI mean, if you're even *talking* about changing to standard resource classes, you must be okay with changing flavors around.13:06
efriedsean-k-mooney: That's already in place.13:06
efriededleafe: That's what we're talking about "fixing".13:06
sean-k-mooneyi can set required traits on a placement RP13:06
efriedsean-k-mooney: yes.13:06
*** mriedem has joined #openstack-placement13:06
edleafeefried: fixing? What's broken13:07
edleafe?13:07
sean-k-mooneyand if you dont request that trait you cant allocate form that RP?13:07
efriedIn the flavor it looks like:  "trait:CUSTOM_FOO": "required"13:07
sean-k-mooneyefried: that is not what i want13:07
efriedsean-k-mooney: Ah, no.  I see, that's what you meant by "required".13:07
sean-k-mooneyya i want to put the required traits on the RP not in the flavor so if you request no tratis in the flavour you cant be allocated from the RP13:08
edleafethat sounds like a filter13:08
efriededleafe: We started with sean-k-mooney asking if he could associate some kind of metadata/description with the baremetal custom resource class, so you would have a way to know e.g. how many CPUs, how much memory, etc.13:08
edleafeefried: yeah, we decided a long time ago not to support metadata in placement13:09
sean-k-mooneyedleafe: basicaly i would like to be able to say this custom resouce class give you x ammount of these other resouce classes13:10
efriededleafe: From there we went to talking about representing the ironic node via its *actual* resources.  But then we have the problem of a) "partially allocated" baremetal nodes, and all that entails; and b) VMs being able to land there.13:10
edleafesean-k-mooney: that info belongs in the flavor13:10
edleafesean-k-mooney: you can set the amounts there, and then override in extra_specs to 013:11
sean-k-mooneyedleafe: it could be ther yes but that just felt messy13:11
sean-k-mooneyedleafe: that was my fallback13:11
edleafesean-k-mooney: that's the design we put in place specifically for this13:11
sean-k-mooneyedleafe: yes but it only works for custom resouces class that model compute hosts13:12
edleafeI don't follow. Why?13:12
sean-k-mooneyedleafe: it wont work for things like FPGAs ectra13:12
edleafeI still don't see why13:13
sean-k-mooneywell i dont want to be forced to spcify them in the nova flavor for one thing in all cases.13:14
openstackgerritEric Fried proposed openstack/nova master: add lower-constraints job  https://review.openstack.org/55596113:14
edleafeThen where would they be specified? They have to be set *somewhere*, no?13:15
sean-k-mooneyedleafe: i am currently working on intergrating RSD with openstack and trying to think about how to model composable hardware within placement13:15
sean-k-mooneyedleafe: in a composable world acclerators and nic could be modeled as sharing resouce providers and then hotpluged into compute systems dynamically13:16
edleafesean-k-mooney: that sounds more like Cyborg than Nova13:17
*** cdent has joined #openstack-placement13:18
sean-k-mooneywell the point stands in either case that i have to decole the metadata about my custom resouce class form nova flavors. cyborg will not handel all cases so we will need cinder support for volumes, and or neutron support also.13:19
efriedsean-k-mooney: yaml to the rescue?13:19
edleafeefried: it does solve all problems13:20
sean-k-mooneyefried: i could encode this info in the resouce_class name or some other hack i was hoping to have a more generic solution long term.13:20
sean-k-mooneyanyway i can live with doing this in the flavor short term but i think it would be nice to standarise it in placement at somepoint13:21
efriedsean-k-mooney: For the sake of discussion, what would that look like?13:21
sean-k-mooneyi was thinking either a) a nested resouce_class type structure or b) yaml using resouce_class->quantity mappings + traits13:23
sean-k-mooneye.g. CUSTOM_COMPUTE_BLADE->{ VCPUS:16, RAM:16GB, DISK[{LOCAL_GB:1024,traits=HDD},{LOCAL_GB:256,traits:ssd}]}13:27
sean-k-mooneyefried: i had not fully taught about how to model it i was just wondering if it had been solve in the ironic case already13:28
sean-k-mooneyefried: edleafe will ye be at the summit out of interest?13:29
efriedsean-k-mooney: We can solve the "partial allocation" problem the same way we did for xen: once the node is deployed, the virt driver changes any unallocated inventories to make reserved=total.13:29
efriedsean-k-mooney: Yes, we both will be.  We're giving a presentation on placement, if you'd like to attend :)13:30
edleafes/attend/heckle13:30
sean-k-mooneyefried: assuming im not on booth duty then i proably will.13:30
efriedsean-k-mooney: ---^ but that still doesn't help us with the issue of VMs accidentally getting deployed to the baremetal node.13:30
sean-k-mooneyedleafe: no heckling is for the foum not the presentation track :P13:31
edleafesean-k-mooney: then why am I always heckled in both?13:31
sean-k-mooneyefried: ya i think require traits for resocue providers is a simpler solution for that13:31
efriedsean-k-mooney: I.e. "here's a trait on a resource provider that the requestor *must* specify, otherwise we won't include that resource provider in the response" ?13:32
efriedThat's a weird one.13:32
sean-k-mooneyefried: yes13:32
*** superdan is now known as dansmith13:33
efriedjaypipes_: When you're around...13:33
sean-k-mooneyit solve the proablem and is not intrusive to the api its additive13:33
*** belmorei_ has joined #openstack-placement13:33
sean-k-mooneyit also wont suck to impement in the sql13:33
efriedYeah, it's simple enough to implement; I'm mainly just having trouble figuring out how to describe it.13:34
edleafeor where to store that tidbit of information13:34
efriedFor starters, we need a new word, because "required" is taken.13:34
*** belmoreira has quit IRC13:35
efriededleafe: Right, it would have to be a separate table, or column on the resource_provider_traits table.13:35
sean-k-mooneyedleafe: as a new table in the placement db with a new enpoint to set/get them.13:35
edleafeefried: IOW, RP metadata13:35
efried:)13:35
cdentlet's not have rp metadata, please13:36
cdentor at least, let's finish everything else first before we even talk about it13:36
sean-k-mooneykindof but it is tracking qualitive requirement to the schduler. i was wondering if it could intersect with dansmith's prefilter work13:36
sean-k-mooneycdent: i can implement what i need with a custom filter for now encode the requirement in nova flavors.13:39
cdentsean-k-mooney: glad to hear you won't be left out in the cold13:40
cdentI think once a todo list gets to a year or more long, it's time to pause13:40
sean-k-mooneycdent: infact we created a filter to solve this usecase 2 years ago. but i was tring to think is there any way to allow this to work withing the existing placemnet api constructs but it look like the answer is no13:40
sean-k-mooneycdent: ya i dont want to add yet another placement todo to that list13:41
openstackgerritMatt Riedemann proposed openstack/nova master: DNM: test raw image live migration with vfat config drive  https://review.openstack.org/56786013:41
jaypipes_efried: yes?13:51
*** jaypipes_ is now known as jaypipes13:51
efriedjaypipes: We were talking with sean-k-mooney about a suggested feature for placement, wanted to get your reaction.13:51
efriedIt's a little tough to describe because the word "required" is already taken.13:51
efriedBut basically it's this: Put a trait on the resource provider that the requestor *must* specify in order for that RP to be returned in an allocation request.13:52
edleafeefried: since it's a reverse of the current required, call it 'deriuqer'13:52
efriedThe use case is so we can model baremetal nodes with their actual resources instead of a single custom resource class.13:52
* edleafe shudders13:53
efriedBut we don't want regular VMs to be able to land there.13:53
efriedSo we want ironic flavors to have to say CUSTOM_BAREMETAL or whatever, and if they don't, they can't land there.13:53
cdentefried: seriously, can we just pause this entire discussion please?13:53
cdentwe have enough going on already that by the time this feature comes to pass we will have learned a lot13:53
openstackgerritBence Romsics proposed openstack/osc-placement master: Add nested resource providers (v1.14)  https://review.openstack.org/54667513:54
sean-k-mooneyi am fine with pausing it for now13:54
openstackgerritBence Romsics proposed openstack/osc-placement master: Limit allocation candidates (v1.15, v1.16)  https://review.openstack.org/54804313:54
openstackgerritBence Romsics proposed openstack/osc-placement master: Allocation candidates parameter: required (v1.17)  https://review.openstack.org/54832613:54
efriedI don't think we're suggesting throwing this into Rocky or anything, cdent13:54
efriedjust tossing around ideas.13:54
cdentI know, but _all_ I do now is context switch13:54
cdentand never actually make any progress13:54
cdentand it is getting so freaking noisy13:54
sean-k-mooneyin my spcific case all the baremetal nodes would be own by the admin tenant so i can just use https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/placement-req-filter.html or https://specs.openstack.org/openstack/nova-specs/specs/rocky/approved/alloc-candidates-member-of.html to support that13:55
efriedoh, that's true too.13:55
efriedThe former, not the latter, at least not yet, because the only way to specify aggs in flavors will be via the az filter that dansmith is doing.13:56
efried(I'm sure I just used both "az" and "filter" wrong.  Please don't yell at me.)13:56
* alex_xu will have a lot of chat log to read13:57
*** jgwentworth is now known as melwitt13:57
sean-k-mooneywell effectivly with either i can create a nova aggregate around my specal nodes and restic the placement queries to that subset. albeit via a slightly different mechaniums in both cases13:57
efriedWhich reminds me, dansmith & jaypipes, we should chat about that at some point.  Specifically, see this comment: https://review.openstack.org/#/c/515811/16/nova/scheduler/utils.py@13313:58
efriedjaypipes: You running the sched mtg?14:00
jaypipesefried: ya14:01
openstackgerritMatt Riedemann proposed openstack/nova master: Add contributor docs on deprecating and removing compute REST APIs  https://review.openstack.org/56768714:12
*** cdent_ has joined #openstack-placement14:16
*** cdent has quit IRC14:17
*** cdent_ is now known as cdent14:17
openstackgerritBob Ball proposed openstack/nova master: XenAPI: define a new image handler to use vdi streaming  https://review.openstack.org/48647514:20
openstackgerritBalazs Gibizer proposed openstack/nova master: Transform missing delete notifications  https://review.openstack.org/41029714:22
openstackgerritShilpa Devharakar proposed openstack/nova master: Update docs, API samples for noVNC 1.0.0  https://review.openstack.org/55017314:29
efriedjaypipes, mriedem: Would you please have a look at gibi's comment here: https://review.openstack.org/#/c/515811/16/nova/scheduler/utils.py@16714:32
efriedGiven that perspective, and the fact there's nothing else around here that raises exceptions, I'm inclined to agree with gibi and remove the enforcement.  Thoughts?14:32
efrieddansmith: Would you please have a look at https://review.openstack.org/#/c/515811/16/nova/scheduler/client/report.py@a368 and let me know whether you would like to do this cutover in a separate patch?14:33
dansmithefried: you're asking if we should support multiple member_of with 1.24, then make this granular change separately yeah?14:34
dansmithif so, I agree14:34
dansmither, I think we should yes14:35
efrieddansmith: Okay.  Do you want to propose the interim change or should I?14:35
dansmithI don14:36
dansmithI don't _want_ to, but I probably should at least try14:36
dansmithgimme a few14:36
efrieddansmith: Okay.  Here's a hint: you're going to need to switch to the tuple (vs. dict) form of url encoding.14:36
dansmithfor qs_params you mean?14:37
efriedyes14:37
dansmithyup14:38
mriedemefried: re https://review.openstack.org/#/c/515811/16/nova/scheduler/utils.py@167 - if we don't check in nova, placement will bomb out with a 400 right?14:54
mriedemduring GET /allocation_candidates14:54
*** belmorei_ has quit IRC14:54
mriedemefried: replied inline14:58
openstackgerritDan Smith proposed openstack/nova master: Make scheduler client allow multiple member_of query parameters  https://review.openstack.org/56831315:05
dansmithefried: ^15:05
dansmithstill running functional tests15:05
openstackgerritMatt Riedemann proposed openstack/nova master: DNM: test raw image live migration with vfat config drive  https://review.openstack.org/56786015:33
openstackgerritBob Ball proposed openstack/nova master: XenAPI: define a new image handler to use vdi streaming  https://review.openstack.org/48647515:35
openstackgerritBob Ball proposed openstack/nova master: XenAPI: Pass expected return codes to resize2fs  https://review.openstack.org/56831815:35
*** cdent has quit IRC15:43
efriedmriedem: Yes, ack, and thanks.15:54
efrieddansmith: Were you going to post func tests (new or changed) or did you just mean you were running to make sure nothing broke?16:05
dansmithefried: I just meant I hadn't run all the existing functional tests before submitting16:06
efriedrgr16:06
dansmithefried: we have coverage for the member_of thing already so the fact that it didn't break any is sufficient I think,16:06
dansmithand I'll have functional tests in my filter patch that uses this with multiple ones16:06
efriedrgr16:06
openstackgerritEric Fried proposed openstack/nova master: Granular requests to get_allocation_candidates  https://review.openstack.org/51581116:14
efriedgibi, mriedem (and jaypipes): Done ^16:15
efried...but still need to rebase on dansmith's16:15
efrieddansmith: (I just checked the change set where you introduced the quasi-multiple-member_of hack, and there were no func tests there, so I think you're probably clean)16:16
gibiefried: looks good to me16:22
efriedgibi: thanks16:22
openstackgerritMatt Riedemann proposed openstack/nova master: Implement granular policy rules for placement  https://review.openstack.org/52442516:27
openstackgerritMatt Riedemann proposed openstack/nova master: Add granular policy rules for /resource_classes*  https://review.openstack.org/56557816:27
mriedemefried: don't you think we should probably have a functional test for https://review.openstack.org/#/c/515811/ ?16:28
mriedemor maybe unit is enough16:29
efriedmriedem: We have functional tests (granular.yaml gabbit) for the placement side.  The unit tests handle the parsing.  You're asking for kind of and end-to-end func test where we go all the way from flavor through placement to scheduling?16:30
mriedemalso, do we have any documentation for granular flavors besides https://review.openstack.org/#/c/515811/17/releasenotes/notes/granular-extra-specs-50b26b8f63717942.yaml and specs?16:30
mriedemefried: yes that's what i was thinking of16:30
efriedmriedem: No, no docs other than the reno & flavors.  I can work up a doc like we did for u-p-t (mostly capy/paste of the spec).16:30
mriedemreno & specs you mean?16:31
efriedsorry, yes16:31
mriedemyeah i was thinking something should live in https://docs.openstack.org/nova/latest/user/flavors.html#extra-specs16:31
mriedemcould be follow up changes of course16:31
efriedmriedem: As for the func test, I thought that would be better waiting for nrp-in-alloc-cands to be done, because that's going to be where we get the most bang out of granular.16:31
efriedsince we still don't truly claim support for sharing providers.16:32
efriedfor that matter, perhaps the doc would be better off waiting for nrp-in-alloc-cands too.16:32
jaypipesefried: k. I'm pretty much done on reviewing tetsuro's member_of+alloc candidates series. needs to be rebased, though, according to gerrit16:32
mriedemwe could test the negative scenario we already spent some time talking about, the novalidhost one because scope isn't specified16:34
efriedjaypipes: The series starting here is ready, right? https://review.openstack.org/#/c/567113/16:34
jaypipesefried: that's a different series, but yes, I think it is.16:35
mriedemanyway, functional e2e could be a follow up16:35
jaypipesefried: I'll review that one now.16:35
efriedjaypipes: I think that was the "bottom" of the nrp-in-alloc-cands series, and he was going to rebase the others on top.16:35
efriedmriedem: Roger that.16:36
jaypipesefried: k16:36
mriedemone thing i just thought of - how many e2e functional tests are going to no longer work once we don't have a running placement service in-tree...16:36
mriedemlike, we have to use fixtures for cinder and neutron with stubs for the actual data interactions, we haven't had to do that for placement b/c we have the service running in our functional tests16:36
efriedmriedem: I think cdent's plan for that includes... running the placement service in-tree.16:36
efriedbut I don't know for sure how that's going to work.16:37
efriedmriedem: Have you seen his placecat thingy?16:37
efriedhttps://github.com/cdent/placecat16:37
mriedemno16:37
efriedNot sure if it's related to how he plans to "install" placement in tree for tests.16:38
efriedthis would be a good topic for his forum session.16:38
efriedmriedem: ^ https://etherpad.openstack.org/p/YVR-placement-extraction ^16:39
efriednot sure if this concern is included in L42-3 or 45.16:39
efriedadded L4616:40
mriedemvirtualThumbsUp16:41
openstackgerritMatt Riedemann proposed openstack/nova master: add lower-constraints job  https://review.openstack.org/55596116:47
openstackgerritSylvain Bauza proposed openstack/nova-specs master: Proposes Multiple GPU types  https://review.openstack.org/55706517:07
*** efried has quit IRC17:19
*** efried has joined #openstack-placement17:19
openstackgerritMatt Riedemann proposed openstack/nova master: Wait for network-vif-plugged before starting live migration  https://review.openstack.org/55800117:25
openstackgerritMatt Riedemann proposed openstack/nova master: Add check if neutron "binding-extended" extension is available  https://review.openstack.org/52354817:25
openstackgerritMatt Riedemann proposed openstack/nova master: Add "bind_ports_to_host" neutron API method  https://review.openstack.org/52360417:25
openstackgerritMatt Riedemann proposed openstack/nova master: Add "delete_port_binding" network API method  https://review.openstack.org/55217017:25
openstackgerritMatt Riedemann proposed openstack/nova master: Add "activate_port_binding" neutron API method  https://review.openstack.org/55594717:25
openstackgerritMatt Riedemann proposed openstack/nova master: Delete port bindings in setup_networks_on_host if teardown=True  https://review.openstack.org/55633317:25
openstackgerritMatt Riedemann proposed openstack/nova master: Implement migrate_instance_start method for neutron  https://review.openstack.org/55633417:25
openstackgerritMatt Riedemann proposed openstack/nova master: Add VIFMigrateData object for live migration  https://review.openstack.org/51542317:25
openstackgerritMatt Riedemann proposed openstack/nova master: Add VIFMigrateData.get_dest_vif  https://review.openstack.org/56693117:25
openstackgerritMatt Riedemann proposed openstack/nova master: libvirt: factor out pre_live_migration plug_vifs call  https://review.openstack.org/56693217:25
openstackgerritMatt Riedemann proposed openstack/nova master: libvirt: use dest host port bindings during pre_live_migration  https://review.openstack.org/56693317:25
openstackgerritMatt Riedemann proposed openstack/nova master: libvirt: use dest host vif migrate details for live migration  https://review.openstack.org/55137017:25
openstackgerritMatt Riedemann proposed openstack/nova master: Annotate flows and handle PortBindingDeletionFailed in ComputeManager  https://review.openstack.org/55137117:25
openstackgerritMatt Riedemann proposed openstack/nova master: Port binding based on events during live migration  https://review.openstack.org/43487017:25
openstackgerritMatt Riedemann proposed openstack/nova master: conductor: use port binding extended API in during live migrate  https://review.openstack.org/52253717:25
openstackgerritDan Smith proposed openstack/nova master: Honor availability_zone hint via placement  https://review.openstack.org/54628217:39
dansmithefried: ^ that will make use of multiple member_of, and covers it in more tests17:40
dansmithjaypipes: ^17:40
efriedack17:40
*** cdent has joined #openstack-placement17:48
*** tssurya has quit IRC17:48
jaypipesdansmith: rock on, thanks brother.17:52
cdentefried, mriedem : placecat has nothing to do with fixtures for nova17:56
cdentmy thinking/expectation was that we produce a re-usable fixture in placement itself that nova could choose to import17:56
cdentas I understand it zuulv3 makes it pretty easy to use master of another project from one project, so we could effective continue using a fixture that provides the same functionality as the current one17:58
cdentthe point of placecat is to play with placement however one might like. if for some reason we really did want a throwaway placement container to run in integration tests (which might use handy) then that would be https://github.com/cdent/placedock (not cat, cat uses dock)17:59
cdentStarting to use throwaway containers in integration tests strikes me a pretty useful thing but not really germane to mriedem's concern18:00
cdentfor that I think we should consider doing whatever we can to make the existing tests continue to work18:00
mriedemi expect the easiest thing would just be nova has a test-requirement on placement18:03
mriedemthe repo18:03
cdentthat's pretty much what I mean18:03
cdentbut I had heard that zuul has some new jiggery pokery for ways to make that special18:04
cdentbut I guess those special bits are when there are non-test requirements18:04
openstackgerritMerged openstack/nova master: Suppress UUID warning in map_instance unit tests  https://review.openstack.org/56826318:07
openstackgerritMohammed Naser proposed openstack/nova master: Added ability to configure default architecture for ImagePropertiesFilter  https://review.openstack.org/56642518:07
openstackgerritMohammed Naser proposed openstack/nova master: Added ability to configure default architecture for ImagePropertiesFilter  https://review.openstack.org/56642518:42
openstackgerritEric Fried proposed openstack/nova master: __str__ methods for RequestGroup, ResourceRequest  https://review.openstack.org/56835319:07
efrieddansmith, jaypipes: As promised ^19:07
cdentefried: I like, mostly, but think it has a fairly significant problem19:17
efriedtell me19:17
cdentI commented on it, but \n\t in log messages -119:19
cdentor in stringifications in general19:19
efriedcdent: I was afraid that would be a problem.  I just really want the friggin thing to be readable.  Kind of the whole point of this change.19:20
cdentyeah, I hear that, but it's problematic for processing19:21
efriedcdent: processing of what?19:22
* efried goes to read the comment...19:22
cdentlogs19:22
cdentI didn't say much more than what's here19:22
efriedbutbutbut19:22
efriedexception traces have line breaks all over them.19:23
efried...and that's the only thing that makes them friggin readable, btw.19:23
cdentikr19:23
cdentI'm stating a personal preference here19:23
cdentsorry NOT stating19:23
cdentI think the difference here between a stacktrace and stringification is about what is consider the atom. And also people complain about stacktraces not being atoms all the time19:24
cdentdan, jay, etc may disagree19:24
*** e0ne has joined #openstack-placement19:24
efriedcdent: So what do you suggest to make this readable?19:26
cdentefried: one possibility: do something a bit like what my very old Java recalls: RequestGroup<$WHAT_YOU_HAVE>, RequestGroup< ....19:27
*** belmoreira has joined #openstack-placement19:38
openstackgerritZack Cornelius proposed openstack/nova-specs master: Libvirt file backed memory  https://review.openstack.org/56370419:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: CLI for traits (v1.6)  https://review.openstack.org/51464319:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: Resource class set (v1.7)  https://review.openstack.org/51464419:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: Usages per project and user (v1.8, v1.9)  https://review.openstack.org/51464619:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: CLI allocation candidates (v1.10)  https://review.openstack.org/51464719:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: New dict format of allocations (v1.11, v1.12)  https://review.openstack.org/54281919:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: Transactionally update allocations (v1.13)  https://review.openstack.org/54667419:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: Add nested resource providers (v1.14)  https://review.openstack.org/54667519:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: Limit allocation candidates (v1.15, v1.16)  https://review.openstack.org/54804319:53
openstackgerritMatt Riedemann proposed openstack/osc-placement master: Allocation candidates parameter: required (v1.17)  https://review.openstack.org/54832619:53
mriedem1.6 at the bottom ^ should be happy to go19:54
jaypipesmriedem: ty sir.19:56
openstackgerritEric Fried proposed openstack/nova master: __str__ methods for RequestGroup, ResourceRequest  https://review.openstack.org/56835319:59
openstackgerritEric Fried proposed openstack/nova master: Granular requests to get_allocation_candidates  https://review.openstack.org/51581119:59
efriedcdent: Did that ^  And dansmith jaypipes this is now rebased on dansmith's 1.24-usin patch (entirely supplants it, in fact).20:00
openstackgerritChris Dent proposed openstack/nova master: Extract part of PlacementFixture to placement  https://review.openstack.org/56835920:00
openstackgerritArtom Lifshitz proposed openstack/nova master: Refactor _build_device_metadata  https://review.openstack.org/53380420:00
efried(But I understand why we had to do it that way, sigh.)20:00
openstackgerritArtom Lifshitz proposed openstack/nova master: Consider hostdev devices when building metadata  https://review.openstack.org/53380520:00
openstackgerritZack Cornelius proposed openstack/nova-specs master: Libvirt file backed memory  https://review.openstack.org/56370420:00
jaypipesefried: been trying to get through tetsuro's patch series reviews.20:01
cdentefried: yeah that seems better and more proper (even though it is harder to read)20:01
cdentefried, mriedem : the "Extract part of PlacementFixture" above is related to the discussions earlier about fixtures between placement and nova20:02
efriedjaypipes: Roger that, I need to do the same.20:03
efriedack20:03
openstackgerritMatt Riedemann proposed openstack/nova stable/queens: libvirt: Report the virtual size of RAW disks  https://review.openstack.org/56836320:14
*** efried has quit IRC20:17
openstackgerritChris Dent proposed openstack/nova master: Extract part of PlacementFixture to placement  https://review.openstack.org/56835920:20
*** avolkov has quit IRC20:22
*** cdent has quit IRC20:26
openstackgerritMatt Riedemann proposed openstack/nova stable/pike: libvirt: Report the virtual size of RAW disks  https://review.openstack.org/56836920:30
*** belmoreira has quit IRC20:33
*** belmoreira has joined #openstack-placement20:42
*** edmondsw has quit IRC20:47
*** edmondsw has joined #openstack-placement20:47
*** belmoreira has quit IRC20:47
*** edmondsw has quit IRC20:52
openstackgerritMohammed Naser proposed openstack/nova master: Added ability to configure default architecture for ImagePropertiesFilter  https://review.openstack.org/56642520:56
*** efried has joined #openstack-placement21:04
*** e0ne has quit IRC21:16
openstackgerritMatt Riedemann proposed openstack/nova stable/ocata: libvirt: Report the virtual size of RAW disks  https://review.openstack.org/56838221:17
*** edmondsw has joined #openstack-placement22:03
*** efried1 has joined #openstack-placement22:05
*** efried has quit IRC22:07
*** efried1 is now known as efried22:07
*** edmondsw has quit IRC22:08
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in test_conductor.py (1)  https://review.openstack.org/56465822:20
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in test_conductor.py (2)  https://review.openstack.org/56465922:21
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in libvirt/test_driver.py (1)  https://review.openstack.org/56655522:21
openstackgerritTakashi NATSUME proposed openstack/nova master: api-ref: Example verification for servers.inc  https://review.openstack.org/52952022:21
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in test_live_migrate.py  https://review.openstack.org/56465622:22
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in tests/unit/api/openstack/compute  https://review.openstack.org/56652822:22
*** mriedem has quit IRC22:22
openstackgerritTakashi NATSUME proposed openstack/nova master: Remove mox in tests/unit/api/*/test_volumes.py  https://review.openstack.org/56465522:22
openstackgerritTakashi NATSUME proposed openstack/nova master: Fix 500 error while passing 4-byte unicode data  https://review.openstack.org/40751422:33
openstackgerritTakashi NATSUME proposed openstack/nova master: Adds view builders for keypairs controller  https://review.openstack.org/34728922:34

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