Earlier  
Posted Nick Remark
#openstack-nova - 2021-05-06
10:54:31 sean-k-mooney the allocation dont need to move
10:54:35 gibi yepp
10:55:14 sean-k-mooney what we can do its encode the libvirt logic which is in the neutron patch in an oslo patch
10:55:14 sean-k-mooney what we can do its encode the libvirt logic which is in the neutron patch in an oslo patch
10:55:20 sean-k-mooney and then use that
10:55:20 sean-k-mooney and then use that
10:55:42 sean-k-mooney for libvirt at least it woudl not change behaivor and for other driver i suspect it wont either
10:55:42 sean-k-mooney for libvirt at least it woudl not change behaivor and for other driver i suspect it wont either
10:55:56 gibi I cannot comment on other drivers cases
10:55:56 gibi I cannot comment on other drivers cases
10:56:11 sean-k-mooney well ironic they use the ironic node uuid as the name right?
10:56:11 sean-k-mooney well ironic they use the ironic node uuid as the name right?
10:56:32 sean-k-mooney not sure what hyperv or vmware does
10:56:32 sean-k-mooney not sure what hyperv or vmware does
10:56:38 gibi yes. but I don't know if neutron ever needs that
10:56:38 gibi yes. but I don't know if neutron ever needs that
10:56:49 gibi that = ironic node name
10:56:49 gibi that = ironic node name
10:56:57 sean-k-mooney ya the neutron agent dont run on the ironic nodes
10:56:57 sean-k-mooney ya the neutron agent dont run on the ironic nodes
10:57:35 gibi I have to jump to a call from the top of the hour
10:57:35 gibi I have to jump to a call from the top of the hour
10:57:50 gibi I linked this discussion to the neutron patch for reference
10:57:50 gibi I linked this discussion to the neutron patch for reference
10:57:54 sean-k-mooney no worries thanks for litening
10:57:54 sean-k-mooney no worries thanks for litening
10:58:51 sean-k-mooney ill try an follow up downstream and see if we can come to can concreate conclutions
10:58:51 sean-k-mooney ill try an follow up downstream and see if we can come to can concreate conclutions
10:59:09 gibi OK
10:59:34 gibi sorry for being dense
10:59:34 gibi sorry for being dense
10:59:51 sean-k-mooney you werent being dense
10:59:51 sean-k-mooney you werent being dense
10:59:58 sean-k-mooney it helped
10:59:58 sean-k-mooney it helped
11:00:55 gibi then I'm glad :)
11:00:55 gibi then I'm glad :)
12:18:18 sean-k-mooney gibi: would adding a new weigher need a spec. or could that be a specless blueprint
12:18:18 sean-k-mooney gibi: would adding a new weigher need a spec. or could that be a specless blueprint
12:18:49 gibi if the config of the weigher is trivial then I'm OK with a specless bp
12:18:49 gibi if the config of the weigher is trivial then I'm OK with a specless bp
12:19:37 sean-k-mooney i have 2 that i think might be useful. 1 is weighe based on the number of runing instnace and the other is a weigher that prefers the current host an instance is on
12:19:37 sean-k-mooney i have 2 that i think might be useful. 1 is weighe based on the number of runing instnace and the other is a weigher that prefers the current host an instance is on
12:20:59 gibi please note that today all the weigher is turned on by default so more weigher means a more complex behavior.
12:20:59 gibi please note that today all the weigher is turned on by default so more weigher means a more complex behavior.
12:21:23 gibi * all the weighers are
12:21:23 gibi * all the weighers are
12:21:59 sean-k-mooney yep
12:22:20 sean-k-mooney we may or may not want that for these
12:22:20 sean-k-mooney we may or may not want that for these
12:22:44 sean-k-mooney basically our perf team has a bunch of hosts with differnt size for ram disk and cpu
12:22:44 sean-k-mooney basically our perf team has a bunch of hosts with differnt size for ram disk and cpu
12:23:11 sean-k-mooney and they are booting a bunch of small instance and they are all landing on 2 hosts because it has much more ram,cpu and disk then the others
12:23:11 sean-k-mooney and they are booting a bunch of small instance and they are all landing on 2 hosts because it has much more ram,cpu and disk then the others
12:24:36 gibi I think it is a valid need to have weighers that are not turned on by default
12:24:36 gibi I think it is a valid need to have weighers that are not turned on by default
12:24:38 sean-k-mooney as in the have 46 hosts and booted about 520 instace at this point and they have 2 host with 237 and 247 instances
12:24:38 sean-k-mooney as in the have 46 hosts and booted about 520 instace at this point and they have 2 host with 237 and 247 instances
12:25:57 sean-k-mooney so having a pretty dumb weither that jsut spread or packed by instances would help them. im goign to get them to set host_subset_size=46 so its just a random choice for now
12:25:57 sean-k-mooney so having a pretty dumb weither that jsut spread or packed by instances would help them. im goign to get them to set host_subset_size=46 so its just a random choice for now
12:26:34 sean-k-mooney that will get the the even distibution they want but i think it coudl be useful
12:26:34 sean-k-mooney that will get the the even distibution they want but i think it coudl be useful
12:27:04 sean-k-mooney the current host weigher would be so that people that want resize to same host to not change host could expess that preference if they really wanted too by truning on that weither
12:27:04 sean-k-mooney the current host weigher would be so that people that want resize to same host to not change host could expess that preference if they really wanted too by truning on that weither
12:27:51 sean-k-mooney gibi: im going to proably right a mini spec for moveing some of the fitlers to placmenet native approch so i could also add this there too
12:27:51 sean-k-mooney gibi: im going to proably right a mini spec for moveing some of the fitlers to placmenet native approch so i could also add this there too
12:28:14 gibi hm, I think if allow_resize_to_same_host=False then we add the scheduler will ignore the current host
12:28:14 gibi hm, I think if allow_resize_to_same_host=False then we add the scheduler will ignore the current host
12:28:22 sean-k-mooney just make it a generic schduling enhancements spec.
12:28:22 sean-k-mooney just make it a generic schduling enhancements spec.
12:28:32 sean-k-mooney gibi: it will the host manager will remove it
12:28:32 gibi sean-k-mooney: that also works for me
12:28:32 sean-k-mooney gibi: it will the host manager will remove it
12:28:32 gibi sean-k-mooney: that also works for me
12:28:56 sean-k-mooney but if you set it to ture there is no prefernce for stayingon the same host or not staying on the same host
12:28:56 sean-k-mooney but if you set it to ture there is no prefernce for stayingon the same host or not staying on the same host
12:29:20 gibi ohh, I did not know that, then I see why you need the weigher
12:29:20 gibi ohh, I did not know that, then I see why you need the weigher
12:29:37 sean-k-mooney well need is a stong word but it might be nice ot have
12:29:37 sean-k-mooney well need is a stong word but it might be nice ot have
12:30:15 gibi yeah, I agree
12:30:15 gibi yeah, I agree
12:30:31 sean-k-mooney we ocationally get customer confused by that, its not that common but it happens
12:30:31 sean-k-mooney we ocationally get customer confused by that, its not that common but it happens
12:42:56 rmart04 Hello, having some IRC issues, hopefully this works!
12:42:56 rmart04 Hello, having some IRC issues, hopefully this works!
12:43:54 rmart04 I've noticed that in VM's on Stein / host-passthrough cpu mode and dedicated core pinning policy, that the L2 and L3 cache values for the CPU do not match the physical CPU. Is this expected? Any way to configure?
12:43:54 rmart04 I've noticed that in VM's on Stein / host-passthrough cpu mode and dedicated core pinning policy, that the L2 and L3 cache values for the CPU do not match the physical CPU. Is this expected? Any way to configure?
12:47:13 gibi belmoreira: thanks for the report https://bugs.launchpad.net/nova/+bug/1924123 it is an interesting finding. Unfortunately it is not easy to fix.
12:47:15 openstack Launchpad bug 1924123 in OpenStack Compute (nova) "If source compute node is overcommitted instances can't be migrated" [Medium,Triaged]
12:47:15 openstack Launchpad bug 1924123 in OpenStack Compute (nova) "If source compute node is overcommitted instances can't be migrated" [Medium,Triaged]
12:47:15 gibi belmoreira: thanks for the report https://bugs.launchpad.net/nova/+bug/1924123 it is an interesting finding. Unfortunately it is not easy to fix.
12:50:00 sean-k-mooney rmart04: yes
12:50:00 sean-k-mooney rmart04: yes
12:50:19 sean-k-mooney you can also configure passthough of the host cache info but we dont do that in nova today
12:50:19 sean-k-mooney you can also configure passthough of the host cache info but we dont do that in nova today
12:53:07 rmart04 Ah, ok so possible in Libvirt/KVM but not exposed to nova?
12:53:07 rmart04 Ah, ok so possible in Libvirt/KVM but not exposed to nova?
12:53:37 sean-k-mooney correct
12:53:37 sean-k-mooney correct

Earlier   Later