| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2022-05-10 | |||
| 16:18:12 | Uggla | bauzas, sorry was out | |
| 16:18:24 | bauzas | kashyap: but I don't want to enforce any rules | |
| 16:18:28 | kashyap | sean-k-mooney: The point I'm making is: sharing experiences from other communities how public bug triage used to be sustained. | |
| 16:18:37 | kashyap | bauzas: Sigh, you keep saying that. I'm saying to "enforce" any rules :) | |
| 16:18:48 | Uggla | bauzas, ok for the bug baton | |
| 16:18:51 | bauzas | kashyap: proposing to send an email is a rule :) | |
| 16:19:03 | kashyap | It's not; it's a suggestion. "Proposal" != "rule" | |
| 16:20:00 | bauzas | kashyap: sorry about the confusion, I just wanted to explain the bug triage rotation upstream is necessarly something people opt-in on their free time with their own things | |
| 16:20:11 | kashyap | bauzas: We can move on; really. I've done community bug triages with much larger groups in the past (Fedora test days, RDO, CentOS, etc). Just sharing what worked. | |
| 16:20:21 | kashyap | (There isn't possibility, given the thinness of the community here.) | |
| 16:20:44 | kashyap | Of course, everything is "opt-in" upstream. | |
| 16:21:07 | bauzas | kashyap: noted, I just wanted to clarify that triage etherpads *are* optional | |
| 16:21:08 | kashyap | bauzas: (I missed a word earlier: I'm saying NOT to "enforce" any riles) | |
| 16:21:17 | kashyap | s/riles/rules/ | |
| 16:22:04 | kashyap | Sure. Just as a general point: in upstreams I never suggest anything as a "rule". Everything _is_ optional. As you can't "demand" community time. | |
| 16:22:48 | bauzas | kashyap: that's why emails are difficult, because operators and consumers of this perodic email are in demand with more | |
| 16:23:05 | bauzas | either the email is read and people ask for a new one | |
| 16:23:22 | bauzas | or the email isn't read and then the sake of sending such email is meaningless | |
| 16:23:54 | bauzas | that's why I can only propose myself to send such periodic emails | |
| 16:24:27 | kashyap | Sure. It doesn't have to be. We've tried everything in the past, "bug czars", etc. | |
| 16:24:52 | bauzas | ... with a short period of life :) | |
| 16:24:58 | bauzas | anyway, I guess we can move on | |
| 16:25:40 | bauzas | Uggla: thanks for offering your time, again, no rush | |
| 16:27:09 | bauzas | next topic | |
| 16:27:10 | bauzas | #topic Gate status | |
| 16:27:15 | bauzas | #link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs | |
| 16:27:20 | bauzas | #link https://zuul.openstack.org/builds?project=openstack%2Fplacement&pipeline=periodic-weekly Placement periodic job status | |
| 16:27:31 | bauzas | #link https://zuul.opendev.org/t/openstack/builds?job_name=nova-emulation&pipeline=periodic-weekly&skip=0 Emulation periodic job runs | |
| 16:27:55 | bauzas | things look good, AFAICS | |
| 16:28:14 | bauzas | we have tho a new gate bug https://bugs.launchpad.net/nova/+bug/1970642 | |
| 16:28:51 | bauzas | nothing to tell tho | |
| 16:28:52 | bauzas | moving on | |
| 16:28:59 | bauzas | #info Please look at the gate failures and file a bug report with the gate-failure tag. | |
| 16:29:03 | bauzas | #info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures | |
| 16:29:17 | bauzas | next topic, | |
| 16:29:22 | bauzas | #topic Release Planning | |
| 16:29:27 | bauzas | #link https://releases.openstack.org/zed/schedule.html | |
| 16:29:31 | bauzas | #info Zed-1 is due in 1 week | |
| 16:29:38 | bauzas | well, 9 days tbc | |
| 16:30:00 | bauzas | there is no deadline about this milestone in terms of code or spec review tbc | |
| 16:30:10 | bauzas | #info Spec review day happens today on May 10th | |
| 16:30:25 | bauzas | I've seen good efforts from a couple of people here | |
| 16:30:34 | sean-k-mooney | for m1 we should try and land any traits for approved specs | |
| 16:30:35 | bauzas | thanks to all who played this game today | |
| 16:30:46 | sean-k-mooney | so that they can be inlcuded in the m1 release | |
| 16:30:54 | bauzas | this will continue until end of our day, depending on your TZ of course :) | |
| 16:31:28 | bauzas | sean-k-mooney: good call | |
| 16:32:47 | bauzas | sean-k-mooney: I guess you meant https://review.opendev.org/c/openstack/osc-placement/+/828545 ? | |
| 16:34:12 | sean-k-mooney | no | |
| 16:34:29 | bauzas | link then ? | |
| 16:35:25 | sean-k-mooney | things like this https://review.opendev.org/c/openstack/os-traits/+/832769 | |
| 16:35:36 | bauzas | oh | |
| 16:35:37 | sean-k-mooney | that is not appoved yet | |
| 16:35:52 | sean-k-mooney | but for our unit tests to pass traits need to be in a release version of os-traits | |
| 16:35:54 | bauzas | for the library release on zed-1, gotcha | |
| 16:36:04 | sean-k-mooney | yes | |
| 16:36:07 | bauzas | surely, we can make it | |
| 16:36:39 | bauzas | sean-k-mooney: let's coordinate tomorrow for some review effort on the libs changes then | |
| 16:36:51 | opendevreview | Artom Lifshitz proposed openstack/nova master: Reproduce bug 1952745 https://review.opendev.org/c/openstack/nova/+/841170 | |
| 16:36:51 | opendevreview | Artom Lifshitz proposed openstack/nova master: Move evacuated instance destruction to new post_start_hook https://review.opendev.org/c/openstack/nova/+/841308 | |
| 16:37:10 | sean-k-mooney | sure its not the end of the world if we dont have them merge by m1 | |
| 16:37:29 | sean-k-mooney | i just blocks us mergin the nova code until we do an os-triats release whihc is cheap | |
| 16:37:33 | bauzas | sean-k-mooney: the only problem with the change you just proposed is that it depends on a spec which hasn't been approved yet :) | |
| 16:37:47 | bauzas | sean-k-mooney: yup, we had that problem in the past | |
| 16:37:56 | sean-k-mooney | yep | |
| 16:38:14 | sean-k-mooney | so we may have approves specs today that added traits. not sure we did | |
| 16:38:21 | bauzas | maybe let's focus on reviewing specs that have library dependencies | |
| 16:38:44 | sean-k-mooney | jsut wanted to highlight for peopel if you own one fo those spec then please submit a os-tirat patch if it had traits and ill be happy to review | |
| 16:38:46 | bauzas | sean-k-mooney: no, but I can personnally focus my effort on such specs | |
| 16:38:58 | bauzas | moving on tho, time flies | |
| 16:39:04 | bauzas | #topic Review priorities | |
| 16:39:11 | 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:39:15 | bauzas | #link https://review.opendev.org/c/openstack/project-config/+/837595 Gerrit policy for Review-prio contributors flag. Naming bikeshed in there. | |
| 16:39:22 | bauzas | #link https://docs.openstack.org/nova/latest/contributor/process.html#what-the-review-priority-label-in-gerrit-are-use-for Documentation we already have | |
| 16:39:43 | bauzas | sean-k-mooney: I just noticed we allow any contributor to flag with +1 | |
| 16:39:59 | bauzas | but the doc says we should not allow the owner to do it directly | |
| 16:40:07 | sean-k-mooney | correct | |
| 16:40:12 | sean-k-mooney | we cant make that distinction | |
| 16:40:30 | sean-k-mooney | i tried with chanve_owner:0 | |
| 16:40:43 | bauzas | ok, then we'll need to have a smarter Gerrit query | |
| 16:40:43 | sean-k-mooney | but that will not override registered owner | |
| 16:40:56 | sean-k-mooney | or we can just discuage it when we see it | |
| 16:41:08 | sean-k-mooney | the doc still says they should not flag there own change | |
| 16:41:21 | bauzas | yup, educational enforcement :) | |
| 16:41:34 | opendevreview | Artom Lifshitz proposed openstack/nova-specs master: Domain names in metadata https://review.opendev.org/c/openstack/nova-specs/+/840974 | |
| 16:41:39 | sean-k-mooney | if it ends up being a proablem we can revaluate | |
| 16:41:40 | bauzas | ok, let's bikeshed on the names in the gerrit change itself | |
| 16:42:07 | bauzas | I don't wanna drag this meeting's time by us disagreeing on how we would label those rights | |
| 16:42:19 | sean-k-mooney | ok if there are no objection to the names as written i think we could ask infra to review | |
| 16:42:35 | bauzas | but if people care about naming such things, they should review the change | |
| 16:43:12 | bauzas | sean-k-mooney: gibi had an objection, but let's continue off this meeting | |
| 16:43:20 | sean-k-mooney | ah ok | |
| 16:43:23 | bauzas | (about the +2 naming) | |
| 16:43:31 | bauzas | #topic Stable Branches | |
| 16:43:37 | bauzas | elodilles: are you around N? | |
| 16:43:42 | elodilles | yepp | |
| 16:43:51 | bauzas | cool | |
| 16:44:12 | elodilles | i did not update the page, though, as there's no news unfortunately, | |
| 16:44:54 | elodilles | from yoga till victoria the gate looks OK afaik | |
| 16:44:58 | bauzas | ok, then | |