16:00:31 <Uggla> #startmeeting nova
16:00:31 <opendevmeet> Meeting started Tue Oct 21 16:00:31 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:31 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:31 <opendevmeet> The meeting name has been set to 'nova'
16:00:40 <fwiesel> o/
16:00:49 <r-taketn> hello
16:01:22 <nicolairuckel> o/
16:01:23 <Uggla> Hello everyone
16:01:36 <gmaan> o/
16:01:39 <gibi> o/
16:02:17 <elodilles> o/
16:03:02 <Uggla> Let's start
16:03:12 <Uggla> #topic Bugs (stuck/critical)
16:03:21 <Uggla> #info No Critical bug
16:03:30 <Uggla> #topic Gate status
16:03:34 <bauzas> \o
16:03:43 <Uggla> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:03:47 * bauzas was preparing a coffee on his new barista machine
16:03:53 <Uggla> #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:04:00 <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:04:05 <Uggla> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:04:11 <Uggla> #info Please try to provide a meaningful comment when you recheck
16:04:58 <Uggla> I have not seen something special about it, unless I miss something.
16:06:41 <gibi> o/
16:06:47 <Uggla> gibi, bauzas something to say about the gate ?
16:06:58 <bauzas> nothing on my radar
16:07:10 <gibi> there was issues with the wsgi package in the jobs using debian
16:07:23 <gibi> causign python3.11 crashes on the gate mostly in keystone service
16:07:38 <gibi> I don't have a tracker for it but it was discussed on -qa
16:08:12 <gibi> I did not see it today yet but I did not dig for it either
16:08:56 <Uggla> ok thanks gibi
16:09:06 <Uggla> moving on to next topic
16:09:09 <gmaan> one other thing related to gate. grenade jobs settings are updated and now grenade on master will be testing the correct branches upgrade
16:09:25 <Uggla> thx gmaan
16:09:28 <gmaan> stable/2025.2 change still in gate but will be merging soon
16:09:34 <gmaan> #link https://review.opendev.org/c/openstack/grenade/+/961914
16:10:43 <gmaan> that's all, we can move to next topic
16:10:51 <Uggla> #topic tempest-with-latest-microversion job status
16:11:17 <Uggla> gmaan anything you want to say  about it ?
16:11:21 <gmaan> no, did not get chance to look into it.
16:11:51 <Uggla> no worries, thx gmaan
16:12:11 <Uggla> #topic Release Planning
16:12:19 <Uggla> #link https://releases.openstack.org/gazpacho/schedule.html
16:12:57 <Uggla> ^  dates will be discussed and refined during the PTG.
16:13:12 <Uggla> #info PTG etherpad for 2026.1 is available: https://etherpad.opendev.org/p/nova-2026.1-ptg
16:13:21 <Uggla> #info Please add the topics you would like to discuss in the above document.
16:13:29 <Uggla> #info Take care EU daylight time change this Sunday (26 Oct).
16:14:00 <Uggla> ^ confused me last week, so here are the expected timelines
16:14:07 <Uggla> #info PTG meetings (to be confirmed) will happen room grizzly 14:00UTC (start) -> 17:00UTC (end) 4H from Tuesday to Friday.
16:14:21 <Uggla> #info Please enter your review comments (what was ok, what is not working...)
16:14:41 <Uggla> I mean comments for the retro
16:14:46 <Uggla> #info Please update the courtesy ping list, if you want me to notify you about a particular topic.
16:15:00 <Uggla> #info You might have a earlier session next week for our contributors from Japan (compute graceful shutdown)
16:15:22 <bauzas> yeah, not only that
16:15:23 <Uggla> #info the upstream meeting (this one) will be canceled
16:16:00 <bauzas> we had hallway discussions with some of the Japan contributors, they had a couple of topics to discuss at the PTG
16:16:20 <Uggla> oh yes, the metadata protection too.
16:16:27 <bauzas> so it would be nice if we could book some timeslot earlier in the day that's more asian-friendly
16:16:34 <bauzas> 1 hour should be enough
16:16:51 <Uggla> 1h for the 2 topics ?
16:17:03 <bauzas> 1 hour for *any* topic
16:17:10 <gmaan> early sessions you mean during allocated slots right? from 14 UTC onwards or some other time whihc is more close to japan?
16:17:37 <bauzas> as soon as you open the possibility for folks to join, please don't expect them to not use that possibility for discussing more
16:17:59 <Uggla> gmaan no I have not requested the timeslot.
16:18:02 <bauzas> gmaan: 14UTC is already very late for many of them
16:18:16 <bauzas> JST is UTC+8 I believe
16:18:17 <gmaan> yeah, it seems 1 AM
16:18:39 <gmaan> I want to know if something early than 14 UTC we want to schedule
16:18:56 <bauzas> well, that's why we have a conversation now
16:18:56 <gmaan> not later than 14 UTC
16:19:11 <bauzas> having it earlier would mean that we wouldn't have a solid quorum
16:19:35 <bauzas> so I need to know who could join something earlier
16:20:36 <bauzas> another possibility is a very late slot for European, I could try to make it, but again, I'm not sure we would have quorum
16:20:53 <gibi> I rather be early from EU than late
16:22:17 <Uggla> Yep I think around 9 or 10 UTC.
16:22:26 <bauzas> we would miss gmaan, dansmith and melwitt if so
16:22:31 <gibi> I can join any day on those times
16:22:53 <bauzas> here is one thought
16:22:59 <gmaan> yeah, it will be 3 AM in PST
16:23:00 <gibi> we can have a discussion and have a recap session during the normal hours so other cores get updated
16:23:03 <dansmith> yeah 10UTC is pretty early for us
16:23:15 <Uggla> I just expect gibi, bauzas, sean-k-mooney.
16:23:31 <bauzas> let's try to make it at Thursday or Friday EU mornings
16:23:47 <gibi> I think there is no good single timeslot hence I suggesting two. One with the folks from far east and then one with the core team
16:23:48 <sean-k-mooney> sorry
16:23:48 <bauzas> and ask the Asian contributors to put their topics in advance into the etherpad
16:23:51 <sean-k-mooney> was on a call
16:23:54 <Uggla> bauzas, ok I will sync up with them.
16:24:06 <sean-k-mooney> reading back are you dicussing the meeting slot
16:24:14 <bauzas> so people not being to attend can still leave comments on the the etherpad in advance
16:24:16 <sean-k-mooney> or ptg
16:24:27 <bauzas> sean-k-mooney: some asian-friendly ptg slot
16:24:32 <sean-k-mooney> ah ok
16:24:44 <bauzas> based on the hallway talks we had at Summit
16:24:50 <sean-k-mooney> ack
16:24:56 <ali> I have a question. I have two aggregates named general and dedicated. The availability zone of general is nova, and the zone of dedicated is another one I wanted to live migrate an instance from the nova zone to the other zone To do this, I removed the host from the dedicated aggregate and added it to the general aggregate. After the live migration completed, I moved the compute host back to the dedicated aggregate After that, I tried to resize the
16:24:57 <ali> instance to its own flavor, but I got an error related to FilterScheduler and zone specifications. I found that in the nova_api database, the availability_zone was updated correctly, but in the nova database, the availability_zone was not updated.
16:24:57 <ali> Why did this happen?
16:25:21 <bauzas> ali: we are on a meeting, could you please ask your question after we're done ?
16:25:40 <ali> ok
16:26:05 <bauzas> dansmith: would you be okay if you could comment on the asian topics before it happens so we could convey your concerns at time ?
16:26:06 <Uggla> are we good with that topic ?
16:26:22 <dansmith> bauzas: I mean.. we don't really have any other option
16:26:56 <gmaan> I wanted to join the graceful shutdown topic but depends on what time we select
16:27:51 <gmaan> one idea, if 13 UTC can work for them though we did not book slot in 13 UTC for nova but can do
16:27:53 <bauzas> dansmith: well, we could ask them to join again later
16:27:58 <sean-k-mooney> well the other option woudl be do the NA/asia slot
16:28:25 <sean-k-mooney> so very late UTC
16:28:49 <sean-k-mooney> if there are more na based folks instereted i nthee topics that might work better
16:29:18 <sean-k-mooney> that woudl likely have toe bu thrusday however to be in there friday morning
16:32:29 <Uggla> 23:00 UTC ?
16:33:08 <bauzas> that's exactly why I miss in-person PTGs
16:33:27 <Uggla> I will check with them if the prefer morning/afternoon.
16:33:36 <Uggla> bauzas, yeah I know.
16:33:41 <sean-k-mooney> ya.. i dont have a stong opion either way
16:33:52 <bauzas> what we need is a clarified PTG etherpad
16:33:58 <gibi> if it will be late EU then I would like to get a recap session next day
16:34:03 <gibi> in the normal slots
16:34:03 <bauzas> with a list of topics they want to discuss
16:34:19 <bauzas> and then we can let people indicate their interest
16:34:24 <sean-k-mooney> gibi: i think we will wnat to do that in either case
16:34:29 <bauzas> yup
16:34:40 <Uggla> bauzas sure, I hope they will get in touch with me soon. If not I'll try to ping.
16:34:58 <Uggla> So I could update the schedule.
16:35:10 <bauzas> having PTG right after Summit doesn't help, in particular when most of attendees take a few days off after the latter
16:35:35 <gibi> sean-k-mooney: yes
16:35:47 <bauzas> sure, and please people let mention your interest if you wanna speak up on those topics
16:36:51 <Uggla> can we move on ?
16:37:23 <gibi> +
16:37:32 <Uggla> next topic
16:37:33 <Uggla> #topic OpenAPI
16:37:39 <Uggla> #link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned
16:37:45 <Uggla> #info still 28 remaining atm.
16:37:52 <Uggla> #topic Stable Branches
16:38:02 * Uggla giving the mic to elodilles
16:38:10 <elodilles> thanks
16:38:18 <elodilles> #info stable branches (stable/2025.* and stable/2024.*) seem to be in OK state
16:38:29 <elodilles> #info final stable 2024.1 Caracal release (and all other stable/202*.* release patches) are proposed: https://review.opendev.org/c/openstack/releases/+/964471
16:38:45 <elodilles> #info 2024.1 Caracal (stable/2024.1) is planed to move to Unmaintained in less than a week
16:39:05 <elodilles> and that's all for now about stable from me
16:39:23 <Uggla> thx elodilles
16:39:37 <Uggla> #topic vmwareapi 3rd-party CI efforts Highlights
16:39:50 <Uggla> fwiesel anything you'd like to tell us ?
16:39:51 <fwiesel> #info Cinder VMware bug fixed for reimaging volume
16:40:00 <fwiesel> #link https://review.opendev.org/c/openstack/cinder/+/961357
16:40:21 <fwiesel> Took a while, but that was blocking me from fixing the last two failing tempest tests.
16:40:28 <fwiesel> That and the still broken CI
16:40:36 <fwiesel> But that's it from my side
16:41:02 <fwiesel> Uggla: back to you
16:41:04 <Uggla> thanks fwiesel, thx correting this
16:41:29 <Uggla> #topic Gibi's news about eventlet removal.
16:41:36 <Uggla> gibi anything to report ?
16:42:47 <gibi> o/
16:42:52 <gibi> basically the same as last week
16:43:06 <gibi> * please look at the topic in the PTG etherpad
16:43:43 <gibi> * you can review things on the eventlet-removal topic, we have couple of smallish green patches on the unittest side
16:44:17 <gibi> + I finally get back to the rally job patch and iterating on it https://review.opendev.org/c/openstack/nova/+/960130
16:44:21 <gibi> that is is
16:44:23 <gibi> it
16:45:42 <Uggla> gibi, fyi I gave some ad about eventlet testing at the end of my presentation.
16:46:10 <Uggla> Explaining that if folks want to test it that would be hihgly appreciated.
16:46:21 <gibi> Uggla: thanks
16:46:30 <gibi> was there any further question about it?
16:46:59 <Uggla> yes, just one about the overall plan : If all the services will remove eventlet.
16:47:38 <Uggla> and I explained quickly our approach for nova. 2 steps phases and current services "migrated"
16:48:11 <Uggla> Then I got a question about python 3.14 support for us, from Canonical guys.
16:48:39 <gibi> yeah I have no comment on 3.14. That is too far ahead
16:49:02 <gibi> I would assume that with GIL mode and threading we will work in 3.14 without issues
16:49:07 <Uggla> yep I said that and explain that it will probably happen after eventlet removal.
16:49:14 <gibi> the GILles mode is a different beast probably
16:49:56 <Uggla> sure, tbh I did not have the time to speak about GIL.
16:50:47 <gibi> :)
16:50:51 <Uggla> Especially because at the same time I noticed that someone took my bag. Hopefully it was just a mistake, and I managed to find it quickly.
16:51:00 <gibi> ohh
16:51:06 <gibi> anyhow thanks for the advertisment
16:51:29 <Uggla> moving on because we are almost at the top of the hour
16:51:36 <Uggla> #topic Open discussion
16:51:45 <Uggla> reminder:
16:51:46 <Uggla> (Uggla) Pool for the new schedule of upstream meeting: https://framadate.org/ao12zK6wR3K3nfbF
16:51:55 <Uggla> #linkAnnonce : https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/H5PBFZJ4X3TSGSC4YF6E4WTV43CBOVS6/
16:52:04 <Uggla> the trend seems to go on Monday
16:52:27 <nicolairuckel> I iterated on my NVRAM patch (https://review.opendev.org/c/openstack/nova/+/959682) but there's still an open issue regarding the file permissions.
16:53:36 <nicolairuckel> Also, I heard that it would be a good idea to bring that up for the PTG as a crossproject topic, so I'll add that to the etherpad later.
16:54:02 <Uggla> nicolairuckel, yep please do
16:54:35 <Uggla> crossproject with cinder ?
16:55:09 <nicolairuckel> I think so
16:55:25 <nicolairuckel> I was told it was related to image encryption
16:55:42 <Uggla> more glance though
16:55:50 <nicolairuckel> tbh, I'm still quite new to openstack so I'm not *that* sure about the scope yet.
16:56:32 <Uggla> ok I'll look at that and try to find the appropriate slot.
16:56:38 <nicolairuckel> thank you
16:56:40 <Uggla> Any expected duratio, ?
16:56:46 <Uggla> *duration
16:56:48 <sean-k-mooney> gibi: supporting freethread pytyon is defeintly a post eventlet topic.
16:57:44 <Uggla> r-taketn I think you would like to share something, aren't you ?
16:57:55 <sean-k-mooney> nicolairuckel: the nvram patch is not related to the image encyption work
16:57:57 <nicolairuckel> I'm not sure yet. I'll think about that and add it to the Etherpad if that's okay.
16:57:58 <r-taketn> yes. Thank you. I have one quick request. Could someone please check this spec and give some feedbacks later?
16:58:10 <r-taketn> #link https://review.opendev.org/c/openstack/nova-specs/+/962578
16:58:19 <r-taketn> I have proposed this spec for generalizing sev/sev-es code to add new confidential computing from other architecture(Intel TDX,Arm CCA)
16:58:25 <sean-k-mooney> but we shoudl dicuss the imange encyption work in the nova/glance slot.
16:58:25 <r-taketn> I have re-written the spec. In particular, I detailed the problem description about current sev/sev-es code.
16:58:42 <sean-k-mooney> r-taketn: i have not had time yet but ill tray and look at that again
16:58:56 <r-taketn> I have this topic on ptg slot, but I'd appreciate if you give some feedbacks in advance
16:59:04 <r-taketn> sean-k-mooney: Thank you
16:59:27 <sean-k-mooney> the real goal of this work is to enabel you to supprot arm CCA and SEV-SNP more eaisly in the future right
16:59:44 <r-taketn> yes
16:59:51 <sean-k-mooney> this is prepareing the memory encyption logic to be more generic and extensible in advance of the hardware
17:01:10 <sean-k-mooney> r-taketn: ok small comment initally . most of tghe work items shoudl be experses in pros in the proposed changes section and the work ites shoudl be a very short list of the thing that need to be deliverd
17:01:59 <gibi> sorry folks I have to drop.
17:02:01 <gibi> I will read back
17:02:14 <Uggla> gibi no pb about to close
17:02:16 <sean-k-mooney> r-taketn: so if you look at the sev-es spec form last cycle https://github.com/openstack/nova-specs/blob/master/specs/2025.2/implemented/amd-sev-es-libvirt-support.rst?plain=1#L287
17:02:34 <Uggla> Anything else you'd like to share ?
17:02:39 <sean-k-mooney> you can see more or less what is expected for that section vs proposed changes https://github.com/openstack/nova-specs/blob/master/specs/2025.2/implemented/amd-sev-es-libvirt-support.rst?plain=1#L50
17:03:18 <r-taketn> sean-k-mooney: ok. sorry. I'll fix it.
17:03:18 <sean-k-mooney> r-taketn: the sev spec is a good example fo what level of detail ectra is expected that you can use as a guide
17:03:19 <bauzas> we're overtime :)
17:03:59 <Uggla> bauzas atm reasonable overtime
17:04:31 <r-taketn> Uggla: That's all from me. thank you
17:04:46 <Uggla> ok so I'm going to close.
17:04:57 <Uggla> Thank you for participating in this meeting.
17:05:04 <sean-k-mooney> r-taketn: no worries at all. we just do it this way so that we we have discsed what we want to change  before dissusing the impact of the change. ill look at your proposal regardless
17:05:19 <Uggla> #endmeeting