Earlier  
Posted Nick Remark
#openstack-nova - 2018-03-30
14:10:16 bauwser indeed, it's not registered to your main account
14:11:05 bauwser but fried_chicken isn't ;)
14:11:29 bauwser oops, I meant fried_bunny
14:12:19 fried_bunny bauwser: fried_bunny is just for today. Maybe through Monday (that's still an Easter thing, right?)
14:12:42 bauwser Easter for us is on Monday
14:13:00 bauwser Good Friday has nothing to do with egs
14:13:02 bauwser eggs
14:18:38 fried_bunny claudiub: in case you're still around, just posted some comments on https://review.openstack.org/#/c/141219/ which should be easy to rev.
14:20:02 fried_bunny bauwser: Oh, you see, in the US, the entire month preceding Easter Monday gets completely overrun with bunnies and eggs and garish plastic grass and hideous pastel colors. It's how we capitalist pigs roll.
14:22:19 bauwser haha
14:25:58 leakypipes bhagyashris: you do not want to specify parent_provider_uuid for your compute node.
14:26:11 leakypipes bhagyashris: the shared storage pool is not the parent of the compute node.
14:26:54 leakypipes bhagyashris: the relationship between the shared storage pool and the compute node is via the aggregate, not via a parent-child relationship.
14:27:31 leakypipes bhagyashris: I'm not sure that we support "re-parenting", so you may need to delete the resource provider records in your placement DB entirely and start over.
14:27:52 bhagyashris leakypipes: ok. through aggregate also i have tried and tested but still it's not taking DISK_GB from shared resource provider
14:27:59 leakypipes bhagyashris: alternately, you could just execute an UPDATE statement directly in the placement DB to fix the provider records up.
14:28:46 leakypipes bhagyashris: UPDATE resource_providers SET parent_provider_id = NULL, root_provider_id = $INTERNAL_ID_OF_COMPUTE_NODE WHERE id = $INTERNAL_ID_OF_COMPUTE_NODE;
14:29:54 leakypipes bhagyashris: allocations definitely do not yet work when nested providers are present. there may be a bug regarding sharing resource providers, but let's eliminate the nested scenario for starters, ok?
14:33:28 bhagyashris leakypipes: you mean to say I will need to update the compute node resource provider
14:34:09 leakypipes bhagyashris: correct.
14:35:40 bhagyashris leakypipes: and on current master the shared resource provider provider is not implemented completely i mean to say that is not taken into account when user rquest to boot the instance
14:36:09 leakypipes bhagyashris: yes, it should be.
14:36:56 leakypipes bhagyashris: or at least, if the *only* provider of DISK_GB is the shared storage pool (and the compute node doesn't itself have local disk), then everything should work...
14:37:26 leakypipes bhagyashris: there is currently a bug where if both the local compute node and a shared pool have DISK_GB resources, that we will always pick the local compute node.
14:38:11 leakypipes bhagyashris: tetsuro has been fixing that bug in this patch: https://review.openstack.org/#/c/533396/
14:38:36 bhagyashris leakypipes: aI have debug the code as well and observed that the when user request the boot server then only the compute node resource provider allocation_candidates are return so from that it seems like the shared resource provider is not taken into account while scheduling.
14:40:11 leakypipes bhagyashris: when both the compute node and the shared pool have inventory of DISK_GB, right?
14:40:23 leakypipes bhagyashris: and I'm saying that that is a known bug.
14:40:30 leakypipes bhagyashris: being addressed in https://review.openstack.org/#/c/533396/
14:40:41 bhagyashris leakypipes: yes
14:41:38 bhagyashris leakypipes: ok. this patch will help me to success my test scenario :)
14:42:12 leakypipes bhagyashris: would be awesome if you were able to apply that patch locally and see if that resolves your issues.
14:42:16 leakypipes bhagyashris: :)
14:42:37 claudiub fried_bunny: done, thanks. :)
14:43:46 leakypipes stephenfin, mriedem, dansmith, fried_bunny, melwitt: reviews on the three bottom patches of the patches here from tetsuro would be appreciated: https://review.openstack.org/#/c/533396/
14:43:59 fried_bunny leakypipes: ack
14:44:05 leakypipes danke
14:44:16 leakypipes fried_bunny: 10-4 good bunny.
14:44:27 fried_bunny leakypipes: I'm +1 on the bottom one already FYI
14:45:08 leakypipes cool, thanks
14:45:30 fried_bunny claudiub: have you posted the rev yet?
14:45:39 claudiub amending
14:45:41 bhagyashris leakypipes: for testing i will not need to update any shared resource provider entry. I will just need to add all the resource provider under one aggregate and set the traits right?
14:45:53 claudiub there was an unclear question
14:46:07 claudiub i hope i answered right. can you check?
14:47:57 leakypipes bhagyashris: the traits are already set properly, AFAICT
14:48:26 leakypipes bhagyashris: the only thing you'll need to do is change the parent_provider_id and root_provider_id on the compute node resource provider record and then remove the inventory on the compute node for the DISK_GB resource class.
14:48:44 cdent kashyap: stein, not solar, sadly
14:49:09 leakypipes cdent: sadly would have been a better name.
14:49:16 cdent i wanted shellhaus
14:49:21 cdent seemed so spot on
14:49:41 leakypipes shellout...
14:50:56 openstackgerrit Claudiu Belu proposed openstack/nova-specs master: Adds spec for instance live resize https://review.openstack.org/141219
14:51:12 cdent leakypipes, fried_bunny, figleaf, bauwser : I've just published the latest placement update. It's freakin' huge man. We're probably going to need to do some rationalization.
14:53:02 bhagyashris leakypipes: ok just confirming: the parent_provider_id will be nulland root_provider_id will be the shared resource provider right?
14:53:35 leakypipes cdent: ack
14:54:04 leakypipes bhagyashris: no. root_provider_id should be the same value as id column (for the compute node resource provider).
14:54:13 leakypipes bhagyashris: and parent_provider_id should be NULL, yes
14:56:42 figleaf cdent: I'll add that as a discussion item for Monday's scheduler meeting
14:56:53 figleaf Or are most people off on Monday? (I'm not)
14:57:00 cdent rad
14:57:06 cdent oh, yeah. I'm supposed to be
14:57:09 cdent but meh
14:57:21 bhagyashris leakypipes: ok thank you for your inputs I will test this by applying this patch but as i am working in IST time so it's almost End of the day so i will check and will let you know once testing done
14:57:29 bhagyashris leakypipes: thank you :)
14:57:47 leakypipes bhagyashris: no problem at all. thanks much for your testing help!
15:06:31 mriedem leakypipes: musing in https://review.openstack.org/#/c/553122/
15:06:38 mriedem will hold for fried_bunny
15:11:04 leakypipes fried_bunny: did you catch melwitt's question to you on https://review.openstack.org/#/c/533821/?
15:19:34 leakypipes mriedem: left some notes for you on that
15:30:19 fried_bunny sorry guys, was afk for a few. Catching up.
15:31:05 fried_bunny mriedem: Ack
15:31:21 fried_bunny leakypipes: Yes, was planning to dig into that today.
15:33:45 leakypipes fried_bunny: cool, np. just checking to see if you had
15:33:57 fried_bunny yuh, thanks.
15:34:20 leakypipes cdent: understatement of the year in your placement update: "There's also been a _lot_ of discussion around NUMA handling"
15:34:30 fried_bunny leakypipes: I've slowed myself way down by picking up lots of extra reviews - probably too many, need to scale back some.
15:34:46 leakypipes fried_bunny: learn, you will, young paduan.
15:37:36 openstackgerrit Matt Riedemann proposed openstack/nova master: Add "bind_ports_to_host" neutron API method https://review.openstack.org/523604
15:37:37 openstackgerrit Matt Riedemann proposed openstack/nova master: Add VIFMigrateData object for live migration https://review.openstack.org/515423
15:37:37 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: libvirt: use dest host vif migrate details for live migration https://review.openstack.org/551370
15:37:38 openstackgerrit Matt Riedemann proposed openstack/nova master: Add "delete_port_binding" network API method https://review.openstack.org/552170
15:37:38 openstackgerrit Matt Riedemann proposed openstack/nova master: Add "activate_port_binding" neutron API method https://review.openstack.org/555947
15:37:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Delete port bindings in setup_networks_on_host if teardown=True https://review.openstack.org/556333
15:37:39 openstackgerrit Matt Riedemann proposed openstack/nova master: Implement migrate_instance_start method for neutron https://review.openstack.org/556334
15:37:40 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: compute: use port binding extended API during live migration https://review.openstack.org/551371
15:37:40 openstackgerrit Matt Riedemann proposed openstack/nova master: WIP: Port binding based on events during live migration https://review.openstack.org/434870
15:37:41 openstackgerrit Matt Riedemann proposed openstack/nova master: conductor: use port binding extended API in during live migrate https://review.openstack.org/522537
15:39:54 openstackgerrit Merged openstack/nova-specs master: Update the vGPU spec https://review.openstack.org/557912
16:15:55 openstackgerrit Arvind Nadendla proposed openstack/nova master: Update ImageMetaProp object to expose traits https://review.openstack.org/557795
16:16:35 openstackgerrit Ed Leafe proposed openstack/nova master: Add the 'generation' column to the consumers table https://review.openstack.org/557958
16:16:35 openstackgerrit Ed Leafe proposed openstack/nova master: Add handlers for consumer_generation https://review.openstack.org/557959
16:17:06 figleaf leakypipes: fried_bunny: cdent: ^^ First crack at consumer generations. More to come
16:17:39 fried_bunny figleaf: ack
16:17:52 leakypipes figleaf: nice, thank you sir.
16:18:20 cdent figleaf: I'm going to ignore that until next week please and thank you
16:19:06 fried_bunny claudiub|2: Still around?
16:23:16 figleaf cdent: ignore away
16:23:19 figleaf :)
16:26:58 claudiub|2 fried_bunny: i am now

Earlier   Later