Thursday, 2025-08-14

*** mhen_ is now known as mhen01:30
gouthamr#startmeeting manila15:01
opendevmeetMeeting started Thu Aug 14 15:01:03 2025 UTC and is due to finish in 60 minutes.  The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'manila'15:01
haixino/15:01
zgogginHello!15:01
vhari_hi15:01
*** vhari_ is now known as vhari15:02
* carloss joins in RO mode :)15:02
* gouthamr waits a couple mins15:04
vhario/ carloss :)15:04
gireesho/15:04
kpdevhi15:05
gouthamrhello everyone15:05
gouthamrthanks for joining, i'm running this meeting, but carloss is available for async communication on #openstack-manila 15:06
gouthamrlet's get started15:06
gouthamr#topic Announcements15:06
gouthamrwe're making good progress on the release15:07
gouthamr#link https://releases.openstack.org/flamingo/schedule.html (Flamingo Schedule)15:07
gouthamrAugust 28th is Feature Freeze, so we're expecting all featureful patches targeted at this release to be merged by then15:08
gouthamrthis is also when we'll be finalizing python-manilaclient for the Flamingo release.. 15:08
gouthamrwhich means that we'll be releasing manilaclient shortly after, and won't be accepting anything that looks like a feature until we ship the client 15:08
gouthamrthank you all for joining the midcycle last week15:09
gouthamryou'll find the recordings on our Youtube channel:15:10
gouthamr#link https://www.youtube.com/watch?v=KkgxPgkm4n015:10
gouthamr#link https://www.youtube.com/watch?v=e8fux6Lv-oA15:10
gouthamri thought it was super productive, thank you for taking us through the code patches you were authoring, and for reviewing/commenting on the changes 15:11
gouthamrpursuant to this, we've merged one set of changes that were discussed there:15:11
gouthamr#link https://review.opendev.org/q/hashtag:%22powerscale-rename-manila%22+(status:open%20OR%20status:merged) 15:12
gouthamrwe'll talk through the others in this meeting 15:12
gouthamrthe final announcement i have is regarding Elections for OpenStack PTL and TC positions15:12
gouthamr#link https://governance.openstack.org/election/ 15:13
gouthamrthe nomination period ends next week (Aug 20th)15:13
gouthamrso if you're interested in becoming either and wanted to chat, please do ping carloss and me, we've gathered quite some experience between us in these roles, and are always willing to help bring someone new to lead the community15:14
carloss++15:14
gouthamralright, that's all the announcements i had for today, did anyone else have any?15:15
gouthamr#topic Review Focus15:16
gouthamrhttps://etherpad.opendev.org/p/manila-flamingo-review-focus (Review focus etherpad)15:16
gouthamr#link https://etherpad.opendev.org/p/manila-flamingo-review-focus (Review focus etherpad)15:16
gouthamrlets walk through things that we're targeting for FF:15:18
gouthamr#link https://review.opendev.org/q/topic:%22bp/share-encryption%2215:18
gouthamrthanks for the reviews here, and for the updates kpdev 15:18
gouthamrand Sai 15:19
* gouthamr is looking at the latest patches, will post comments soon15:19
gouthamranything to discuss here regarding these changes?15:20
gouthamr#link https://review.opendev.org/q/topic:%22bp/share-backup-out-of-place-restore%22 15:21
gouthamrzgoggin: i saw that you tackled many of  the comments made last week..15:22
gouthamrty!15:22
zgogginHi Goutham! I've been working this week on getting a positive hit with the tempest tests still15:23
gouthamrack, locally?15:23
zgogginthanks for taking the time to review, I will address your comments by the end of the week hopefully :)15:23
zgogginindeed15:23
zgogginI will try to create a recipie for others to test targeted restores with NFS / the LVM share driver.15:24
gouthamrperfect15:24
gouthamrkpdev: can you please review these changes too?15:25
kpdevok15:26
gouthamrty15:26
zgogginkpdev: thanks in advance for your time!15:27
gouthamrthere are other feature changes on the etherpad that need reviewer attention15:27
gouthamrplease do help us close these out15:27
gouthamrdo we want to chat about any feature change here?15:28
kpdevzgoggin: can you please review PRs , I have opened. thanks in advance. 15:28
zgogginwill do, thanks.15:29
gouthamr#topic Bug Triage (vhari)15:29
vharihi there were 3 new bugs 15:29
gouthamrgreat share 'em vhari 15:30
vharity for everyone who started working on these and all are in progress15:30
vhariusually we don't discuss wip bugs here 15:30
vhariwould like to revisit a couple of old bugs 15:30
vhari#link https://bugs.launchpad.net/manila/+bug/165035715:31
vhariis this bug still relevant15:31
* gouthamr is thinking15:33
gouthamrso we have this for a long time now15:33
vhariack, currently wishlisted15:34
gouthamrno i meant the feature exists15:34
vhariack15:34
gouthamrperhaps arne wanted us to parse the share type in manila-ui15:35
gouthamrinstead of needing extra configuration15:35
gouthamrthat's indeed a nice thing to have15:35
gouthamri can take this bug and investigate15:36
vharia nice ease-of-use add 15:36
vharigouthamr++ will keep this on the monitor list 15:37
vhari#link https://bugs.launchpad.net/manila/+bug/1810988         15:37
vhariditto for this bug15:37
gouthamrah, hasn't been seen in the CI in a long time15:37
vharigood to know, in that case we close it with a note 15:38
gouthamryes, we can close it - we occasionally do still see SSH issues but not of the nature tbarron described here15:38
vharithe bug can b e reopened if the failure is hit again15:38
vhariack, will do .. 15:39
gouthamrhe actually fixed some ssh client issues in manila-tempest-plugin and tempest itself and we committed several CI optimizations since15:39
gouthamrto deal with resource contention 15:39
vhariall good enhancements 15:40
vhariwould anyone like to bring up any other bugs here?15:41
vharitaking silence as no :)15:42
gouthamrack, ty vhari 15:42
vharithat's a wrap for bugs all15:42
gouthamr#topic Open Discussion15:42
fungii had a late addition to the agenda15:43
fungi(sorry, added it shortly before the meeting)15:43
fungiis this a good time to cover it?15:44
gouthamrhey fungi 15:44
gouthamryes15:44
fungiBridging the gap between community and contributing orgs: survey and metric analyses15:44
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 from a month or so back:15:44
fungi#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/NTBNI7YIDCWBR6BTPEKVZIODWTVUIOXO/ BtG metrics analysis15:44
fungialso could be worthwhile to revisit her previous post in that thread going over the contributor and maintainer survey results (and anyone who hasn't filled those out for epoxy, please see if you can find a few minutes to do that!)15:44
fungias a follow-up activity, we've started doing some team-specific analyses, focusing on teams that had multiple contributor and maintainer survey responses (already did nova, cinder, ironic, octavia, kolla and neutron in recent weeks)15:44
fungiwe're early in the process of analyzing these 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 expected15:45
fungia big part of this is establishing a baseline so that we can better gauge whether future attempts at improving have any observable impact, but we aren't at the point where we have much in the way of guidance or recommendations yet15:45
fungiwe have plans to continue with this sort of surveying and metrics analysis over coming release cycles; as for the initial results...15:45
fungithe contributor survey had 1 response for manila and the respondent self-identified as a new contributor who had contributed to a few other open source projects15:45
fungifeedback was mostly positive (4 or 5 out of 5) except for a 2 on "Changes you propose are reviewed in a timely manner" which is pretty commonly downranked in other openstack projects we've looked at as well15:45
fungichallenges reported were getting review attention, needing guidance to act on review feedback, and being asked to expand the scope of their change15:45
fungithe maintainer survey also had only 1 response so far, ranking 4 on most everything except for a 5 on "You receive actionable feedback from other reviewers" and 3 on "Changes you propose are reviewed in a timely manner"15:46
fungithe only contributing challenge reported by that maintainer was similar to that from the contributor survey (review attention), and for reviewing it was contributors not addressing feedback or test failures in a timely manner15:46
fungilooking at metrics we gathered from gerrit for the past 5 development cycles, review activity has been hovering around merging/closing as many changes as are being opened, so mostly keeping up with the volume lately (except in bobcat)15:46
fungithe number of active maintainers actually climbed in recently, going from 8 to 10 in the dalmatian cycle where it has held steady otherwise15:46
fungicontributor documentation seems to be highly utilized and got good feedback overall, though the contributor survey respondent highlighted that they needed more guidance which suggests some mentoring beyond the docs could be helpful15:46
fungiwhile it's hard to draw conclusions from such a small number of responses, the relationship between challenges mentioned by both contributor and maintainer suggests miscommunication in reviews, so consider more attention to clarity there15:46
fungisorry, i know that's a pretty big info dump (i tried to pare it down as much as possible), and i'm happy to answer questions or take feedback either here in the meeting or any time after in #openstack-manila too15:47
gouthamrthis is very insightful15:47
gouthamrty fungi 15:47
gouthamri think _we_ didn't advertise the surveys enough here in this meeting and the various events we've hosted15:48
fungiperfect time to start, i guess ;)15:48
gouthamrbut, since its a rolling survey, we can try to get folks (maintainers and contributors) to fill it out 15:48
gouthamryes15:48
fungii would say more open-ended. after flamingo releases we'll be updating it a bit too15:49
fungiwe have at least one additional question i'm working on for the maintainer survey to try and get a better idea as to what development and review prioritization solutions are working well15:50
gouthamr++15:50
fungia lot of the feedback across teams has been that contributors have trouble understanding what the team is prioritizing and how to participate in determing future priorities15:50
fungithat didn't come up specifically for manila, but it's been a common theme in other projects15:51
gouthamryes, we also use etherpads to prioritize reviews.. but, we're not limiting ourselves to reviewing things only on the etherpad15:51
fungiso an obvious communicaiton gap i'm hoping we can figure out and share solutions to15:51
gouthamrwe bring things to the etherpad just to manage the limited core reviewer time15:51
fungiyeah, that's similar to how i understand nova is doing it too15:52
gouthamrand for targeted things, we've resorted to using taiga15:52
fungii noticed that lots of teams have and are using review-priority label votes in gerrit, but that seems to be orthogonal to their actual priority tracking15:52
gouthamri.e., we want to run a hackathon where we needed 20 things completed, LP was less suited for driving synergy15:53
fungimakes sense. i guess taiga has a kanban sort of task planner?15:53
gouthamrbut, since we're all not familiar with taiga, even for those limited use cases, we've taken the trouble of onboarding people, creating roles for permissions etc15:53
gouthamrits not "open" enough :D 15:53
gouthamryes15:53
gouthamr#link https://tree.taiga.io/project/gouthampacha-manila-jsonschema-openapi/kanban 15:54
gouthamr#link https://tree.taiga.io/project/silvacarloss-openstack-manila-ui/kanban 15:54
gouthamr#link https://tree.taiga.io/project/ashrod98-openstacksdk-manila-support/kanban 15:54
gouthamr#link https://tree.taiga.io/project/gouthampacha-openstack-manila-osc-integration-with-python-manilaclient/kanban 15:54
gouthamr#link https://tree.taiga.io/project/gouthampacha-openstack-manila-container-storage-interface/kanban15:54
fungii vaguely remember taiga being one of the alternatives or inspirations we looked into back when storyboard was being designed15:54
fungibut i don't recall much about it now, it's been a long time (and it's probably changed a lot over the years as well)15:55
gouthamr^ some links, but you get the idea15:55
fungiyep, makes sense15:55
fungianyway, i didn't have anything else prepared to present on this topic, so if there are no questions right now then that's all i've got15:57
gouthamrthank you15:57
fungibut as i said feel free to hit me up with questions later should any occur to you15:57
gouthamri'll let folks noodle this a bit more, and create a topic for next week's meeting.. i'd like each of us to take these surveys, and perhaps we'll have good insights to take to the PTG15:57
fungicool, i was planning to lurk the next meeting anyway in case follow-up discussion happened15:57
gouthamr++15:58
gouthamrty very much for raising awareness and for the insights :) 15:58
fungimy pleasure! it's been interesting to dig into15:58
gouthamranything else from anyone before we close the meeting?15:58
gouthamrthank you all for joining.. and for reviewing changes! see you on #openstack-manila15:59
gouthamr#endmeeting15:59
opendevmeetMeeting ended Thu Aug 14 15:59:47 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
opendevmeetMinutes:        https://meetings.opendev.org/meetings/manila/2025/manila.2025-08-14-15.01.html15:59
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/manila/2025/manila.2025-08-14-15.01.txt15:59
opendevmeetLog:            https://meetings.opendev.org/meetings/manila/2025/manila.2025-08-14-15.01.log.html15:59

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