| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-10-02 | |||
| 15:25:27 | sean-k-mooney | if you dont install it then it does not run | |
| 15:25:32 | sean-k-mooney | if you do its just --no-verify | |
| 15:25:40 | sean-k-mooney | but we can updated it to be more clear | |
| 15:25:47 | melwitt | you can also just do -n | |
| 15:26:06 | bauzas | I think I can and shall update that docv | |
| 15:26:33 | melwitt | and the doc was clear enough to me, fwiw. i.e. I understood pre-commit doesn't happen unless you install the pre-commit package | |
| 15:26:34 | sean-k-mooney | melwitt: oh good to know | |
| 15:26:48 | sean-k-mooney | yep "This must be enabled locally to function:" | |
| 15:26:53 | sean-k-mooney | was ment to capture that in the doc | |
| 15:27:37 | bauzas | then I'll remove my vote on the pre-commit additions change | |
| 15:27:46 | melwitt | (I'm not objecting to improving the doc btw, just saying at least to me I've used the doc and it made sense for me) | |
| 15:28:18 | sean-k-mooney | bauzas: for what its worht i have other related but seperate changes | |
| 15:28:54 | sean-k-mooney | https://review.opendev.org/c/openstack/nova/+/896987 | |
| 15:32:45 | sean-k-mooney | i was going to add a "tech-debt reduction and code modernization" topic to the ptg (items for this seession would by hyperv and vmware driver removal. black and pyupgrade) | |
| 15:34:13 | sean-k-mooney | we have blueprints filed for at least 3 of those. https://blueprints.launchpad.net/nova/+spec/remove-hyperv-driver https://blueprints.launchpad.net/nova/+spec/pyupgrade and https://blueprints.launchpad.net/nova/+spec/remove-vmware-support | |
| 15:34:47 | sean-k-mooney | i dont know if we have or need one for automated formating but we can at least have the conversation at the ptg | |
| 15:35:00 | bauzas | sean-k-mooney: I'd be in favor of more fine-scoped topic names | |
| 15:35:20 | stephenfin | bauzas: Thanks. Good to hear that confusion is cleared up (y) | |
| 15:35:22 | dansmith | I'm prepared to die on black hill | |
| 15:35:38 | bauzas | at least for clarifying the intent and clearly timekeep on subjects | |
| 15:36:23 | bauzas | one topic I could add could be "volume attachment improvements" but that's exactly kind of the same vague bucket :) | |
| 15:36:38 | sean-k-mooney | i wanted to group related topics | |
| 15:36:43 | sean-k-mooney | hence the sub items | |
| 15:37:08 | bauzas | sean-k-mooney: if you don't mind, stick with items per each, and I'll just make sure we loop thru them as a group | |
| 15:37:12 | stephenfin | dansmith: You'll be happy to hear sean-k-mooney also does not like the spreading of arguments across multiple lines 0:) Apparently there's some way to change that but I didn't look into it yet | |
| 15:37:16 | sean-k-mooney | those 3 are all tech debth reduction and as an fyi i have fully implemted pyupgrade adn vmware removal | |
| 15:38:04 | bauzas | (fwiw, the vmware one seems to me quite non-controversial :) ) | |
| 15:38:12 | sean-k-mooney | i have one open question on it | |
| 15:38:25 | sean-k-mooney | baiscally i intentionl didn not make any api changes but i proably should | |
| 15:38:32 | bauzas | if you stopped a dead corner, then sure :) | |
| 15:38:40 | sean-k-mooney | i.e. i did not remove the mks console server or any of the extra specs validation ectra | |
| 15:38:43 | bauzas | spotted* | |
| 15:38:53 | sean-k-mooney | but want to hear how people want that to be done | |
| 15:38:55 | bauzas | yeah, I thought it was API-related | |
| 15:39:05 | sean-k-mooney | the currnt patch is not api related | |
| 15:39:15 | bauzas | we have a solid experience on API stability while we remove backends | |
| 15:39:23 | sean-k-mooney | just the virt driver and remvoe teh virt dirver spcifric cofnig options and docs. | |
| 15:39:48 | sean-k-mooney | i belive gman has also already done hyperv and has the same open | |
| 15:39:58 | sean-k-mooney | i.e. waht to do with hyperv specific api aspect | |
| 15:40:08 | sean-k-mooney | so i wanted to group does disucssions togetehr | |
| 15:40:13 | sean-k-mooney | since hte approch should likely be the same | |
| 15:41:05 | bauzas | sounds a good idea to me | |
| 15:41:17 | bauzas | thanks for catching it | |
| 15:41:34 | sean-k-mooney | do we have the ptg etherpad yet | |
| 15:42:23 | bauzas | yep | |
| 15:42:33 | bauzas | oh but you weren't in the last meeting, sec | |
| 15:42:47 | sean-k-mooney | ya still catching up form PTO | |
| 15:42:54 | bauzas | np | |
| 15:43:25 | bauzas | https://etherpad.opendev.org/p/nova-caracal-ptg | |
| 15:43:42 | bauzas | (didn't made any huge effort for the naming) | |
| 15:44:23 | sean-k-mooney | cool ill add something to that then and you cna feel frre to rearragne things | |
| 15:45:09 | bauzas | cool | |
| 15:53:24 | opendevreview | Sylvain Bauza proposed openstack/nova master: doc: clarify that pre-commit is optional https://review.opendev.org/c/openstack/nova/+/897057 | |
| 16:08:16 | stephenfin | sean-k-mooney: I wonder if we could start setting and exposing ACPI index for network devices, as a consistent identifier that will be respected (unless PCI device addresses) https://libvirt.org/formatdomain.html#network-interfaces | |
| 16:08:44 | sean-k-mooney | hum let me read | |
| 16:08:48 | sean-k-mooney | but maybe | |
| 16:09:19 | sean-k-mooney | """Since 7.3.0, one can set the ACPI index against network interfaces. With some operating systems (eg Linux with systemd), the ACPI index is used to provide network interface device naming, that is stable across changes in PCI addresses assigned to the device. This value is required to be unique across all devices and be between 1 and (16*1024-1).""" | |
| 16:09:33 | sean-k-mooney | interesting so ya maybe | |
| 16:10:28 | sean-k-mooney | stephenfin: of the top of my head i dont see why not | |
| 16:11:01 | sean-k-mooney | well hum | |
| 16:11:06 | sean-k-mooney | there might be some issues with that | |
| 16:11:21 | sean-k-mooney | so the problem iw going to be how to corralate it with the port | |
| 16:11:31 | sean-k-mooney | so we willl likely need to store it in the virtural interfaces table | |
| 16:12:10 | sean-k-mooney | so that its accesable to the api or store it in the binding_profile on the neutorn port | |
| 16:52:03 | sean-k-mooney | ok so testing the acpi index theory <acpi index="4"/> is accepted in the xml | |
| 16:52:40 | sean-k-mooney | and the interface name becomes eno4 | |
| 16:52:44 | sean-k-mooney | so that is a good sigh | |
| 16:53:23 | sean-k-mooney | sean@upstream-devstack:~$ cat /sys/class/net/eno4/device/acpi_index | |
| 16:53:25 | sean-k-mooney | 4 | |
| 16:53:35 | sean-k-mooney | stephenfin: ^ so ya that is trivially discoverable | |
| 16:53:52 | stephenfin | \o/ | |
| 16:53:54 | stephenfin | noice | |
| 16:53:59 | sean-k-mooney | so if we were to add that to the metadata that would work | |
| 16:54:11 | sean-k-mooney | im going to make it 42 just to be sure it actully is working the way i think | |
| 16:55:26 | sean-k-mooney | sean@upstream-devstack:~$ cat /sys/class/net/eno42/device/acpi_index | |
| 16:55:28 | sean-k-mooney | 42 | |
| 16:55:47 | sean-k-mooney | yep so it will result in a stable device name as well as the docs suggest | |
| 18:22:05 | opendevreview | Dan Smith proposed openstack/nova master: Sanity check that new hosts have no instances https://review.opendev.org/c/openstack/nova/+/897076 | |
| 19:35:14 | opendevreview | Dan Smith proposed openstack/nova master: Sanity check that new hosts have no instances https://review.opendev.org/c/openstack/nova/+/897076 | |
| 20:38:09 | opendevreview | sean mooney proposed openstack/nova master: remove deprecated vmware virt driver https://review.opendev.org/c/openstack/nova/+/897017 | |
| 22:04:26 | opendevreview | sean mooney proposed openstack/nova master: fix sphinx-lint issues in releasenotes https://review.opendev.org/c/openstack/nova/+/897087 | |
| 22:04:27 | opendevreview | sean mooney proposed openstack/nova master: fix sphinx-lint errors in docs and add ci https://review.opendev.org/c/openstack/nova/+/897089 | |
| 22:04:27 | opendevreview | sean mooney proposed openstack/nova master: fix sphinx-lint issues in api guide https://review.opendev.org/c/openstack/nova/+/897088 | |
| 23:54:20 | opendevreview | sean mooney proposed openstack/nova master: [codespell] start fixing all the typos https://review.opendev.org/c/openstack/nova/+/897092 | |
| #openstack-nova - 2023-10-03 | |||
| 00:33:08 | opendevreview | sean mooney proposed openstack/nova master: [codespell] apply codespell to the releasenotes https://review.opendev.org/c/openstack/nova/+/897095 | |
| 00:33:08 | opendevreview | sean mooney proposed openstack/nova master: [codespell] fix typos in api-ref https://review.opendev.org/c/openstack/nova/+/897094 | |
| 00:33:09 | opendevreview | sean mooney proposed openstack/nova master: [codespell] doc,devstack and gate typos https://review.opendev.org/c/openstack/nova/+/897096 | |
| 07:36:49 | bauzas | cores, could you please quickly merge https://review.opendev.org/c/openstack/nova-specs/+/895815 before our Bobcat GA ? | |
| 08:12:45 | gibi | bauzas: Is it better to mark the ironic shard implemented with a note that it is reverted? Do we expect that shard spec will be reproposed in C? | |
| 08:13:06 | bauzas | gibi: have you seen the next change in the series ? | |
| 08:13:59 | bauzas | https://review.opendev.org/c/openstack/nova-specs/+/896679/1/specs/2023.2/implemented/ironic-shards.rst | |
| 08:14:11 | gibi | bauzas: I saw the note yes | |
| 08:14:32 | gibi | my question is will there be a new spec in C to merge the shard implementation again? | |
| 08:14:39 | bauzas | gibi: I hope so | |
| 08:14:50 | gibi | then we should not put the current shard spec to implemented | |
| 08:15:03 | bauzas | johnthetubaguy: do you know if you could be able to create a new spec in Caracal for ironic-shards ? | |
| 08:15:36 | gibi | we should only put the shard spec to implemented that was implemented and *released* | |
| 08:16:46 | bauzas | okay, then let me change the Launchpad blueprint | |
| 08:23:23 | opendevreview | Sylvain Bauza proposed openstack/nova-specs master: Move Bobcat implemented specs https://review.opendev.org/c/openstack/nova-specs/+/895815 | |
| 08:23:24 | opendevreview | Sylvain Bauza proposed openstack/nova-specs master: explain why ironic-shards was reverted in the spec https://review.opendev.org/c/openstack/nova-specs/+/896679 | |