Wednesday, 2025-06-18

raghavendrat_hi14:01
agalicao/14:02
jbernard#startmeeting cinder14:02
opendevmeetMeeting started Wed Jun 18 14:02:44 2025 UTC and is due to finish in 60 minutes.  The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
opendevmeetThe meeting name has been set to 'cinder'14:02
jbernard#topic roll call14:02
jbernardo/ hello14:02
nileshthathagarhi14:02
agalicao/14:03
raghavendrat_hello14:03
* fungi is around for this one14:03
yuval0/14:03
whoami-rajathi14:03
sfernandhi14:05
hvlcchao1hi14:05
agamboao/14:05
kpdevhi14:05
Saio/14:06
jbernardwelcome everyone14:07
jbernard#link https://etherpad.opendev.org/p/cinder-flamingo-meetings14:08
jbernard#topic followup14:08
gireeshhi14:09
jbernard1) gate issues with image encryption patch14:09
jbernardmhen: ^ any insights there? i haven't looked at the most recent failure14:09
jbernardbut it seemed like the failures we were seeing were unrelated14:10
fungiwere they post_failure results?14:10
fungiovh's swift was having a bad day yesterday14:10
hemnamep14:11
jbernard#link https://review.opendev.org/c/openstack/cinder/+/92629814:11
jbernardfungi: yes14:12
jbernardin nfs-tempest-full test14:12
fungi#link https://wiki.openstack.org/wiki/Infrastructure_Status is the OpenDev status feed14:13
jbernardok, maybe a recheck there will help, fungi do you know if ovh's issues are resolved today?14:13
fungiper the above, we took them out of the configuration around 22:39 utc14:14
eharneyfyi cinder pep8 is failing everywhere until https://review.opendev.org/c/openstack/cinder/+/952687 lands14:14
fungiwe haven't tried to revert the removal yet, but won't until log uploads there are working correctly of course14:14
hemnaeharney we found that one internally testing against antalope14:15
eharneyhemna: heh, so did we14:15
hemnaEike is a new dev on our team. 14:15
jbernardnice14:16
jbernardok, once that one lands we can recheck mhen's patch14:16
hemnayah I'm stoked he found a few issues and put up a few upstream fixes14:16
rmnijgh_Hi All, I'd like to request a review for this issue if thats possible https://review.opendev.org/c/openstack/cinder/+/86360014:18
jbernard2) barbican is still broken for stable/2025.114:18
jbernard/but/ octavia has been fixed and the patch has a +2, so hopefully that will resolve soon14:18
jbernard#link https://review.opendev.org/c/openstack/barbican/+/94909614:18
jbernard3) I updated launchpad with flamingo series and milestones, so blueprints can target the current dev branch14:19
jbernardthat's all for followup from last week14:20
jbernard#topic topics14:20
jbernard:)14:21
jbernardvery quickly, pep8 tests are failing14:21
jbernard#link https://review.opendev.org/c/openstack/cinder/+/95268714:21
jbernardthis is waiting a final gate run before being merged, that should happen reasonably soon14:22
jbernardnext is fungi's item, bridging the gap14:22
fungii'll try to be quick, but there's a lot we dug into... for some background on openstack-wide metrics analysis see ildikov's most recent ml post yesterday:14:23
fungi(er, monday actually)14:23
fungi#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/NTBNI7YIDCWBR6BTPEKVZIODWTVUIOXO/ BtG metrics analysis14:23
fungialso could be worthwhile to revisit her previous post in that thread going over the contributor and survey results (and anyone who hasn't filled those out for epoxy, please see if you can find a few minutes to do that!)14:23
fungias a follow-up activity, we've started doing some team-specific analyses, focusing on teams that had multiple contributor and maintainer survey responses, i had a similar topic in nova's meeting yesterday14:23
fungithe contributor survey had 2 responses for cinder and both respondents had contributed for at least 2 years and were contributors to at least two other open source projects14:24
fungimost feedback was relatively neutral (averaging 2.5-4 out of 5) with the lowest scores being on "Changes you propose are reviewed in a timely manner" and "Automated test failures quickly direct you to problems in your changes"14:24
fungithe top challenge reported was trouble with review attention, while additional feedback mentioned unstable test jobs leading to a lot of rechecks and longer delays getting approvals or merging approved changes14:24
fungithe maintainer survey also had 2 responses with mostly higher scores than the cntributor survey (averaging 4-4.5), except for "Changes you propose are reviewed in a timely manner" which averaged 1.014:24
fungicontributing challenges reported were similar to those from the other survey (review attention), while the top challenges with reviewing were from contributors failing to address review comments or ci failures and insufficient familiarity with some parts of the code14:24
fungilooking at metrics we gathered from gerrit for the past 5 development cycles, we saw caracal was particularly slow for reviews (also observed for nova and their guess was slurp), but then things got somewhat better again in the past year14:24
fungifinding some way to improve the time to first review might help keep contributors, new and established, involved and engaged; we observed similar trends in some other projects and suspect it may be more pronounced where there's heavier reliance on third-party ci results?14:25
fungiunstable ci testing also featured in responses, so could indicate a need to re-prioritize fixes to tests or underlying test frameworks (devstack?)14:25
fungiit looks like cinder is mostly merging as many changes as are proposed, though there may be some slight increase in backlog in the past few years14:26
fungiwe think that might be related to people proposing more changes late in the cycle14:27
fungisorry, i know that's a pretty big info dump (i tried to pare it down as much as possible)14:27
fungido note that we're pretty early in the process of analyzing these sorts of stats with a focus on improving the experience for maintainers and contributors, so for now this is probably a lot of stuff you already know, or at least confirming what you expected14:28
jbernardfungi: thank you for the summary, i haven't had a chance to yet process the ml mail, there's quite a bit to think about14:29
fungiwe also aren't at the point where we have much in the way of guidance or recommendations yet14:29
hemnalots of info14:29
fungianyway, i'm happy to answer questions or take feedback either here in the meeting or in the cinder channel later14:30
jbernardi agree, the results are close to what i would have predicted.  even though it's not surprising, the date will allow us to have a more informed conversation going forward14:30
fungiwe're of course planning to continue with this sort of surveying and metrics analysis over coming release cycles14:30
fungiand yeah, a big part of this is establishing a baseline so that we can better gauge whether future attempts at improving some aspects of this have any observable impact14:31
whoami-rajatthe review bandwidth has been a concern for i-dont-know-how-many cycles, we've done several efforts to improve it but seems like there is still scope of improvement there14:32
jbernardok, let's make this a followup for next meeting so folks have time to process14:32
fungianyway, i didn't have anything else on this topic at the moment, if there are no immediate questions14:32
fungiin the nova discussion yesterday, we talked about how it might be helpful to have more transparent communication to contributors when the sorts of changes they're proposing are unlikely to get reviewed in the foreseeable future, and to avoid over-committing on specs whose changes are unlikely to get reviewed14:33
fungibasically there's no shame in saying that there's more work to do than there are people to do it, and while interest in getting some small change or feature implemented is laudable, what the project really needs is help shouldering the overall maintenance burden14:34
jbernardwell said14:35
whoami-rajatone of the key things we've identified is that there are more contributors than reviewers hence we started asking contributors to review (also proposed review guidelines to ease the task) so they can receive reviews in return14:35
whoami-rajatsome of the contributors we know do this actively which is really good14:36
fungiit's good if their reviews help reduce the workload on the final reviewers, or help those new contributors gain a deeper understanding of the project so they might in time be able to help maintain it14:36
whoami-rajatexactly14:38
fungii guess there are no more questions for now, so i'm happy to stop monopolizing the meeting ;)14:40
jbernardfungi: thanks for presenting this!14:41
fungiany time, my pleasure14:41
rmnijgh_I'd still like to ask if anyone could review this issue when he/her has time for it https://review.opendev.org/c/openstack/cinder/+/86360014:41
jbernardrmnijgh_: noted in the etherpad14:44
jbernard#topic open discussion14:44
raghavendrat_we have couple of bug fixes in Dalmatian. Is backport to Caracal allowed ?14:44
hemnarmnijgh_ you might want to take a look at https://review.opendev.org/c/openstack/cinder/+/83608314:44
hemnaI've had that patch out there for a while...14:46
jbernardraghavendrat_: that's 2024.1, i believe so yes14:47
jbernardraghavendrat_: it's the last non-eol stable release currently14:48
raghavendrat_ok, thanks14:48
fungiyeah, scheduled to reach end of maintenance in ~3.5 months14:48
rmnijgh_hemna: I think my earlier mentioned issue (863600) fixes the same problem. So that one might not be needed? (not sure)14:49
hemnawell my fix doesn't require pulling all volumes from the db every 60 seconds either.14:52
jbernardok, last call14:56
jbernardthank you everyone, have a good rest of your day14:58
jbernard#endmeeting14:58
opendevmeetMeeting ended Wed Jun 18 14:58:11 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-06-18-14.02.html14:58
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-06-18-14.02.txt14:58
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-06-18-14.02.log.html14:58

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!