Tuesday, 2025-10-21

*** mhen_ is now known as mhen01:47
opendevreviewAhmad Hassan proposed openstack/nova-specs master: Offline VM migration using https  https://review.opendev.org/c/openstack/nova-specs/+/96444406:18
opendevreviewAhmad Hassan proposed openstack/nova-specs master: Offline VM migration using https  https://review.opendev.org/c/openstack/nova-specs/+/96444406:33
*** ralonsoh_ is now known as ralonsoh06:40
opendevreviewAhmad Hassan proposed openstack/nova-specs master: Offline VM migration using https  https://review.opendev.org/c/openstack/nova-specs/+/96444406:55
jlejeuneelodilles: hello, as requested, now my change has been merged on 2025.2, is it ok for you for moving on 2025.1 ? https://review.opendev.org/c/openstack/nova/+/96177407:32
elodillesjlejeune: sorry, i was at OpenStack Summit in the past days and was traveling yesterday, but yepp, i'm adding the patch to my TODO list ;)07:39
gibielodilles: welcome back o/07:44
gibihope you did not get croissant overdose (/me jealous)07:45
elodillesgibi: thanks :] we ate just enough croissant ;)07:55
jlejeuneelodilles: I was also there, I missed you...08:15
elodillesjlejeune: good to hear that you were there! maybe next time we'll meet :]08:17
elodillesi hope you had great talks with other openstackers!08:18
jlejeuneyeah, and I saw bauzas, Uggla and sean-k-mooney[m] :)08:19
Ugglajlejeune o/08:19
jlejeunehi :)08:19
Ugglajlejeune I hope you had a nice trip back to britany. 08:20
jlejeunea bit long by train but it was ok and you ?08:22
UgglaNot bad except my train was delayed 15mn because someone forgot a bagage inside the previous one.08:26
jlejeuneclassic...08:27
bauzasmy own train line was blocked in between Lyon and Grenoble, the train I was in went back to Lyon and then I had to use another train to Grenoble :)08:29
jlejeune:/08:31
bauzaswell, I'm used to it :) I had the exact same issue last time for the OpenInfra Paris Day in Palaiseau as well, that's why I took a stayover this time on Sunday just to make sure I couldn't have this issue around 11pm :)08:34
jlejeuneso, I hope for the next summit in Paris it won't be there anymore :)08:36
bauzaslong story short, easier to travel by flight08:38
jlejeunethanks elodilles :)09:14
elodillesnp! thanks too o/09:15
jlejeuneand if you have time, I would really appreciate that my topics (bug-2044235 and bug/2085135) moved forward until 2024.1 before that release is set to 'unmaintained' :)09:19
elodillesjlejeune: i'm planning to review all stable patches that are ready to merge, but on the other hand we are very late already with the final stable release of 2024.1 Caracal, so I don't think we have time to merge there any more patches :/09:32
elodillesjlejeune: note that bug fixes can land to unmaintained/2024.1 after the transition09:33
elodillesjlejeune: though i understand that it is less comfortable for consumers as the releases have to be cut downstream by themselves from unmaintained/2024.1 branches09:34
jlejeuneok understandable, so I would need to repush my change on new unmaintained/2024.1 branch later and abandon my changes over stable/2024.1 branches09:40
elodillesjlejeune: yes, that will be the way forward09:58
jlejeuneok got it10:05
opendevreviewMerged openstack/nova stable/2025.1: Adds regression test for bug LP#2044235  https://review.opendev.org/c/openstack/nova/+/96160110:39
gibidansmith: could you add back your +2 on https://review.opendev.org/c/openstack/nova/+/937275 ? The devstack dependency landed finally so we can good to go and test the placement optimization stuff in nova-next permanently10:43
gibis/can/are/10:43
gibiand if you are around that then there is a similar patch that enables such optimizations in some of the nova func tests https://review.opendev.org/c/openstack/nova/+/96303610:44
gibicores, there is a super easy doc patch that needs a second +2 https://review.opendev.org/c/openstack/nova/+/963281 10:44
sean-k-mooneygibi: o/ still gong thorugh my email but ill take a look in a bit, i think i looked at the docs patch before while traveling but didn leave a review10:54
opendevreviewMerged openstack/nova stable/2025.1: nova-conductor puts instance in error state  https://review.opendev.org/c/openstack/nova/+/96177411:16
opendevreviewNicolai Ruckel proposed openstack/nova master: Preserve UEFI NVRAM variable store  https://review.opendev.org/c/openstack/nova/+/95968211:17
nicolairuckelsean-k-mooney: I changed my patch according to your comments. The patch is now a lot smaller but it still only works if I set the permissions manually. I was hoping that just letting libvirt do its thing would solve that. :/11:20
opendevreviewBalazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal  https://review.opendev.org/c/openstack/nova/+/96013011:22
opendevreviewBalazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal  https://review.opendev.org/c/openstack/nova/+/96013011:27
opendevreviewBalazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal  https://review.opendev.org/c/openstack/nova/+/96013011:32
sean-k-mooneynicolairuckel: thats odd. i guess we can try and replicate the behvior and see if we can avoid this but. did you test this with a new vm? is it possibel that you previous attempet left the files in a non standard state?11:37
sean-k-mooneygibi: by the way the numa in placemetn talk was very good. they also appremntly foudn hand fixed the placment scaling issue in there work11:43
nicolairuckelAh, that could be the problem.11:43
nicolairuckelI didn't create a new VM.11:43
opendevreviewAhmad Hassan proposed openstack/nova-specs master: Offline VM migration using https  https://review.opendev.org/c/openstack/nova-specs/+/96444411:55
opendevreviewMerged openstack/nova master: [doc]PCI in Placement tuning  https://review.opendev.org/c/openstack/nova/+/96328111:58
opendevreviewJulien LE JEUNE proposed openstack/nova stable/2024.2: nova-conductor puts instance in error state  https://review.opendev.org/c/openstack/nova/+/96177512:11
opendevreviewJulien LE JEUNE proposed openstack/nova stable/2024.2: Update start_service() function in test  https://review.opendev.org/c/openstack/nova/+/96384812:16
opendevreviewJulien LE JEUNE proposed openstack/nova stable/2024.2: Adds regression test for bug LP#2085135  https://review.opendev.org/c/openstack/nova/+/96384912:16
opendevreviewJulien LE JEUNE proposed openstack/nova stable/2024.2: Reset the mapped field of nodes at service deletion  https://review.opendev.org/c/openstack/nova/+/96385012:16
gibisean-k-mooney: I looked at their slidset. What I decoded form there is that they found something similar but maybe not exactly the same as they mentioned same_subtree which was not part of our problem or our solution for the PCI case12:36
gibisean-k-mooney: I left some comments / question on the PTG etherpad related to this12:36
sean-k-mooneygibi im not sure if its exactly the same, related or independent fo what you fixed12:37
sean-k-mooneybut yes it would be nice to see what there solution was and if its an addtional enhancement or not needed now12:38
gibiI have a hunch that we could move the same_subtree check also inside the product() call if we want that might help pruning the searchspace in case same_subtree is used for their NUMA solution12:42
gibifor PCI we don't need that but for NUMA RP with multiple children under it it is needed12:42
sean-k-mooneyyep maybe.12:43
sean-k-mooneywe can cross that bridge when we evaulate there solution12:43
gibiyepp12:43
sean-k-mooneythey hope to upstream it 12:43
sean-k-mooneywhich would be cool if it work well12:44
opendevreviewJulien LE JEUNE proposed openstack/nova stable/2024.1: nova-conductor puts instance in error state  https://review.opendev.org/c/openstack/nova/+/96177812:44
sean-k-mooneythey apprently have backported it to yoga internaly had have custoemr using it in production12:44
sean-k-mooneyso at least for there use cases it apprenlty funcitonal at the scale they are using it at12:44
gibiyeah if it not spread or exaggerate the placement performance issue then lets get it, if it is then we need to think a bit more and assess the risk12:44
sean-k-mooneyi also think i agree with them about the ux issue 12:45
sean-k-mooneyi.e. the workaround they had to do for member_of ectra related to the unamed group12:46
opendevreviewJulien LE JEUNE proposed openstack/nova stable/2024.1: Update start_service() function in test  https://review.opendev.org/c/openstack/nova/+/96385112:46
opendevreviewJulien LE JEUNE proposed openstack/nova stable/2024.1: Adds regression test for bug LP#2085135  https://review.opendev.org/c/openstack/nova/+/96385212:46
opendevreviewJulien LE JEUNE proposed openstack/nova stable/2024.1: Reset the mapped field of nodes at service deletion  https://review.opendev.org/c/openstack/nova/+/96385312:46
sean-k-mooneyi forget the explcit excption they said they got but i dont think they shoudl have got that12:46
sean-k-mooneyit would be good to get that into a placmenet bug report so we can assess it properly12:47
sean-k-mooneywith out going into the detail is sounded like a design oversight that could be condiered a bug12:47
gibisure, I'm happy to read incoming bugreports12:49
gibithe slideset is low on details so most of I know are based on guesses and extrapolations12:50
sean-k-mooneywe invited them to the ptg. they have some pto this week so they proably wont have time to prepare much. bauzas added the topic on there behalf but we can try and connect with them on irc or the list seperatly as well12:54
sean-k-mooneygibi: bauzas offered to help them with engaging with the upstream comunity so i assume if they submit a spec they will act as the feature liason or at least helping them if they have any issues with that12:55
UgglaHi sean-k-mooney, I hope you had a nice trip back to your home town. Can you point me to the patch about image encryption (lucks), we need to discuss next weak ?12:59
sean-k-mooneyam sure. the oen that is is currently kind fo blocked is on the glance side one sec13:00
sean-k-mooneyand ya the trip back was pretty ok. of couse when we got back to ireand it was raining and the car was parked in a 1 inch high puddel of water but other hten that it was fine13:01
sean-k-mooneyi more or less went to bed after getting back and slept until 2 am. i went back to sleep but got up again at liek 4 so my slep patther is off but not unexpected13:02
sean-k-mooneyUggla: https://review.opendev.org/c/openstack/glance/+/92629513:02
sean-k-mooneyUggla: how was your train? did you and sylvain travel back together?13:03
Ugglado you think we need to discuss that at the glance/nova cross session ?13:03
sean-k-mooneyya i think we should 13:04
sean-k-mooneythe featuer is addign a new luks disk_format and we need to be able to supprot that in nova13:04
sean-k-mooneyi dont really see how we can supprt dans request ot bea able to valdiate that its a ` luks-encrypted GPT disk image` without breaking the convidental comptue usecases13:05
sean-k-mooneybut i get the concer as well13:06
Ugglasean-k-mooney, it was ok a minor delay, but I managed to be at home around midnight(sunday). Sylvain took the train on Monday morning.13:07
nicolairuckelsean-k-mooney, I have the same problem with a fresh VM.13:07
bauzassean-k-mooney: I already told the train story earlier in the chat. Long story short, never ever take the Lyon-Grenoble line if you want to visit the Alps13:09
sean-k-mooneybauzas: hehe ill keep that in mind :)13:10
elodillesbauzas Uggla : sorry, a bit late, but finally i've proposed the Nova stable release patches (flamingo-caracal). please review them. note that all of them contain some api related code changes, hence all bumps MINOR versions. please review them with extra care that they are OK to release (especially Caracal, which will be the final release, after this point, we won't be able to do any further 14:12
elodillesrelease!) -> https://review.opendev.org/c/openstack/releases/+/964471 (and its parents)14:12
bauzaselodilles: ack, I'm on vtpm review mode but I'll look14:13
bauzasdon't be afraid of harassing me :)14:13
Ugglaelodilles, o/ I'm gonna have a look either later or tomorrow morning, thanks!14:14
elodillesbauzas Uggla : thanks both of you o:) and sorry for already harassing you, but the releases should merge soon, well, the sooner the better, as we should move Caracal to unmaintained in less than a week o:)14:15
elodilles(sorry for not proposing the release patches last week, in that way, i could have harass you IRL at the Summit o:))14:17
Ugglaelodilles 👍14:17
bauzaselodilles: physical harassment is not accepted by the Summit Code of Conduct unfortunately14:36
bauzasbut you could have bribed with beers14:36
opendevreviewBalazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal  https://review.opendev.org/c/openstack/nova/+/96013014:38
opendevreviewBalazs Gibizer proposed openstack/nova master: Rally job for eventlet-removal  https://review.opendev.org/c/openstack/nova/+/96013014:43
opendevreviewYateesh Kumar MN proposed openstack/nova master: Don't destroy TPM during hard reboot  https://review.opendev.org/c/openstack/nova/+/96447514:48
elodillesbauzas: ahh, i've missed the bribe :/ maybe next time then! ;)15:02
UgglaNova meeting in ~40mn15:20
aliI have a question.15:33
aliI have two aggregates named general and dedicated. The availability zone of general is nova, and the zone of dedicated is another one.15:33
aliI wanted to live migrate an instance from the nova zone to the other zone.15:33
aliTo 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.15:33
aliAfter that, I tried to resize the 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.15:33
aliWhy did this happen?15:33
Uggla#startmeeting nova16:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
fwieselo/16:00
r-taketnhello16:00
nicolairuckelo/16:01
UgglaHello everyone16:01
gmaano/16:01
gibio/16:01
elodilleso/16:02
UgglaLet's start16:03
Uggla#topic Bugs (stuck/critical)16:03
Uggla#info No Critical bug16:03
Uggla#topic Gate status16:03
bauzas\o16:03
Uggla#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:03
* bauzas was preparing a coffee on his new barista machine16:03
Uggla#link https://etherpad.opendev.org/p/nova-ci-failures-minimal16:03
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 status16:04
Uggla#info Please look at the gate failures and file a bug report with the gate-failure tag.16:04
Uggla#info Please try to provide a meaningful comment when you recheck16:04
UgglaI have not seen something special about it, unless I miss something.16:04
gibio/16:06
Ugglagibi, bauzas something to say about the gate ?16:06
bauzasnothing on my radar16:06
gibithere was issues with the wsgi package in the jobs using debian16:07
gibicausign python3.11 crashes on the gate mostly in keystone service16:07
gibiI don't have a tracker for it but it was discussed on -qa 16:07
gibiI did not see it today yet but I did not dig for it either16:08
Ugglaok thanks gibi16:08
Ugglamoving on to next topic16:09
gmaanone other thing related to gate. grenade jobs settings are updated and now grenade on master will be testing the correct branches upgrade16:09
Ugglathx gmaan16:09
gmaanstable/2025.2 change still in gate but will be merging soon16:09
gmaan#link https://review.opendev.org/c/openstack/grenade/+/96191416:09
gmaanthat's all, we can move to next topic16:10
Uggla#topic tempest-with-latest-microversion job status16:10
Ugglagmaan anything you want to say  about it ?16:11
gmaanno, did not get chance to look into it.16:11
Ugglano worries, thx gmaan16:11
Uggla#topic Release Planning16:12
Uggla#link https://releases.openstack.org/gazpacho/schedule.html16:12
Uggla^  dates will be discussed and refined during the PTG.16:12
Uggla#info PTG etherpad for 2026.1 is available: https://etherpad.opendev.org/p/nova-2026.1-ptg16:13
Uggla#info Please add the topics you would like to discuss in the above document.16:13
Uggla#info Take care EU daylight time change this Sunday (26 Oct).16:13
Uggla^ confused me last week, so here are the expected timelines16:14
Uggla#info PTG meetings (to be confirmed) will happen room grizzly 14:00UTC (start) -> 17:00UTC (end) 4H from Tuesday to Friday.16:14
Uggla#info Please enter your review comments (what was ok, what is not working...)16:14
UgglaI mean comments for the retro16:14
Uggla#info Please update the courtesy ping list, if you want me to notify you about a particular topic.16:14
Uggla#info You might have a earlier session next week for our contributors from Japan (compute graceful shutdown)16:15
bauzasyeah, not only that16:15
Uggla#info the upstream meeting (this one) will be canceled 16:15
bauzaswe had hallway discussions with some of the Japan contributors, they had a couple of topics to discuss at the PTG16:16
Ugglaoh yes, the metadata protection too.16:16
bauzasso it would be nice if we could book some timeslot earlier in the day that's more asian-friendly16:16
bauzas1 hour should be enough16:16
Uggla1h for the 2 topics ?16:16
bauzas1 hour for *any* topic16:17
gmaanearly sessions you mean during allocated slots right? from 14 UTC onwards or some other time whihc is more close to japan?16:17
bauzasas soon as you open the possibility for folks to join, please don't expect them to not use that possibility for discussing more16:17
Ugglagmaan no I have not requested the timeslot.16:17
bauzasgmaan: 14UTC is already very late for many of them16:18
bauzasJST is UTC+8 I believe16:18
gmaanyeah, it seems 1 AM 16:18
gmaanI want to know if something early than 14 UTC we want to schedule16:18
bauzaswell, that's why we have a conversation now16:18
gmaannot later than 14 UTC16:18
bauzashaving it earlier would mean that we wouldn't have a solid quorum16:19
bauzasso I need to know who could join something earlier16:19
bauzasanother possibility is a very late slot for European, I could try to make it, but again, I'm not sure we would have quorum16:20
gibiI rather be early from EU than late16:20
UgglaYep I think around 9 or 10 UTC.16:22
bauzaswe would miss gmaan, dansmith and melwitt if so16:22
gibiI can join any day on those times16:22
bauzashere is one thought16:22
gmaanyeah, it will be 3 AM in PST16:22
gibiwe can have a discussion and have a recap session during the normal hours so other cores get updated16:23
dansmithyeah 10UTC is pretty early for us16:23
UgglaI just expect gibi, bauzas, sean-k-mooney.16:23
bauzaslet's try to make it at Thursday or Friday EU mornings16:23
gibiI think there is no good single timeslot hence I suggesting two. One with the folks from far east and then one with the core team16:23
sean-k-mooneysorry16:23
bauzasand ask the Asian contributors to put their topics in advance into the etherpad16:23
sean-k-mooneywas on a call16:23
Ugglabauzas, ok I will sync up with them.16:23
sean-k-mooneyreading back are you dicussing the meeting slot16:24
bauzasso people not being to attend can still leave comments on the the etherpad in advance16:24
sean-k-mooneyor ptg16:24
bauzassean-k-mooney: some asian-friendly ptg slot16:24
sean-k-mooneyah ok16:24
bauzasbased on the hallway talks we had at Summit16:24
sean-k-mooneyack16:24
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
aliinstance 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
ali Why did this happen?16:24
bauzasali: we are on a meeting, could you please ask your question after we're done ?16:25
aliok 16:25
bauzasdansmith: 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
Ugglaare we good with that topic ?16:26
dansmithbauzas: I mean.. we don't really have any other option16:26
gmaanI wanted to join the graceful shutdown topic but depends on what time we select 16:26
gmaanone idea, if 13 UTC can work for them though we did not book slot in 13 UTC for nova but can do16:27
bauzasdansmith: well, we could ask them to join again later 16:27
sean-k-mooneywell the other option woudl be do the NA/asia slot16:27
sean-k-mooneyso very late UTC16:28
sean-k-mooneyif there are more na based folks instereted i nthee topics that might work better16:28
sean-k-mooneythat woudl likely have toe bu thrusday however to be in there friday morning 16:29
Uggla23:00 UTC ?16:32
bauzasthat's exactly why I miss in-person PTGs16:33
UgglaI will check with them if the prefer morning/afternoon.16:33
Ugglabauzas, yeah I know.16:33
sean-k-mooneyya.. i dont have a stong opion either way16:33
bauzaswhat we need is a clarified PTG etherpad16:33
gibiif it will be late EU then I would like to get a recap session next day16:33
gibiin the normal slots16:34
bauzaswith a list of topics they want to discuss16:34
bauzasand then we can let people indicate their interest16:34
sean-k-mooneygibi: i think we will wnat to do that in either case16:34
bauzasyup16:34
Ugglabauzas sure, I hope they will get in touch with me soon. If not I'll try to ping.16:34
UgglaSo I could update the schedule.16:34
bauzashaving PTG right after Summit doesn't help, in particular when most of attendees take a few days off after the latter16:35
gibisean-k-mooney: yes16:35
bauzassure, and please people let mention your interest if you wanna speak up on those topics16:35
Ugglacan we move on ?16:36
gibi+16:37
Ugglanext topic16:37
Uggla#topic OpenAPI 16:37
Uggla#link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned16:37
Uggla#info still 28 remaining atm.16:37
Uggla#topic Stable Branches 16:37
* Uggla giving the mic to elodilles16:38
elodillesthanks16:38
elodilles#info stable branches (stable/2025.* and stable/2024.*) seem to be in OK state16:38
elodilles#info final stable 2024.1 Caracal release (and all other stable/202*.* release patches) are proposed: https://review.opendev.org/c/openstack/releases/+/96447116:38
elodilles#info 2024.1 Caracal (stable/2024.1) is planed to move to Unmaintained in less than a week16:38
elodillesand that's all for now about stable from me16:39
Ugglathx elodilles16:39
Uggla#topic vmwareapi 3rd-party CI efforts Highlights16:39
Ugglafwiesel anything you'd like to tell us ?16:39
fwiesel#info Cinder VMware bug fixed for reimaging volume16:39
fwiesel#link https://review.opendev.org/c/openstack/cinder/+/96135716:40
fwieselTook a while, but that was blocking me from fixing the last two failing tempest tests.16:40
fwieselThat and the still broken CI16:40
fwieselBut that's it from my side16:40
fwieselUggla: back to you16:41
Ugglathanks fwiesel, thx correting this16:41
Uggla#topic Gibi's news about eventlet removal.16:41
Ugglagibi anything to report ?16:41
gibio/16:42
gibibasically the same as last week16:42
gibi* please look at the topic in the PTG etherpad16:43
gibi* you can review things on the eventlet-removal topic, we have couple of smallish green patches on the unittest side16:43
gibi+ I finally get back to the rally job patch and iterating on it https://review.opendev.org/c/openstack/nova/+/96013016:44
gibithat is is16:44
gibiit16:44
Ugglagibi, fyi I gave some ad about eventlet testing at the end of my presentation.16:45
UgglaExplaining that if folks want to test it that would be hihgly appreciated.16:46
gibiUggla: thanks16:46
gibiwas there any further question about it?16:46
Ugglayes, just one about the overall plan : If all the services will remove eventlet.16:46
Ugglaand I explained quickly our approach for nova. 2 steps phases and current services "migrated"16:47
UgglaThen I got a question about python 3.14 support for us, from Canonical guys.16:48
gibiyeah I have no comment on 3.14. That is too far ahead 16:48
gibiI would assume that with GIL mode and threading we will work in 3.14 without issues16:49
Ugglayep I said that and explain that it will probably happen after eventlet removal.16:49
gibithe GILles mode is a different beast probably16:49
Ugglasure, tbh I did not have the time to speak about GIL.16:49
gibi:)16:50
UgglaEspecially 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:50
gibiohh 16:51
gibianyhow thanks for the advertisment16:51
Ugglamoving on because we are almost at the top of the hour16:51
Uggla#topic Open discussion 16:51
Ugglareminder:16:51
Uggla(Uggla) Pool for the new schedule of upstream meeting: https://framadate.org/ao12zK6wR3K3nfbF16:51
Uggla#linkAnnonce : https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/H5PBFZJ4X3TSGSC4YF6E4WTV43CBOVS6/16:51
Ugglathe trend seems to go on Monday16:52
nicolairuckelI 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:52
nicolairuckelAlso, 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:53
Ugglanicolairuckel, yep please do16:54
Ugglacrossproject with cinder ?16:54
nicolairuckelI think so16:55
nicolairuckelI was told it was related to image encryption16:55
Ugglamore glance though16:55
nicolairuckeltbh, I'm still quite new to openstack so I'm not *that* sure about the scope yet.16:55
Ugglaok I'll look at that and try to find the appropriate slot.16:56
nicolairuckelthank you16:56
UgglaAny expected duratio, ?16:56
Uggla*duration16:56
sean-k-mooneygibi: supporting freethread pytyon is defeintly a post eventlet topic.16:56
Ugglar-taketn I think you would like to share something, aren't you ?16:57
sean-k-mooneynicolairuckel: the nvram patch is not related to the image encyption work16:57
nicolairuckelI'm not sure yet. I'll think about that and add it to the Etherpad if that's okay.16:57
r-taketnyes. Thank you. I have one quick request. Could someone please check this spec and give some feedbacks later?16:57
r-taketn#link https://review.opendev.org/c/openstack/nova-specs/+/96257816:58
r-taketnI have proposed this spec for generalizing sev/sev-es code to add new confidential computing from other architecture(Intel TDX,Arm CCA)16:58
sean-k-mooneybut we shoudl dicuss the imange encyption work in the nova/glance slot.16:58
r-taketnI have re-written the spec. In particular, I detailed the problem description about current sev/sev-es code.16:58
sean-k-mooneyr-taketn: i have not had time yet but ill tray and look at that again16:58
r-taketnI have this topic on ptg slot, but I'd appreciate if you give some feedbacks in advance16:58
r-taketnsean-k-mooney: Thank you16:59
sean-k-mooneythe real goal of this work is to enabel you to supprot arm CCA and SEV-SNP more eaisly in the future right16:59
r-taketnyes16:59
sean-k-mooneythis is prepareing the memory encyption logic to be more generic and extensible in advance of the hardware16:59
sean-k-mooneyr-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 deliverd17:01
gibisorry folks I have to drop.17:01
gibiI will read back17:02
Ugglagibi no pb about to close17:02
sean-k-mooneyr-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#L28717:02
UgglaAnything else you'd like to share ?17:02
sean-k-mooneyyou 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#L5017:02
r-taketnsean-k-mooney: ok. sorry. I'll fix it.17:03
sean-k-mooneyr-taketn: the sev spec is a good example fo what level of detail ectra is expected that you can use as a guide17:03
bauzaswe're overtime :)17:03
Ugglabauzas atm reasonable overtime17:03
r-taketnUggla: That's all from me. thank you17:04
Ugglaok so I'm going to close.17:04
UgglaThank you for participating in this meeting.17:04
sean-k-mooneyr-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 regardless17:05
Uggla#endmeeting17:05
opendevmeetMeeting ended Tue Oct 21 17:05:19 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:05
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2025/nova.2025-10-21-16.00.html17:05
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2025/nova.2025-10-21-16.00.txt17:05
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2025/nova.2025-10-21-16.00.log.html17:05
elodillesthanks Uggla o/17:05
Ugglaelodilles you are welcome.17:05
r-taketnThank you for discussion all17:05

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!