16:00:26 #startmeeting nova 16:00:26 Meeting started Tue Nov 14 16:00:26 2023 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:26 The meeting name has been set to 'nova' 16:00:39 o/ 16:00:42 I was about to write 'startmeeting nvidia' 16:00:48 :S 16:00:52 ETOOMANYTHINGS 16:00:53 o/ 16:01:05 someone spend too much time with nvidia things? :-o 16:01:07 #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 16:01:18 elodilles: probably me, but who guesses ? 16:01:22 :) 16:02:03 o/ 16:02:11 o/ 16:02:12 let's start 16:02:19 and let's be quick 16:02:26 #topic Bugs (stuck/critical) 16:02:30 #info No Critical bug 16:02:34 #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 32 new untriaged bugs (+0 since the last meeting) 16:02:37 #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster 16:02:55 elodilles: anything you want to tell about bugs ? 16:03:00 (damn, it was 31 one hr ago..) 16:03:06 nothing to tell 16:03:12 cool 16:03:16 had little time to deal with bugs :/ 16:03:33 auniyal6: want to be the next for triaging ? 16:04:45 okay, given his TZ, he's probably off 16:04:57 no worries at all, will discuss with him later tomorrow 16:05:42 #info bug baton may be auniyal 16:05:48 #topic Gate status 16:05:53 #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:05:57 #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status 16:06:02 periodics are green 16:06:06 #info Please look at the gate failures and file a bug report with the gate-failure tag. 16:06:19 dansmith: what's up with the grenade vnc failure ? 16:06:27 long since fixed? 16:06:31 because melwitt 16:06:33 \o/ 16:06:57 okay, so, no other gate issues we just discovered this week ? 16:07:09 o/ 16:07:30 this is not new... but as you may now the earlier issue with sqlalchemy 2.0 job has been fixed and it should be green now 16:07:40 so we can merge https://review.opendev.org/c/openstack/nova/+/900538 to make the job voting again 16:08:06 tkajinam: ahah, good time for telling this, we're on a meeting and we discuss about CI failures :) 16:08:07 (which is waiting for 2nd +2 16:08:25 yeah I saw it and that's why I jumped in here ;-) 16:08:32 tkajinam: sent to the gate 16:08:50 thanks ! 16:09:21 tkajinam: perfect timing ! ;-) 16:09:21 anyway, anything else to say about failures ? 16:09:34 looks not 16:09:36 #topic Release Planning 16:09:40 #link https://releases.openstack.org/caracal/schedule.html 16:09:44 #info Nova deadlines will be proposed in the schedule above 16:09:50 ... once I have time :) 16:09:54 #info Caracal-1 milestone this week 16:10:04 I also need to look at my gerrit emails :) 16:10:22 elodilles: have we already a release change for it ? 16:10:32 * bauzas goes looking at Gmail 16:10:32 changes were generated yes 16:10:36 let me look 16:11:15 os-vif is proposed https://review.opendev.org/c/openstack/releases/+/900762?usp=email 16:11:17 and as i see there's no nova related caracal-1 release 16:11:21 but I don't see nova in my mailbox 16:11:58 elodilles: cool, will check emails later 16:12:07 so, something else 16:12:26 I wrote 2 weeks before that today is an implementation review day 16:12:30 of course, I forgot about it 16:12:39 bauzas: btw, you told some time ago that we could release beta/milestone releases off nova. do you want me to propose a patch for that? 16:12:52 so, would people agree with us having an implementation review day tomorrow ? 16:13:44 bauzas: ++ 16:13:49 elodilles: what have I said ? 16:13:54 :) 16:14:12 I mean, I can surely propose a m-1 release change if nobody does this 16:14:39 for cycle-with-rc (like nova) release team does not generate release patches 16:14:40 that said, I don't know how many people use that tag tbh 16:14:49 doh my bad 16:14:53 then I'll do my duty 16:15:25 bauzas: i'm just asking :) maybe i misheard something :) 16:15:54 I honestly can't remember anything, apart the fact I think noone is using milestone-1 tag 16:15:59 milestone-3 for sure 16:16:17 but the first two ones are just there for nothing :) 16:16:22 OK, then i'll wait for Caracal-3 :) 16:16:33 ACK :) 16:16:51 sorry for the noise :X 16:16:58 nah, I'll create caracal-1 and caracal-2 because creating a tag named "caracal-3" alone would be super bizarre, right ? :D 16:17:25 we're not Microsot 16:17:31 Microsoft* 16:17:36 anyway 16:17:42 #action bauzas to propose caracal-1 tag 16:17:51 #undo 16:17:51 Removing item from minutes: #action bauzas to propose caracal-1 tag 16:17:57 #action bauzas to propose caracal-1 tag for nova and placement 16:17:57 (it won't be caracal-3, it'll be 29.0.0.0b1 ;)) 16:18:28 I'm lost and don't have a lot of time, but I trust you 16:18:37 anyway, thanks for asking 16:18:50 np 16:18:51 so, back on track 16:19:09 I heard dansmith saying yay for tomorrow being implementation review day 16:19:15 who else nays ? 16:19:59 yay from me 16:20:10 at least I can add implementation to review :) 16:20:18 cool 16:20:21 heh 16:20:27 https://review.opendev.org/q/topic:bp%252Flibvirt-migrate-with-hostname-instead-of-ip 16:20:33 I admit I'm biased since I just pushed an implementation _to_ review :P 16:20:40 #agreed Tomorrow (Nov 15) will be implementation review day 16:20:42 same here :) 16:21:21 #action bauzas to create an etherpad for tracking features and bugs like we agreed at PTG, so it would be used tomorrow 16:21:25 well any review that are rety can be reviewd including they ones you just pushed so 16:21:39 I too much punted that action item 16:22:07 #action bauzas to notify by email about both the implementation review day and the etherpad to use 16:22:18 the email will be late today for sure 16:23:22 #topic Review priorities 16:23:32 #action bauzas need to create the etherpad he just said above 16:23:41 #topic Stable Branches 16:23:46 elodilles: I'm all ears 16:23:53 o7 16:24:02 #info stable gates don't seem blocked 16:24:20 i've seen some failing jobs but nothing constantly failing... 16:24:34 (or I'm not aware of it) 16:24:41 #info stable release patches still open for review: https://review.opendev.org/q/project:openstack/releases+is:open+intopic:nova 16:24:53 +1: yoga is going to be unmaintained, so final stable/yoga release should happen ASAP - https://etherpad.opendev.org/p/nova-stable-yoga-eom 16:25:34 if we want to do a final release at all 16:26:01 that's a need 16:26:08 otherwise we can just live with the last release from summer(?) 16:26:20 elodilles: nah, I'd prefer we do some release 16:26:31 elodilles: bug me this week or next week 16:26:37 now we have 1 merged patch as can be seen in the etherpad 16:26:50 I guess you know that I'm busy, so I'll forget if nobody harasses me 16:27:11 bauzas: i'll ping you then some time 16:27:18 thanks 16:27:31 the open patches are also listed on the etherpad 16:27:40 I'm unfortunately not very good at doing multiple things at the same time 16:27:42 feel free to use the pad, edit it if you want 16:27:50 like, my mind is not good for concurrency 16:28:46 i'll try to add details to the pad so that will be easier to reviewers to look at 'things-to-be-reviewed' 16:28:54 ack 16:29:01 anyway, last but not least: 16:29:04 #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci 16:29:25 add stable gate issues here if you find one ^^^ 16:29:36 and that was all from me 16:30:08 cool 16:30:13 last topic 16:30:19 #topic open discussion 16:30:22 anything anyone ? 16:30:26 o/ In the open discussion topic I would like to remind about ability to reviwe this cool spec file:) https://review.opendev.org/c/openstack/nova-specs/+/895924/8 16:30:35 Sorry, I forgot to fill agenda with this 16:30:43 i have two related things we we can talk about after ^ 16:31:40 dvo-plv: if dansmith and bauzas feel stronly that the tait is not required and want to use a min compute service check instead i can relent on that 16:32:00 but you will need to modify the spec to say that the feature will only work when its fully upgraded 16:32:20 bauzas: dansmith ^ is that still your prefernce 16:32:39 I have never been super opinionated about it.. I'm pretty meh all around 16:32:50 i beleive that we alreadt agreed with trait usage 16:32:52 I still feel like a trait is just too much work for such a thing 16:33:13 I added upgrade impact https://review.opendev.org/c/openstack/nova-specs/+/895924/8/specs/2024.1/approved/virtio_packedring_configuration_support.rst#126 16:33:33 dvo-plv: is this what you wanted to discuss by the way 16:33:43 i want to make sure we have a path to unblocking you 16:34:27 yes, I also want a path to unblock this feature and i thought that nova core already agreed with that 16:34:41 so I've updated spec and nova code 16:34:46 im fine with the trait i assuemd that was the only open 16:34:54 i can re review the new version of the spec 16:35:02 I think I said loudly a couple of times that I eventually give up 16:35:18 so, I let other cores accept using traits 16:36:04 my only concern is that I just want to make sure nobody would use that trait in a flavor so we could eventually remove it if we want, but given I won't review the spec, I leave others to say what they want 16:36:47 I suggest to add thi item somewhere regarding trait usage 16:37:09 but it does not required as far as it will assigned automatically 16:37:45 https://review.opendev.org/c/openstack/nova/+/876075/27/nova/scheduler/request_filter.py#275 here for instance 16:38:08 https://review.opendev.org/c/openstack/nova/+/876075/27/nova/virt/libvirt/driver.py#12429 here for node 16:40:33 so can i suggest we take a look at this (the spec and the implematnion) tomorrow n the implemation review day 16:40:37 for those that are interested 16:40:58 I am not but that's a good idea 16:41:24 anyway, can we end the meeting now ? 16:41:34 i would like to add 2 thigns quickly 16:41:42 https://blueprints.launchpad.net/nova/+spec/remove-hyperv-driver and https://blueprints.launchpad.net/nova/+spec/remove-vmware-support 16:42:00 are we ok to appove those or would you like use to expeand the description with more details 16:42:35 I think gmann wrote specs 16:42:45 yes which they abandoned 16:42:51 okay 16:42:55 because multiple of us said it was not requried 16:42:58 so we need to review both blueprints in a meeting 16:43:04 yeah, including me 16:43:11 Thank you 16:43:17 so i just want to decied on a path forward for the paper work 16:43:21 but I don't wanna force someone to not write a spec if he/she really wants to :) 16:43:22 if we want to review them next week we can 16:43:37 but i would like to merge the first patches for the removal sooner rather then later 16:43:38 sure 16:43:44 and sure 16:43:58 bauzas: i was orgianlly hoping ot merge the vmware removal patch tomorrow in the implemation day 16:44:02 but it can wait 16:44:12 then, we can approve those today 16:44:15 folks, 16:44:32 anyone having concerns with https://blueprints.launchpad.net/nova/+spec/remove-hyperv-driver as a specless BP for one ? 16:46:26 im fine with that. for the vmware one i do have more patches ill need to write to complete the removal but the inital patch https://review.opendev.org/c/openstack/nova/+/897017 is the entirty of the driver removal. i need to remove the console and objects in follow up patches 16:46:38 okay, so 16:46:52 #agreed https://blueprints.launchpad.net/nova/+spec/remove-hyperv-driver to be accepted as a specless bp 16:46:57 next one 16:47:22 anyone having concerns with https://blueprints.launchpad.net/nova/+spec/remove-vmware-support as a specless BP ? 16:47:59 sean-k-mooney: the fact that you have left things to implement is just some implementation nit 16:48:03 we can still approve the bp 16:48:09 yep 16:48:14 like we did with nova-net 16:48:21 just wanted to clarify that since we expanded the scope at the ptg 16:48:23 anyone having concerns again ? 16:48:33 okay so 16:48:50 #agreed https://blueprints.launchpad.net/nova/+spec/remove-vmware-support to be accepted as a specless BP 16:48:54 there we go 16:49:11 sean-k-mooney: I'll just set the LP fields right after the meeting 16:49:15 thanks 16:49:18 thats all from me 16:49:23 and we can start to review your patches tomorrow 16:49:26 cool 16:49:35 so, let me call it a wrap 16:49:42 thanks all 16:49:45 #endmeeting