Earlier  
Later
New Search
Posted Nick Remark
#openstack-nova - 2022-05-10
16:07:08 bauzas ok, don't want to overdiscuss this bug in large, so I trust you, folks
16:07:36 bauzas let's say Valid and we can nitpick on whether it's requiring a BP or not during the code review
16:07:55 sean-k-mooney i think we can proceed as a bug
16:08:13 sean-k-mooney but its borderline
16:08:20 sean-k-mooney so we can move on i think
16:08:40 bauzas my first thoughts wonder whether this should be supported or not
16:08:48 bauzas but I need to look at other comments
16:09:09 bauzas but I agree, evacuate should work even if the compute is definitely gone
16:09:26 bauzas that's actually why we have evacuate :)
16:09:51 bauzas but let's not bikeshid this by noxw
16:09:55 bauzas next point
16:10:03 bauzas #info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster
16:10:15 kashyap bauzas: On bugs ...
16:10:22 bauzas which leads me to the next point,
16:10:27 bauzas #info Next bug baton is passed to Uggla
16:10:38 bauzas Uggla: you're ok with this ?
16:10:58 bauzas reminder : this is best-effort
16:11:18 bauzas metrics are cool, but that's not important
16:11:25 bauzas any effort counts, even the lowest
16:11:44 kashyap Having dedicated days of public bug triage would be nice. We did it in the distant past (here and also for RDO)
16:11:48 bauzas hmmmm, looks like Uggla is gone for today
16:11:54 kashyap But doing it off alone quietly ... it's hard to sustain
16:12:15 sean-k-mooney kashyap: i think that is the reason to have it rotate
16:12:23 bauzas kashyap: we can discuss the opportunity of a Bug Triage day later if you wish
16:12:38 bauzas but this is exceptional by nature
16:12:52 bauzas rotation helps with the triage fatigue
16:13:00 kashyap Right. A small idea:
16:13:20 kashyap When we were bootstrapping the RDO community, I used to do these public reports to the mailing list:
16:13:23 bauzas I don't want people to mark their agendas with a triage day, we're upstream here and I don't want to order people
16:13:23 kashyap https://kashyapc.fedorapeople.org/virt/openstack//rdo-bug-status/2017/nova-bugs-05-SEP-2017.txt
16:13:42 kashyap _With_ the title of the bug in the mail; so people could skim it via email ...
16:14:16 kashyap (I'm not sure if that'll work here, to send them to the -discuss list. Once every month? I don't know)
16:14:26 kashyap bauzas: No, you're misunderstanding me :)
16:14:27 bauzas kashyap: again I don't want to force any formalization of things
16:14:33 kashyap bauzas: We're not "ordering" anyoone on anything.
16:14:46 sean-k-mooney that feels a bit heavy wait but proably workable i would be less enclined to do it if i had to send a main however
16:14:57 kashyap bauzas: We've done this countless times before when doing upstream RDO community work:
16:15:11 bauzas sean-k-mooney: even the triage etherpad has to be kept *optional*
16:15:26 kashyap You simply mark a day ahead of time, note it on the list, as an announce to let people know. If people have time, thye'll join
16:15:31 bauzas this is nice artom, melwitt and gibi created one
16:15:41 kashyap bauzas: This is standard proceduce that's also done in much bigger communities like Fedora
16:15:41 bauzas but this hasn't to be mandatory
16:15:56 sean-k-mooney ok take me off the triage list then
16:16:03 sean-k-mooney this is getting more compliated then i want
16:16:12 bauzas sean-k-mooney: again, no, I want to keep it simple
16:16:19 bauzas no triage etherpad, no mailing lists
16:16:42 kashyap Sure, I know people also have lesser "will power", with shorter teams and bandwidth.
16:16:44 sean-k-mooney ack i was happen to skim hte new bugs a few time a week during my week
16:16:50 kashyap bauzas: That's fine, we can actually move on.
16:17:02 sean-k-mooney but dont really want to have to add more paperwork
16:17:19 bauzas sean-k-mooney: I'm fully on the same page, see my previous comments
16:17:28 kashyap bauzas: The mail list is an "announce". People won't magically suddenly think: "Yay! I'm going to dedicate this morning for bug triage"
16:17:37 kashyap It's a rare thing unless one has a habit, and good filters for it.
16:17:59 bauzas kashyap: about the mailing-list reminder email once per month, that's maybe something a PTL *could* do
16:18:04 kashyap sean-k-mooney: Sure, I'm the last one to suggest adding "paperwork" (yikes)
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

Earlier   Later