16:01:57 <Uggla> #startmeeting nova
16:01:57 <opendevmeet> Meeting started Tue Sep 30 16:01:57 2025 UTC and is due to finish in 60 minutes.  The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:57 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:57 <opendevmeet> The meeting name has been set to 'nova'
16:02:17 <Uggla> Hello everyone
16:02:20 <bauzas> \o
16:02:28 <r-taketn> Hello
16:02:43 <elodilles> o/
16:03:01 <tkajinam> o/
16:03:07 <Uggla> awaiting a couple of minutes, so people can join
16:03:28 <Uggla> I know some of them are already in another meeting
16:03:49 <gibi_> o/
16:04:07 <Uggla> Let's start
16:04:16 <Uggla> #topic Bugs (stuck/critical)
16:04:22 <Uggla> #info No Critical bug
16:04:36 <Uggla> #topic Gate status
16:04:44 <Uggla> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:04:48 <fwiesel> o/
16:04:56 <Uggla> #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:05:02 <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:05:09 <Uggla> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:05:17 <Uggla> #info Please try to provide a meaningful comment when you recheck
16:05:42 <Uggla> #info I have seen (last week) "nova-tox-py312-threading fails intermittently" https://bugs.launchpad.net/nova/+bug/2125185 from gibi
16:06:04 <Uggla> gibi is it something you want to discuss here or later in the eventlet part ?
16:06:11 <gibi_> I will recheck the fix there as it failed on the gate
16:06:15 <gibi_> 961781
16:06:19 <gibi_> https://review.opendev.org/c/openstack/nova/+/961781
16:06:37 <gibi_> my point here is just if you see nova-tox-py312-threading failing on your patch
16:06:43 <gibi_> but the other py312 job does not
16:06:47 <gibi_> then please let me know
16:07:07 <Uggla> 👍
16:07:07 <gibi_> I monitor the nova-tox-py312-threading job but I might miss things
16:07:13 <gibi_> that is it here
16:07:51 <Uggla> Anything else to discuss about the gate ? I have not seen anything special but... ?
16:08:20 <gibi> maybe one
16:08:57 <gibi> if you see strange failures in nova-next regarding scheduling then let me no too :) nova-next uses threading mode for n-sch n-api n-metadata
16:09:11 <gibi> /let me no/ let me know/
16:09:38 <gibi> I spotted some strange failurs there and even filed a bug
16:09:49 <gibi> but I lost the link :)
16:10:18 <gibi> https://bugs.launchpad.net/nova/+bug/2125598
16:10:20 <gibi> here it is
16:10:28 <gibi> I need to get back to this and look deeper
16:10:47 <gibi> that is it really for me now :)
16:11:05 <Uggla> ok*
16:11:13 <Uggla> Moving on to next topic skipping gmann's one due to PTO.
16:11:23 <Uggla> #topic Release Planning
16:11:31 <Uggla> #link https://releases.openstack.org/flamingo/schedule.html
16:11:38 <Uggla> #info Nova deadlines are set in the above schedule
16:11:49 <Uggla> #info release in progress.
16:11:57 <Uggla> #info PTG etherpad for 2026.1 is available: https://etherpad.opendev.org/p/nova-2026.1-ptg
16:12:03 <Uggla> #info Please add the topics you would like to discuss in the above document.
16:12:24 <Uggla> #info PTG meetings (to be confirmed) will happen room grizzly 15:00UTC -> 17:00UTC from Tuesday to Friday
16:12:46 <opendevreview> Balazs Gibizer proposed openstack/placement master: Reproduce GET a_c slowness  https://review.opendev.org/c/openstack/placement/+/962596
16:13:14 <Uggla> ^ I have booked the timeslots, but that could change.
16:13:20 <tkajinam> maybe we need deadilines for G added to https://releases.openstack.org/gazpacho/schedule.html
16:13:52 <bauzas> tkajinam: we usually discuss it at the PTG
16:14:02 <tkajinam> ah, yes. ok
16:14:03 <Uggla> tkajinam, this is something that will be added after PTG
16:14:41 <bauzas> Uggla: fwiw, we could need to leave the Tuesday slots for cross-project discussions... or booking x-p topics into our own slots
16:15:08 <bauzas> moderators should get proper information about x-p needs soon
16:15:36 <Uggla> bauzas, yep sure. We will fine tune the schedule based on cross session projects and constraints.
16:16:20 <Uggla> I guess for now the most important thing is to add topics to the etherpad.
16:16:59 <Uggla> moving on
16:17:06 <Uggla> #topic OpenAPI
16:17:13 <Uggla> #link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned
16:17:21 <Uggla> #info still 28 remaining atm.
16:17:45 <Uggla> #topic Stable Branches
16:17:51 * Uggla giving the mic to elodilles
16:17:59 <elodilles> thanks o/
16:18:05 <elodilles> #info stable branches (stable/2025.* and stable/2024.*) seem to be in OK state
16:18:41 <elodilles> a couple of stable backports landed on old stable branches but we haven't merged anythin to stable/2025.2 yet,
16:19:04 <elodilles> maybe the day after tomorrow, if the 2025.2 Flamingo release will be successful :)
16:19:19 <elodilles> i think that's it from me about stable branches for now
16:19:44 <Uggla> 🤞for thursday.
16:20:00 <Uggla> thanks elodilles
16:20:05 <elodilles> np
16:20:31 <Uggla> #topic vmwareapi 3rd-party CI efforts Highlights
16:20:42 <Uggla> fwiesel anything from you
16:20:45 <fwiesel> Hi, sorry for the last time. I was on a company workshop.
16:21:13 <Uggla> no worries
16:21:14 <fwiesel> This week, I am working on fixing a problem in the pipeline. A Neutron update conflicts with our agent.
16:21:24 <fwiesel> So, the agent won't even start up anymore.
16:21:30 <fwiesel> I hope to fix that soon.
16:21:34 <fwiesel> That's from my side.
16:21:47 <fwiesel> Uggla: Back to you
16:22:29 <Uggla> thx fwiesel
16:22:42 <Uggla> #topic Gibi's news about eventlet removal.
16:22:50 * Uggla giving the mic to gibi
16:23:21 <gibi> o/
16:23:36 <gibi> #link Gazpacho plans are collected in the PTG etherpad: https://etherpad.opendev.org/p/nova-2026.1-ptg
16:23:43 <gibi> #link We need a formal approval of the new BP: https://blueprints.launchpad.net/nova/+spec/eventlet-removal-gazpacho
16:23:59 <gibi> #link We are going to restart our weekly eventlet sync every Wednesday 16:30 CEST, 14:30 UTC (during the summer) on meet.google.com/bcy-uqoz-hje
16:24:05 <gibi> actually we restarted last week
16:24:46 <sean-k-mooney> ack so the next wone is tomorow correct
16:24:50 <gibi> next thing to land is nova-conductor https://review.opendev.org/c/openstack/nova/+/958575 please help me reviewing it
16:25:03 <gibi> sean-k-mooney: yepp next one is tomorrow 14:30 UTC
16:25:55 <gibi> that is all from me. Uggla lets try to approve the bp :)
16:26:38 <Uggla> ok
16:26:55 <gibi> is there any questions or objections against that bp?
16:27:36 <sean-k-mooney> Uggla: one admin thing can you create teh 2026.1 seriese tomorrow and set it as the current devlopemnt cycle and upstea the 2025.2 serise and 2025.1 serose to reflect the current stable and supproted status reflecitvly
16:27:47 <sean-k-mooney> i.e. once 2025.2 is offically released tomorow
16:28:03 <sean-k-mooney> an no no objections to the blueprint form me :)
16:28:17 <bauzas> sean-k-mooney: I'll help Uggla about how to do this for launchpad but sure
16:28:26 <Uggla> sean-k-mooney you mean in launchpad right ?
16:28:27 <sean-k-mooney> cool
16:28:32 <sean-k-mooney> yep in launchpad
16:28:46 <bauzas> and yeah, +1 on accepting the gazpacho eventlet bp as a specless one
16:29:04 <sean-k-mooney> we will need to creat the serise in launchpadc before we can target theh bp to it
16:29:11 <sean-k-mooney> that why i was bringin it up
16:29:13 <Uggla> sean-k-mooney, sure as soon as F will be released, I'll update LP.
16:30:05 <Uggla> #topic Open discussion
16:30:47 <gibi> thanks folks
16:30:48 <Uggla> (Uggla) I'm going to send a poll with new schedules proposal.
16:31:14 <Uggla> for the upstream meetings.
16:32:16 <Uggla> Last week I managed to collect some trends, so I can narrow a bit the choices.
16:33:06 <Uggla> That's all 4 me.
16:33:42 <Uggla> Does anyone whant to discuss about something ?
16:33:46 <r-taketn> Uggla: I've just added one more topic to the agenda right before the meeting. Can I share it now?
16:34:23 <Uggla> Sure, sorry I missed it because my mage was not refreshed.
16:34:31 <Uggla> please go ahead r-taketn
16:34:33 <r-taketn> Thank you
16:34:41 <r-taketn> #link https://review.opendev.org/c/openstack/nova-specs/+/962578
16:34:51 <r-taketn> We proposed to adjust the existing SEV/SEV-ES code.
16:35:03 <r-taketn> We think there is the need to generalize the existing SEV/SEV-ES code a bit to support other confidential computing features (e.g. Intel TDX, Arm CCA).
16:35:29 <r-taketn> We would like to discuss the timing of this introduction. Specifically, we propose this as a standalone enhancement in advance to accept other features. Could we consider this approach?
16:36:41 <gibi> I feel like this needs a spec and a PTG discussion and we need tkajinam present :)
16:37:11 <sean-k-mooney> +1 to ^
16:37:22 <Uggla> gibi spec link above, but I agree to with ^
16:37:34 <tkajinam> :-)
16:37:37 <sean-k-mooney> but the overall intent is to generalise teh code now so that it can be extended in teh future correct for more usecase and or vendors/plathforms
16:37:56 <tkajinam> yeah like CCA and even TDX
16:38:06 <r-taketn> sean-k-mooney: yes
16:38:16 <sean-k-mooney> we have talked about TDX in the past as soemting that shoule eventually be supproted
16:38:31 <Uggla> that sounds a reasonable "refactoring"
16:38:45 <tkajinam> I'll check the spec and try to leave some feedback there for the discussion
16:38:56 <gibi> Uggla: I blame the clock for not noticing the spec link :)
16:39:08 <r-taketn> tkajinami: Thank you.
16:39:44 <tkajinam> my quick suggestion at my first glance is that if you can put more focus on describing the expected problems of the current code, rather than how you update codes in details, that would help us understand the direction.
16:40:07 <Uggla> I can say that my employer is interested in TDX and CCA support at some point.
16:40:50 <Uggla> tkajinam +1
16:41:21 <sean-k-mooney> on thing i will say just glancing at it
16:41:23 <sean-k-mooney> MemEncryptionConfig
16:41:25 <r-taketn> tkajinami: Thank you for your feedbacks. I will clarify the purpose and merit to merge this refactoring in advance more.
16:41:37 <sean-k-mooney> is currently a named touple or inhertied form it
16:41:55 <sean-k-mooney> we may actully want to formmalise that inot a real class if we intend to build out more functionality with it
16:42:04 <sean-k-mooney> i.e. have properties/functions assocated with it
16:42:33 <sean-k-mooney> espcially if this woudl ever be inlcuded in any rpc object
16:42:47 <sean-k-mooney> but we can reviw that as part of the spec
16:43:23 <tkajinam> yeah
16:43:39 <Uggla> sean-k-mooney +1, tuple is evil. :)
16:43:54 <tkajinam> I'm guessing we may need to convert it to a class and create sub class per mechanisms.
16:44:02 <sean-k-mooney> named tupples are less so but if we ever thing that class will be part fo an rpc call
16:44:07 <sean-k-mooney> then it need to be an ovo
16:44:29 <sean-k-mooney> ffor now its not so its fine so again lets look at that when we think about the generalisation
16:44:39 <tkajinam> yeah
16:44:59 <sean-k-mooney> it may not be relevent but nova.virt.hardware is used in the schdler and the computes already and maybe the conductor
16:45:21 <sean-k-mooney> anyway i dont really ahve anythign else on that
16:47:42 <r-taketn> Thank you for some feedbacks. My intent is the same to the above discussion(Specifically, MemEncryptionConfig)
16:48:32 <r-taketn> Anyway, I need to write the spec in detail more.
16:49:33 <r-taketn> I will improve the spec constantly. It would be helpful if we could discuss this at PTG or on Gerrit.
16:49:52 <r-taketn> That's all from me today. thanks all.
16:49:52 <gibi> sounds like a plan
16:50:12 <Uggla> r-taketn 👍
16:50:30 <Uggla> Anything else to discuss.
16:50:37 <gibi> -
16:50:49 <tkajinam> nothing from me
16:52:07 <bauzas> -
16:52:48 <Uggla> #topic Bug scrubbing
16:52:56 <Uggla> #info up to 186 (+9 from previous week :( )
16:53:23 <Uggla> ^ just providing the info that it increases a lot compare to last week.
16:53:50 <Uggla> I know gibi is contributing to it. ;)
16:54:33 <Uggla> I will try to look at them tomorrow, if I can answer/close some of them.
16:54:49 <Uggla> Anyway I think that's all for today.
16:55:38 <gibi> hey, I saw bugs, I open trackers :)
16:56:55 <Uggla> Thank you for participating in this meeting. I’ll keep you posted if the next meeting is rescheduled.
16:57:12 <Uggla> #endmeeting