Friday, 2019-09-06

*** artom has quit IRC00:38
*** openstackgerrit has joined #openstack-placement06:10
openstackgerritMichael Davies proposed openstack/os-traits master: Add support for ppc64le platforms  https://review.opendev.org/68058006:10
*** cdent has joined #openstack-placement08:19
*** e0ne has joined #openstack-placement08:24
*** cdent has quit IRC08:44
openstackgerritQitao proposed openstack/placement master: Fix misspell word  https://review.opendev.org/68062608:51
*** zigo has quit IRC08:57
*** zigo has joined #openstack-placement09:05
*** cdent has joined #openstack-placement09:25
*** spatel has joined #openstack-placement09:31
*** spatel has quit IRC09:35
*** artom has joined #openstack-placement10:07
*** spatel has joined #openstack-placement11:01
*** spatel has quit IRC11:05
*** cdent has quit IRC11:32
*** cdent has joined #openstack-placement11:43
*** mriedem has joined #openstack-placement12:46
cdentbiab14:28
*** cdent has quit IRC14:28
*** cdent has joined #openstack-placement15:22
*** johnthetubaguy has quit IRC15:37
*** mriedem is now known as mriedem_lunch16:11
sean-k-mooneycdent: by the regarding placement feature for you there is 1 maybe too that im vagely aware of on the other hand there are several feature nova has not used yet so we might not get to a point where we need the new feature16:23
cdentsean-k-mooney: what's that?16:25
sean-k-mooneyinplace rebuild without duplicate allocations16:28
sean-k-mooneyif you rebuild normally you dont change resouce requiremetns16:28
sean-k-mooneyhowever if you have the numa toplogy or cpu pinning set in the image you could16:28
cdentthat sounds like a nova feature, not a placement feature?16:29
cdentthat is: what allocations you write is up to nova16:29
sean-k-mooneyyes but the allocation could chagne16:29
cdentagain: the client is entirely in charge of what the allocations are for any consumer id16:29
sean-k-mooneyso the feature we were toying with was could we ask placemetn is this existing allocation valid for this new request16:29
cdentas in "is this mine"? that sounds like a client side memory of associated consumer ids16:30
cdentemphasis on the client side16:30
cdentmight be able to hack consumer types (if they merge)16:30
sean-k-mooneyyes i think we might be able to do it client side however the image can also ask for things like traits16:31
sean-k-mooneysoe changing the image might invalidate the host16:31
cdentI'm still not really understanding how placement would be able to help in this situation16:31
cdentI think I don't have enough context16:32
cdentbut I would hope/guess that what you said about nova needing to catch up other places first is probalby right16:32
sean-k-mooneywell basicaly i am saying i have already have allocation x. i need resouces y and assing on the current resouce provider can placmeent satify the request using the current allcoation or the remaing free resouces16:32
cdentoh! you want to be able to say "can I extend this allocation in the same resource provider"16:33
cdentwhich needs to be somewhat atomic16:33
cdentnow I get you16:33
sean-k-mooneyyes kind of16:33
sean-k-mooneyso instead of doubleing the allcoation16:33
sean-k-mooneywhich is what we do on resize to same host16:34
sean-k-mooneycan i in place atomicaly update theam16:34
sean-k-mooneyfor rebuild we cant move the instace unlike resize16:34
sean-k-mooneyso it much more likely for the double allcoation to fail16:34
* cdent nods16:34
sean-k-mooneytoday i dont think we go back to placement on rebuild16:35
sean-k-mooneybut that means we are ignoreing tratis on the new image if that is correct16:35
sean-k-mooneyi know we rerun some fo the filter16:35
sean-k-mooneyif we do go back to placemnt then we have the double allocation problem16:35
cdenti suppose you could ask for resources in GET /a_c that are the (positive) difference between what you have and what you want, and use the in_tree param16:36
cdentbut you'll race on that16:36
sean-k-mooneyyes possibley16:36
cdentthe thing we want to absolutely avoid is placement having to manage any more state than it already does16:37
cdents/state/types of state/16:38
*** e0ne has quit IRC16:39
sean-k-mooneyya16:39
sean-k-mooneyi get that16:39
sean-k-mooneyhow i would expect it to work if it was added is i say this is my exsting allocation and the desitred state16:40
sean-k-mooneyand placmeent either rturns an error 409?/nothing or the update allcoation16:40
sean-k-mooneybut i would like to see if we can do it client side first16:40
sean-k-mooneyor if its neeeded at all16:40
cdentI kind of get the impression that there's going to need to be quite a bit of hard deciding about which features actually get attention in nova in U16:43
cdentand since there's quite the backlog...16:43
*** efried is now known as efried_afk16:51
*** cdent has quit IRC16:58
*** mriedem_lunch is now known as mriedem17:38
*** e0ne has joined #openstack-placement17:58
*** e0ne has quit IRC18:15
*** efried_afk is now known as efried18:54
*** efried is now known as efried_afk20:19
*** efried_afk is now known as efried21:22
*** mriedem has quit IRC21:41
*** e0ne has joined #openstack-placement22:02
*** e0ne has quit IRC22:34
openstackgerritMerged openstack/placement master: Fix misspell word  https://review.opendev.org/68062623:28
*** efried has quit IRC23:51

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