16:00:54 <bauzas> #startmeeting nova
16:00:54 <opendevmeet> Meeting started Tue Nov 28 16:00:54 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:54 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:54 <opendevmeet> The meeting name has been set to 'nova'
16:00:59 <elodilles> o/
16:01:02 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:06 <bauzas> who's around ?
16:01:10 <fwiesel> \o
16:02:42 <auniyal6> o/
16:03:06 <Uggla> o/
16:03:40 <bauzas> okay let's start
16:03:48 <bauzas> #topic Bugs (stuck/critical)
16:03:53 <bauzas> #info No Critical bug
16:03:56 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 38 new untriaged bugs (+1 since the last meeting)
16:04:06 <bauzas> I've triaged two simple bugs
16:04:23 <bauzas> maybe gmann could look at https://bugs.launchpad.net/nova/+bug/2044035
16:05:33 <bauzas> nothing else to say
16:05:40 <bauzas> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:05:44 <bauzas> #info bug baton is gibi
16:05:47 <bauzas> shit
16:05:49 <bauzas> #undo
16:05:49 <opendevmeet> Removing item from minutes: #info bug baton is gibi
16:05:51 <bauzas> sorry
16:05:59 <bauzas> gibi: can you actually take the baton ?
16:08:59 <bauzas> looks gibi is not there, we'll see later
16:09:01 <bauzas> moving on
16:09:47 <bauzas> #topic Gate status
16:09:52 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:09:57 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:10:04 <bauzas> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:10:21 <bauzas> nova-emulation still fails :(
16:10:31 <bauzas> #link https://zuul.openstack.org/build/13439683a24840f8b7a358c5e51e5c4e
16:10:37 <sean-k-mooney> it likely will until someone has time to fix it
16:11:14 <sean-k-mooney> to be clear looking at the output only 1 test failed
16:11:42 <dansmith> gate is not very healthy
16:12:02 <dansmith> I've been rechecking something for a while and can't make it past
16:12:23 <dansmith> 13 rechecks so far :/
16:12:46 <dansmith> this is my last day of the year, unfortunately, so I'm hoping someone else can take up the charge of trying to track down and improve things
16:13:25 <bauzas> yeah I've seen some rechecks
16:13:41 <bauzas> I'll see if I have time... after all those mdev thingies unfortunately :(
16:14:22 * gibi joins late
16:14:53 <bauzas> anyway, I don't think we can discuss anything now
16:15:18 * gibi does not make promises
16:16:33 <bauzas> shall we move on ?
16:16:40 <bauzas> gibi: ack
16:18:45 <bauzas> #topic Release Planning
16:18:49 <bauzas> #link https://releases.openstack.org/caracal/schedule.html#nova
16:19:03 <bauzas> (the releases patch got merged :) )
16:19:21 <elodilles> \o/
16:19:26 <bauzas> next week, we'll have a spec review day
16:19:48 <bauzas> #info Spec review day planned next Dec 5th 2024
16:19:53 <bauzas> #unso
16:19:56 <bauzas> #undo
16:19:56 <opendevmeet> Removing item from minutes: #info Spec review day planned next Dec 5th 2024
16:19:59 <bauzas> #info Spec review day planned next Dec 5th 2023
16:21:29 <bauzas> #info Caracal-2 (and spec freeze) milestone in 6 weeks
16:21:49 <bauzas> anything about releases ?
16:24:34 <bauzas> looks not
16:24:40 <bauzas> #topic Review priorities
16:24:45 <bauzas> #link https://etherpad.opendev.org/p/nova-caracal-status
16:24:50 <bauzas> we have a review demand
16:25:10 <bauzas> #link https://bugs.launchpad.net/nova/+bug/1869804 and https://review.opendev.org/c/openstack/nova/+/877773
16:25:43 <bauzas> I've seen sean-k-mooney already reviewing it so I'm fine with moving it to the 'accepted bugfixes' section
16:27:16 <bauzas> anyway
16:27:19 <bauzas> moving on
16:27:40 <bauzas> #topic Stable Branches
16:27:45 <bauzas> elodilles: go for it
16:27:46 <sean-k-mooney> yes its a non trivial fix but im reviewing it
16:27:57 <elodilles> #info stable gates don't seem blocked
16:28:07 <elodilles> #info stable release patches still open for review: https://review.opendev.org/q/project:openstack/releases+is:open+intopic:nova
16:28:18 <elodilles> +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:28:27 <elodilles> actually, i've updated the release patches ^^^
16:28:46 <elodilles> to contain the recently merged stable backports
16:29:00 <elodilles> and i suggest to not to wait anymore
16:29:13 <elodilles> the patches were proposed 1 month ago :(
16:29:23 <elodilles> and we can release *anytime*
16:29:42 <elodilles> (except yoga of course, as that release is the final one)
16:30:10 <elodilles> so release liaisons or PTL pls review o:)
16:30:49 <elodilles> and the usual, last item:
16:30:49 <elodilles> #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci
16:30:58 <elodilles> that's all from me
16:31:27 <bauzas> ++
16:31:41 <bauzas> and yeah I've seen the releases patches
16:32:15 <bauzas> fwiw, I'm ok with releasing 2023.1 and 2023.2 since both have the fixes I want
16:32:25 <elodilles> \o/
16:32:25 <bauzas> Zed is still missing the RPC backports
16:32:37 <bauzas> I'll try to look at them tomorrow
16:32:44 <bauzas> elodilles: ping me again tomorrow
16:33:11 <elodilles> bauzas: ack, thanks in advance!
16:36:09 <bauzas> ok, next is a new topic
16:36:11 <bauzas> #topic vmwareapi 3rd-party CI efforts Highlights
16:36:31 <fwiesel> Shall I?
16:36:49 <bauzas> fwiesel: shoot :)
16:36:53 <fwiesel> #Info Gerrit Event Stream connected to our CI (Argo) with personal user
16:37:27 <fwiesel> So, nothing spectacular. Events go in, they could trigger whatever we want to run later. That part is the more tricky one, and peope are working on it.
16:38:07 <fwiesel> The most complicated part is the networking, we try to cut it down as much as possible so we test only nova.
16:38:48 <fwiesel> #Info CI user needs a name. According to naming convention: SAP vmwareapi CI. Has risk of confusion, as SAP is not a vendor of the technology. Our preference simply "SAP CI" or "SAP tempest CI".
16:39:34 <fwiesel> So, the naming convention on the 3rd party CI suggests "Company Technology CI"
16:39:37 <bauzas> fwiesel: I'd prefer 'vmwareapi CI run by SAP'
16:40:02 <bauzas> something telling users what exactly has been run
16:40:24 <gibi> +1 on keep mentioning vmwareapi in the name
16:40:26 <fwiesel> That would work. But if we run another CI, say for cinder, then we end up with the same thing as the VMware nsxt CI running cinder
16:40:27 <bauzas> or yeah, "SAP vmwareapi CI"
16:41:01 <bauzas> honestly, I don't wanna bikeshed
16:41:17 <bauzas> I understand that you'd appreciate the SAP name in the CI job name
16:41:27 <fwiesel> Okay then we go with your proposal "vmwareapi CI run by SAP"
16:41:34 <bauzas> but I also want my users to know that it's testing with vmwareapi virt driver
16:41:47 <bauzas> so, please keep both names
16:41:54 <fwiesel> Fine by me.
16:41:57 <bauzas> I'm French and I'm bad at namings :)
16:42:17 <bauzas> but my gut is saying "any words with both SAP and vmwareapi are fine by me"
16:42:51 <fwiesel> Then we agree on "vmwareapi CI run by SAP"?
16:43:58 <fwiesel> #agreed The CI user will be named "vmwareapi CI run by SAP"
16:44:11 <fwiesel> That's from my side. Any questions?
16:45:21 <fwiesel> Well, then I think we are through.
16:46:23 <bauzas> ++
16:46:38 <bauzas> thanks fwiesel for the report
16:46:40 <bauzas> :)
16:46:53 <bauzas> greatly appreciated
16:46:59 <fwiesel> You're welcome
16:47:00 <bauzas> last topic then
16:47:03 <bauzas> #topic Open discussion
16:47:12 <bauzas> the agenda is empty
16:47:19 <bauzas> anything anyone ?
16:48:10 <sean-k-mooney> nope
16:48:12 <bauzas> cool
16:48:20 <bauzas> thanks all, giving you back 12 mins
16:48:22 <bauzas> #endmeeting