Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2022-02-08
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
16:59:06 bauzas patches*
16:59:22 bauzas DHilsbos: then, let's close this meeting and we'll discuss this right after
16:59:32 bauzas thanks all
16:59:34 bauzas #endmeeting
16:59:34 opendevmeet Meeting ended Tue Feb 8 16:59:34 2022 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:59:34 opendevmeet Minutes: https://meetings.opendev.org/meetings/nova/2022/nova.2022-02-08-16.00.html
16:59:34 opendevmeet Minutes (text): https://meetings.opendev.org/meetings/nova/2022/nova.2022-02-08-16.00.txt
16:59:34 opendevmeet Log: https://meetings.opendev.org/meetings/nova/2022/nova.2022-02-08-16.00.log.html
16:59:45 elodilles thanks bauzas o/
16:59:53 bauzas DHilsbos: what do you want about the release process for Z ?
17:00:05 bauzas what do you want to know*
17:00:12 gibi dmitriis: I will check tomorrow
17:00:19 dmitriis gibi: ack, tyvm
17:01:21 DHilsbos I have made changes to the libvirt driver that brings it inline (maybe) with a feature for Hyper-V, I'd like to submit that code.
17:02:14 bauzas DHilsbos: then you'll need a blueprint
17:02:30 bauzas DHilsbos: you can start writing this blueprint
17:02:40 bauzas and then working on patches
17:02:58 DHilsbos Ok, that's what I trhought. Are there blueprint forms?
17:03:09 bauzas but we won't look at both patches and the blueprint until RC1 which is when Z becomes a thing
17:03:27 dansmith I'm sure anything with that description requires a spec and not just a blueprint
17:03:29 dansmith and yes, there's a spec template :)
17:03:30 bauzas DHilsbos: there is even a button
17:03:48 bauzas dansmith: don't disagreed, just oversimplified the explanation
17:04:10 DHilsbos I'm not suprised by the need for the spec.
17:04:25 bauzas https://docs.openstack.org/nova/latest/contributor/process.html#when-do-i-need-a-blueprint-vs-a-spec
17:04:25 DHilsbos So; Blueprint, spec, patches, yeah?
17:04:42 bauzas blueprint is the first procedural step
17:05:35 DHilsbos Ok.
17:05:45 bauzas then you'd have to upload a spec if you really care in advance but given the directory name isn't created yet due to legal naming implications ( :) ) you'd have to either refrain to push or fake a name when you uploda

Earlier   Later