| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2021-05-20 | |||
| 10:35:02 | sean-k-mooney | what do you think ? | |
| 10:35:02 | sean-k-mooney | what do you think ? | |
| 10:35:38 | artom | sean-k-mooney, ah, interesting... | |
| 10:35:38 | artom | sean-k-mooney, ah, interesting... | |
| 10:36:25 | stephenfin | how would you detect that. I was under the impression that changing the hostname meant the compute node was re-registering itself or something | |
| 10:36:25 | stephenfin | how would you detect that. I was under the impression that changing the hostname meant the compute node was re-registering itself or something | |
| 10:36:45 | sean-k-mooney | not in all cases | |
| 10:36:45 | sean-k-mooney | not in all cases | |
| 10:37:07 | sean-k-mooney | it will but the compute service record wont always change | |
| 10:37:07 | sean-k-mooney | it will but the compute service record wont always change | |
| 10:37:10 | artom | stephenfin, compare the hostname from the OS to the existing DB record? | |
| 10:37:10 | artom | stephenfin, compare the hostname from the OS to the existing DB record? | |
| 10:37:14 | admin0 | in my case, i cannot migrate, spawn new instance, work on security groups, so i think its no harm kind of | |
| 10:37:14 | admin0 | in my case, i cannot migrate, spawn new instance, work on security groups, so i think its no harm kind of | |
| 10:37:38 | sean-k-mooney | artom: there is a chiken and egg problem | |
| 10:37:38 | sean-k-mooney | artom: there is a chiken and egg problem | |
| 10:38:13 | sean-k-mooney | artom: i was thinkign we look up the compute service recored using conf.host then look up the compute node records | |
| 10:38:13 | sean-k-mooney | artom: i was thinkign we look up the compute service recored using conf.host then look up the compute node records | |
| 10:38:24 | sean-k-mooney | if its the libvirt dirver their shoudl be at most one | |
| 10:38:24 | sean-k-mooney | if its the libvirt dirver their shoudl be at most one | |
| 10:38:45 | sean-k-mooney | we then check the compute node recored and compare the hypervior hostname | |
| 10:38:45 | sean-k-mooney | we then check the compute node recored and compare the hypervior hostname | |
| 10:39:04 | sean-k-mooney | for ironic this wont work but for libvirt we can do that | |
| 10:39:04 | sean-k-mooney | for ironic this wont work but for libvirt we can do that | |
| 10:39:28 | artom | sean-k-mooney, so it would have to be a driver-level check, not compute service | |
| 10:39:28 | artom | sean-k-mooney, so it would have to be a driver-level check, not compute service | |
| 10:39:35 | sean-k-mooney | yes | |
| 10:39:43 | sean-k-mooney | init_host in the driver not in the compute manager | |
| 10:39:43 | sean-k-mooney | init_host in the driver not in the compute manager | |
| 10:40:32 | sean-k-mooney | admin0: you cant perform api action because the compute agent create a queue with the vauels of CONF.host | |
| 10:40:32 | sean-k-mooney | admin0: you cant perform api action because the compute agent create a queue with the vauels of CONF.host | |
| 10:41:01 | sean-k-mooney | admin0: but the conductor send rpc calls to the queue named in instance.host | |
| 10:41:01 | artom | If we can make it work I think it'd be worthwhile | |
| 10:41:01 | sean-k-mooney | admin0: but the conductor send rpc calls to the queue named in instance.host | |
| 10:41:01 | artom | If we can make it work I think it'd be worthwhile | |
| 10:41:29 | sean-k-mooney | so if the instance.host does not match the agent queu name it gets lost | |
| 10:41:29 | sean-k-mooney | so if the instance.host does not match the agent queu name it gets lost | |
| 10:41:33 | admin0 | is there a quick way to check what is the value of CONF.host and what is the value of instance.host ? | |
| 10:41:33 | admin0 | is there a quick way to check what is the value of CONF.host and what is the value of instance.host ? | |
| 10:41:40 | sean-k-mooney | you will also have the schduelr issue you hit | |
| 10:41:40 | sean-k-mooney | you will also have the schduelr issue you hit | |
| 10:41:45 | artom | But I suspect it would have to be overridable, with a conf option or something | |
| 10:41:45 | artom | But I suspect it would have to be overridable, with a conf option or something | |
| 10:42:02 | sean-k-mooney | artom: im not sure it would | |
| 10:42:02 | sean-k-mooney | artom: im not sure it would | |
| 10:42:16 | sean-k-mooney | but we can discuss that in the implemantion | |
| 10:42:17 | sean-k-mooney | but we can discuss that in the implemantion | |
| 10:42:57 | sean-k-mooney | artom: the only time it would be allowable but ill advised to change the hostname today is if there are no instnaces on the host | |
| 10:42:57 | sean-k-mooney | artom: the only time it would be allowable but ill advised to change the hostname today is if there are no instnaces on the host | |
| 10:43:46 | artom | sean-k-mooney, oh, I agree with you in principle | |
| 10:43:46 | artom | sean-k-mooney, oh, I agree with you in principle | |
| 10:43:51 | artom | But you know how operators be ;) | |
| 10:43:51 | artom | But you know how operators be ;) | |
| 10:45:05 | openstackgerrit | norman shen proposed openstack/nova master: Saving security group to info_cache https://review.opendev.org/c/openstack/nova/+/786348 | |
| 10:45:06 | admin0 | mine was an oversight.. unintentional | |
| 10:45:06 | admin0 | mine was an oversight.. unintentional | |
| 10:45:45 | admin0 | midway we decided to not have .openstack.local but the playbooks updated every hostname ( including existing ones) | |
| 10:45:45 | admin0 | midway we decided to not have .openstack.local but the playbooks updated every hostname ( including existing ones) | |
| 10:46:17 | admin0 | what creates a new queue in rabbitmq? is it the compute node ? | |
| 10:46:17 | admin0 | what creates a new queue in rabbitmq? is it the compute node ? | |
| 10:46:42 | artom | admin0, they usually are, and this is what sean-k-mooney is trying to prevent. But I can easily imagine someone saying "no no, we know what we're doing, we're totally going to rename this host" | |
| 10:46:42 | artom | admin0, they usually are, and this is what sean-k-mooney is trying to prevent. But I can easily imagine someone saying "no no, we know what we're doing, we're totally going to rename this host" | |
| 10:47:14 | admin0 | i also think its a lack of documentation or warning . i don't recall reading this otherwise we would have put it in the policy | |
| 10:47:15 | admin0 | i also think its a lack of documentation or warning . i don't recall reading this otherwise we would have put it in the policy | |
| 10:47:28 | artom | Fair point. I guess we thought it was implicit? | |
| 10:47:28 | artom | Fair point. I guess we thought it was implicit? | |
| 10:48:28 | admin0 | you guys know the code and for you all.. its implicit .. we ( operators) read the deployment guide and make policies based on the guides .. so this point got overlooked | |
| 10:48:28 | admin0 | you guys know the code and for you all.. its implicit .. we ( operators) read the deployment guide and make policies based on the guides .. so this point got overlooked | |
| 10:49:13 | artom | "you guys know the code" Should... should we tell them? ;) | |
| 10:49:13 | artom | "you guys know the code" Should... should we tell them? ;) | |
| 10:49:23 | admin0 | :D | |
| 10:49:23 | admin0 | :D | |
| 10:49:51 | sean-k-mooney | artom: operators tend to get annoy wehn we tell them we explictly dont support this so your on your own to fix your mess | |
| 10:49:52 | sean-k-mooney | artom: operators tend to get annoy wehn we tell them we explictly dont support this so your on your own to fix your mess | |
| 10:51:15 | sean-k-mooney | admin0: we should have documenation for this as far as i know we dissuced adding it a few times | |
| 10:51:15 | sean-k-mooney | admin0: we should have documenation for this as far as i know we dissuced adding it a few times | |
| 10:55:22 | sean-k-mooney | admin0: i still cant finx the warning we said shold be added like 2 years ago :( | |
| 10:55:22 | sean-k-mooney | admin0: i still cant finx the warning we said shold be added like 2 years ago :( | |
| 10:56:42 | sean-k-mooney | admin0: not to dismay you but this is one of the harder thing to fix to the point that the only supporte way to actully change the host name is generally to scale in and redeploy | |
| 10:56:42 | sean-k-mooney | admin0: not to dismay you but this is one of the harder thing to fix to the point that the only supporte way to actully change the host name is generally to scale in and redeploy | |
| 11:09:36 | admin0 | sean-k-mooney, if i have a way to migraete ceph backed instances off this hypervisor to another one, i would happilfy redeploy | |
| 11:09:36 | admin0 | sean-k-mooney, if i have a way to migraete ceph backed instances off this hypervisor to another one, i would happilfy redeploy | |
| 11:09:55 | admin0 | i don't understand nova :) .. https://gist.githubusercontent.com/a1git/9d4f3115529a53793703ef08bdfd752b/raw/ceec98a6145170143146d9dbd276156c5a52278f/gistfile1.txt | |
| 11:09:55 | admin0 | i don't understand nova :) .. https://gist.githubusercontent.com/a1git/9d4f3115529a53793703ef08bdfd752b/raw/ceec98a6145170143146d9dbd276156c5a52278f/gistfile1.txt | |
| 11:10:04 | admin0 | i changed all to h3 .. then it still adds as h3. | |
| 11:10:04 | admin0 | i changed all to h3 .. then it still adds as h3. | |
| 11:11:17 | sean-k-mooney | is h3. in the instance.host | |
| 11:11:17 | sean-k-mooney | is h3. in the instance.host | |
| 11:12:18 | sean-k-mooney | by the way libvirt also caches info | |
| 11:12:18 | sean-k-mooney | by the way libvirt also caches info | |
| 11:13:11 | sean-k-mooney | so i think you will need to restart libvirt when you make these change before you restart the compute agent | |
| 11:13:11 | sean-k-mooney | so i think you will need to restart libvirt when you make these change before you restart the compute agent | |
| 11:13:57 | sean-k-mooney | have you restarted the nova-compute agent after the hostname change | |
| 11:13:58 | sean-k-mooney | have you restarted the nova-compute agent after the hostname change | |
| 11:15:40 | admin0 | i have restarted the nova-compute agent only | |
| 11:15:41 | admin0 | i have restarted the nova-compute agent only | |
| 11:15:44 | admin0 | and not libvirt | |
| 11:15:44 | admin0 | and not libvirt | |
| 11:15:53 | admin0 | will restarting libvirt cause a downtime to the guests ? | |
| 11:15:53 | admin0 | will restarting libvirt cause a downtime to the guests ? | |