| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-10-14 | |||
| 16:17:05 | Uggla | yep 15:00 --> 18:00 CET | |
| 16:17:05 | gibi | ack, so 3 hours for 4 days | |
| 16:17:11 | gibi | works forme | |
| 16:17:15 | sean-k-mooney | based on https://ptg.opendev.org/ptg.html | |
| 16:17:34 | Uggla | yep as usual, starting (Tue) | |
| 16:17:52 | sean-k-mooney | well you need to adjust that actully | |
| 16:18:03 | sean-k-mooney | it curernly show all 5 hours not just the fine 3 in the slot | |
| 16:20:01 | Uggla | sean-k-mooney yes I reserved a bit larger at the first shot | |
| 16:21:29 | bauzas | at least the slots are booked | |
| 16:21:39 | Uggla | yep :) | |
| 16:21:53 | bauzas | if we need to continue to discuss, we can book another slot... or we can unbook another one :) | |
| 16:22:28 | Uggla | I'will arrange that in the coming days | |
| 16:24:57 | Uggla | ok moving on | |
| 16:25:03 | Uggla | #topic OpenAPI | |
| 16:25:13 | Uggla | #link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned | |
| 16:25:20 | Uggla | #info still 28 remaining atm. | |
| 16:25:43 | Uggla | #topic Stable Branches | |
| 16:26:12 | elodilles | thanks o/ | |
| 16:26:20 | elodilles | #info stable branches (stable/2025.* and stable/2024.*) seem to be in OK state | |
| 16:26:26 | elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | |
| 16:26:40 | elodilles | #info 2024.1 Caracal (stable/2024.1) moves to Unmaintained at the end of next week - final stable Caracal release should be proposed and merged ASAP | |
| 16:26:56 | elodilles | #info elod will propose the release patches tomorrow | |
| 16:27:06 | elodilles | and a question: | |
| 16:27:13 | elodilles | does anyone have any important patch to land to stable/2024.1 before we release? (list of open patches: https://etherpad.opendev.org/p/nova-stable-caracal-eom ) | |
| 16:27:30 | Uggla | - | |
| 16:27:36 | gibi | - | |
| 16:27:40 | elodilles | thanks for the reviews so far, btw! | |
| 16:28:37 | elodilles | Uggla: gibi: ACK, then i'll propose the review patches right away (flamingo, epoxy, dalmatian, caracal) | |
| 16:28:51 | elodilles | (though caracal is the most important for now o:)) | |
| 16:29:07 | elodilles | and that's all from me about stable for now | |
| 16:29:10 | gibi | poor caracal, I will miss it | |
| 16:29:15 | elodilles | :] | |
| 16:29:15 | Uggla | rip caracal | |
| 16:29:37 | elodilles | you don't have to dig it, it won't go to EOL, just Unmaintained o:) | |
| 16:29:55 | elodilles | so people can still backport bug fixes to unmaintained/2024.1 ;) | |
| 16:30:01 | sean-k-mooney | elodilles: as an aside there is only ment to be one unmtianed slurp release at a time | |
| 16:30:14 | gibi | yeah basicaly kicked out to the streets nice elodilles :) | |
| 16:30:23 | sean-k-mooney | elodilles: im fine with not enforce that as long as you still care about the rest | |
| 16:30:49 | elodilles | sean-k-mooney: in case there is no volunteer to keep open unmaintained/2023.1 | |
| 16:30:49 | sean-k-mooney | but in thory 2023.1 is ment to go eol when 2024.1 moves to unmainted | |
| 16:31:09 | gmaan | antelope is still unmaintained, any plan to move to EOL before caracal moving to unmaintained ? | |
| 16:31:18 | gmaan | sean-k-mooney: yeah | |
| 16:31:38 | sean-k-mooney | so i think elodilles is still interested in keeping it alive | |
| 16:31:44 | gmaan | because based on that we need to see if we can continue running grenade job on unmaintained caracal | |
| 16:31:46 | sean-k-mooney | so as long as the gates are green that is fine | |
| 16:32:10 | sean-k-mooney | well grenade is not ment to test upgrades form unmaintained | |
| 16:32:46 | gmaan | as long as it run green then no harm to test it but if previous base relaese is not maintained or broken then yes we can remove | |
| 16:32:48 | elodilles | sean-k-mooney: yes, i want to step up as a volunteer to keep it open | |
| 16:33:04 | sean-k-mooney | or rahter the oldest stable is not ment to test upgrading form unmaintaiend but you coudl run it your self i guess | |
| 16:34:53 | elodilles | sean-k-mooney: yes, the oldest stable is officially not supported, so can be disabled, though if it works then i'd rather ask for keeping it, and also help maintaining it as long as it possible | |
| 16:35:24 | sean-k-mooney | well the counter point to that | |
| 16:35:38 | sean-k-mooney | is we want to evntually be able to remove old disto images and mirrors | |
| 16:36:11 | sean-k-mooney | so im not objecting to keepign it for a release or two bvut we shoudl nto keep it indefinetly | |
| 16:36:18 | elodilles | of course if it blocks the gate then it can be removed (though i'd rather set it as non-voting if not completely unfixable or broken forever) | |
| 16:36:49 | elodilles | sean-k-mooney: +1 | |
| 16:36:50 | sean-k-mooney | 2023.1 is using ubuntu 22.04 which is supprot until 2027 | |
| 16:36:58 | sean-k-mooney | that kind of the upper bound on testing that IMO | |
| 16:37:29 | sean-k-mooney | so it has 18months+ runway i think | |
| 16:37:53 | sean-k-mooney | anyway we can likely move on since its not being EOLd this cycle but we could talk about it more at the ptg if poepel wanted | |
| 16:38:40 | elodilles | yepp | |
| 16:39:04 | gmaan | I am only concern about the running grenade skip job on Epoxy which will be from caracal to Epoxy and if we can continue running it it will be great | |
| 16:39:25 | gmaan | and it seems like we will do that until it is broken so I am good here | |
| 16:39:41 | elodilles | gmaan: ++ | |
| 16:40:28 | Uggla | ok so moving on. | |
| 16:40:36 | Uggla | thx elodilles | |
| 16:40:42 | Uggla | #topic vmwareapi 3rd-party CI efforts Highlights | |
| 16:40:50 | fwiesel | No updates from my side | |
| 16:41:03 | Uggla | fwiesel thanks | |
| 16:41:15 | Uggla | #topic Gibi's news about eventlet removal | |
| 16:41:18 | gibi | o/ | |
| 16:41:37 | Uggla | gibi anything on your side ? | |
| 16:42:06 | gibi | then first couple of patches are reviewable on https://review.opendev.org/c/openstack/nova/+/956089/ | |
| 16:42:16 | gibi | and the ptg etherpad as the longer term plan | |
| 16:42:53 | gibi | Also please report any strange test failures from nova-next, since last week we run conduct there in threading mode as well | |
| 16:43:08 | gibi | (top of scheduler api, and metadata) | |
| 16:43:13 | gibi | that is ti | |
| 16:43:15 | gibi | it | |
| 16:43:18 | sean-k-mooney | hum on the rbd thread pool i guess everually we will wnat to use the asinc api instead | |
| 16:43:30 | sean-k-mooney | so we can actully pass timeouts ectra | |
| 16:44:17 | sean-k-mooney | but i guess the intial plan is to just not swapn it on a tread pool at all which i guess is ok | |
| 16:44:19 | gibi | sean-k-mooney: this will not prevent doing that later when we actaully go and translate the nova-compute | |
| 16:44:44 | sean-k-mooney | ack ya just chekcign that still the medium term plan | |
| 16:44:46 | gibi | the patches on that series are for unblocking unit testing | |
| 16:44:47 | opendevreview | Merged openstack/nova master: Move cleanup of vTPM secret from driver to compute https://review.opendev.org/c/openstack/nova/+/962007 | |
| 16:45:17 | sean-k-mooney | ah ok | |
| 16:47:03 | gibi | I think we can move on | |
| 16:47:11 | Uggla | thx gibi | |
| 16:47:20 | Uggla | #topic Open discussion | |
| 16:47:45 | Uggla | Just a reminder for the poll: Pool for the new schedule of upstream meeting: https://framadate.org/ao12zK6wR3K3nfbF | |
| 16:48:10 | Uggla | Anything you want to discuss ? | |
| 16:48:25 | nicolairuckel | I worked on a patch to preserve the NVRAM after reboots that got mentioned a few weeks ago. | |
| 16:48:39 | nicolairuckel | I'm not sure if that's the correct place to talk about that. | |
| 16:48:47 | Uggla | yes | |
| 16:48:54 | nicolairuckel | https://review.opendev.org/c/openstack/nova/+/959682 | |
| 16:49:29 | sean-k-mooney | looks like it needs a rebase | |
| 16:49:59 | nicolairuckel | The only caveat is that at the moment you have to set the permissions for the NVRAM file manually. I wasn't able to figure out if there's a way to change the permissions through libvirt. | |
| 16:50:08 | nicolairuckel | sean-k-mooney, I'll do that! | |
| 16:50:35 | sean-k-mooney | why do you need to do that? | |
| 16:51:27 | nicolairuckel | If you don't add read permissions, there will be a permissions error on a reboot and it won't be preserved. | |
| 16:52:04 | nicolairuckel | The libvirt people told me that the permissions are like than intentionally. It's just a bit weird to me that the disk file has read permissions. | |