Earlier  
Posted Nick Remark
#openstack-nova - 2022-05-17
16:07:37 bauzas and not fine like in a fire
16:07:51 artom I think Uggla had a bug he wanted to double-check? Dunno if you want to leave that for the open discussion
16:07:59 artom 1959186 (appears to be valid TBC tomorrow)
16:07:59 artom triaged
16:08:01 bauzas artom: we can
16:08:52 sean-k-mooney https://bugs.launchpad.net/nova/+bug/1959186
16:08:59 bauzas I'll leave it for open discussion then
16:09:06 bauzas people can start digesting it meanwhile
16:09:25 sean-k-mooney initally this does not seam like a bug
16:09:28 bauzas #info Please look at the gate failures and file a bug report with the gate-failure tag.
16:09:29 sean-k-mooney but know behavior but ya
16:09:34 bauzas #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures
16:09:35 sean-k-mooney lets wait till later
16:09:46 bauzas #topic Release Planning
16:09:52 bauzas #link https://releases.openstack.org/zed/schedule.html
16:09:56 bauzas #info Zed-1 is due in 2 days
16:09:58 bauzas \o/
16:10:09 bauzas before we discuss about this milestone
16:10:13 bauzas #info Spec review day happened last week on May 10th
16:10:18 bauzas #info 2 specs were approved but a lot of them were reviewed. Kudos to the team for this hard work.
16:10:26 gibi <3
16:10:42 bauzas I've seen lot of feedback there
16:10:50 bauzas very happy
16:10:54 bauzas now,
16:10:57 bauzas zed-1
16:11:20 bauzas in theory, we only have one thing to take care of for this milestone
16:11:31 bauzas libraries releases
16:12:29 sean-k-mooney yep the release patches have been proposed
16:12:36 sean-k-mooney i have not looked at them yet
16:13:07 sean-k-mooney are theree any patches peopel would like to wait for?
16:13:18 bauzas that's my humble question
16:13:32 bauzas do people care of something they'd like to see published before end of this cycle for the libs ?
16:13:32 sean-k-mooney there is one patch in flight in os-vif but i dotn think we have to wait for that
16:13:44 gibi no need to wait, we can push out a new lib release any time it is freeee
16:13:45 bauzas os-traits seems interesting to look at
16:14:08 sean-k-mooney yep we use cycle with intermdiaries
16:14:16 sean-k-mooney which requries at least 1 release per cycle
16:14:22 sean-k-mooney but we can have as many as we want
16:14:29 bauzas https://review.opendev.org/q/project:os-traits+is:open is empty :)
16:14:48 sean-k-mooney yep i think we close to approving spec that would add some
16:14:48 bauzas oh shit
16:14:52 bauzas https://review.opendev.org/q/project:openstack/os-traits+is:open
16:14:56 bauzas better now:)
16:15:26 sean-k-mooney so the manial share spec is still pending
16:15:30 bauzas ok, only the manila-related traits
16:15:34 sean-k-mooney so Uggla's patch cant merge yet
16:15:36 bauzas and yeah the spec is pending
16:15:38 bauzas correct
16:15:46 bauzas so, let's release os-traits by now
16:15:52 sean-k-mooney we can merge teh runtim patch but that is not urgent
16:16:00 sean-k-mooney +1
16:16:04 bauzas and we'll publish a newer os-traits release once the spec is approved
16:16:07 bauzas Uggla: ^
16:17:16 elodilles note: os-traits is in independent release model, so release patch won't be generated by release team
16:17:21 bauzas https://review.opendev.org/q/project:openstack/os-resource-classes+is:open is a bit more crap
16:17:32 bauzas oh shit you're right
16:17:44 bauzas I was looking at https://governance.openstack.org/tc/reference/projects/nova.html#deliverables
16:17:50 Uggla bauzas, \o/
16:17:52 bauzas but it's not describing the release models
16:17:54 sean-k-mooney elodilles: os-traits isnt independint is it
16:18:09 bauzas I'm lost with all the references
16:18:20 sean-k-mooney oh it is
16:18:22 bauzas for release models, this is another website unrelated to governance
16:18:24 sean-k-mooney well that does not make sense
16:18:34 sean-k-mooney because placment is tightly coupled ot it
16:18:36 elodilles sean-k-mooney: it is
16:18:53 sean-k-mooney elodilles: placmentn currently only works with exactly one version of os-triats
16:18:55 bauzas ok, found the right doc https://releases.openstack.org/teams/nova.html
16:19:03 sean-k-mooney https://github.com/openstack/releases/blob/master/deliverables/_independent/os-traits.yaml
16:19:24 bauzas this leaves os-r-c and os-traits be independent
16:19:49 sean-k-mooney right but placment assert the exact numober of triat and resouce classes in its test
16:19:55 bauzas https://releases.openstack.org/teams/nova.html#independent
16:20:13 bauzas sean-k-mooney: we discussed this at the PTG right ?
16:20:15 sean-k-mooney so it only works form a unit test perspecive with exactly one version of os-traits/os-rescoue classes
16:20:16 bauzas and we agreed on a proposal
16:20:17 sean-k-mooney yep
16:20:22 sean-k-mooney relax the test
16:20:25 bauzas yup
16:20:29 bauzas so let's do it
16:20:33 sean-k-mooney yep
16:20:45 sean-k-mooney just pointing out that indpenent did not make sense wiht that context
16:21:00 sean-k-mooney but ok we can wait to release it until we have new traits
16:21:08 sean-k-mooney and fix the test in the interim
16:21:22 bauzas point is, we should only care of os-vif and client releases for placement and nova, that's it
16:21:40 bauzas (for zed-1 I mean)
16:21:58 sean-k-mooney yep
16:23:06 bauzas gmann: btw. this is not going well for https://review.opendev.org/c/openstack/os-vif/+/840020
16:23:15 bauzas but let's discuss this on open discussion ^
16:23:26 bauzas and let's continue the agenda
16:23:35 bauzas #topic Review priorities
16:23:40 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:23:59 bauzas #link https://review.opendev.org/c/openstack/project-config/+/837595 Gerrit policy for Review-prio contributors flag. Naming bikeshed in there.
16:24:08 bauzas reviews are welcome on ^
16:24:21 bauzas I see gibi having concerns on the naming
16:24:49 gibi I have no good suggestion
16:24:53 gibi so feel free to ignore me
16:27:03 gibi my problem on the current naming is that is sounds like a core approves that something is a prioirty
16:27:19 gibi but the aim is instead that the core says "I will review this"
16:27:33 bauzas gibi: I can propose something else
16:27:39 bauzas to unblock the patch

Earlier   Later