| carloss | #startmeeting manila | 15:00 |
|---|---|---|
| opendevmeet | Meeting started Thu Jun 11 15:00:12 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 |
| carthaca | hi | 15:00 |
| carloss | courtesy ping: dviroel vhari Sai gireesh Kumar_T Anoop_Shukla dari-c Silvia-Wachira | 15:00 |
| vhari | hi | 15:00 |
| * fungi is on hand as well for my topic | 15:01 | |
| kpdev | hi | 15:01 |
| * carloss waves at fungi o/ - and thanks for adding the topic | 15:02 | |
| carloss | let's get started. our meeting agenda for today: | 15:02 |
| Kumar_T | o/ | 15:02 |
| carloss | #link https://wiki.openstack.org/wiki/Manila/Meetings (Weekly meeting agenda) | 15:02 |
| carloss | #topic Announcements | 15:02 |
| carloss | Schedule and deadlines | 15:02 |
| carloss | #link https://releases.openstack.org/hibiscus/schedule.html (Hibiscus Schedule) | 15:02 |
| carloss | what's new in the agenda? well, we have our dates there | 15:03 |
| carloss | first bugsquash of the cycle will happen in a month from now, so stay tuned | 15:03 |
| * carloss was trying to avoid holidays across the globe plus some upcoming PTO of mine | 15:03 | |
| carloss | and today is - in theory - spec freeze | 15:04 |
| Sai | o/ | 15:04 |
| Silvia-Wachira | o/ | 15:04 |
| carloss | last week we mentioned that we'd do a mid point check today to see how we're doing in our specs | 15:04 |
| Anoop_Shukla | O/ | 15:04 |
| carloss | we don't have the specs we planned merged, but all of them got good reviews so far | 15:06 |
| carloss | with two exceptions | 15:06 |
| carloss | #link https://review.opendev.org/c/openstack/manila-specs/+/988495 (Specs for share server replica) | 15:06 |
| gireesh | o/ | 15:06 |
| carloss | this feels close - I appreciate gireesh's efforts on following up on comments and posting replies quickly | 15:06 |
| carloss | #link https://review.opendev.org/c/openstack/manila-specs/+/987622 (Add per-process healthcheck for Manila services) | 15:07 |
| carloss | also feels close and has my blessing (now only +1 because of the noted updates) | 15:07 |
| carloss | but from the reviews, reviewers were not disagreeing on the approach and there is consensus that it will be a great addition | 15:08 |
| carloss | #link https://review.opendev.org/c/openstack/manila-specs/+/987307 (Add Lustre share driver spec) | 15:08 |
| carloss | a couple of reviews on this spec and mostly fomenting some discussions. no disagreements yet and I don't think there should be at this point | 15:09 |
| carloss | it's a new driver addition and the spec is well written | 15:09 |
| carloss | I'd love to get more eyes and possibly some votes on this | 15:09 |
| carloss | as well as | 15:09 |
| carloss | #link https://review.opendev.org/c/openstack/manila-specs/+/991288 (Add Startup Service Reconciliation) | 15:09 |
| carloss | all of these features were discussed at the PTG | 15:09 |
| carloss | none of them merged yet but I believe this is due to the nature of contributors having holidays around the world for this and the past couple of weeks | 15:10 |
| carloss | as I stated in previous meetings | 15:12 |
| carloss | we should also pursue | 15:12 |
| carloss | #link https://review.opendev.org/c/openstack/manila-specs/+/985196 (Add VirtioFS testing scenarios) | 15:12 |
| carloss | even though it doesn't need to merge at the spec freeze deadline | 15:13 |
| carloss | considering the good progress we've had, I'd like to grant a one week's spec freeze exception to all specs I mentioned | 15:13 |
| carloss | no more specs should be proposed at this point... if more show up, we'll need to defer to the upcoming release cycle | 15:13 |
| carloss | any questions on spec freeze and the specs? | 15:13 |
| carloss | #topic Review Focus | 15:16 |
| * carloss moving faster today to have more time for the last two topics of the meeting | 15:16 | |
| carloss | #link https://review.opendev.org/c/openstack/manila-tempest-plugin/+/973489 (QoS Type tests) | 15:18 |
| carloss | this has been pending review for a while and would be awesome to have some coverage | 15:18 |
| carloss | vhari Anoop_Shukla Sai: can you please take a look? | 15:18 |
| carloss | I'll do the same | 15:18 |
| Sai | Sure carloss | 15:19 |
| Anoop_Shukla_ | Sure | 15:19 |
| vhari | ofc carloss | 15:20 |
| carloss | thank you | 15:20 |
| carloss | we should continue looking at the bug fixes - the reviews have been slow so far | 15:22 |
| carloss | I have been working on | 15:22 |
| carloss | #link https://review.opendev.org/q/topic:%22bp/privsep-migration%22 (Rootwrap to privsep migration) | 15:22 |
| carloss | and also need some reviews, as we're targeting the completion of eventlet removal to this release cycle | 15:23 |
| carloss | can I get some eyes on these changes? | 15:23 |
| Anoop_Shukla_ | + | 15:24 |
| carloss | thank you | 15:25 |
| carloss | any other changes you'd like to bring up today? | 15:25 |
| Anoop_Shukla_ | Did we talk about share migration patches? | 15:26 |
| carloss | nope, not yet | 15:26 |
| carloss | there's been some progress, yes | 15:27 |
| Anoop_Shukla_ | https://review.opendev.org/q/topic:%22bug/2108851-get-progress%22 | 15:27 |
| Anoop_Shukla_ | https://review.opendev.org/c/openstack/manila-tempest-plugin/+/989949 | 15:28 |
| carloss | ah, I remember the request | 15:28 |
| carloss | sounds like a low hanging fruit to merge | 15:28 |
| carloss | thanks for bringing up the change | 15:30 |
| carloss | carthaca can you please take a look? I'll do too | 15:30 |
| carthaca | https://review.opendev.org/c/openstack/manila/+/989941/3 belongs to it as well, I have a question if we really should put this onto a new microversion | 15:30 |
| carloss | that's a good question - we are changing the method we get to reach an API | 15:32 |
| carloss | I think the same applies to this case | 15:34 |
| * carloss got distracted looking into the directives | 15:34 | |
| carloss | I used to have it bookmarked | 15:34 |
| carloss | #link https://docs.openstack.org/manila/latest/contributor/api_microversion_dev.html (Manila API microversions guide) | 15:35 |
| carloss | this is my go-to thing | 15:35 |
| carloss | I'd say we can discuss that in the change too | 15:36 |
| carloss | Anoop_Shukla_: thanks for bringing this up | 15:36 |
| carloss | let's switch topics :) | 15:36 |
| carloss | #topic Bug Triage | 15:36 |
| carloss | vhari: o/ | 15:36 |
| vhari | ty carloss :) | 15:36 |
| carloss | #link https://etherpad.opendev.org/p/manila-hibiscus-review-focus (Hibiscus Review Focus etherpad) | 15:36 |
| carloss | #undo | 15:36 |
| opendevmeet | Removing item from minutes: #link https://etherpad.opendev.org/p/manila-hibiscus-review-focus | 15:36 |
| carloss | #link https://etherpad.opendev.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) | 15:37 |
| vhari | we have 5 new bugs to triage .. lmk if we need to time box it for discussions | 15:37 |
| vhari | #link https://bugs.launchpad.net/manila/+bug/2155646 | 15:37 |
| carloss | yes, let's try time boxing these | 15:37 |
| carloss | more logs would be appreciated indeed | 15:38 |
| fungi | (i can squeeze my topic into 5-10 minutes at the end) | 15:38 |
| carloss | thanks for adding that comment, vhari | 15:38 |
| carloss | fungi: ack, thank you! | 15:38 |
| vhari | great .. https://bugs.launchpad.net/manila/+bug/2156130 | 15:38 |
| carloss | s/thank you/thank you for the flexibility | 15:38 |
| carloss | fungi: we can start today and continue in the next meetings too, as we did in the past :) | 15:39 |
| fungi | right, that's the plan | 15:39 |
| vhari | ty fungi will cover one more bug and pass the toke to you | 15:39 |
| carloss | carthaca: thanks for the report | 15:40 |
| carloss | this seems like a low hanging fruit | 15:40 |
| carloss | and definitely the message should not be using the 'error' type | 15:40 |
| vhari | carloss, agreed | 15:41 |
| vhari | if anyone is interested to take this on . pls self assign or reachout | 15:41 |
| vhari | last one for the day .. #link https://bugs.launchpad.net/manila/+bug/2156333 | 15:42 |
| carloss | carthaca: we missed adding message level to https://github.com/openstack/manila/blob/master/manila/share/manager.py#L7186 | 15:43 |
| carloss | should be a simple fix | 15:43 |
| carloss | > if anyone is interested to take this on . pls self assign or reachout | 15:43 |
| carloss | ++ - I think low prio and triaged status should do the trick for now | 15:43 |
| carloss | > carthaca: we missed adding message level to https://github.com/openstack/manila/blob/master/manila/share/manager.py#L7186 | 15:44 |
| carloss | this is the fix :D | 15:44 |
| carloss | on 2156333 | 15:45 |
| carloss | I agree the logging should be there, yes | 15:45 |
| carthaca | And coming up with a level name for that e.g. INFO. I think https://github.com/openstack/manila/blob/master/manila/message/message_levels.py wants to standardise the levels that can be used .. | 15:46 |
| carloss | > Or I would like it even better on metadata delete if the driver would reset the respective setting back to default (driver knows best, what that would be, i.e. setting without any metadata to begin with). | 15:46 |
| carloss | re this, I think it would make us get back to the default? likely drivers would need to store this | 15:46 |
| carloss | either in the driver private storage | 15:46 |
| carloss | or have defaults pre-configured | 15:47 |
| carloss | I'd be okay with the fix though, but if we're reverting, we need to ensure that a default is there in the first place | 15:47 |
| carloss | yeah, info sounds more accurate | 15:47 |
| carthaca | I meant, that it would be reset to the same that would happen if you create a share/subnet without any metadata | 15:48 |
| carloss | ah, I see! | 15:48 |
| carloss | thanks for explaining | 15:48 |
| carloss | I think it makes sense, yes | 15:48 |
| carloss | carthaca: is it something you folks are willing to work on? | 15:50 |
| carthaca | yes, I will find someone :) | 15:50 |
| carloss | carthaca: awesome, thank you! | 15:51 |
| vhari | ty carloss++ | 15:51 |
| vhari | that's a wrap for bugs .. floor is yours carloss / fungi | 15:51 |
| carloss | vhari: thanks for the speedrun through the bugs :D | 15:51 |
| carloss | #topic Bridging the Gap Gazpacho Cycle Survey and Metrics Analysis (fungi) | 15:51 |
| fungi | ildiko posted openstack-wide 2026.1 (gazpacho) cycle retrospective contributor/maintainer survey results and metrics to openstack-discuss recently: | 15:51 |
| fungi | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/3POML6PYPDWQNYM5IFB54O4ASXEPK4Z5/ Bridging the Gap Gazpacho Cycle Retrospective Survey Results | 15:51 |
| vhari | sure glad to help :) | 15:51 |
| fungi | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/CVLQIFEVNNJJ7BJSFZJ4RNZZA7ELQKDS/ Bridging the Gap Gazpacho Cycle Retrospective Metrics Analysis | 15:51 |
| 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 past cycles, to go over how things may have changed | 15:52 |
| fungi | once again, the manila team had the most survey responses across all of openstack (7 contributors and 3 maintainers), so i'd love to know what survey promotion efforts you may have been engaging in and where | 15:52 |
| fungi | just over half of the contributors indicated 2 or more years in the project while the others considered themselves new or almost new to manila, with most contributing to 2 or more other open source projects | 15:52 |
| fungi | average ratings on the contributor survey questions were positive overall, with actionable feedback from reviewers coming in highest at 4.7 out of 5 and discoverability of contributor documentation lowest with 3.7 | 15:52 |
| fungi | the most common contribution challenge selected was inability to determine where changes fall relative to team priorities, as well as some trouble getting reviewer attention and long silences with review activity just before deadlines | 15:52 |
| fungi | contributors remarked on having a great contributing experience, and that staying involved and learning how the team works and aligning priorities helped get their changes landed faster | 15:52 |
| fungi | some comments indicated project and contributor documentation could benefit from including a stripped-down "quick start" version covering basic concepts with a minimum necessary toolset | 15:52 |
| fungi | the new survey questions about ai tools indicate roughly a third of respondents did not use any ai assistance, while the majority used claude code (and a smattering of cursor) | 15:52 |
| fungi | these tools helped contributors find the right parts of the codebase faster, write tests and analyze failures, prototype multiple approaches for implementation, and reviewing their patches prior to putting in front of maintainers | 15:53 |
| fungi | the rankings on the maintainer survey responses were even higher, ranging from 4 (contributor documentation being up to date) to 5 (receiving actionable feedback from other reviewers) | 15:53 |
| fungi | contributing challenges among maintainers were very similar to those noted in the contributor survey responses, and when reviewing saw many incomplete changes (missing tests and docs) as well as priority mismatches | 15:53 |
| fungi | all maintainers indicated using claude code rview to help review changes, as well as one additionally using a self-built claude code review workflow along with it | 15:53 |
| fungi | the recurring priority mismatch theme is notable, as contributors indicated looking at irc, mailing lists, launchpad blueprints and gerrit change topics while maintainers are relying primarily on reporting in team meetings, gerrit change topics and gerrit hashtags | 15:53 |
| fungi | survey results across the board were comparable with the prior cycle, and engagement as i said was great compared to other teams so i'd love to know a bit more about how we can replicate that | 15:54 |
| fungi | as for metrics, active maintainer count fell by 22% while reviewer count rose by 10% compared to flamingo, and even though change volume increased 40% the team still managed to basically keep up by closing 98% as many as were opened | 15:54 |
| fungi | an 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 counted | 15:54 |
| fungi | because 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 methods | 15:54 |
| fungi | we're also still temporarily missing some numbers we have traditionally reported on, and are working out some bugs in lfx insights with their team | 15:55 |
| 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:55 |
| fungi | one 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 analyses | 15:55 |
| fungi | though i'm happy to answer any immediate feedback now too if there's time | 15:55 |
| carloss | > once again, the manila team had the most survey responses across all of openstack (7 contributors and 3 maintainers), so i'd love to know what survey promotion efforts you may have been engaging in and where | 15:56 |
| carloss | well, that's a good question and glad to know zorillas were the most participative again! some things that could help: I think I brought this up in at least 5 weekly meetings, and I also poked people in DMs trying to share how important this is to the community | 15:56 |
| fungi | that certainly could have helped | 15:57 |
| fungi | and i'm thrilled you find this helpful | 15:57 |
| carloss | we do our best to promote the survey, so I think having someone nagging contributors to respond can be one way to have more responses | 15:58 |
| carloss | and yes, it is really helpful - at least for me as PTL and for the whole community I think | 15:58 |
| carloss | we took great insights from the previous surveys | 15:58 |
| fungi | i agree more persistent follow-up is likely the reason, now to figure out how to get more teams to do *that* | 15:58 |
| carloss | I also brought that up at the PTG and we discussed what we can do better | 15:58 |
| carloss | > now to figure out how to get more teams to do *that* | 15:59 |
| carloss | very challenging for sure | 15:59 |
| fungi | also as always, if this stuff is getting onto ptg session agendas, give me a heads up and i'm happy to try to work it into my schedule | 15:59 |
| vhari | carloss, how about allocating a time slice for the survey during a weekly call? | 15:59 |
| carloss | vhari: that can be a good way out, for sure | 16:00 |
| carloss | or around PTG too? | 16:00 |
| vhari | it would alert folks of the importance but also help set a dedicated time from their busy schedules? | 16:00 |
| fungi | we try to time the survey deadlines just after the ptg, in order to enable that | 16:00 |
| vhari | ack | 16:00 |
| carloss | iirc the survey kept open through the PTG, so if all moderators used some time of their retro to ask people to do this and already start discussing what people will suggest | 16:00 |
| fungi | yes, exactly, that was our hope at least | 16:01 |
| carloss | the response window definitely helps | 16:01 |
| vhari | ++ | 16:01 |
| carloss | maybe we can try to note this to moderators? | 16:01 |
| carloss | in the emails moderators receive prior to the PTG | 16:01 |
| carloss | as a gentle reminder | 16:01 |
| fungi | ooh, good idea. i'll bring it up with diablo | 16:02 |
| fungi | anyway, please noodle on all the above and i'll be back next week in case you have more questions or ideas | 16:02 |
| carloss | fungi: I have to thank you folks for pursuing the enhancements for the LF dashboards - I was getting used to bitergio and the amount of data it produced and then it did not feel the same when we made the switch | 16:02 |
| fungi | yeah, it's been rough, but we're trying to work through it as fast as possible. ildiko and clark have done more of that than i have | 16:03 |
| carloss | on defining the priorities, we talked about something last time and I did propose a change that will definitely help | 16:04 |
| carloss | but | 16:04 |
| carloss | I don't think that will be enough | 16:04 |
| carloss | and on the "finding documentation" - I've been noticing that with google more actively doing the gemini results on the search | 16:05 |
| carloss | it's being harder to find exactly what you need | 16:05 |
| carloss | because it's been mixing up results from blogs and OpenStack docs | 16:05 |
| fungi | makes sense | 16:05 |
| carloss | that is me though | 16:05 |
| carloss | but I do think it would be useful indeed to put together a "getting started" guide | 16:06 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/978076 (Manila team priorities documentation) | 16:06 |
| carloss | > #link https://review.opendev.org/c/openstack/manila/+/978076 (Manila team priorities documentation) | 16:06 |
| carloss | I've proposed this, but I can tell you that this might not be too easy to get to it | 16:06 |
| carloss | we're a couple of minutes past the meeting time... that's great food for though, fungi | 16:07 |
| carloss | thank you for bringing this up | 16:08 |
| fungi | thanks! and you know where to find me in the meantime | 16:08 |
| carloss | and yes, let's continue this discussion in the next weekly meeting | 16:08 |
| carloss | alright, let's wrap up | 16:08 |
| carloss | thank you everyone for participating | 16:08 |
| carloss | let's get back to #openstack-manila | 16:08 |
| carloss | have a great day! | 16:08 |
| carloss | #endmeeting | 16:08 |
| opendevmeet | Meeting ended Thu Jun 11 16:08:50 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:08 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/manila/2026/manila.2026-06-11-15.00.html | 16:08 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/manila/2026/manila.2026-06-11-15.00.txt | 16:08 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/manila/2026/manila.2026-06-11-15.00.log.html | 16:08 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!