Earlier  
Posted Nick Remark
#openstack-nova - 2021-05-06
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
12:54:06 sean-k-mooney https://libvirt.org/formatdomain.html#cpu-model-and-topology
12:54:06 sean-k-mooney https://libvirt.org/formatdomain.html#cpu-model-and-topology
12:54:16 sean-k-mooney you can add <cache mode='passthrough'/>
12:54:16 sean-k-mooney you can add <cache mode='passthrough'/>
12:54:20 sean-k-mooney to the cpu element
12:54:20 sean-k-mooney to the cpu element
12:55:19 rmart04 Interesting, is there anyway to add config like this that will persist? Or is it a case of modifying the XML and rebooting the VM in nova and when its trashed, start again?
12:55:19 rmart04 Interesting, is there anyway to add config like this that will persist? Or is it a case of modifying the XML and rebooting the VM in nova and when its trashed, start again?
12:55:39 sean-k-mooney not without modifying the nova code to add it no
12:55:39 sean-k-mooney not without modifying the nova code to add it no
12:55:49 rmart04 OK
12:55:49 rmart04 OK
12:55:53 rmart04 thanks for the information!!
12:55:53 rmart04 thanks for the information!!
12:55:54 sean-k-mooney we regenerate teh xml every time we move the vm or reboot it
12:55:54 sean-k-mooney we regenerate teh xml every time we move the vm or reboot it
12:55:58 rmart04 spot on as always
12:55:58 rmart04 spot on as always
12:56:30 sean-k-mooney this is proably something we could add as a feature but its never really come up
12:56:30 sean-k-mooney this is proably something we could add as a feature but its never really come up
14:19:29 openstackgerrit Tobias Urdin proposed openstack/nova master: When Nova-Api runs behind the load balancer or Reverse proxy, Loadbalancer IP is getting logged in nova_api.log instead of end user source ip by RequestLog https://review.opendev.org/c/openstack/nova/+/786766
15:46:38 openstackgerrit Balazs Gibizer proposed openstack/nova-specs master: QoS minimum guaranteed packet rate https://review.opendev.org/c/openstack/nova-specs/+/785014
15:56:34 gibi nova meeting starts in 4 minutes in #openstack-meeting-3
15:56:34 gibi nova meeting starts in 4 minutes in #openstack-meeting-3
16:51:35 sean-k-mooney dansmith: artom how we are fixing this for them is having them change all the config value to lowercase to match what neturon is expecting. and then doing a db update of all the things
16:51:35 sean-k-mooney dansmith: artom how we are fixing this for them is having them change all the config value to lowercase to match what neturon is expecting. and then doing a db update of all the things
16:52:28 dansmith yeah, I like the hardening of course, but in the interim we have to provide them a way to migrate and fix, since we don't control rabbit
16:52:28 dansmith yeah, I like the hardening of course, but in the interim we have to provide them a way to migrate and fix, since we don't control rabbit
16:53:00 dansmith so either we say "don't change it once you've set it" (which seems reasonable to me) or we say we're going to change everybody, so get your homework done (also reasonable)
16:53:00 dansmith so either we say "don't change it once you've set it" (which seems reasonable to me) or we say we're going to change everybody, so get your homework done (also reasonable)
16:53:20 dansmith if neutron is making some change that is going to require consistency then presumably the latter is the only option
16:53:20 dansmith if neutron is making some change that is going to require consistency then presumably the latter is the only option
16:59:48 bauzas I don't have a particular opinion on how we should fix those RPC issues, but I'm frightened by us trying to change the queue names
16:59:48 bauzas I don't have a particular opinion on how we should fix those RPC issues, but I'm frightened by us trying to change the queue names
17:00:04 bauzas as it's a impactful and visible change
17:00:04 bauzas as it's a impactful and visible change
17:01:06 bauzas anyhow, time to stop
17:01:06 bauzas anyhow, time to stop
17:01:26 artom My brain has mostly checked out at this point (I know, it's only 13:00 here), and I need to run errands anyways
17:01:26 artom My brain has mostly checked out at this point (I know, it's only 13:00 here), and I need to run errands anyways
17:01:34 artom I'll post a spec... I want to say next week?
17:01:34 artom I'll post a spec... I want to say next week?
17:03:04 sean-k-mooney well we can have this just be a workaround config option and never enable it by default
17:03:04 sean-k-mooney well we can have this just be a workaround config option and never enable it by default
17:12:08 openstackgerrit Elod Illes proposed openstack/placement master: Add periodic-stable-jobs template https://review.opendev.org/c/openstack/placement/+/775384
17:12:08 openstackgerrit Elod Illes proposed openstack/placement master: Add periodic-stable-jobs template https://review.opendev.org/c/openstack/placement/+/775384
17:15:25 dansmith sean-k-mooney: artom: We could probably lower() the hostname on service.create() and not service.update() in the short term
17:15:25 dansmith sean-k-mooney: artom: We could probably lower() the hostname on service.create() and not service.update() in the short term
17:15:43 dansmith that won't fix the cell mapping issue, but sounds like that's not the primary concern (or the biggest impact)
17:15:43 dansmith that won't fix the cell mapping issue, but sounds like that's not the primary concern (or the biggest impact)
17:18:41 artom So what's the call mapping issue again?
17:18:41 artom So what's the call mapping issue again?
17:21:15 sean-k-mooney dansmith: am maybe. that word normalise any new service yes
17:21:15 sean-k-mooney dansmith: am maybe. that word normalise any new service yes
17:21:39 dansmith sean-k-mooney: we could do the same for cell mappings actually
17:21:39 dansmith sean-k-mooney: we could do the same for cell mappings actually
17:21:41 sean-k-mooney dansmith: althougy we would have to ensure that compute agents used the host value form the service record not form the config when settin up rpc
17:21:41 sean-k-mooney dansmith: althougy we would have to ensure that compute agents used the host value form the service record not form the config when settin up rpc
17:22:02 dansmith sean-k-mooney: yeah
17:22:02 dansmith sean-k-mooney: yeah
17:23:55 sean-k-mooney im not actully sure where that happens i was expecting to see it here but here https://github.com/openstack/nova/blob/master/nova/cmd/compute.py but i guess its elsewhere
17:23:55 sean-k-mooney im not actully sure where that happens i was expecting to see it here but here https://github.com/openstack/nova/blob/master/nova/cmd/compute.py but i guess its elsewhere
17:24:09 sean-k-mooney proably in the compute manager
17:24:09 sean-k-mooney proably in the compute manager
17:26:27 sean-k-mooney ah
17:26:27 sean-k-mooney ah
17:26:28 dansmith it's probably buried in rpc.py
17:26:28 dansmith it's probably buried in rpc.py
17:26:31 sean-k-mooney https://github.com/openstack/nova/blob/7953c0197d1a4466cb5b78070d47626c92f9db6e/nova/compute/rpcapi.py#L53
17:26:31 sean-k-mooney https://github.com/openstack/nova/blob/7953c0197d1a4466cb5b78070d47626c92f9db6e/nova/compute/rpcapi.py#L53
17:26:43 sean-k-mooney proably but that is where we get the name
17:26:43 sean-k-mooney proably but that is where we get the name
17:26:51 sean-k-mooney we are using instance.host
17:26:51 sean-k-mooney we are using instance.host
17:28:05 dansmith yeah, which might also bring some problems updating those as well
17:28:05 dansmith yeah, which might also bring some problems updating those as well
17:28:18 dansmith unless we use instance.host to look up service.hostname case insensitively and then use the result
17:28:18 dansmith unless we use instance.host to look up service.hostname case insensitively and then use the result
17:31:49 sean-k-mooney we are usign instace.host for the server filed in the client
17:31:49 sean-k-mooney we are usign instace.host for the server filed in the client
17:32:07 sean-k-mooney so if we look at the srever side of the rpc it has to match
17:32:07 sean-k-mooney so if we look at the srever side of the rpc it has to match
17:32:26 sean-k-mooney which is likly using the host value form the config
17:32:26 sean-k-mooney which is likly using the host value form the config
17:33:56 sean-k-mooney https://github.com/openstack/nova/blob/7953c0197d1a4466cb5b78070d47626c92f9db6e/nova/service.py#L184-L194
17:33:56 sean-k-mooney https://github.com/openstack/nova/blob/7953c0197d1a4466cb5b78070d47626c92f9db6e/nova/service.py#L184-L194
17:34:23 sean-k-mooney so ya its usign self.host which shoudl be form the conf
17:34:23 sean-k-mooney so ya its usign self.host which shoudl be form the conf
17:34:37 dansmith right,
17:34:55 dansmith I'm saying that (a) instance.host has to be kept to match service.hostname, so we can't change one without the other
17:34:55 dansmith I'm saying that (a) instance.host has to be kept to match service.hostname, so we can't change one without the other
17:35:07 sean-k-mooney oh yes

Earlier   Later