Posted	Nick	Remark
#openstack-nova - 2022-02-08
16:30:07	bauzas	#topic Release Planning
16:30:12	bauzas	#link https://releases.openstack.org/yoga/schedule.html#y-ff FeatureFreeze in 2.5 weeks
16:30:17	bauzas	#link https://etherpad.opendev.org/p/nova-yoga-blueprint-status Etherpad for blueprints tracking
16:30:30	bauzas	thanks gibi for having made a couple of insighful reviews
16:30:36	bauzas	I started to review as well
16:31:14	bauzas	folks, just a reminder to use this etherpad for coordinating review requests and comments
16:31:41	bauzas	any particular BP someone wanting to address by now ? (provided this is not about asking reviews)
16:32:32	gmann	added link for policy refresh 2 BP and moved up for review section #link https://etherpad.opendev.org/p/nova-yoga-blueprint-status#L40
16:32:49	gmann	It is not complete yet, I am working on system_reader conversion
16:33:00	gmann	but existing patches is up for review
16:33:12	gmann	dansmith: ^^ I am +2 on your patches for server policy
16:33:17	opendevreview	Merged openstack/nova-specs master: Avoid Sphinx 4.4.0 to fix specs doc build https://review.opendev.org/c/openstack/nova-specs/+/828368
16:33:24	bauzas	gmann: thanks
16:33:36	dansmith	gmann: ack, I've been wondering when that was going to go
16:33:41	bauzas	anyone wanting to discuss now about priorities ?
16:33:47	dansmith	bauzas: want a note on the quotas stuff?
16:33:54	gmann	dansmith: lot of test to fix so taking time but I am working on remaining policies
16:33:58	bauzas	dansmith: I started looking at your comment
16:34:07	bauzas	on the next patch I wanted to review
16:34:22	dansmith	bauzas: well,
16:34:28	bauzas	dansmith: those are reasonable concerns but I started reviewing this patch too
16:34:41	dansmith	melwitt and I discussed a few refactoring changes
16:34:50	dansmith	after my first review, and we're still working on hammering those out
16:35:20	bauzas	dansmith: given the series, do you feel she needs to rebase his change or can she work on a follow-up patch ?
16:35:30	bauzas	(well, can ping melwitt actually for the answer)
16:35:33	dansmith	I'm working on the rebase now,
16:35:45	dansmith	but yeah, we're actually going to drop the latest PS, back to the previous and iterate from there
16:35:52	dansmith	I'm almost done with that actually,
16:36:03	dansmith	but want to sync with her when she's around this morning before I push that major change up :)
16:36:14	bauzas	dansmith: ok, then I'll look at other bps tonight and I'll look back at the unified limits one tomorrow
16:36:28	bauzas	thanks for the notice
16:36:56	dansmith	aye
16:37:14	bauzas	fwiw, I thought about a simple thing for giving ourselves visibility during the last 3-week sprint
16:37:46	bauzas	if cores don't disagree, I'd recommend cores to mark their IRC nicks on the BPs they'd like to review this week
16:37:52	bauzas	no obligation
16:38:07	bauzas	just a matter of giving a bit of visibility for the people who want
16:38:37	bauzas	feel it like it's runways or whatever name it is
16:39:12	bauzas	it's just about adding a bullet point below each blueprint on the blueprint etherpad for people willing to mark their names
16:39:30	bauzas	another option could be the Review-Priority flag :)
16:40:11	bauzas	what folks think about it ? maybe this is a bit early ?
16:40:35	gibi	I can do both
16:41:38	gmann	either is fine, I will review tenant-id series this week
16:41:38	bauzas	I don't want to ask for duplicate things
16:42:12	bauzas	I feel we can use the review-prio flag then
16:42:24	bauzas	but that means we need to clean it up first
16:43:41	gibi	there is not much marked with review priority at the moment
16:43:56	bauzas	ok, then let's jump straight to the next topîc
16:44:22	bauzas	#topic Review priorities
16:44:28	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:45:03	gibi	pack and spread, remote-manged and unified limits are all has core review attention so they are good having the prio label
16:45:19	bauzas	right
16:45:24	gibi	the other patches in that list feels less important now
16:45:58	bauzas	pack-n-spread doesn't match a bp
16:46:35	bauzas	but I'm ok with treating it as some kind of feature request
16:46:50	bauzas	anyway, let's overthink that
16:47:24	bauzas	sean-k-mooney: can you drop r-p flag on https://review.opendev.org/c/openstack/os-vif/+/765912 and https://review.opendev.org/c/openstack/os-vif/+/765970
16:47:41	bauzas	those are old patches that fail CI, hence meaningless to be 'priorities'
16:48:17	sean-k-mooney	yes
16:48:20	bauzas	https://review.opendev.org/c/openstack/os-resource-classes/+/819207 will be tonight's priority for me
16:48:29	bauzas	so hopefully we could merge it
16:48:46	sean-k-mooney	done
16:48:56	bauzas	that would leave the other changes having r-p matching blueprints
16:49:00	opendevreview	Dmitrii Shcherbakov proposed openstack/nova master: Bump os-traits to 2.7.0 https://review.opendev.org/c/openstack/nova/+/826675
16:49:01	opendevreview	Dmitrii Shcherbakov proposed openstack/nova master: Add supports_remote_managed_ports capability https://review.opendev.org/c/openstack/nova/+/827839
16:49:01	opendevreview	Dmitrii Shcherbakov proposed openstack/nova master: Filter computes without remote-managed ports early https://review.opendev.org/c/openstack/nova/+/812111
16:49:02	opendevreview	Dmitrii Shcherbakov proposed openstack/nova master: [yoga] Add support for VNIC_REMOTE_MANAGED https://review.opendev.org/c/openstack/nova/+/824835
16:50:22	bauzas	let's finish this discussion next week and make the r-p flag be the tool for coordinating review priorities for this feature freeze
16:50:34	bauzas	agreed ?
16:50:48	gibi	works for me
16:51:22	bauzas	anyway, moving on, time is flying
16:51:37	bauzas	#topic Stable Branches
16:51:41	bauzas	elodilles: your turn
16:51:50	elodilles	#info stable/queens and stable/pike gates are blocked by docs job (details: http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027106.html )
16:52:17	elodilles	i'm planning to propose some patch to unblock the gate
16:52:48	elodilles	probably just removing the doc job (if i cannot make the sphinx job to work)
16:52:57	elodilles	#info other stable gates are not blocked, but hard to merge patches due to intermittent failures
16:53:11	elodilles	probably Lee's patches, that would disable guest's apic in CI, could eliminate some part of the problem for wallaby and older branches: https://review.opendev.org/q/topic:workaround-disable-apic
16:53:36	elodilles	so if any stable core has some time to review ^^^ that would be nice
16:53:57	elodilles	and that's all i think :X
16:54:01	dmitriis	sean-k-mooney, gibi: resubmitted with the VNIC type change and other stuff included.
16:54:18	bauzas	dmitriis: we're in a meeting, please
16:54:31	bauzas	elodilles: thanks elod
16:54:31	dmitriis	bauzas: apologies
16:54:55	bauzas	dmitriis: no worries, that's one of the issues we have with meetings running at the existing channel
16:55:08	bauzas	elodilles: will promise a few reviews if I have time
16:55:12	bauzas	last topic
16:55:24	bauzas	#topic Open discussion
16:55:24	elodilles	bauzas: thanks in advance! \o/
16:55:34	bauzas	(skipping the subteam topic meaningless)
16:55:42	bauzas	Z release name should be known in 1 or 2 weeks
16:55:58	bauzas	let's hold until we know which Zen or Zombie we'll have
16:57:08	bauzas	not saying some chip company used that word
16:57:13	DHilsbos	Maybe they'll meditate on it...
16:57:27	bauzas	anyway
16:57:37	bauzas	any other business before we close ?
16:58:10	DHilsbos	Is now a good time to ask for assistance with a feature for Z?
16:58:27	bauzas	DHilsbos: nothing prevents you to get assistance
16:58:37	bauzas	DHilsbos: this is just a matter of priorities
16:59:00	DHilsbos	My question is more along the lines of process.
16:59:02	bauzas	the Z specs repo isn't yet created but you can work on WIP patchers

Earlier   Later