16:03:18 <bauzas> #startmeeting nova
16:03:18 <opendevmeet> Meeting started Tue Feb  4 16:03:18 2025 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:18 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:18 <opendevmeet> The meeting name has been set to 'nova'
16:03:27 <bauzas> sorry I was on a meeting
16:03:42 <sean-k-mooney> o/
16:03:48 <r-taketn> o/
16:03:53 <masahito> o/
16:03:58 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:04:16 <gibi> o/
16:04:45 <elodilles> o/
16:05:44 <sean-k-mooney> while we get started i have one item for open discuss, specificaly corrdinating patches and microversion for the 3 api feature we have in flight. i would like to propose  spice 2.98 schduler hitns 2.99 and image properties 2.100
16:05:54 <sean-k-mooney> we can loop back to that later in the meeting
16:06:04 <bauzas> sean-k-mooney: sure, that's a good ask
16:06:19 <bauzas> we'll discuss that in open discussion
16:06:31 <bauzas> let's start
16:06:34 <bauzas> #topic Bugs (stuck/critical)
16:06:40 <bauzas> #info One Critical bug
16:06:46 <bauzas> #link https://bugs.launchpad.net/nova/+bug/2070501
16:07:12 <bauzas> I don't know why the bug state changed, that one looks to be fixed
16:07:43 <dansmith> o/
16:07:48 <Uggla> o/
16:08:06 <bauzas> unless people argue, I'll set again the bug state to Invalid
16:08:36 <sean-k-mooney> it look like it was triage by someone
16:08:45 <bauzas> yup
16:08:50 <sean-k-mooney> i think revert back to invalid is correct
16:08:51 <bauzas> moving it back to Invalid
16:08:55 <bauzas> moving on then
16:09:02 <bauzas> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:09:08 <bauzas> #topic Gate status
16:09:14 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:09:20 <bauzas> #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:09:25 <bauzas> #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:09:58 <bauzas> I clicked on that page 30 mins before and I'm still awaiting the result
16:10:19 <bauzas> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:10:25 <bauzas> #info Please try to provide meaningful comment when you recheck
16:11:17 <bauzas> okay, I won't wait too much, moving on
16:11:25 <bauzas> anything about the gate state ?
16:11:38 <bauzas> fwiw, I started back to look at upstream and AFAIK, nothing new
16:12:14 <bauzas> okay, crickets
16:12:21 <bauzas> I guess it's time to go to the next topic
16:12:30 <bauzas> #topic Release Planning
16:12:37 <bauzas> #link https://releases.openstack.org/epoxy/schedule.html
16:12:43 <bauzas> #info Nova deadlines are set in the above schedule
16:12:49 <bauzas> #info 3 weeks before Feature Freeze
16:12:55 <bauzas> #link https://review.opendev.org/c/openstack/releases/+/940363 os-traits was released this week
16:13:15 <bauzas> time is flying
16:13:19 <sean-k-mooney> we may want to do another release of os-traits
16:13:37 <bauzas> that was planned in my mind
16:13:42 <sean-k-mooney> there are some nice to have triats for the spice-direct supprot
16:13:54 <bauzas> I definitely want to go back reviewing this week
16:14:01 <sean-k-mooney> so if we proceed with merging those we shoudl ideally do another one this week
16:14:02 <bauzas> so I'll probably figure out when to release traits
16:14:17 <bauzas> sean-k-mooney: cool
16:14:28 <bauzas> moving on the status, because we could disucss that there
16:14:35 <bauzas> #topic Review priorities
16:14:39 <fwiesel> o/
16:14:42 <bauzas> #link https://etherpad.opendev.org/p/nova-2025.1-status
16:14:53 <bauzas> the etherpad is stale but I'll update it tomorrow
16:15:28 <bauzas> for traits, I could also look at the existing series and try to organize a list of traits changes to review
16:15:35 <bauzas> those things are small
16:16:05 <bauzas> sean-k-mooney: for the question you asked at the beginning, that's probably the right time to talk about it
16:16:35 <bauzas> sean-k-mooney: so you wanna want to prioritize all the API changes by a list ? I'm like fine with that, we did this previously IIRC
16:16:56 <sean-k-mooney> yes so we have 3 api changes competing for 2.98
16:17:21 <sean-k-mooney> i woudl like to merge the speic direct patches with that since it was there first effectivly
16:17:49 <sean-k-mooney> the other two serise are the two to add schduler hints to server show and image properties
16:18:13 <sean-k-mooney> im not sure about the sate of the later two series in terms fo which can merge first
16:18:33 <gibi> does the spice series close to land?
16:18:48 <sean-k-mooney> i am +2 on the first 3 patches which is up to the api change
16:19:02 <bauzas> I basically have no clear view on the mergeable state of those 3 series :(
16:19:05 <sean-k-mooney> the final too add sound devices and usb to spice
16:19:10 <bauzas> but we can try something
16:19:17 <sean-k-mooney> so those are optional and can merge later
16:19:37 <sean-k-mooney> gibi: so up to here https://review.opendev.org/c/openstack/nova/+/924844/29 yes
16:19:50 <bauzas> what we can do for THIS week is to try to merge spice-direct API microversion
16:19:51 <sean-k-mooney> thats the mvp for that feature
16:19:59 <gibi> ack
16:20:18 <bauzas> if we're not able to merge it, then we can discuss whether one of the two other API patches can merge before that one
16:20:29 <bauzas> let's say during the nova meeting
16:20:47 <bauzas> call it sprint, call it runway, I don't care
16:20:57 <sean-k-mooney> does anyone know the state of the other two api series?
16:20:58 <bauzas> but let's try to merge spice-direct first
16:21:24 <sean-k-mooney> im hopign to take a pass over both thise week but have not been following them closely
16:21:32 <gibi> sean-k-mooney: I have a one week old context on the image properties
16:21:35 <ratailor> sean-k-mooney, functional tests are failing on my series.
16:21:48 <gibi> there we needed extend the series for the rebuild response
16:21:58 <gibi> I think the same requirement is true for the scheduler hints
16:22:17 <sean-k-mooney> ack i think doug is working on that currently but i dont know the eta
16:22:31 <sean-k-mooney> so soudn like either of those could be 2.99 and the other will get 2.100
16:22:38 <gibi> yepp
16:22:44 <ratailor> sean-k-mooney, for this https://review.opendev.org/c/openstack/nova/+/939649 I am also not sure how to correctly write rebulid schema validation.
16:23:12 <sean-k-mooney> it shoudl be identical to the server show repsponce schema
16:23:45 <gibi> sean-k-mooney: there is no server show response schema yet in tree :)
16:23:53 <bauzas> is anyone merging 2.100 getting a perk ? :)
16:23:53 <sean-k-mooney> there is
16:23:56 <gibi> rebuild has it, it needs to be extended
16:24:05 <ratailor> sean-k-mooney, there is no server show response schema here https://opendev.org/openstack/nova/src/branch/master/nova/api/openstack/compute/schemas/servers.py
16:24:26 <sean-k-mooney> i tough ti linked to the chagne where it was added
16:24:44 <sean-k-mooney> maybe show is using the rebuild schdmea but i tought this was merrged in novmber
16:24:55 <ratailor> gibi, but the catch here is that we are adding 'image_properties' in 'properties' subkey and 'properties' has special meaning in schema validation, so we might need to change it to 'image_properties' in response.
16:24:56 <sean-k-mooney> we can follow up after the metting
16:25:15 <bauzas> are we then clear with what I proposed ?
16:25:22 <ratailor> sean-k-mooney, sure.
16:25:31 <sean-k-mooney> oh ok stephn responded so rebuild is there btu show is still pending
16:25:42 <gibi> sean-k-mooney: yep that is my view
16:26:25 <gibi> ratailor: even if properties is a keyword for jsonschema we should have a way to have a schema that matches a field called properties :) but I have to load context and dig
16:26:49 <sean-k-mooney> ok ya looking at https://review.opendev.org/c/openstack/nova/+/915743/8/nova/api/openstack/compute/schemas/servers.py that correct.
16:27:15 <sean-k-mooney> gibi: oh does it not like having a feild in the repsonce called properties
16:27:33 <ratailor> gibi, sure. Thanks! that would be helpful.
16:29:10 <bauzas> can we move on folks ?
16:29:14 <sean-k-mooney> yep
16:29:21 <bauzas> I think we agreed on the plan
16:29:32 <sean-k-mooney> we can pick this up on gerrit or after the meeting
16:29:36 <bauzas> we'll look where we are next week
16:29:46 <bauzas> cool
16:29:54 <bauzas> #topic Stable Branches
16:29:59 <bauzas> elodilles: welcome back
16:30:02 <elodilles> o/
16:30:06 <elodilles> #info nothing to report, stable gates seem to be healthy
16:30:13 <elodilles> #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:30:19 <elodilles> that's all i got
16:32:18 <bauzas> thanks
16:32:24 <bauzas> moving on
16:32:33 <bauzas> #topic vmwareapi 3rd-party CI efforts Highlights
16:32:40 <bauzas> fwiesel: hello
16:33:03 <bauzas> any news so far ?
16:33:06 <fwiesel> So, I fixed the "regression". As it turns out, I didn't clean properly up after each run in the network department, which eventually became too much.
16:33:41 <fwiesel> Looking at the past test runs, it looks fairly stable with the one know broken test.
16:33:43 <bauzas> bravo then
16:33:45 <fwiesel> That's from my side.
16:34:03 <bauzas> excellent news and thanks for the hard work on investigating the root cause and fixing it
16:34:26 <bauzas> #topic Open discussion
16:34:47 <bauzas> I have one topic
16:35:04 <r-taketn> bauzas: I want to add one topic (request) , is it ok?
16:36:08 <bauzas> r-taketn: sure, I'm just grabbing some email link, sec
16:36:52 <r-taketn> I have another topic to mention from last week..
16:37:08 <bauzas> there we go
16:37:21 <bauzas> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/3DBNNHXAPGVUX44NHH43WTDFMIDJ3X5U/
16:37:30 <bauzas> disabling the instance info caching
16:37:47 <bauzas> sean-k-mooney: I guess we can move forward and propose the patch, then ?
16:38:13 <bauzas> we said to look at the results this week
16:38:23 <bauzas> and the only person who replied was very happy with it
16:38:44 <bauzas> sean-k-mooney: so I guess you'll propose the instance info cache disabling patch
16:38:55 <sean-k-mooney> ah well the patch is already up
16:39:00 <sean-k-mooney> so we can proceed with the review
16:39:10 <bauzas> oh my bad you're right
16:39:13 <sean-k-mooney> https://review.opendev.org/c/openstack/nova/+/939476
16:39:29 <bauzas> I'll then proceed with the review
16:40:04 <sean-k-mooney> i have at least one typo to correct so ill respin it this evnnign or tomorrow
16:40:12 <bauzas> ++
16:40:14 <bauzas> cool
16:40:17 <sean-k-mooney> so if there are other comments ill try and adress those too
16:40:20 <bauzas> r-taketn: your turn then
16:40:46 <r-taketn> ok, i just added topic today's agenda.
16:40:56 <r-taketn> Request for replies on the following - About RDT/MPAM feature
16:41:04 <r-taketn> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/HIKLBMNMTJR6GFPKFKODECMR56SYPT5J/
16:41:07 <bauzas> oh sorry
16:41:25 <bauzas> I removed it because I was thinking it was the topic we discussed last week
16:41:29 <bauzas> but indeed, this is different
16:41:46 * bauzas clicks on the email
16:41:59 <r-taketn> Yes. I have another topic to mention from last week.
16:42:08 <r-taketn> I'm considering the feasibility of MPAM/RDT feature within OpenStack to solve noisy neighbor problems on VM clouds.
16:42:08 <sean-k-mooney> r-taketn: the best way to move forward with that is to start a spec and bring it up to dicuss in the ptg
16:42:50 <sean-k-mooney> r-taketn: depending on how its mature it may be something that can be supproted
16:42:54 <bauzas> agreed
16:42:59 <sean-k-mooney> its a very invasive change
16:43:27 <sean-k-mooney> which is partly why the previous efforts were abandonded
16:44:18 <bauzas> r-taketn: the PTG dates are now known
16:44:18 <r-taketn> I intended to discuss the feasibility of this before submitting spec because its implementation will not be simple
16:44:33 <bauzas> r-taketn: would you be able to join us remotely ?
16:45:09 <r-taketn> sure.
16:45:20 <bauzas> cool thanks
16:45:29 <bauzas> then let's discuss this at the PTG
16:45:39 <bauzas> I need to create an etherpad for tracking those topics
16:45:43 <sean-k-mooney> r-taketn  i was off on firday and yesterday so i have not fully read your latest post on this topic
16:45:53 <sean-k-mooney> ill see if i can do that later today
16:46:12 <r-taketn> sean-k-mooney: Thanks
16:46:58 <r-taketn> It's for confirming. Should I submit a spec before the PTG?
16:47:07 <bauzas> it would be nice
16:47:17 <bauzas> fwiw, I just created a PTG etherpad
16:47:20 <sean-k-mooney> it does not hurt to do so, it give use somethign concrete to dicuss
16:47:22 <bauzas> #link https://etherpad.opendev.org/p/nova-2025.2-ptg
16:47:38 <bauzas> r-taketn: could you please add your two topics at the bottom of that etherpad ?
16:47:49 <r-taketn> ok, i'll prepare
16:47:58 <r-taketn> bauzas: ok i'll add
16:48:00 <bauzas> the one we discuss last week and the other one from this week
16:48:09 <bauzas> r-taketn: thanks
16:48:17 <bauzas> I'll also add a couple of topics too
16:48:27 <bauzas> and I'll tell about the PTG etherpad next week
16:49:24 <bauzas> are we done for today?
16:49:27 <masahito> is it okay to start adding some topics on the etherpad?
16:49:34 <MengyangZhang[m]> I have a question. I was wondering if it is still possible to request an exception to add this bp https://blueprints.launchpad.net/openstack/?searchtext=add-burst-length-support to Eproxy. The code change is minor and is ready for review https://review.opendev.org/c/openstack/nova/+/939490
16:49:37 <masahito> it's quick question.
16:49:46 <sean-k-mooney> r-taketn: https://review.opendev.org/c/openstack/nova-specs/+/662264 was the spec i wrote for RDT 5 years ago just an fyi.
16:50:03 <bauzas> masahito: yes indeed, you can add topics
16:50:14 <sean-k-mooney> MengyangZhang[m]: its very very late to do that
16:50:14 <masahito> thanks.
16:50:34 <bauzas> MengyangZhang[m]: yeah unfortunately, we're past approval freeze from 3 weeks now
16:50:42 <bauzas> and feature freeze is in 3 weeks too
16:51:18 <bauzas> the main reason why we have that approval freeze is for making sure we have enough capacity to review all the already approved ones
16:51:55 <MengyangZhang[m]> understood sorry i was away for two weeks, so i will need to resubmit it for 2025-02?
16:51:57 <bauzas> that wouldn't be fair to unprioritize some reviews by looking at some other patch, whatever big it is
16:52:06 <r-taketn> sean-k-mooney: thanks, and sorry,  i have not checked it.
16:52:17 <bauzas> MengyangZhang[m]: unfortunately yes
16:52:36 <MengyangZhang[m]> okk will do
16:53:00 <bauzas> thanks
16:53:04 <bauzas> I guess we're done then
16:53:06 <bauzas> thanks all
16:53:09 <sean-k-mooney> MengyangZhang[m]: the folder is already created and the specs for next cycle are open for review, so this could be done early next cycle
16:53:09 <MengyangZhang[m]> do i need to re-attend nova meeting once that's updated?
16:53:53 <sean-k-mooney> not nessisarly we can just review it once its posted
16:54:02 <MengyangZhang[m]> okk thanks!
16:54:29 <bauzas> MengyangZhang[m]: you don't need to attend the meeting in person, but please add it in our agenda for asking for a specless blueprint when you want
16:55:03 <MengyangZhang[m]> ok do you have a link to the agenda?
16:55:26 <bauzas> https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:55:39 <MengyangZhang[m]> thanks!
16:55:42 <bauzas> just add it in the open discussion and request for a specless blueprint approval
16:56:56 <bauzas> see the documentation here for trivial features approval https://specs.openstack.org/openstack/nova-specs/readme.html#trivial-specifications
16:57:30 <bauzas> or ping me whenever you want
16:57:38 <bauzas> anyway, we're almost at time
16:57:43 <MengyangZhang[m]> thanks!
16:57:44 <bauzas> anything anyone ?
16:58:08 <bauzas> then thanks all
16:58:12 <bauzas> #endmeeting