| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2024-10-15 | |||
| 16:19:08 | elodilles | i've proposed some patches that removes periodics from unmaintained/* | |
| 16:19:18 | bauzas | but still the question remains : should we care of the state of unmaintained branches ? | |
| 16:19:34 | bauzas | ack | |
| 16:19:44 | bauzas | moving on then | |
| 16:19:46 | elodilles | so yepp, it's not a general concern | |
| 16:19:47 | bauzas | #topic Release Planning | |
| 16:19:54 | bauzas | #link https://releases.openstack.org/epoxy/schedule.html | |
| 16:20:05 | bauzas | as a reminder, we'll discuss the epoxy nova deadlines next week | |
| 16:20:17 | bauzas | nothing further to say | |
| 16:20:22 | bauzas | #topic Review priorities | |
| 16:20:27 | bauzas | #link https://etherpad.opendev.org/p/nova-2025.1-status | |
| 16:20:42 | bauzas | I did some cleanup in the etherpad and added the recent approved blueprints | |
| 16:20:53 | bauzas | a round of reviews is strongly encouraged | |
| 16:21:38 | bauzas | #topic PTG planning | |
| 16:21:45 | bauzas | #info as a reminder, we'll meet (virtually) at the PTG on Oct 21-25 2024 | |
| 16:21:52 | bauzas | ... which is next week :-) | |
| 16:21:58 | bauzas | # info Please register yourself to the virtual PTG | |
| 16:22:04 | bauzas | #info Please register yourself to the virtual PTG | |
| 16:22:10 | bauzas | #link https://etherpad.opendev.org/p/nova-2025.1-ptg | |
| 16:22:19 | bauzas | feel free to add more topics in the above etherpad | |
| 16:24:55 | bauzas | also, we'll have a x-p session between Horizon and Nova | |
| 16:25:03 | bauzas | feel free to add items for that session | |
| 16:25:12 | bauzas | which will happen on Wed 1600UTC | |
| 16:25:28 | tkajinam | iirc we have a few slots in tc PTG to discuss eventlet removal, so we may want to decide the plan for it and nova specific one. | |
| 16:25:52 | tkajinam | my current preference is to have global discussion first and then nova one but I'm open for different opinions | |
| 16:25:52 | bauzas | yeah I heard it | |
| 16:25:58 | bauzas | when would those topics happen ? | |
| 16:26:02 | bauzas | ditto | |
| 16:26:28 | tkajinam | I think we have a slot on Monday and the other on Wednesday | |
| 16:26:29 | bauzas | I hope the eventlet talks would happen on Monday or Tuesday to leave other projects time for discussing that again | |
| 16:26:30 | sean-k-mooney | there is a sperate etherpad for an overall session | |
| 16:26:36 | tkajinam | https://etherpad.opendev.org/p/oct2024-ptg-os-tc | |
| 16:27:15 | tkajinam | ok it seems they canceled the slots on Wednesday | |
| 16:27:16 | sean-k-mooney | not that oen this https://etherpad.opendev.org/p/oct2024-ptg-eventlet-removal | |
| 16:27:26 | tkajinam | ah, ok | |
| 16:27:42 | bauzas | okay, I'll mention that etherpad in our own Nova etherpad | |
| 16:27:47 | sean-k-mooney | but yes curerntly a monday and wednesday slot but no adjenda | |
| 16:27:54 | bauzas | I need to write the agenda, I'll refer to that session | |
| 16:28:36 | tkajinam | sean-k-mooney, ok. thanks for the info. | |
| 16:30:30 | bauzas | cool, ditto | |
| 16:30:33 | bauzas | moving on then | |
| 16:30:49 | bauzas | there will also be an i18n discussion I'll attend | |
| 16:31:07 | bauzas | I'll refer to it too with possibly follow-up discussions during nova sessions | |
| 16:31:36 | bauzas | #topic Stable Branches | |
| 16:31:42 | bauzas | elodilles: floor is yours | |
| 16:31:45 | elodilles | ack | |
| 16:31:49 | elodilles | #info stable/202*.* gates seem to be OK | |
| 16:32:03 | elodilles | #info final 2023.1 Antelope nova release before the branch transitions to 'unmaintained': https://review.opendev.org/c/openstack/releases/+/932406 | |
| 16:32:08 | elodilles | does anyone have any bug fix that should be part of the final antelope release? | |
| 16:32:19 | elodilles | open & merged patches on stable/2023.1: https://etherpad.opendev.org/p/nova-stable-2023.1-eom | |
| 16:32:58 | elodilles | there are some patches that wait for a 2nd +2, but otherwise i don't know if anything would be important | |
| 16:33:13 | elodilles | and that's all from me | |
| 16:33:38 | tkajinam | maybe we should check if all follow-up fixes for image inspector have been backported | |
| 16:34:27 | elodilles | tkajinam: good point. afair, we had quite many of that backported, | |
| 16:34:44 | elodilles | though i don't know if that were all | |
| 16:35:05 | bauzas | well, there are a bunch of them | |
| 16:35:19 | sean-k-mooney | i think for the issues that are already fix the answer is yes | |
| 16:35:31 | bauzas | if you speak of the CVE fixes, yeah | |
| 16:35:41 | tkajinam | ah, ok | |
| 16:35:51 | sean-k-mooney | we also backported the fix for the aws and iso regressions on stable | |
| 16:35:52 | elodilles | https://review.opendev.org/q/topic:%22format-inspector%22+branch:stable/2023.1 | |
| 16:35:57 | bauzas | if that's about the 'improvements' (like raw means raw), then I'm unsure | |
| 16:36:17 | elodilles | these are the ones that i'm aware of, at least (plus the bug fixes) | |
| 16:36:45 | bauzas | those are the CVE fixes | |
| 16:37:17 | tkajinam | My thought was mostly about regression fixes, not improvements. but I think we are ok about the known issues. | |
| 16:37:49 | elodilles | ACK | |
| 16:38:22 | bauzas | yeah so I checked | |
| 16:38:37 | bauzas | https://review.opendev.org/c/openstack/nova/+/926144 is more a signal patch, like 'dude, you shouldn't be doing that' | |
| 16:39:35 | bauzas | and this was following https://review.opendev.org/c/openstack/nova/+/924866 which was backported | |
| 16:39:56 | tkajinam | lgtm | |
| 16:40:31 | bauzas | we recently merged https://review.opendev.org/c/openstack/nova/+/930754 but I don't see any interest in backporting it down | |
| 16:40:51 | bauzas | and there is a dep on glance | |
| 16:41:08 | bauzas | so I think we can't use the glance safebelt | |
| 16:41:17 | bauzas | hence the non-backport | |
| 16:41:30 | bauzas | so I guess we're cool | |
| 16:42:02 | bauzas | moving on ten | |
| 16:42:06 | bauzas | then* | |
| 16:42:09 | elodilles | ++ | |
| 16:42:23 | bauzas | #topic vmwareapi 3rd-party CI efforts Highlights | |
| 16:42:31 | bauzas | fwiesel: anything to mention ? | |
| 16:42:43 | fwiesel | No, nothing from my side. | |
| 16:42:48 | fwiesel | Sorry for the lack of progress. | |
| 16:43:29 | bauzas | no worries, we're all busy | |
| 16:43:35 | bauzas | particularly me. | |
| 16:43:51 | bauzas | #topic Open discussion | |
| 16:43:57 | bauzas | (tkajinam): Removing db migration tool from nova_placement to placement: https://review.opendev.org/c/openstack/placement/+/932324 | |
| 16:43:59 | bauzas | shoot | |
| 16:44:28 | tkajinam | I discussed this already with sean-k-mooney and gibi but I think it may make sense to bring the topic here to get any additional feedback | |
| 16:45:10 | tkajinam | placement repository has carried the migration tool which pulls placement db from nova db. This was required in upgrade from Stein to Train and I'm wondering if we can directly drop it now because I don't think anyone may use it from master nowadays | |
| 16:45:45 | bauzas | this is old code | |
| 16:45:55 | bauzas | I don't see any controversy in removing it | |
| 16:46:09 | tkajinam | :-) | |
| 16:46:15 | bauzas | and people wanting to use it could just pip install in a venv an older release of placement | |
| 16:46:23 | bauzas | and use that tool | |
| 16:46:31 | gibi | yeah, drop it. | |
| 16:46:50 | tkajinam | A quick question I still have is whether we should keep the upgrade note which is almost empty https://8f5091142d0d93e54bb3-66f76d6fb4c84b410723fddf17d0dbe7.ssl.cf5.rackcdn.com/932324/2/check/openstack-tox-docs/93314e0/docs/admin/upgrade-notes.html or keep it (and the administrator guide section) as a placeholder | |
| 16:47:03 | opendevreview | Amit Uniyal proposed openstack/nova master: Update Nova bdm with updated swap info https://review.opendev.org/c/openstack/nova/+/929858 | |
| 16:47:04 | bauzas | from a procedural perspective, I litterally see zero paperwork to fill | |
| 16:48:20 | bauzas | tkajinam: keep that | |
| 16:48:26 | gibi | tkajinam: that upgrade-notes seem still relevant | |