| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-08-25 | |||
| 19:25:09 | atmark | yes, I manually deleted it from db cuz it won't let me delete via API | |
| 19:25:54 | atmark | still seeing the compute when running `openstack compute service list` | |
| 19:26:11 | atmark | this is a dev env | |
| 19:26:28 | sean-k-mooney | ok so you porblay could not delete it form the api because it had allcoation assocated with it | |
| 19:26:30 | atmark | how can I totally clean this up? | |
| 19:26:49 | sean-k-mooney | asuming you have stoped nova-compute on the host in your dev env | |
| 19:27:00 | atmark | yep it's stopped | |
| 19:27:07 | sean-k-mooney | then you will likely need to delete the compute service in the cell 1 db | |
| 19:27:18 | sean-k-mooney | is this devstack or somethign else | |
| 19:27:30 | atmark | kolla-ansible | |
| 19:27:58 | sean-k-mooney | ok i need to check the db name but it will likely be either nova_cell1 or just nova | |
| 19:28:08 | atmark | there's no nova | |
| 19:28:17 | atmark | nova_cell1 and nova_cell0 | |
| 19:28:47 | sean-k-mooney | ya so in nova_cell1 there is a comptue service table and a compute nodes table and you will need to mark the relevent row as deleted in both | |
| 19:29:24 | atmark | compute_nodes ? | |
| 19:29:56 | atmark | is that the table name ? | |
| 19:30:44 | atmark | that's the only table name that starts with compute_* | |
| 19:31:26 | sean-k-mooney | hum i guess that is a recent change my home kolla ansibel has nova isntead of nova_cell1 | |
| 19:31:32 | sean-k-mooney | one sec while i check | |
| 19:31:55 | sean-k-mooney | so you will have a table called services | |
| 19:32:15 | atmark | yeah, my prod env has three nova tables, nova, nova_cell0 and nova_cell1 | |
| 19:32:22 | atmark | dev only has two | |
| 19:33:00 | atmark | this isn't any issue right ? | |
| 19:33:05 | sean-k-mooney | you should really have nova_api nova_cell1 and nova_cell0 | |
| 19:33:17 | atmark | i have nova_api all envs | |
| 19:33:24 | atmark | in all envs* | |
| 19:33:27 | sean-k-mooney | ah ok | |
| 19:33:38 | sean-k-mooney | ya so the nova cell1 db used to be called nova | |
| 19:33:45 | atmark | but no 'nova' db in dev | |
| 19:33:48 | sean-k-mooney | we recommend however that you call it nova_cell1 | |
| 19:34:01 | sean-k-mooney | that fine they proably just change the defautl name to follow our recomendations | |
| 19:34:20 | sean-k-mooney | select count(*) from nova_cell1.services; | |
| 19:34:28 | sean-k-mooney | if you do that you will have multiple rows | |
| 19:35:42 | atmark | https://paste.openstack.org/show/b5Sy9Ww7HUGcRG7zWKhc/ | |
| 19:36:09 | sean-k-mooney | so if you do "select * from nova.services s where s.binary='nova-compute';" you will see the compute node records | |
| 19:36:19 | sean-k-mooney | and you will need to clean up the one for the host you removed | |
| 19:36:28 | atmark | got it | |
| 19:36:54 | sean-k-mooney | you shoudl also do the same in the compute_nodes table but it the service table that is used when you do a openstack compute service list | |
| 19:37:08 | atmark | nova_cell1.services and nova_cell0.services right ? | |
| 19:37:12 | sean-k-mooney | the compute_nodes table is use by openstack hypervisor list | |
| 19:37:39 | sean-k-mooney | no you only need to remove the compute record form cell 1 | |
| 19:37:47 | sean-k-mooney | dont remove them all | |
| 19:38:03 | sean-k-mooney | technially you actully want ot set deleted=id for that specific row | |
| 19:39:21 | atmark | ok nova_cell0 table are controllers services | |
| 19:39:24 | atmark | make sense | |
| 19:39:28 | sean-k-mooney | yes | |
| 19:39:49 | sean-k-mooney | cell0 is special and never has computes | |
| 19:40:13 | sean-k-mooney | cell1 is the first "real" cell in that it the first cell that can have computes | |
| 19:40:40 | sean-k-mooney | the name does not actully matter but cell0 or rhat the cell with the all 0 uuid is special in nova | |
| 20:08:36 | opendevreview | Jay Faulkner proposed openstack/nova master: [ironic] Optionally set lessee on deployment https://review.opendev.org/c/openstack/nova/+/888290 | |
| 20:31:29 | opendevreview | Merged openstack/nova master: [functional]Fix remaining greenlet leaks https://review.opendev.org/c/openstack/nova/+/892793 | |
| 20:48:42 | opendevreview | Jay Faulkner proposed openstack/nova master: [ironic] Optionally set lessee on deployment https://review.opendev.org/c/openstack/nova/+/888290 | |
| 20:50:42 | JayF | https://review.opendev.org/c/openstack/nova/+/888290 is tested in devstack, working, simple, and limited to Ironic's virt driver. Your reviews are appreciated :) | |
| 20:57:13 | atmark | sean-k-mooney: what should be id for deleted in compute_nodes table ? | |
| 20:57:54 | atmark | the id between services and compute_nodes table don't match https://paste.openstack.org/show/b2yJiggYenod3SoioAyo/ | |
| 20:58:13 | atmark | i'm trying to get rid of compute05.dev | |
| 21:38:19 | atmark | sean-k-mooney: figured it out. I matched the value in id and deleted in compute_nodes table | |
| 21:38:27 | atmark | Thanks for your help | |
| 23:57:45 | opendevreview | sean mooney proposed openstack/nova master: remove untils.spawn_n https://review.opendev.org/c/openstack/nova/+/892722 | |
| #openstack-nova - 2023-08-26 | |||
| 01:54:18 | opendevreview | sean mooney proposed openstack/nova master: Handle inactive port binding in _update_port_binding_for_instance https://review.opendev.org/c/openstack/nova/+/653506 | |
| 03:26:26 | opendevreview | OpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata https://review.opendev.org/c/openstack/nova/+/891648 | |
| 03:49:03 | opendevreview | melanie witt proposed openstack/nova master: block_device: Add encryption attributes to swap disks https://review.opendev.org/c/openstack/nova/+/884312 | |
| 12:44:16 | opendevreview | Merged openstack/nova stable/zed: Don't provide MTU value in metadata service if DHCP is enabled https://review.opendev.org/c/openstack/nova/+/877500 | |
| #openstack-nova - 2023-08-28 | |||
| 04:17:37 | opendevreview | OpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata https://review.opendev.org/c/openstack/nova/+/891648 | |
| 07:36:29 | dvo-plv | sean-k-mooney, Hello. Are you here ? | |
| 09:16:28 | gokhani | hello folks, ı am trying to migrate from vmware to openstack and my vm stuck at booting from harddisk. I converted from vmdk to raw. I followed https://superuser.openinfra.dev/articles/how-to-migrate-from-vmware-and-hyper-v-to-openstack/ guide. my fstab file on my vm is https://paste.openstack.org/show/bqO5mJ9gCpyHEEBgvMjZ/. what can be reason of stucking at boot from harddisk ? | |
| 09:16:28 | gokhani | hello folks, ı am trying to migrate from vmware to openstack and my vm stuck at booting from harddisk. I converted from vmdk to raw. I followed https://superuser.openinfra.dev/articles/how-to-migrate-from-vmware-and-hyper-v-to-openstack/ guide. my fstab file on my vm is https://paste.openstack.org/show/bqO5mJ9gCpyHEEBgvMjZ/. what can be reason of stucking at boot from harddisk ? | |
| 09:16:54 | gokhani | vm is ubuntu 20.04 and cloudinit package is installed | |
| 10:32:41 | bauzas | good morning Nova | |
| 10:32:50 | sean-k-mooney | o/ | |
| 10:33:35 | sean-k-mooney | i would say a lot has changed since you were last here but until last week the ci has been mostly unable to merge thigns so... | |
| 10:34:32 | bauzas | argh | |
| 10:34:46 | sean-k-mooney | gmann: dansmith and other have fortunetly managed to improve that of late but the reality is very little had merge in the early part of your pto | |
| 10:34:52 | bauzas | I haven't yet looked at gerrit | |
| 10:35:10 | bauzas | but this afternoon, I'll do | |
| 10:35:26 | bauzas | this morning, paperwork + email scrubbing :( | |
| 10:35:53 | sean-k-mooney | i feel like configing that to morning is probably ambious | |
| 10:39:06 | bauzas | tbh, I need way more coffee before looking at the gate :) | |
| 10:41:17 | sean-k-mooney | its relitivly fine at the moment | |
| 10:41:44 | sean-k-mooney | bar the normaly volume detach issues which i think will be a ptg topic | |
| 11:34:39 | gibi | bauzas: o/ welcome back. we did not pass the bug triage baton around during your PTO, I was lazy to find a candidate during the meeting. Otherwise the meetings were held and producitve as much as summer period allows. | |
| 11:34:55 | bauzas | ++ thanks for the offer | |
| 12:42:48 | dvo-plv | sean-k-mooney, What do you think regarding multi nic support in the our patch by adding additional configuration via config file or even better using binding profile | |
| 12:43:11 | sean-k-mooney | hard no on config file | |
| 12:43:32 | sean-k-mooney | or user specifying data in the binding profile | |
| 12:44:00 | sean-k-mooney | well it depends on where the config file would be used, whats in it and how that is confiugred | |
| 12:44:12 | sean-k-mooney | but i dont think that likely to work. | |
| 12:44:18 | dvo-plv | get configuration here to generate correct socket name https://review.opendev.org/c/openstack/neutron/+/869510/13/neutron/plugins/ml2/drivers/openvswitch/mech_driver/mech_openvswitch.py#221 | |
| 12:44:30 | dvo-plv | and here to create correct vf number https://review.opendev.org/c/openstack/os-vif/+/859574/8/vif_plug_ovs/ovs.py#349 | |
| 12:44:31 | sean-k-mooney | note that binding_profile is expclivily for nova to pass data to the network backend | |
| 12:45:29 | sean-k-mooney | as in you woudl have someihng in the neurton l2 agents config file | |
| 12:45:44 | sean-k-mooney | which gets pass as part fo agent['configurations'] | |
| 12:45:58 | sean-k-mooney | that you need use to calulate the vf number | |
| 12:47:45 | sean-k-mooney | i dont really think that is the correct approch honestly | |
| 12:49:00 | dvo-plv | but we need to correlate somehow formula for socket and vf number calculating | |
| 12:49:59 | sean-k-mooney | how i think this shoudl work is likely nova shoudl gather the info required adn store it in the binidng_profile and then neutron shoudl use that to calualte the path | |
| 12:50:25 | dvo-plv | we use simple number for vf and socket name stdvio+vf number. Mellanox uses something like pf0vf0 formulation | |
| 12:50:49 | dvo-plv | sorry, what info required, where what entity we should parse to get this info | |
| 12:51:35 | sean-k-mooney | the vf number is only meainifn if you know the parent PF pci device | |
| 12:52:53 | sean-k-mooney | can you express what exactly is required to match | |