Earlier  
Posted Nick Remark
#openstack-nova - 2022-05-10
15:23:00 bauzas I'll briefly mention it in the right topic
15:23:01 sean-k-mooney just are we good to proceed with that
15:23:30 bauzas I'll call out for reviews and summarize the namings
15:23:40 bauzas shall be quick hopefully
15:37:04 erlon hey folks, can someone else +2 this patch so I can continue the backporting?
15:37:04 erlon https://review.opendev.org/c/openstack/nova/+/836014
15:40:43 sean-k-mooney melwitt:^
15:57:59 bauzas nova meeting in 2 mins here
16:00:12 bauzas #startmeeting nova
16:00:12 opendevmeet Meeting started Tue May 10 16:00:12 2022 UTC and is due to finish in 60 minutes. The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:12 opendevmeet Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:12 opendevmeet The meeting name has been set to 'nova'
16:00:19 bauzas hello everyone
16:00:21 stephenfin o/
16:00:22 elodilles o/
16:00:39 bauzas #link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting
16:00:53 chateaulav \0
16:01:50 bauzas ok, let's start, people can join
16:01:54 bauzas #topic Bugs (stuck/critical)
16:02:00 bauzas #info No Critical bug
16:02:06 bauzas #link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 19 new untriaged bugs (-3 since the last meeting)
16:02:14 bauzas thanks artom et al. for the triage
16:02:35 artom \o/ a net minus!
16:02:40 bauzas artom created an etherpad for bugs he looks https://etherpad.opendev.org/p/nova-bug-triage-20220503
16:02:44 bauzas looked*
16:03:04 bauzas artom: nothing to tell about those ?
16:03:19 artom Not really, just the evacuation one that's really funky
16:03:31 artom gibi and sean-k-mooney already looked at the reproducer func test
16:03:33 bauzas okay thanks
16:03:51 bauzas continuing then
16:03:59 sean-k-mooney because it inovled data loss im oke with it being a bug
16:04:05 bauzas #link https://storyboard.openstack.org/#!/project/openstack/placement 26 open stories (0 since the last meeting) in Storyboard for Placement
16:04:10 sean-k-mooney but otherwise i woudl consider it a small specless blueprint
16:04:24 bauzas sean-k-mooney: artom: bug link ?
16:04:46 sean-k-mooney https://review.opendev.org/c/openstack/nova/+/841170
16:04:54 sean-k-mooney https://bugs.launchpad.net/nova/+bug/1952745
16:05:35 bauzas thanks
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 kashyap https://kashyapc.fedorapeople.org/virt/openstack//rdo-bug-status/2017/nova-bugs-05-SEP-2017.txt
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: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 bauzas but this hasn't to be mandatory
16:15:41 kashyap bauzas: This is standard proceduce that's also done in much bigger communities like Fedora
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

Earlier   Later