Earlier  
Posted Nick Remark
#openstack-nova - 2022-08-02
16:03:55 bauzas any bug to discuss ?
16:04:46 bauzas btw. I had fun with https://bugs.launchpad.net/nova/+bug/1983263
16:05:19 bauzas looks we only accept Ussuri computes for Ussuri :p
16:05:43 bauzas could be a FFU issue :)
16:06:36 bauzas just sayin' :)
16:06:47 bauzas anyway, moving on
16:07:01 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:07:15 bauzas elodilles: do you want to get the bug baton for this week ? :)
16:08:04 elodilles bauzas: yes please! \o/
16:08:07 elodilles :)
16:08:12 bauzas suuuuure
16:08:23 bauzas #info Next bug baton is passed to elodilles
16:08:27 bauzas that's it for bugds
16:08:34 bauzas #topic Gate status
16:08:41 bauzas #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs
16:08:48 bauzas #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status
16:08:58 bauzas #link https://zuul.openstack.org/builds?job_name=tempest-integrated-compute-centos-9-stream&project=openstack%2Fnova&pipeline=periodic-weekly&skip=0 Centos 9 Stream periodic job status
16:09:05 bauzas #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs
16:09:15 bauzas I've look at all of above ^
16:09:19 bauzas looked
16:09:24 bauzas no issues I found
16:09:39 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:09:45 bauzas #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
16:09:58 bauzas really, please stop saying 'recheck'
16:10:21 bauzas last time, we found 50% nova rechecks that were blind
16:10:33 bauzas I mean, 50% of all the nova rechecks
16:11:37 bauzas moving on ?
16:12:21 gibi nope
16:12:25 bauzas #topic Release Planning
16:12:35 bauzas #link https://releases.openstack.org/zed/schedule.html
16:12:40 bauzas #info Zed-3 is in 4 weeks
16:12:55 bauzas now, hopefully you've seen my email from yesterday
16:13:28 bauzas #link https://lists.openstack.org/pipermail/openstack-discuss/2022-August/029789.html
16:13:56 bauzas I propose now to look at the etherpad I created
16:14:09 bauzas #link https://etherpad.opendev.org/p/nova-zed-microversions-plan
16:14:23 bauzas we have 3 open changes asking for a microversion
16:15:57 bauzas so I'd like to ask you folks how we could organize and triage those 3 between them for a microversion
16:16:46 gibi for me it depends on how close they are to land
16:17:20 bauzas two of them were already modified to use 2.92
16:17:36 bauzas so it looks to me both can be priorital
16:17:48 bauzas one is touching the /servers API
16:18:07 bauzas but only by a single rebuild action
16:18:51 bauzas the other one is technically a WIP and adding a new API resource /os-server-shares
16:19:15 gibi if the second one is a WIP then I guess the first one has priority: )
16:19:29 bauzas any concerns about this ?
16:19:32 gibi but I guess we don't have to decide it now
16:19:40 opendevreview Balazs Gibizer proposed openstack/nova master: Fix mocking SafeConnectedTestCase https://review.opendev.org/c/openstack/nova/+/851909
16:20:18 bauzas gibi: well, I would have preferred to have it decided by now
16:20:28 gibi sure, then lets decide :)
16:20:40 bauzas but it looks that we don't have a lot of folks around
16:20:40 gibi anybody has any opinion?
16:20:57 bauzas rajat was asking me about this at least loudly
16:21:08 artom Decide who gets what microversion?
16:21:34 bauzas at least decide who would get 2.93
16:21:39 artom Are all 2 guaranteed (inasmuch as that's possible in upstream world) to land?
16:21:46 artom *all 3
16:21:48 bauzas I think we could say yes to https://review.opendev.org/c/openstack/nova/+/816157
16:21:53 bauzas for 2.93
16:22:29 bauzas dansmith already looked at it and it was already around last cycle
16:22:48 bauzas but this means we would prioritize this change
16:22:54 artom I'd say it's up to the owner and reviwers to determine how close something is to land, and to give the next smallest microversion to the closest, then next closest, and so on
16:23:34 bauzas artom: problem is about merge conflicts
16:23:52 bauzas at least we have now https://review.opendev.org/c/openstack/nova/+/816157 and https://review.opendev.org/c/openstack/nova/+/830883 that got merge conflicts
16:24:10 gibi (probably everything is in merge conflict as unittest.mock change landed)
16:24:39 bauzas gibi: and you're just telling me this before I'm going off ? :)
16:24:56 gibi bauzas: it is landed yesterday?
16:25:18 bauzas haven't seen it then
16:25:20 gibi Aug 01 21:07
16:25:20 bauzas anyway
16:25:57 bauzas if we don't have consensus, let's just tell the owners they need to provide their changes and ask for reviewes
16:26:01 bauzas reviews*
16:28:40 gibi Im fine with https://review.opendev.org/c/openstack/nova/+/816157 being the next one
16:28:47 sean-k-mooney[m] o/
16:29:20 bauzas gibi: cool, then let's prioritize it
16:30:22 bauzas whoami-rajat and Uggla could then modify their change to ask for 2.95 and we'll see in the meantime if jhartkopf can upload his series soon
16:30:41 bauzas I'll drop a gerrit comment on https://review.opendev.org/c/openstack/nova/+/816157 telling him to rebase quickly
16:30:53 bauzas if he can't, then whoami-rajat could use this API slot
16:31:04 bauzas wfy folks ?
16:31:22 gibi or they can both rebase to 2.93 and have a race for landing :)
16:31:38 gibi both works for me
16:31:56 whoami-rajat let me know which one is suitable and i will rebase
16:32:15 whoami-rajat s/which/whichever
16:34:03 bauzas gibi: yeah, we'll see
16:34:32 bauzas it's the first time we're trying to organize API microversions, I guess we don't wanna be too much optimistic
16:35:05 bauzas whoami-rajat: I'd say prepare for 2.94 but be ready to propose 2.93 if https://review.opendev.org/c/openstack/nova/+/816157 doesn't get rebased next week
16:35:25 sean-k-mooney[m] normally we only do this if they already have at least 1 +2
16:36:17 artom I guess you can't easily template Python code, which we would need
16:36:43 artom Otherwise, if we keep a single running counter of source in a file or something, folks can just write %{next_microversion} or similar
16:36:45 whoami-rajat ack
16:37:06 bauzas I think we're done with this
16:37:10 bauzas moving on
16:37:21 bauzas #topic Review priorities
16:37: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:38:10 bauzas anything to discuss ?
16:39:58 gibi bauzas: you need to add OR label+2
16:40:06 gibi as now the query shows only +1
16:40:20 gibi ie
16:40:20 gibi 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+OR+label:Review-Priority%252B2)
16:40:49 bauzas wait
16:40:54 bauzas bad copy/paste

Earlier   Later