16:03:01 <bauzas> #startmeeting nova
16:03:01 <opendevmeet> Meeting started Tue Oct 15 16:03:01 2024 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:01 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:01 <opendevmeet> The meeting name has been set to 'nova'
16:03:06 <tkajinam> :-)
16:03:13 <bauzas> hey folks, this time I'm on the right channel :)
16:03:18 <tkajinam> o/
16:03:20 <elodilles> o/
16:03:28 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:03:37 <bauzas> I was wondering why I was getting crickets :)
16:04:09 <bauzas> so, who's around ?
16:04:26 <Uggla> o/
16:05:16 <bauzas> okay, we can softly start
16:05:23 <bauzas> #topic Bugs (stuck/critical)
16:05:29 <bauzas> #info One Critical bug
16:05:34 <bauzas> #link https://bugs.launchpad.net/nova/+bug/2083518
16:05:40 <fwiesel> o/
16:05:40 <bauzas> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:05:58 <bauzas> I'm considering to change the priority of the critical bug to High
16:06:01 <tkajinam> I downgraded the importance of it as I learned that distutils may be available via setuptools (IIUC)
16:06:20 <bauzas> oh thanks, all good then
16:06:24 <tkajinam> However as it is deprecated we definitely need an alternative. As recent python more actively drops things
16:06:45 <bauzas> we'll have py312 jobs that should see that
16:06:49 <tkajinam> I started adding something to oslo.utils to replace distutils now and may ping you once that becomes available
16:06:50 <tkajinam> yeah
16:07:09 <tkajinam> the tricky thing is that it may not appear as long as we use virtualenv
16:07:17 <tkajinam> but it appears if you do python -m venv
16:07:20 <tkajinam> iiuc
16:07:23 <bauzas> oh, okay, so tox wouldn't see it
16:07:32 <tkajinam> yup
16:07:35 <bauzas> and our jobs too, hence why this is not failing in the jobs
16:07:53 <bauzas> because I guess the tox embedded python version has distutils ?
16:08:06 <bauzas> s/tox/venv
16:08:10 <sean-k-mooney> distutils is installable
16:08:15 <sean-k-mooney> on py312
16:08:18 <sean-k-mooney> as a sperate package
16:08:20 <tkajinam> no but it installs setuptools which brings distutils and pkg_resources
16:08:37 <tkajinam> but these were kicked out from core python in 3.12
16:08:40 <sean-k-mooney> but i belive that is not the case on 3.13
16:09:07 <tkajinam> +1
16:10:13 <bauzas> so we need to remove that dep from our code
16:10:24 <bauzas> I'm just sad we don't have any canary in the coal mine
16:10:24 <sean-k-mooney> https://packages.ubuntu.com/noble/python3-distutils-extra
16:10:31 <sean-k-mooney> yes eventualy
16:10:42 <sean-k-mooney> sooner rather then later which is why tkajinam started on it
16:10:59 <tkajinam> yes :-)
16:11:10 <sean-k-mooney> our acutal deps on it are somewhat limisted
16:11:47 <sean-k-mooney> but that is not the same as 0
16:12:12 <bauzas> okay, I think this is important to keep that bug report in mind
16:13:18 <bauzas> I just added the bug report in the 2025.1 status etherpad
16:13:31 <bauzas> I guess we can move on
16:13:44 <bauzas> unless someone wants to discuss about another bug report
16:14:18 <bauzas> okay, moving on
16:14:25 <bauzas> #topic Gate status
16:14:32 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:14:37 <bauzas> #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:14:42 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:14:48 <bauzas> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:14:53 <bauzas> #info Please try to provide meaningful comment when you recheck
16:15:06 <bauzas> the periodics were fine, that's cool
16:16:01 <bauzas> except placement in stable/yoga but that should be EOM, right?
16:16:19 <bauzas> elodilles: ^
16:16:53 <elodilles> yepp
16:16:55 <elodilles> hmmm
16:17:21 <elodilles> i'll add it to my TODO to check what's going on
16:17:26 <bauzas> thanks
16:17:48 <bauzas> but is there any reason why we keep CI checking that stable branch ?
16:18:16 <elodilles> you mean the unmaintained?
16:18:30 <bauzas> nevermind, my mind blipped
16:18:52 <bauzas> unmaintained != EOL
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 <bauzas> yeah I heard it
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: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
16:48:35 <bauzas> running a status check pre-flight is important
16:48:50 <tkajinam> yes
16:49:10 <bauzas> anyway, I think we're done with that item, we'll review it
16:49:20 <tkajinam> ok then https://review.opendev.org/c/openstack/placement/+/932324 is ready. I had to wipe previous +2 to fix doc issues
16:49:22 <tkajinam> thanks !
16:49:23 <bauzas> tkajinam: feel free to add your patch into the status etherpad
16:49:42 <tkajinam> will do
16:49:48 <bauzas> ++
16:50:06 <bauzas> another item, less easy to answer
16:50:08 <bauzas> (tkajinam): Can we remove (or at least deprecate) WIndows OS support ?
16:50:21 <bauzas> any good reason for doing it ?
16:50:55 <bauzas> oh, the hypervisor bits
16:51:11 <tkajinam> So as you know WinStackers project has been retired and now OpenStack on Windows is no longer maintained
16:51:12 <bauzas> for a second, I thought it was about the image type and the instances :)
16:51:41 <tkajinam> I've seen some issues with cross platform support when working on replacing unmaintained libs (eg netifaces)
16:52:16 <tkajinam> I wonder if we can completely drop the windows support if it's not really tested/maintained or at least deprecate it so that we can get rid of it when something is completely broken
16:52:23 <bauzas> if that's removing tech debt on things that we removed but left remains, sure I second your work
16:53:14 <bauzas> anyone having any concerns about that ?
16:54:11 <bauzas> I checked and apparently you can install a libvirt client on windows
16:54:39 <bauzas> it would require your hypervisor to be remote tho, which is something we don't support
16:54:48 <tkajinam> yes
16:54:54 <tkajinam> as we don't support hyper-v via libvirt
16:55:02 <tkajinam> I personally prefer direct removal given the fact hyper-v driver was already removed, but if we want to do it safe then we can deprecate it this cycle. We can discuss the strategy in the review https://review.opendev.org/c/openstack/nova/+/932407
16:55:29 <sean-k-mooney> ya so hyperv via libvirt ws never supported
16:55:39 <bauzas> I just think we can process with reviewing your patch
16:55:49 <bauzas> nothing controversial so far
16:55:53 <tkajinam> thanks
16:56:27 <bauzas> anything else before we wrap up ?
16:56:53 <tkajinam> just fyi. I've added a few bugs (and their fixes) to the bottom of status etherpad https://etherpad.opendev.org/p/nova-2025.1-status (L87-91)
16:57:14 <sean-k-mooney> tkajinam: we have some windows supprot we can delete in os-vif too by the way
16:57:15 <tkajinam> these replaces the deprecated/unmaintained libs so I appreciate reviews for these.
16:57:28 <tkajinam> sean-k-mooney, yeah I remember I did deprecate these in the past cycle
16:58:01 <bauzas> tkajinam: ack
16:58:07 <tkajinam> so it maybe time to drop it, as we usually use eventlet patch differently for windows removing the logic may help removing eventlet.
16:58:27 <gmann> tkajinam: what exactly left to remove window support?
16:58:41 <tkajinam> gmann, tons of os.name == 'nt' checks
16:58:42 <bauzas> gmann: see above, there is a cleanup patch
16:58:59 <tkajinam> maybe not 'tons' but 'numbers'
16:59:05 <gmann> ohk, just cleanup things. got it
16:59:28 <gmann> but we have already declared the winbdow support removal during hyper-V removal
16:59:49 <tkajinam> yes
17:00:17 <tkajinam> that's all from me today
17:00:57 <bauzas> cool and we're at time
17:00:59 <bauzas> thanks all
17:01:02 <bauzas> #endmeeting