Wednesday, 2026-06-17

opendevreviewSam Clippinger proposed openstack/cinder master: Add additional rbd options to improve download speed. For some rudimentary benchmarks, see: https://bugs.launchpad.net/cinder/+bug/2120509  https://review.opendev.org/c/openstack/cinder/+/95719001:29
opendevreviewwanghongtao proposed openstack/cinder master: fix: validate extend size using admin metadata  https://review.opendev.org/c/openstack/cinder/+/99370702:02
opendevreviewwanghongtao proposed openstack/cinder master: Fix volume extend size validation logic  https://review.opendev.org/c/openstack/cinder/+/99370702:03
opendevreviewwanghongtao proposed openstack/cinder master: Fix retype failure between DM and Huawei storage  https://review.opendev.org/c/openstack/cinder/+/99285103:05
opendevreviewLiron Kuchlani proposed openstack/cinder-tempest-plugin master: Add support for volume replication  https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/95288207:00
opendevreviewAmit Uniyal proposed openstack/cinder master: Add CI job to run cinder-tempest-plugin tests with native threading (no-eventlet)  https://review.opendev.org/c/openstack/cinder/+/99106507:05
opendevreviewAmit Uniyal proposed openstack/cinder master: Add CI jobs to run tests with native threading (no-eventlet)  https://review.opendev.org/c/openstack/cinder/+/98874707:05
opendevreviewAmit Uniyal proposed openstack/cinder master: Adds threading mode tests for semaphore funcs  https://review.opendev.org/c/openstack/cinder/+/99068107:05
opendevreviewAmithabh proposed openstack/cinder master: Shield backend driver exceptions from API response  https://review.opendev.org/c/openstack/cinder/+/99371507:19
*** elodilles_pto is now known as elodilles07:50
opendevreviewLucas Lafontaine proposed openstack/cinder master: Fujitsu Driver: Improve the SSH connection method  https://review.opendev.org/c/openstack/cinder/+/90712707:53
opendevreviewLiron Kuchlani proposed openstack/cinder-tempest-plugin master: Add failover/failback API tests for volume replication  https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/99365907:54
opendevreviewSaikumar Pulluri proposed openstack/cinder master: NetApp ONTAP: begin closing ZAPI-to-REST gaps  https://review.opendev.org/c/openstack/cinder/+/99336310:09
opendevreviewNimesh Desai proposed openstack/cinder master: [IBM SVf Driver] Added support of clone operation for volumegroup  https://review.opendev.org/c/openstack/cinder/+/98261710:18
opendevreviewNimesh Desai proposed openstack/cinder master: [IBM SVf driver] Adding support for individual volume snapshots  https://review.opendev.org/c/openstack/cinder/+/94900610:18
opendevreviewAmithabh proposed openstack/cinder master: Shield backend driver exceptions from API response  https://review.opendev.org/c/openstack/cinder/+/99371511:19
jbernard#startmeeting cinder14:00
opendevmeetMeeting started Wed Jun 17 14:00:50 2026 UTC and is due to finish in 60 minutes.  The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'cinder'14:00
jbernard#link https://etherpad.opendev.org/p/cinder-hibiscus-meetings14:00
jbernardcourtesy ping: jungleboyj rosmaita smcginnis tosky whoami-rajat m5z e0ne geguileo eharney jbernard hemna fabiooliveira yuval tobias-urdin adiare happystacker dosaboy hillpd msaravan sp-bmilanov Luzi sfernand simondodsley  zaubea nileshthathagar flelain wizardbit agalica lutimura kaisers aloke_dev Anoop_Shukla erlon14:01
jbernard#topic roll call14:01
jbernardo/14:01
auniyalo/14:01
rosmaitao/14:01
whoami-rajathi14:01
* fungi is around for his topic too14:02
agalicao/14:02
agalicaoh snap, it's Rajat14:02
Jyotsnao/14:03
whoami-rajatlol, didn't realize i was famous :D14:03
agalica:D14:03
fungiinfamous14:03
jbernardwelcome everyone14:07
jbernard#topic annoucements14:07
jbernardperiodic weekly jobs...14:08
jbernardI think we're in good shape14:08
jbernardyes14:08
rosmaita\o/14:09
fungicongrats! that's no small feat14:09
rosmaitai anticipate something breaking after M-2, but i am a pessimist14:09
jbernardif it's going to break, it'll break late ;)14:10
rosmaitaat the most inconvenient time14:10
jbernardbut that time is not now, so yay!14:11
rosmaita:D14:11
jbernardthat's all for annoucements, fungi you're up14:11
fungii'll try to make this quick14:11
fungi#topic Bridging the Gap Gazpacho Cycle Survey and Metrics Analysis14:12
jbernard#topic survey and metrics analysis (fungi)14:12
jbernard#topic Bridging the Gap Gazpacho Cycle Survey and Metrics Analysis14:12
jbernardsorry14:12
fungino problem, i wasn't sure if you were waiting for me to #topic (not sure if i can as not a chair anyway)14:12
fungiildiko posted openstack-wide 2026.1 (gazpacho) cycle retrospective contributor/maintainer survey results and metrics to openstack-discuss recently:14:13
fungi#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/3POML6PYPDWQNYM5IFB54O4ASXEPK4Z5/ Bridging the Gap Gazpacho Cycle Retrospective Survey Results14:13
fungi#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/CVLQIFEVNNJJ7BJSFZJ4RNZZA7ELQKDS/ Bridging the Gap Gazpacho Cycle Retrospective Metrics Analysis14:13
fungii and the other community managers on the openinfra foundation staff have also been digging into team-specific details and i'm doing a round of outreach similar to past cycles, to go over how things may have changed14:13
fungicinder had more survey responses than most teams in openstack (4 contributors and 2 maintainers), so this is great though additional participants for the next round would, as always, help us draw even more accurate conclusions14:13
fungimost contributors indicated spending 2 or more years in the project, half the respondents had experience in at least 1 other open source project while the other half only participate in this one14:13
fungiaverage ratings on the contributor survey questions were encouragingly positive overall, with actionable reviewer feedback averaging highest at 4.5 out of 5 while timeliness of review feedback was scored lowest at 2.75 average out of 514:13
fungithe most common contribution challenge selected was getting reviewer attention, followed by struggles with unstable testing, conflicting feedback from different maintainers, and nit-picky reviews at times while too shallow at other times14:14
fungiestablished contributors remarked that the review experience in cinder had improved compared to prior cycles, noting the team is small and overloaded by the volume, but indicated disappointment in some features not landing for gazpacho14:14
fungithe new survey questions about ai tools indicate only a quarter of respondents used any ai assistance (copilot for writing some unit tests), while the majority used no ai tools when contributing14:14
fungithe rankings on the maintainer survey responses were slightly lower, ranging from 4 (contributor documentation being comprehensive and up to date) down to 2 (receiving actionable and timely feedback from other reviewers)14:14
fungicontributing challenges among maintainers were very similar to those noted by contributors, most commonly trouble getting review attention from other maintainers but also unclear priorities, scope creep from reviewers, and unstable testing14:15
fungiwhen reviewing, maintainers saw many that needed further discussion but change owners were unavailable, incomplete changes (missing tests and docs), as well as priority mismatches14:15
fungione maintainer indicated using copilot to help review changes (to better understand the changes and their risks), while the other did not rely on any ai assistance in their code review workflow14:15
fungiboth maintainers used some ai assistance in preparing their own changes however, to help write unit tests and cleaner code while improving their development speed and efficiency; both used copilot, but one of them additionally used cursor14:15
fungimaintainers also left similar comments as contributors with regard to review efficiency challenges, the overloaded maintainer team's inability to tackle larger reviews, and priority features slipping to later cycles14:15
fungion the recurring priority mismatch, contributors indicated looking mainly at collaborative docs like an etherpad and irc/mailing lists but maintainers said they track them with gerrit change topics/priority votes and specs/blueprints14:16
erlon\o14:16
Anoop_ShuklaO/14:16
fungias for metrics, active maintainer count held steady at the same level as flamingo (still down significantly from epoxy) while reviewer count rose by a modest 1% (now only 5% away from the level it was at in bobcat)14:16
fungiinterestingly, even though change volume increased 17% the team still managed to basically keep up by closing 91% as many as were opened, and a whopping 53% more than were closed in flamingo!14:16
jayaanandO/14:16
rosmaita\o/14:16
fungian important note about metrics this time: since flamingo we've switched from bitergia to lfx insights as our data source, and while the numbers between them are similar there are some slight differences in how activities are counted14:16
fungibecause of this, we re-ran metrics analyses for previous cycles against the new system in order to make sure we weren't trending numbers from different backends and drawing misleading conclusions due to changing measurement methods14:16
fungianyway, that was a quick dump, i know it's a lot to take in but i didn't want to eat up too much of your meeting, so i'll put this on the agenda again for next week to give everyone time to digest and come up with questions or ideas14:17
fungione thing we're interested in finding out is whether the team implemented any new contributor or reviewer practices over the course of the last cycle, for example techniques that were discussed in the previous round of analyses14:17
fungithough i'm happy to answer any immediate feedback now too if there's time14:17
rosmaita"whether the team implemented any new contributor or reviewer practices over the course of the last cycle" -- i don't think so?14:19
jbernardrosmaita: for G?14:19
rosmaitayeah, i don't think we did anything different from F14:19
fungiyeah, for example we did see a lot more changes closed last cycle compared to flamingo, but that could just be attributed to the number of changes that were opened also increasing14:20
jbernardnot officially, no.  i think any changes were individually motivated14:20
rosmaitayeah, i wonder whether the current contributors just got used to how we work14:20
funginot mentioned above, it looked like the time to response on new changes improved dramatically14:20
rosmaitawell, that would be pretty great!14:21
fungithe mean dropped from 22 days to 5, and the average from 69 days to 3014:21
jbernardthat's unexpected, and encouraging14:21
rosmaitawow, that is impressive14:21
fungiso someone seems to be reviewing new changes a lot more often/quickly14:21
funginote that could be basically any comment or vote, even if it's just to flag review priority +/-1 or something14:22
rosmaitastill, any action on a new patch is good action14:22
jbernardi agree14:22
fungiyes, it helps especially casual contributors know their change has been at least noticed/seen14:23
fungiand in gazpacho that seemed to happen within a week most of the time, but still within a month on average14:23
fungi(very long-unaddressed changes skew the averages significantly, so the mean is a better representation of day-to-day activity)14:24
fungianyway, i didn't have anything else specific for this week, but i'll pop this back onto the agenda for next week and give people some time to ponder14:25
jbernardthanks fungi, as always, much appreciated14:26
rosmaitathanks! it is nice to have some good news14:26
fungimy pleasure!14:26
agalicaalways the most useful mushroom in the chat14:26
rosmaitafungi: are you a project-config core?14:26
fungiyes. ping me outside the meeting if you need me to look at something there14:26
jbernardrosmaita: i see what you did there ;)14:26
rosmaitafungi: will do14:27
jbernardas a side annoucement, rosmaita has a patch to make the review priority persist across rechecks, updates, rebases, etc14:28
jbernardhttps://review.opendev.org/c/openstack/project-config/+/99317714:28
erlonNot sure how much of that counted for that measure but I do have a filter to triage the last XM/S changes. Those are usualy minor work quick gains I think it worth spending time:14:28
erlonhttps://review.opendev.org/q/project:openstack/cinder+status:open+is:mergeable+-is:wip+label:Code-Review%3E%3D0+-label:Code-Review%3C%3D-1+label:Verified%3D%252B1+-age:30d++-label:Code-Review%3D1%2Cuser%3Dself+-label:Code-Review%3D-1%2Cuser%3Dself+-path:%22%5Ecinder%5C/volume%5C/drivers.*%24%2214:28
fungioh yep, i saw rosmaita's change, will take a look shortly14:29
jbernardthis should help with our prioritization piece in fungi's earlier messages14:29
fungierlon: yeah if you were actively triaging changes like that, it could easily make the observed impact, great call-out!14:29
agalicajay has been reviewing like a madman this cycle too14:30
agalicajayaanand14:30
jbernardyep, we have serveral folks stepping up recently, many thanks for everyone contributing14:30
jbernard#topic feedback on contributer doc changes (rosmaita)14:31
jbernard#link https://review.opendev.org/c/openstack/cinder/+/99346714:32
rosmaitathis is a follow-up from the ptg14:32
rosmaitaagalica "volunteered" to review the curent doc14:32
rosmaitahttps://etherpad.opendev.org/p/contributor-review-agalica14:32
jbernardvoluteered, voluntoold, all same :)14:33
rosmaitaand erlon give me feedback on the first draft14:33
agalicanah, I actually voluteered14:33
agalicahaha14:33
rosmaitaso would be helpful for some new-ish contributors to take a look14:33
rosmaitalet us know if there's anything missing that would be helpful14:33
rosmaitabut thanks to agalica all the info on the doc now is accurate14:34
Anoop_ShuklaCan we add the logging guidelines to this?14:34
agalicahappy to help14:34
fungias a follow-on to the last topic, making sure the contributor doc helps clarify where and how change review prioritization is tracked by the maintainers may solve some of the impedance mismatch we saw in the survey responses14:34
jayaanandanjalica, jbernard: thanks, appreciate it! trying to keep reviews moving this cycle without bothering everyone too much :)14:35
rosmaitaAnoop_Shukla: maybe at the bottom, in the "special info for driver maintainers" section?14:35
Anoop_Shuklayep..14:35
rosmaitagood idea, i can add that14:35
Anoop_Shuklahttps://etherpad.opendev.org/p/OpenStack_Cinder_Logging_Guidelines14:36
rosmaitathanks!14:36
rosmaitathough we should probably turn that etherpad into a "real" document14:36
Anoop_ShuklaI can convert it to a doc and float a PR14:37
jbernardthat would be great14:38
rosmaitai agree, in the meantime we can use the etherpad link and then update once the other one lands14:38
jbernardrosmaita: you also have a patch that needs attention (https://review.opendev.org/c/openstack/cinder/+/978080)?14:38
rosmaitayeah, Rajat and Eric noticed a possible race condition in PS 4 on that review14:39
rosmaitait has been addressed in PS 514:39
rosmaitabut race conditions are tricky (at least I think so)14:40
rosmaitaso it would be good if a few people could take a look to verify that it looks ok14:40
rosmaitathat's all14:41
jbernardthanks14:43
jbernard#topic open discussion14:43
JyotsnaNew HPE Alletra MP driver patch : https://review.opendev.org/c/openstack/cinder/+/969373 https://review.opendev.org/c/openstack/requirements/+/97432214:43
JyotsnaWe truly appreciate the reviewer's valuable feedback. We have addressed all comments to improve the patch. As this is critical for us to provide timelines to customers, we would be grateful for help in moving it towards merge when possible.14:43
agalicaFestival of Reviews friday since no one's mentioned it (that I saw)14:45
rosmaitaarrgh ... it's on a holiday14:47
agalicaoh, right14:47
rosmaitathis seems to happen a lot14:47
agalicaI don't even have work that day, I forgot14:47
agalicapush it to next week?14:47
rosmaitafor non-USA people, it's the "Juneteenth" holiday14:47
fungiin other news, rosmaita's sticky review-priority vote change should be taking effect here in the next few minutes (the deploy job to update the project acl in production is running now)14:49
rosmaita\o/14:49
rosmaitathanks fungi14:49
JyotsnaI also want to bring one point that we have been waiting for the new driver merge almost for a year so request reviewers to provide their valuable feedback consolidated so we can address them at stretch. 14:49
JyotsnaAs an improvement we have transitioned our CI to Jenkins for new driver to make the CI runs more smooth and easy to debug in case of failures.14:50
rosmaitaJyotsna: yes, you and your team have been patient and have responded to reviews requesting big changes14:50
JyotsnaThanks 14:50
jbernardrosmaita: should we move the review festival do you think? or skip14:51
Anoop_ShuklaWe have some netapp patches we wanted to bring up in review festival.14:52
rosmaitamaybe have it, but keep in mind that the turnout may be low14:52
Anoop_ShuklaBut if its going to be moved we can add it in etherpad for offline look14:52
agalicaI won't be there friday, but i'm going to set aside some time next week to do some reviewing regardless of whether or not we do the fest this week or next14:53
erlonI'll be around both Fridays, so for me either of them are good14:54
rosmaitamaybe what we do is keep the current schedule, move the meeting to meetpad, and i will mention in the email that people who want to participate async can look at the etherpad14:54
rosmaitato get some idea of patches to concentrate on14:55
jbernardthat sounds good14:55
rosmaitaok14:55
agalicaoh, since we're still here:14:55
agalicacan we encourage people to start using the review request etherpad again?14:56
agalicahttps://etherpad.opendev.org/p/cinder-hibiscus-reviews14:56
agalicaI know there's far more patches than that that people want reviewed14:56
jbernardyes, that's a good call14:57
jbernardim hoping we can combine that with brian's persistent priorty change14:58
agalicayeah, good idea14:58
jbernardthanks for mentioning that14:58
agalicanp, always at service my leige14:58
agalicaor is it liege14:59
agalicai before e except after c and the billion exceptions14:59
jbernardcan't forget those :)14:59
jbernardok, last call for things and/or stuff15:00
jbernardthanks everyone15:00
jbernard#endmeeting15:01
opendevmeetMeeting ended Wed Jun 17 15:01:00 2026 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2026/cinder.2026-06-17-14.00.html15:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2026/cinder.2026-06-17-14.00.txt15:01
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2026/cinder.2026-06-17-14.00.log.html15:01
erlon\o15:01
agalicasomewhere there's a very slow typist crying to themselves about not getting in their question in time15:01
opendevreviewEric Harney proposed openstack/cinder master: Tests: Remove F824 skip  https://review.opendev.org/c/openstack/cinder/+/99377215:08
opendevreviewEric Harney proposed openstack/cinder master: Fix F824 hacking errors in rpc.py  https://review.opendev.org/c/openstack/cinder/+/99377315:08
opendevreviewMerged openstack/cinder master: typing: "Import" objects  https://review.opendev.org/c/openstack/cinder/+/98509015:33
opendevreviewMerged openstack/cinder stable/2025.1: Fix missing encryption params in Quobyte driver  https://review.opendev.org/c/openstack/cinder/+/98112916:41
opendevreviewMerged openstack/cinder master: Remove driver-requirements.txt  https://review.opendev.org/c/openstack/cinder/+/99121518:28
opendevreviewMerged openstack/cinder master: Remove TODO re: Semaphore for eventlet-removal  https://review.opendev.org/c/openstack/cinder/+/99294718:29
opendevreviewGhanshyam Maan proposed openstack/cinder-tempest-plugin master: Use the new variable to enable the RBAC new defaults  https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/99383720:24

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