16:00:20 <Uggla> #startmeeting nova
16:00:20 <opendevmeet> Meeting started Tue Mar 25 16:00:20 2025 UTC and is due to finish in 60 minutes.  The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:20 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:20 <opendevmeet> The meeting name has been set to 'nova'
16:00:42 <Uggla> Hello everyone
16:01:41 <masahito> o/
16:02:02 <elodilles> o/
16:02:24 <gibi> o/
16:02:35 <Uggla> awaiting a moment for people to join.
16:02:43 <dansmith> o/
16:03:24 <bauzas> \o (in another meeting)
16:03:45 <Uggla> #topic Bugs (stuck/critical)
16:03:54 <Uggla> #info No Critical bug
16:04:02 <Uggla> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:04:34 <Uggla> anything about bugs ?
16:05:30 <Uggla> #topic Gate status
16:06:06 <Uggla> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:06:14 <Uggla> #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:06:25 <Uggla> #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status
16:06:32 <Uggla> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:06:39 <Uggla> #info Please try to provide meaningful comment when you recheck
16:06:58 <Uggla> anything about the gate ?
16:07:46 <Uggla> seems not.
16:07:57 <Uggla> #topic Release Planning
16:08:07 <Uggla> #link https://releases.openstack.org/epoxy/schedule.html
16:08:15 <Uggla> #info Nova deadlines are set in the above schedule
16:08:21 <Uggla> #link https://etherpad.opendev.org/p/nova-epoxy-rc-potential
16:08:27 <Uggla> #link https://releases.openstack.org/flamingo/schedule.html
16:08:52 <Uggla> #info Remaining post RC1: update min servion version for a SLURP or non-SLURP release : https://review.opendev.org/c/openstack/nova/+/944018/
16:09:11 <Uggla> #info Nova Flamingo deadlines will be discussed at the PTG.
16:09:46 <Uggla> We are almost good for Epoxy release.
16:09:48 <elodilles> note that this week is the week of Final RC for 2025.1 Epoxy :)
16:10:36 <Uggla> #topic Review priorities
16:10:44 <Uggla> #info Flamingo priorities will be discussed at the PTG.
16:10:59 <Uggla> #topic PTG planning
16:11:06 <Uggla> #info Next PTG will be held on Apr 7-11
16:11:11 <Uggla> #link https://etherpad.opendev.org/p/nova-2025.2-ptg
16:11:45 <Uggla> Please add the topics you want to discuss in the pad.
16:12:24 <Uggla> #topic Stable Branches
16:12:30 <Uggla> #info stable gates seem to be healthy
16:12:41 <Uggla> #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:13:03 <Uggla> elodilles, if you want to add something please go ahead.
16:13:14 <elodilles> yepp, one thing maybe:
16:13:17 <elodilles> #info stable/2025.1 branch was cut for nova as well last week
16:13:24 <elodilles> that's all from me
16:13:36 <elodilles> back to you Uggla
16:13:53 <Uggla> thanks elodilles
16:13:58 <elodilles> np
16:15:22 <Uggla> I skip the vmwareapi 3rd-party CI efforts Highlights as fwiesel is ooo this week.
16:15:54 <Uggla> #topic Open discussion
16:16:16 <Uggla> anything to discuss ?
16:16:47 <keerthivasan86[m]> Just quick question why https://bugs.launchpad.net/nova/+bug/1766387 ( why tx_queue_size is not getting implemented in vhost , any specific reason )
16:16:52 <gibi> just to double check
16:17:14 <gibi> we do not track anything for RC2
16:17:17 <sean-k-mooney> keerthivasan86[m]: if i recall corectly its only supproted in vhost-user but not kernel vhost
16:17:19 <gibi> is it corr4ect?
16:18:01 <sean-k-mooney> gibi: not that im aware of
16:19:04 <keerthivasan86[m]> sean-k-mooney: As part of vhost-net able to see rx_queue_size is implemented at vm level as well. It works for vhost-net as well
16:19:10 <Uggla> gibi, not yet. Do you think about FUP for vfio pci migration ?
16:19:43 <sean-k-mooney> keerthivasan86[m]: when it was implented there was a specific reaosn why we didnt enabled it
16:20:12 <gibi> Uggla: it is going to land on master probably today. I'm not advocating for pusing for an RC2 tomorrow just for that single thing. (it is not an Epoxy regression)
16:20:25 <sean-k-mooney> keerthivasan86[m]: that may haved chnted but the current code was becasue of how qemu/libivrt worked at the time we implemtned https://specs.openstack.org/openstack/nova-specs/specs/rocky/implemented/libvirt-virtio-set-queue-sizes.html
16:21:30 <keerthivasan86[m]> sean-k-mooney: if you are ok , can i work on to implement tx_queue_size for vhost-net ?
16:22:11 <sean-k-mooney> sure but we need to know when it started to be supported, and we need to take accound of upgrades
16:22:13 <dansmith> the only PCI FUP that should be backported is doc stuff right?
16:22:19 <dansmith> Uggla: gibi ^
16:22:31 <dansmith> the test and cleanliness things should not be backported, IMHO, but definitely not hold up rc2
16:22:44 <Uggla> gibi, this is what I have in mind as well. Waiting for GA as this is the only thing.
16:22:48 <sean-k-mooney> keerthivasan86[m]: so im not sure fi it needs a spec or if a specless blueprint woudl be enough.
16:23:06 <sean-k-mooney> dansmith: the doc is the one that really should be
16:23:15 <sean-k-mooney> dansmith: some of the others are nice to have but not required
16:23:39 <dansmith> backporting test cleanliness doesn't make sense to me unless it's needed for an actual fix
16:23:57 <gibi> dansmith: for RC2 prespective only  https://review.opendev.org/c/openstack/nova/+/944105/5 in interesting
16:24:04 <sean-k-mooney> right the doc i could see for an RC2 but at this point i woudl just wait and do that after the release
16:24:27 <sean-k-mooney> gibi: oh right to make numa work
16:24:40 <gibi> dansmith: but as I wrote above it is not an E regression and will only land today
16:24:43 <dansmith> gibi: ah I missed that one.. that's not really a regression i t seems, but..
16:24:49 <dansmith> ack yeah okay
16:24:59 <gibi> yeah I would not spin an RC2 just for thish
16:25:10 <gibi> but if there are other things forcing an RC2 ...
16:25:11 <sean-k-mooney> so we can do a stable release basifcally right after the actual release
16:25:17 <dansmith> right
16:25:23 <Uggla> +1
16:25:27 <sean-k-mooney> so i think  RC2 is overkill for any of those
16:25:27 <gibi> yeah doing stable backports is the way to go if nothing else forces RC2
16:25:44 <sean-k-mooney> sounds like we are all in violent agreement
16:26:38 <gibi> yepp
16:26:40 <bauzas> yup
16:26:46 <bauzas> (sorry, meeting was over)
16:27:01 <Uggla> bauzas, no still in the meeting
16:27:17 <bauzas> as a reminder, any new release candidate impacts our distros
16:27:34 <bauzas> so we definitely only need to provide a RC2 if this is a regression
16:27:47 <elodilles> (with my release core hat on) anyway, let me know if an RC2 is needed (or not needed) as this week is when we can release a final RC as i said o:)
16:28:53 <elodilles> (i'll generate final RC patches (where there are merged and unreleased stuff on stable/2025.1) somewhere around 2nd half of the week fwiw)
16:29:18 <bauzas> ack thanks
16:29:22 <elodilles> np
16:30:36 <dansmith> are we done?
16:30:56 <Uggla> keerthivasan86[m], are the answer of sean ok for you ?
16:31:29 <Uggla> any other topic ?
16:31:56 <masahito> question for the ptg topic selection and timeslot
16:32:29 <Uggla> masahito, the current topic are in the etherpad above.
16:32:49 <masahito> thank. ah, yes. I added some.
16:33:06 <Uggla> I think not all of them are available. I know new ones will come.
16:33:22 <Uggla> Then we will organize the timeslot to discuss all of them.
16:33:29 <sean-k-mooney> Uggla: i assume masahito wanted to ask about when there topics will be scheduled
16:33:39 <sean-k-mooney> or perhaps suggest when tehy are aviable
16:33:51 <masahito> my question is the ptg time slot is limited so i don't think the ptg can't cover all topics. so i want to know when and how it's decided.
16:34:13 <sean-k-mooney> masahito: we dont have many topics currently
16:34:20 <masahito> s/ptg can't/ptg can/
16:34:22 <sean-k-mooney> i woudl be surrprised if we didnt cover them all
16:34:52 <Uggla> I think for the time slot it will be almost ok next week.
16:35:04 <keerthivasan86[m]> yes Uggla As sean-k-mooney suggested specless blueprint or fresh blueprint to implement tx_queue_size
16:35:27 <opendevreview> sean mooney proposed openstack/placement master: improve test logging and replace psycopg2 with psycopg2-binary  https://review.opendev.org/c/openstack/placement/+/945487
16:35:35 <sean-k-mooney> dansmith: ^
16:35:50 <keerthivasan86[m]> can i create fresh blueprint to implement tx_queue_size for vhost-net feature ?
16:35:55 <dansmith> sean-k-mooney: ack
16:36:00 <Uggla> Masahito, we’ll try to accommodate your schedule so you can join.
16:36:13 <masahito> i got it for the next week meeting.
16:36:54 <Uggla> any other topic ?
16:36:55 <masahito> thanks. I prefer 14:00UTC or later slot because of family reason as it's remote session :)
16:37:28 <Uggla> masahito, sure I'll keep that in mind.
16:38:31 <Uggla> looks we can close the meeting
16:39:22 <Uggla> thanks all
16:39:27 <Uggla> #endmeeting