| *** mhen_ is now known as mhen | 02:44 | |
| carloss | #startmeeting manila | 15:00 |
|---|---|---|
| opendevmeet | Meeting started Thu Jan 22 15:00:34 2026 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| opendevmeet | The meeting name has been set to 'manila' | 15:00 |
| carloss | courtesy ping: dviroel carloss vhari gouthamr carthaca Sai ashrodri gireesh Kumar_T Anoop_Shukla | 15:00 |
| Kumar_T | Hi | 15:01 |
| carthaca | hi | 15:01 |
| Sai | o/ | 15:01 |
| kpdev | hi | 15:02 |
| carloss | our meeting agenda for today: | 15:02 |
| carloss | #link https://wiki.openstack.org/wiki/Manila/Meetings (Meeting agenda) | 15:02 |
| carloss | alright, let's get started | 15:04 |
| carloss | #topic Announcements | 15:04 |
| carloss | Schedule and Deadlines | 15:05 |
| carloss | #link https://releases.openstack.org/gazpacho/schedule.html (Gazpacho Schedule) | 15:05 |
| carloss | we're 1 week away from feature proposal freeze. I've seen more features surfacing on gerrit | 15:05 |
| * fungi sneaks in a few minutes late, sorry! | 15:05 | |
| * carloss waves at fungi o/ welcome :) | 15:05 | |
| carloss | the list we have on gerrit is pretty much similar to what we discussed at the PTG | 15:06 |
| carloss | what feature proposal freeze means though? | 15:06 |
| carloss | All new Manila features must be proposed and substantially completed, with unit, functional and integration tests by the end of the week. Collaborative review sessions must be proposed at this timeline, in order to speed up the review process | 15:06 |
| carloss | ^ next week | 15:06 |
| carloss | similar to new drivers | 15:07 |
| carloss | so please propose the features you're planning to merge this cycle if you haven't yet until next week | 15:07 |
| carloss | we'll use some time of the next week's meeting to schedule our collab review sessions, which should help us making early progress on reviews | 15:07 |
| carloss | also a reminder that we're ~1 month away from the actual feature freeze, where we should merge all changes we are targeting | 15:08 |
| carloss | that's all I had for $topic. Is there any other announcement you'd like to share? | 15:09 |
| carloss | alright, taking silence as no | 15:11 |
| carloss | #topic Review Focus | 15:11 |
| carloss | #link https://etherpad.opendev.org/p/manila-gazpacho-review-focus (Gazpacho review focus) | 15:11 |
| carloss | gouthamr: and I had a meeting earlier this week and we were chatting about these changes, and gouthamr made some changes to the focus etherpad | 15:12 |
| carloss | we removed some changes that merged and added new ones | 15:12 |
| carloss | and also started adding m-3 candidates in a m-3 chapter | 15:12 |
| carloss | most of the changes on the list are receiving feedback so far, and some of them very slowly | 15:13 |
| carloss | I tagged a bunch of you in the reviewers list of many changes this week | 15:13 |
| carloss | we have a high volume of features being proposed for Dell drivers, so I asked some driver maintainers for their experience | 15:15 |
| carloss | cc Anoop_Shukla_ gireesh kpdev :) | 15:15 |
| carloss | if you could please look into those, the feedback would be much appreciated | 15:16 |
| kpdev | ack | 15:16 |
| carloss | tyvm | 15:16 |
| carloss | just to reiterate: we'll look closer to the list of changes next week and schedule the collab reviews. Also, please submit any features you're planning to get merged in this cycle by next week, or do let me know if you need some extra time | 15:19 |
| carloss | that's all I had for $topic. Is there a change you'd like to highlight today? | 15:19 |
| kpdev | I will do collab review for qos type. approx 15 min slot is ok. @carloss: FYI. | 15:20 |
| kpdev | *next week | 15:21 |
| carloss | kpdev: ack, thank you! I'll add it to the mid cycle etherpad topics | 15:23 |
| carloss | #link https://etherpad.opendev.org/p/manila-gazpacho-mid-cycle (Mid cycle etherpad) | 15:23 |
| carloss | we can repeat the same format as previous 2 or 3 cycles, where we held a "mid cycle" but focused on collab reviews for proposed changes | 15:23 |
| carloss | alright, I think we can switch topics | 15:23 |
| carloss | and please add the changes to the mid cycle etherpad :) | 15:24 |
| carloss | no new bugs in manila, python-manilaclient and manila-ui for this week and we mostly have stale bugs | 15:24 |
| Anoop_Shukla_ | Ack | 15:24 |
| carloss | so I think we can skip bug triaging this week, as we have other topics to cover in open discussion | 15:24 |
| carloss | so let's switch topics | 15:25 |
| carloss | #topic Open Discussion | 15:25 |
| carloss | let's start with | 15:26 |
| carloss | (stephenfin) Integrating manilaclient OSC commands into OSC proper | 15:26 |
| carloss | #link https://review.opendev.org/q/topic:integrate-manilaclient | 15:26 |
| carloss | o/ stephenfin thanks for proposing this and bringing this up in the meeting | 15:26 |
| carloss | floor is yours | 15:26 |
| stephenfin | There's not much to say, other than does it make sense and are you happy to do that? | 15:27 |
| stephenfin | I've proposed using manilaclient as the backing library for now, but I expect to move that to SDK before long | 15:27 |
| carloss | stephenfin: yes, it makes sense. Following the discussion at the PTG, we also had other discussions for impact | 15:28 |
| carloss | and we think this would be a great step forward | 15:29 |
| stephenfin | Sweet. In that case, I'd just like to ask for reviews at some point. Because this is a large enough change, I'd be reluctant to self-approve like I would for e.g. typing stuff | 15:29 |
| carloss | stephenfin: awesome, thank you! I'll add that to our review focus etherpad as well | 15:30 |
| stephenfin | Doesn't have to be this cycle either. Just some point in, like, the next 3 months :) | 15:30 |
| stephenfin | carloss: ty! | 15:30 |
| carloss | stephenfin: ack, thanks for sharing the possible timelines | 15:31 |
| Anoop_Shukla_ | @kpdev: Both common and driver changes for QoS are done? | 15:31 |
| carloss | just a reminder for contributors: with this change (integrating manila into OSC), we'd switch the new features/commands development focus to OSC instead, and we'll need to follow OSC timelines, which are similar to ours | 15:32 |
| carloss | but that would be a great addition. I'll start looking at the changes asap, stephenfin | 15:33 |
| carloss | and thanks for working on it | 15:33 |
| stephenfin | Last thing: I have the steps needed to migrate a command from manilaclient to OSC written down locally. It could probably be fed into an LLM to automate the process (I haven't tried myself yet) | 15:34 |
| stephenfin | If anyone has a suggestion for where to place that, please let me know. | 15:34 |
| stephenfin | maybe manila-specs if that's a thing still | 15:35 |
| carloss | yes, manila-specs is still a thing and it would be a good place | 15:35 |
| stephenfin | ack, will do | 15:35 |
| carloss | that's where we documented OSC support too: | 15:35 |
| carloss | #link https://specs.openstack.org/openstack/manila-specs/specs/release_independent/manila-support-openstackclient.html | 15:35 |
| carloss | stephenfin: sweet, thanks | 15:35 |
| carloss | any other questions or thoughts on integrating manilaclient OSC commands into OSC? | 15:37 |
| carloss | going once... | 15:37 |
| carloss | thanks for bringing this up, stephenfin... that takes us to | 15:38 |
| carloss | (stephenfin) manila-core cleanup | 15:38 |
| stephenfin | Thanks. That one is more of an FYI. I suspect we don't need to discuss it unless you've some important context to add. | 15:38 |
| carloss | nope, thanks for bringing this up. I think this is a good time for a cleanup and we've been discussing adding more people to the core team over this and the next release cycle | 15:39 |
| carloss | we are still relying on some folks at that list as they can sometimes help us with reviews in emergency situations | 15:39 |
| Anoop_Shukla_ | @kpdev: https://review.opendev.org/c/openstack/manila/+/962588 WRT these changes - do you think we should keep the SMB signing as a config driven by manila.conf? | 15:40 |
| stephenfin | carloss: ack, makes sense | 15:40 |
| carloss | but now almost half of the cores in the list shifted focus to something else, and if we can add more active reviewers to the list, that would be preferred | 15:41 |
| kpdev | @anoop: I will reply to your comments and I am ok to control it via config option. | 15:41 |
| Anoop_Shukla_ | Thanks you and ack | 15:41 |
| carloss | I'll ping Victoria, Douglas and Haixin, which switched focus over the past could of years and ask if they are interested on continuing, otherwise I can update the list | 15:42 |
| carloss | any other thoughts on this topic? | 15:42 |
| carloss | (Anoop_Shukla_ ++ on switching https://review.opendev.org/c/openstack/manila/+/962588 to use a config option) | 15:43 |
| carloss | alright, thanks for bringing this up, stephenfin... much appreciated, same for the FYI for the manila channel topic the other day | 15:45 |
| carloss | let's switch topics... | 15:45 |
| carloss | (fungi) Bridging the Gap Flamingo Cycle Retrospective | 15:45 |
| carloss | o/ fungi | 15:45 |
| fungi | ildiko posted openstack-wide 2025.2 (flamingo) cycle retrospective contributor/maintainer survey results and metrics to openstack-discuss last month: | 15:45 |
| carloss | thanks for adding the topic to the meeting | 15:45 |
| fungi | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/XZZYFHMUCB3IZU5AXM366AY7WJXQMTBX/ Bridging the Gap Flamingo Cycle Retrospective Survey Results | 15:45 |
| fungi | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstac | 15:46 |
| fungi | k.org/message/FD4JALJN7OB2YNBUVWCPZZ6YNJMIL2JT/ Bridging the Gap Flamingo Cycle | 15:46 |
| fungi | Retrospective Metrics Analysis | 15:46 |
| fungi | #undo | 15:46 |
| fungi | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/FD4JALJN7OB2YNBUVWCPZZ6YNJMIL2JT/ Bridging the Gap Flamingo Cycle Retrospective Metrics Analysis | 15:46 |
| fungi | i 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 last cycle, to go over how things may have changed | 15:46 |
| fungi | the manila team had the most survey responses across all of openstack (5 contributors and 3 maintainers), more would still be better of course, but this is great! | 15:46 |
| gouthamr | w00t | 15:47 |
| fungi | 2 of the contributors self-identified as established while the other 3 considered themselves new or almost new to manila, with most contributing to 2 or more other open source projects | 15:47 |
| fungi | average ratings on the contributor survey questions were positive overall, with helpful contributor documentation coming in highest at 4.8 out of 5 and timely reviews the lowest with 3.4 (typical of overall openstack response averages) | 15:47 |
| fungi | contributors appreciated how welcoming and friendly the manila team is, as well as the contributor docs, but noted technical docs were inconsistent and following team priorities was challenging | 15:47 |
| fungi | the new survey questions about priorities were insightful: a majority of contributors (4/5) said they follow development and prioritization through launchpad blueprints, surprisingly | 15:48 |
| fungi | team meeting/discussion logs, irc/mailing lists and review topics also ranked high, nobody said they didn't know how priorities are tracked but also none of them indicated following priorities through specifications or gerrit hashtags | 15:48 |
| fungi | by comparison, maintainers indicated primarily communicating priorities through gerrit change topics, reporting in team meetings, and in irc or on the mailing list, though some did also mention blueprints, specs and gerrit hashtags | 15:48 |
| fungi | the rankings on the maintainer survey responses were pretty similar to contributors, all averaging 4.33-4.66 except for timely reviews at 3.66 out of 5 | 15:49 |
| fungi | responses noted that the time spent on mentorship was not as successful as it could have been, due to many mentees disappearing before reaching the point where they could become maintainers or engage in other leadership activities | 15:49 |
| fungi | survey results across the board were comparable with the prior cycle, but slightly better; engagement as i said was great as compared to other teams so i'd love to know a bit more about how we can replicate that | 15:49 |
| fungi | as for metrics, active maintainer and reviewer counts rose by about 10% which is great, but time to review/time to merge slipped slightly in flamingo, around 10% slower compared to the epoxy cycle (closer to antelope/bobcat/caracal) | 15:49 |
| fungi | the community managers have been distilling feedback from last year's discussions, and are working on compiling a concise set of techniques/recommendations for improving communication and efficiency, which i can get into more next week | 15:50 |
| fungi | we're also hoping to get some case studies done in concert with successful contributors and maintainers to highlight how specific practices and behaviors help them achieve better throughput, in hopes of being able to replicate them | 15:50 |
| fungi | anyway, 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 ideas | 15:50 |
| fungi | though i'm happy to answer any immediate feedback now if there's time | 15:50 |
| gouthamr | these are great insights, thank you fungi! I think we can share some feedback on some things we’ve fine tuned over the years that may be working.. | 15:51 |
| fungi | that would be much appreciated | 15:51 |
| gouthamr | the prioritization aspect is discussed here in team meetings weekly; Carlos begins each meeting with a recap of deadlines with what they mean - super useful even if you’re catching up elsewhere … we dive into what an upcoming deadline means for Manila repos and what needs to be done and who needs to do it | 15:53 |
| Anoop_Shukla_ | Timely reviews >> ++ for that and most of the above points! Great insights. | 15:53 |
| fungi | yeah, it seems like some of the contributors were aware of the meeting covering priorities | 15:53 |
| fungi | i suspect the gravitation toward lp blueprints is just old momentum | 15:54 |
| gouthamr | for prioritization we’ve been using an etherpad that everyone duly updates, or shares status on, free form.. we’ve been encouraging collab reviews - sync meetings where we try to make progress on reviews by having the author/s walk through the change | 15:54 |
| fungi | and it will take time and communication for them to better find the priority tracking information | 15:54 |
| carloss | the etherpad: https://etherpad.opendev.org/p/manila-gazpacho-review-focus | 15:55 |
| fungi | interestingly, none of the contributor survey respondents were aware of your prioritization etherpad | 15:55 |
| carloss | oh :) | 15:55 |
| fungi | (or at least didn't indicate following/referring to it) | 15:55 |
| gouthamr | ah, I did find that part interesting… usually, we insist on tracking launchpad blueprints if there’s a change spanning multiple changes or repos | 15:55 |
| gouthamr | yeah - I wonder if, they meant etherpad instead of launchpad - but we’ll never know | 15:56 |
| fungi | this is a great example of why we added the new questions about priority tracking, it does seem in many teams there's an opportunity to better communicate to contributors where and how things get prioritizd | 15:56 |
| fungi | well, the survey question was multiple choice and had launchpad blueprint as an option as well as etherpad | 15:57 |
| gouthamr | we use and emphasize launchpad for bug tracking - I mean, we still use milestones to target bugs and discuss those here | 15:59 |
| fungi | also i don't know if that's a recent shift for the team, keep in mind this survey was about the last development cycle not the currently in-progress one | 15:59 |
| carloss | yeah, so that could be a reason for most people mentioning launchpad/blueprints | 15:59 |
| gouthamr | (vhari isn’t around today but, she keeps us honest about bug tracking with her dedicated slot during these weekly meetings) | 15:59 |
| carloss | the timely reviews are a challenge we've been facing for some releases now, but as I stated earlier in this meeting, we're actively encouraging folks to join the core team | 16:00 |
| carloss | and help us drive that down | 16:00 |
| carloss | maybe we could have some other ideas around that, we used to have review jams in the past | 16:01 |
| fungi | yeah and it does look like you went up from 10 active maintainers in epoxy to 11 in flamingo | 16:01 |
| carloss | we could do something like that | 16:01 |
| carloss | thanks for sharing these great insights, fungi and thanks for all contributors and maintainers that took the time to go through the survey and share your valuable feedback | 16:01 |
| fungi | (where an active maintainer is anyone who exercised cr -2/+2 or wf +1 during the cycle) | 16:01 |
| fungi | yes, thanks for being engaged on this! | 16:02 |
| gouthamr | +1 my long periods of absences in Flamingo screwed up our stats | 16:02 |
| gouthamr | kidding - but, we are vulnerable to people stepping away | 16:03 |
| gouthamr | this is insightful, ty fungi | 16:04 |
| fungi | of course, my pleasure | 16:04 |
| carloss | gouthamr: yes, we're vulnerable... no one's at fault, time away from the project can happen and it's part of the game :) ... I think we should look at it in a perspective of having more review activity from more people | 16:05 |
| carloss | let's work on it on this cycle | 16:05 |
| carloss | still plenty of time | 16:05 |
| carloss | really insightful indeed, thanks fungi | 16:05 |
| fungi | yw | 16:05 |
| carloss | we're 5 minutes past 16 UTC, so let's wrap up and get back to #openstack-manila | 16:05 |
| carloss | thank you everyone for participating | 16:05 |
| carloss | have a great day! | 16:06 |
| carloss | #endmeeting | 16:06 |
| opendevmeet | Meeting ended Thu Jan 22 16:06:25 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:06 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/manila/2026/manila.2026-01-22-15.00.html | 16:06 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/manila/2026/manila.2026-01-22-15.00.txt | 16:06 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/manila/2026/manila.2026-01-22-15.00.log.html | 16:06 |
| Anoop_Shukla | Thank you all..have a great day/evening! | 16:06 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!