16:00:00 <bauzas> #startmeeting nova
16:00:00 <opendevmeet> Meeting started Tue Jan 18 16:00:00 2022 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:00 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:00 <opendevmeet> The meeting name has been set to 'nova'
16:00:12 <gibi> o.
16:00:13 <gibi> o/
16:00:15 * bauzas bows to the community
16:00:55 <chateaulav> \o
16:00:56 <elodilles> o/
16:01:19 <bauzas> #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:01:53 <bauzas> ok, let's start
16:02:01 <bauzas> #topic Bugs (stuck/critical)
16:02:06 <bauzas> #info No Critical bug
16:02:10 <bauzas> #info No Critical bug
16:02:15 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 32 new untriaged bugs (-4 since the last meeting)
16:02:20 <bauzas> #help Nova bug triage help is appreciated https://wiki.openstack.org/wiki/Nova/BugTriage
16:02:24 <bauzas> #link https://storyboard.openstack.org/#!/project/openstack/placement 23 open stories (-2 since the last meeting) in Storyboard for Placement
16:02:34 <bauzas> thanks to those who helped to triage
16:02:43 <bauzas> (I dunno who about placement :p)
16:04:06 <gibi> bauzas: can be that the any-trait spec merges closed the related ticjket
16:04:09 <gibi> I will check
16:04:33 <bauzas> maybe
16:04:35 <bauzas> anyway
16:04:42 <bauzas> any bug to want to discuss ?
16:05:20 <bauzas> looks not
16:05:27 <bauzas> #topic Gate status
16:05:32 <bauzas> #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:05:37 <bauzas> #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:05:43 <bauzas> #info Please look at the gate failures, file a bug, and add an  elastic-recheck signature in the opendev/elastic-recheck repo (example: https://review.opendev.org/#/c/759967)
16:06:21 <bauzas> let's discuss about the centos8 job with elodilles in the stable branches topic
16:06:21 <gibi> (yepp the two missing placement ticket is the any-trait support, I will reopen them by creating an open task on them)
16:06:55 <bauzas> apart from this job, nothing to say
16:06:59 <bauzas> anyone ?
16:08:11 <bauzas> mmmm, ok, let's move
16:08:18 <bauzas> #topic Release Planning
16:08:26 <bauzas> #info FeatureApprovalFreeze was Jan 13st
16:08:32 <bauzas> #link https://blueprints.launchpad.net/nova/yoga 23 approved blueprints for the Yoga cycle with 16 of them having specs
16:08:36 <bauzas> #link https://etherpad.opendev.org/p/nova-yoga-blueprint-status Etherpad for blueprints tracking
16:08:48 <bauzas> so, as you see, I created an etherpad for yoga
16:08:55 <bauzas> I'll look at each of the blueprints
16:09:17 <bauzas> and I'll modify the etherpad to explain which ones are started, and which ones need reviews
16:09:40 <bauzas> but if folks want to modify the etherpad and explain the changes they have for their blueprint, fine by me :)
16:10:08 <bauzas> every meeting until FeatureFreeze, I'll provide this etherpad during the meeting
16:10:24 <gibi> cool
16:10:25 <bauzas> just remember that we now have 6 weeks before it
16:11:31 <bauzas> anyway, let's discuss about this etherpad by next week as I need to modify it for providing the changes
16:11:47 <bauzas> also, last thought
16:12:14 <bauzas> given it's difficult to merge API changes as they're conficting once we merge one
16:12:31 <bauzas> I'll provide all the changes wanting to add a new microversion
16:12:57 <sean-k-mooney> ya we can likely come up with a merge order when we get a little closer to FF
16:12:58 <bauzas> so during the reviews, people could organize themselves to see who and what could be reviewed first etc.
16:13:38 <bauzas> sean-k-mooney: yeah, here I just want to tell it by now so people see
16:13:47 <sean-k-mooney> i think there are only 3 specs that would need a microversion maybe 4
16:13:54 <bauzas> like, for the moment, I wonder how many blueprints are asking to get a microversion
16:14:20 <bauzas> sean-k-mooney: that's the question I have for the moment, but I'll look back at the specs
16:14:24 <bauzas> anyway
16:14:38 <bauzas> the etherpad is just starting, we'll see how we organize it
16:14:50 * artom wonders if some sort of mechanism for grabbing the next available microversion would be worth it
16:14:52 <artom> Probably not
16:15:00 <bauzas> artom: we can't ask slots
16:15:06 <sean-k-mooney> i think they are https://blueprints.launchpad.net/nova/+spec/remove-tenant-id https://blueprints.launchpad.net/nova/+spec/unified-limits-nova and  https://blueprints.launchpad.net/nova/+spec/libvirt-virtiofs-attach-manila-shares
16:15:25 <bauzas> artom: as we need to merge them one after the other
16:15:39 <artom> bauzas, I was thinking some sort of gate job that does it
16:15:50 <bauzas> artom: we don't need a job
16:15:54 <artom> So the final microversion isn't known until merge, it's all placeholders
16:16:02 <artom> Anways, I'm inventing complexity for nothing, carry on :)
16:16:06 <bauzas> artom: you get a merge conflict for your change if another one was merged :p
16:16:09 <gibi> modifying a code by a gate job... hm
16:16:33 <bauzas> gibi: agreed, let's keep it simple
16:17:02 <bauzas> if we only have 4 changes asking microversions, they can organize themselves to be depending on each of them if really needed
16:17:30 <bauzas> but again, before saying this, I need to look at which ones specifically so we know them
16:17:52 * gibi is lucky being the only one wants a new placement microversion...
16:18:07 <bauzas> lol
16:18:36 <bauzas> anyway, moving on ?
16:18:42 <sean-k-mooney> sure
16:19:02 <bauzas> #topic Review priorities
16:19:09 <bauzas> #link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+label:Review-Priority%252B1
16:19:16 <bauzas> #link https://review.opendev.org/c/openstack/nova/+/816861 bauzas proposing a documentation change for helping contributors to ask for reviews, needs a second +2
16:19:45 <bauzas> nothing to tell it for this meeting from me
16:20:28 <bauzas> oh actually my change was +W and got a CI issue
16:20:38 <bauzas> because of the centos8 job
16:20:43 <bauzas> anyway, nothing to tell here
16:20:57 <bauzas> I guess we should discuss about the job and the stable branches now
16:21:15 <bauzas> #topic Stable Branches
16:21:19 <bauzas> elodilles: your turn
16:21:31 <elodilles> #info stable gates were blocked, due to centos-8-stream job, which is now set as non-voting ( https://review.opendev.org/c/openstack/tempest/+/824740 ) so should be OK
16:21:46 <elodilles> at least i think so :)
16:21:53 <elodilles> #info patches waiting for a 2nd +2 (please review some if you have time): https://review.opendev.org/q/project:openstack/nova+branch:%255Estable/.*+is:open+label:Code-Review%253D%252B2
16:22:22 <elodilles> these were probably interesting things for now
16:22:47 <bauzas> agreed
16:22:53 <sean-k-mooney> the centos-8-stream issues should i belive be fixed now with the release of a new package
16:22:57 <elodilles> i know that stable is not the top priority between Yoga-2 and Yoga-3, but if anyone have some time... :)
16:23:10 <sean-k-mooney> so they could go back to voting shortly once we confrim they are stable
16:23:36 <elodilles> sean-k-mooney: thanks for the info!
16:24:15 <bauzas> cool
16:24:44 <clarkb> sean-k-mooney: I don't see commits to systemd or iputils in git.centos.org. Any idea where the fix is?
16:25:16 <sean-k-mooney> oh i tought it had been fixed and pushed to some of our mirrors. was that just pinning to an old verion
16:25:41 <sean-k-mooney> if its not fixed ill flag it internally and see if i can find more info
16:26:03 <bauzas> clarkb: we're in a meeting but should be ended quickly in 5 mins hopefully
16:26:23 <bauzas> nothing to say more about stable branches ?
16:26:33 <bauzas> if not, let's move on and wrap this thing :)
16:26:39 <bauzas> #topic Sub/related team Highlights
16:26:43 <bauzas> #info No subteam left
16:26:47 <bauzas> #topic Open discussion
16:26:50 <bauzas> nothing on the agenda
16:27:02 <bauzas> so, I guess we're done ?
16:27:09 <bauzas> anyone whats to shout something ?
16:27:19 <bauzas> or yelling about something ?
16:27:32 <bauzas> s/whats/wants (gosh)
16:28:14 <bauzas> if not, let's pretend we're done
16:28:18 <bauzas> #endmeeting