16:00:27 <bauzas> #startmeeting nova
16:00:27 <opendevmeet> Meeting started Tue Jan 30 16:00:27 2024 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:27 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:27 <opendevmeet> The meeting name has been set to 'nova'
16:00:41 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:00:45 <bauzas> hello folks
16:00:48 <elodilles> o/
16:00:56 <fwiesel> o/
16:02:06 <dansmith> o.
16:02:33 <bauzas> let's do a soft start
16:03:08 <bauzas> #topic Bugs (stuck/critical)
16:03:13 <bauzas> #info No Critical bug
16:03:16 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 52 new untriaged bugs (+6 since the last meeting)
16:03:25 <bauzas> probably amit had no time to look at bugs
16:03:30 <bauzas> #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:03:48 <bauzas> next guy in the roster in me, so
16:03:56 <bauzas> #info bug baton is bauzas
16:04:05 * bauzas will add something in my calendar to remind myself :)
16:04:17 <auniyal> o/
16:04:33 <auniyal> I triaged few bauzas
16:04:40 <auniyal> comented on few
16:04:41 <bauzas> ack
16:04:49 <bauzas> cool
16:04:55 <bauzas> nothing urgent to raise ?
16:05:07 <Uggla> */
16:05:08 <auniyal> I had 2 bugs if some one can look into
16:05:18 <auniyal> but as we do not discuss bug here
16:05:45 <auniyal> https://bugs.launchpad.net/nova/+bug/2045785
16:06:10 <auniyal> https://bugs.launchpad.net/nova/+bug/2049121 - in this you have already comented once
16:06:38 <auniyal> thats all
16:07:49 <bauzas> I'll add another comment about the last bug
16:08:10 <bauzas> he needs to explain more why he thinks this is nova related
16:08:26 <bauzas> we just passthru the whole PCI device
16:08:31 <auniyal> yes
16:08:48 <bauzas> anyway moving on
16:08:57 <bauzas> thanks auniyal
16:08:59 <bauzas> #topic Gate status
16:09:02 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:09:06 <bauzas> #link https://etherpad.opendev.org/p/nova-ci-failures-minimal
16:09:11 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status
16:09:24 <bauzas> #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:09:42 <bauzas> the gate is more flakey those days
16:09:46 <bauzas> I've seen it
16:09:55 <bauzas> still the same usual suspects
16:10:15 <bauzas> haven't seen a lot of kernel panics tho
16:11:04 <bauzas> anyone wanting to discuss our lovely gate problems ?
16:12:08 <bauzas> looks not
16:12:31 <bauzas> rechecks are back, but as a reminder, please don't say only "recheck", just add the reason you think why it failed
16:12:41 <bauzas> it will help
16:12:44 <bauzas> thanks
16:12:50 <bauzas> #topic Release Planning
16:13:10 <bauzas> #link https://releases.openstack.org/caracal/schedule.html#nova
16:13:14 <bauzas> #info Caracal-3 (and feature freeze) milestone in 4 weeks
16:13:19 <bauzas> tick-tock
16:13:53 <bauzas> (as a reminder, we'll also have non-client libraries freeze by the week before, ie. 3 weeks by now
16:14:07 <bauzas> so if you need to update os-vif, time to think about it
16:14:54 <bauzas> moving on
16:14:56 <bauzas> #topic Review priorities
16:15:10 <bauzas> maybe you lived in a cave from the last 2 months
16:15:19 <bauzas> so it would explain why you don't know yet about it but,
16:15:21 <bauzas> #link https://etherpad.opendev.org/p/nova-caracal-status
16:15:32 <bauzas> is existing and you definitely look at it :)
16:15:49 <bauzas> gibi: thanks gibi for having added your topics
16:16:22 <gibi> we need to resolve some of those questions to land the manila series
16:16:30 <bauzas> the more we add our points, the better it will be a readable and digestable context for others
16:16:52 <bauzas> I know, I just took an example of something someone may add
16:17:01 <bauzas> to give visibility for others
16:18:44 <bauzas> #topic Stable Branches
16:18:47 <bauzas> elodilles: around ?
16:18:49 <elodilles> yepp
16:18:53 <elodilles> i'll be short
16:18:59 <elodilles> with a quick glance a saw that:
16:19:03 <elodilles> #info stable gates don't seem blocked
16:19:12 <elodilles> and that's all for now from me :)
16:19:23 <bauzas> cool
16:20:52 <bauzas> ok, next topic then ?
16:21:06 <bauzas> #topic vmwareapi 3rd-party CI efforts Highlights
16:21:13 <bauzas> fwiesel: floor is yours
16:21:22 <fwiesel> #info Administrative: Account added to Third Party CI mail filter list.
16:21:39 <fwiesel> Nothing interesting. Shout out to frickler who took care of it.
16:21:47 <fwiesel> #info Log-shipping: Generate static index for log retrieval. Struggling to get AWS access permissions right to ship things.
16:22:12 <fwiesel> Not much of progress here, as I do not have access to AWS myself and have to poke people. Sorry about that.
16:22:25 <fwiesel> That's it from my side.
16:22:27 <bauzas> no worries
16:22:42 <bauzas> 9 people don't do babies in 1 month
16:22:51 * gibi likes the consistent effort on the 3rd party CI
16:22:59 <bauzas> ditto indeed
16:23:22 <fwiesel> All that is left is just wiring it up. It may take just a day, if everything is in place.
16:23:38 <bauzas> let's then wait
16:23:44 <bauzas> thanks
16:23:49 <fwiesel> You're welcome.
16:23:53 <bauzas> #topic Open discussion
16:24:02 <bauzas> we have one topic
16:24:04 <bauzas> (NotTheEvilOne) Support for "Bring your own keys" to `Volume.Create()`
16:24:11 <bauzas> NotTheEvilOne: around ?
16:24:14 <NotTheEvilOne> yes
16:25:37 <NotTheEvilOne> Hi everyone. I would like to basically learn if the idea and intentions are the right way to go and what you may suggest. We (Sovereign Cloud Stack) https://scs.community would like to bring the feature "bring you own keys" for encryption to OpenStack,
16:26:03 <NotTheEvilOne> #link https://github.com/SovereignCloudStack/issues/issues/519
16:26:20 <NotTheEvilOne> For that reason I added a bug to launchpad
16:26:31 <dansmith> probably best to write up a spec for how you plan to do that, what the workflow and use-cases are so we can review in that format
16:26:33 <NotTheEvilOne> #link https://bugs.launchpad.net/nova/+bug/2051108
16:27:20 <NotTheEvilOne> Should I add that to the ticket? We already had a basic idea.
16:27:22 <NotTheEvilOne> #link https://input.scs.community/9FbrLgYbT8KFvZGXLzay6Q?view#Go-implementation
16:27:46 <dansmith> that bug is against nova but says cinder lacks the current API to do it, so it's not clear what nova would need here, and we also need to know if/that cinder has an approved design for their side
16:28:19 <bauzas> NotTheEvilOne: we'll have a PTG in April
16:28:23 <dansmith> NotTheEvilOne: that doc of yours also seems to imply only cinder changes
16:28:29 <bauzas> which is one week after the Caracal release
16:29:00 <bauzas> given we're currently on new features approval freeze, we can't even accept your request for this cycle
16:29:07 <NotTheEvilOne> I guess that only some changes are needed to Cinder indeed as most building blocks are already there
16:29:18 <NotTheEvilOne> I see.
16:29:20 <bauzas> so I'd strongly suggest you to attend next PTG in April and join the Cinder community at that time
16:29:24 <dansmith> NotTheEvilOne: okay then you're in the wrong channel/meeting :)
16:29:58 <bauzas> if something is needed from the nova side when discussing w/ the Cinder folks, then surely we could join that session
16:30:04 <dansmith> yep
16:30:16 <NotTheEvilOne> Is it possible to move the bug to the correct category?
16:30:18 <NotTheEvilOne> ok
16:30:32 <bauzas> NotTheEvilOne: https://openinfra.dev/ptg/
16:30:58 <bauzas> NotTheEvilOne: I can point you to the right Cinder folks to bug
16:31:06 <bauzas> in order to make sure your topic is discussed at the PTG
16:31:17 <NotTheEvilOne> Would be great, thanks
16:32:46 <bauzas> NotTheEvilOne: will give you the nicks after the meeting
16:32:53 <bauzas> stay online for a sec
16:33:03 <bauzas> I think we're done by now
16:33:11 <bauzas> any other topic to discuss ?
16:34:40 <bauzas> looks not
16:34:56 <bauzas> let's just call it done
16:34:59 <bauzas> thanks all
16:35:05 <bauzas> #endmeeting