| *** ricolin_ is now known as ricolin | 00:16 | |
| *** mhen_ is now known as mhen | 02:39 | |
| carloss | #startmeeting manila | 15:00 |
|---|---|---|
| opendevmeet | Meeting started Thu Jan 29 15:00:15 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 vhari gouthamr carthaca Sai gireesh Kumar_T | 15:00 |
| vhari_ | o/ | 15:00 |
| Sai | o/ | 15:00 |
| *** vhari_ is now known as vhari | 15:00 | |
| carthaca | hi | 15:00 |
| Kumar_T | o/ | 15:00 |
| VolodymyrBoiko[m] | o/ | 15:01 |
| kpdev | hi | 15:01 |
| fungi | ahoy | 15:02 |
| gouthamr | o/ | 15:02 |
| gireesh | o/ | 15:03 |
| carloss | o/ hello everyone. Welcome! | 15:03 |
| carloss | our meeting agenda for today: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting | 15:04 |
| carloss | let's get started | 15:04 |
| carloss | #topic Announcements | 15:04 |
| carloss | Schedule and Deadlines | 15:04 |
| carloss | #link https://releases.openstack.org/gazpacho/schedule.html (Gazpacho release schedule) | 15:04 |
| carloss | this is feature proposal freeze week | 15:04 |
| carloss | and new driver deadline | 15:05 |
| carloss | what does this mean though? | 15:05 |
| 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:05 |
| carloss | ^ for the feature proposal freeze | 15:05 |
| carloss | and the new driver deadline: by the end of the week all new backend drivers for Manila must be substantially complete, with unit tests, and passing 3rd party CI. Drivers do not have to actually merge until feature freeze | 15:05 |
| carloss | we're 4 weeks away from feature freeze itself | 15:06 |
| carloss | according to the milestones we've added to the official release schedule, our mid cycle should happen in two weeks, but I think considering the high volume of patches being proposed we could have that next week | 15:07 |
| carloss | if you are all okay with it | 15:07 |
| carloss | but first, let me ask: are you working on a feature that has not been proposed to gerrit yet? | 15:08 |
| carloss | if so, please submit the change to gerrit by tomorrow or reach me out so we can chat about it and discuss it | 15:09 |
| carloss | I think that takes us to the second announcement of today: Mid Cycle Tuesday and Thursday (Feb 3rd and 5th) | 15:09 |
| carloss | is everyone okay having the mid cycle next week? the dates I am proposing would be Tuesday and Thursday, from 15:00 to 16:30 UTC | 15:10 |
| carloss | I think that should be enough time for us to go through the changes we have on gerrit | 15:10 |
| gouthamr | +1 | 15:11 |
| kpdev | +1 | 15:12 |
| Sai | +1 | 15:12 |
| vhari | +1 | 15:12 |
| Kumar_T | +1 | 15:13 |
| gireesh | +1 | 15:13 |
| carloss | Thursday means we'd only stay for extra 30 minutes in the next upstream weekly, as we will reuse this meeting slot | 15:13 |
| carloss | thanks for the feedback. I'll send an email to the mailing list asap | 15:13 |
| carloss | last but not least | 15:14 |
| carloss | April 2026 PTG Dates & Registration Now Available :) | 15:14 |
| carloss | next PTG will take place April 20-24, 2026 | 15:14 |
| carloss | so please, mark your calendars | 15:14 |
| carloss | 21 is a holiday in Brazil but traditionally we skipped Tuesdays on PTGs, so I think we'll be alright | 15:15 |
| carloss | and I'm not planning to take the 20th off too, so I'll be around | 15:15 |
| carloss | so please register: | 15:15 |
| carloss | #link https://ptg.openinfra.org/ (PTG registration) | 15:16 |
| carloss | that's all I had for $topic | 15:16 |
| carloss | do you have any other announcement to share with us today? | 15:17 |
| carloss | alright, let's go to the next topic | 15:19 |
| carloss | #topic Review Focus | 15:19 |
| carloss | #link https://etherpad.opendev.org/p/manila-gazpacho-review-focus (Review focus etherpad) | 15:19 |
| carloss | let's use this meeting to go through the featureful changes listed on the etherpad and estimate how much time would be needed in the mid cycle for the collab reviews | 15:20 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/928081 (Allow services API to filter by ensuring) | 15:20 |
| carloss | this is feature freeze material - bumps the API | 15:21 |
| carloss | failing on CI, I need to circle back and fix the issues | 15:21 |
| carloss | it's an RFE though, we can keep it in the parking lot for the mid cycle imho | 15:21 |
| carloss | unless we have strong opinions in the comments considering its design | 15:22 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/952821 (NetApp - Update ensure_shares()) | 15:23 |
| carloss | this is an RFE... had reviews but not sure we'd need some time in collab reviews. I'd say up to kpdev if he'd like to walk us through it | 15:23 |
| gouthamr | the API filtering patch seems like a good one to get in, tech debt imo | 15:23 |
| Anoop_Shukla_ | There are open comments on this review.. | 15:24 |
| carloss | gouthamr++ | 15:24 |
| carloss | Anoop_Shukla_: yep | 15:24 |
| carloss | if you guys would like to use the opportunity to cover that over a call that's also a good option | 15:25 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/957200 (Dell PowerScale: Added support of revert to snapshot) | 15:26 |
| * carloss is sharing this but there is kind of ten features being proposed in the Dell drivers :) | 15:26 | |
| Anoop_Shukla_ | +1 I think we can have a call to close some of these open comments. | 15:27 |
| carloss | Anoop_Shukla_: ack, thanks. I'll add that to the mid cycle etherpad | 15:27 |
| carloss | #link https://etherpad.opendev.org/p/manila-gazpacho-mid-cycle (Mid cycle etherpad) | 15:27 |
| * carloss apologizes, thought the link was sent in the announcement parts | 15:27 | |
| carloss | I'll message the Dell engineers and ask them to join us | 15:29 |
| carloss | I think their participation can help a lot with feedback from other driver maintainers on their changes | 15:29 |
| srinesh | Hi, from HPE we have raised a new driver review for HPE Alletra MP File https://review.opendev.org/c/openstack/manila/+/968969. We have addressed a couple of rounds of review comments from gouthamr. Wanted to check about review from another reviewer and if we should add it to the review focus etherpad ? | 15:29 |
| carloss | hey srinesh thanks for bringing this up. yeah, please add it to the etherpad | 15:30 |
| srinesh | sure will include it | 15:31 |
| carloss | srinesh: I'd also encourage you to join us at the mid cycle next week if possible - we are planning on having collab review sessions, where the change authors walks the other contributors over the changes and we can collect feedback in the call | 15:31 |
| carloss | it also helps with the review process | 15:31 |
| carloss | srinesh: thanks for looking into adding it to the etherpad | 15:32 |
| carloss | #link https://review.opendev.org/q/topic:%22bp/manage-with-mount-point-name%22 (manage with mount point name) | 15:33 |
| srinesh | sure, will attend the review sessions | 15:33 |
| carloss | srinesh: awesome, we'll be glad to have you in the call | 15:33 |
| gouthamr | srinesh: the latest code changes look good, but, still concerned about the CI reporting … do you need any help from the folks on #opendev | 15:33 |
| fungi | note that it's now #opendev:opendev.org on matrix | 15:34 |
| fungi | though if this is openstack-specific discussion, the #openstack-infra irc channel on oftc is a better fit | 15:35 |
| gouthamr | +1 | 15:35 |
| srinesh | gouthamr: Yes looks like we will need help regarding account permissions.. | 15:36 |
| srinesh | I will check with our CI team and get back on specifics | 15:38 |
| gouthamr | ack, another option is to email openstack-discuss@lists.openstack.org with your query if it’s better to articulate the situation. probably helps with timezone conflicts too | 15:38 |
| carloss | ++ | 15:39 |
| srinesh | gouthamr: sure, will do that | 15:39 |
| srinesh | carloss: For the mid cycle reviews is there a separate invite which will be shared? | 15:40 |
| carloss | srinesh: I will share a .ics file in the openstack-discuss mailing list | 15:40 |
| srinesh | sure | 15:42 |
| carloss | alright, couple more changes that qualify for feature freeze: | 15:42 |
| carloss | QoS Types: | 15:42 |
| carloss | #link https://review.opendev.org/q/topic:%22bp/qos-types%22 | 15:42 |
| carloss | Manilaclient cleanups: | 15:42 |
| carloss | #link https://review.opendev.org/c/openstack/python-manilaclient/+/973726/ (Removal of "manila" CLI) | 15:42 |
| carloss | #link https://review.opendev.org/c/openstack/python-manilaclient/+/647538/ (Transition to keystoneauth) | 15:42 |
| carloss | Remove API v1: | 15:43 |
| carloss | #link https://review.opendev.org/q/topic:%22remove-v1%22+project:openstack/manila | 15:43 |
| carloss | #link https://review.opendev.org/q/project:openstack/manila-tempest-plugin+topic:remove-v1 | 15:43 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/940564 (Fix delete scheduler hints when share not found) | 15:43 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/973777 (Metadata for Share Replica Resource) | 15:43 |
| carloss | #link https://review.opendev.org/c/openstack/python-manilaclient/+/973923 | 15:43 |
| carloss | #link https://review.opendev.org/c/openstack/manila/+/973578 (NetApp - Add support for Synchronous replication for share ) | 15:43 |
| carloss | I'll add the collab review for these directly to the etherpad, considering the magnitude of the changes | 15:43 |
| carloss | if you'd like to drop them, please edit the mid cycle etherpad | 15:43 |
| carloss | and | 15:44 |
| carloss | #link https://review.opendev.org/q/project:openstack/manila+topic:eventlet-removal+status:open (eventlet removal changes) | 15:44 |
| gouthamr | ^ the api-v1 removal and manila CLI removal patches are significant and could use extended testing… I’d be happy to collab review these, but, it’s code deletion :D I’d be glad to start getting eyes on this sooner | 15:44 |
| carloss | gouthamr: ack, makes sense :) | 15:44 |
| carloss | alright, I think that covers feature proposal freeze and the mid cycle topic | 15:46 |
| * carloss was just chatting to vhari and we have no new bugs, so we can use the extra time to cover open discussion topics | 15:47 | |
| carloss | before we switch topics, anything else you'd like to share on $topic? | 15:47 |
| carloss | #topic Open Discussion | 15:48 |
| carloss | fungi: thanks for joining us again to continue the discussion we had last week | 15:48 |
| fungi | my pleasure! continuing from last week's conversation... | 15:48 |
| fungi | this effort started with representatives from member organizations sharing frustrations with, primarily, their employees' experiences trying to contribute patches in various openstack projects | 15:48 |
| fungi | investigating these reports on a case-by-case basis, foundation staff concluded most misunderstandings were due to mismatched expectations arising from incomplete communication or silence (and not necessarily on the part of the maintainers) | 15:49 |
| fungi | what we've observed from successful exchanges in some projects is that increasing communication effectiveness ultimately leads to improved efficiency and time savings for all parties involved; some examples include: | 15:49 |
| fungi | documenting review priorities and the prioritization process, as well as publicizing it more (e.g. with pointers in review comments), so that change owners know the priority for their own work and how to get involved in that decision | 15:49 |
| fungi | proactively communicating reviewer availability, changes in availability, and explicit handoff to other reviewers, so that change owners know how long they might be waiting (and encouraging them to communicate their own availability) | 15:49 |
| fungi | overall clearer communications with change owners, for example avoiding heavy reliance on acronyms and team-specific jargon, since english is not the primary language for a majority of our community and their familiarity with it varies | 15:49 |
| fungi | to this end, i and other community managers on the foundation staff are working on putting together some materials that we hope teams will find useful, and will collaborate with us to help improve and expand further | 15:49 |
| fungi | one thing we want to try is cut-and-paste review response templates for common situations; the vulnerability management team has used similar techniques for bug triage and assembling advisories, and they've found it saves a lot of time | 15:49 |
| fungi | another is assembling contributor and reviewer checklists to help avoid common pitfalls and anti-patterns, based on all of the earlier focus group feedback and brainstorming sessions we held with the community in 2024 | 15:49 |
| fungi | something else we want to try is collaborating to produce case studies with companies who have been investing in project maintenance work and whose employees have a track record of successful contribution patterns | 15:49 |
| fungi | we also plan to continue identifying additional tactics and strategies that teams have positive experiences with, to see if there's a way they can be generalized for adoption by other teams facing similar challenges | 15:50 |
| fungi | if anybody has follow-up thoughts or questions on any of the above, as well as for the survey and metrics analysis from last week now that you've had time to mull it over, i'm happy to answer questions and entertain feedback here | 15:50 |
| fungi | (or in the #openstack-manila irc channel after the meeting, or on the openstack-discuss mailing list, or even directly/in private for that matter) | 15:50 |
| carloss | fungi: one question, from the data from the survey, what method the teams that are clearly communicating priorities are using for it? is there a method that stands out? | 15:53 |
| fungi | not so far, for the most part it seems like at least in the survey responses, contributors are looking in the wrong places for that information | 15:54 |
| gouthamr | one thing we could do is put the review prioritization etherpad in our documentation. | 15:54 |
| fungi | also, like i suggested above, you can even link to it in initial review comments | 15:55 |
| carloss | yeah, I think documenting that would be nice | 15:55 |
| gouthamr | we do switch it every cycle currently, so it might go stale - but we use predictable naming | 15:55 |
| fungi | that sidesteps the related problems with contributors not finding the team's contributor docs | 15:55 |
| carloss | I think I can also set something to the #opensatack-manila channel's topic | 15:55 |
| carloss | as we often see contributors asking for reviews there | 15:56 |
| carloss | ^ not thinking this will be a game changer, but I think it can help | 15:57 |
| carloss | and if we have places pointing to it, maybe we could also reword it | 15:57 |
| carloss | to also mention the priority of the reviews | 15:57 |
| carloss | > but we use predictable naming | 15:57 |
| carloss | ++ | 15:57 |
| carloss | > and if we have places pointing to it, maybe we could also reword it | 15:58 |
| carloss | sorry, I was referring to the review focus etherpad | 15:58 |
| carloss | and setting the priorities there | 15:58 |
| carloss | and trying to clearly communicate where to look at to see the team's priorities | 15:58 |
| fungi | makes sense, i agree that's worth trying | 15:58 |
| carloss | just thought of something: is there a way to have a bot on gerrit? | 15:59 |
| fungi | we used to, and resurrecting that came up in earlier discussions about this | 15:59 |
| carloss | that when you propose the first patch set of a change, it displays a message on where the team is keeping their priorities list? | 15:59 |
| carloss | yeah, I think it can be useful | 16:00 |
| carloss | requires the change author to also be paying attention to it | 16:00 |
| fungi | when gerrit changed its user database backend from sql to git (notesdb), the welcomebot stopped working because it needed to be redone for looking up the user's change history | 16:00 |
| fungi | but also for this purpose we'd probably want a somewhat different design | 16:01 |
| carloss | yeah | 16:01 |
| fungi | probably a table mapping repository names to the data that should be posted would be sufficient | 16:02 |
| fungi | that way teams can have their own team-spoecific information posted in the initial comment to every change | 16:02 |
| * vhari joining late in the discussion .. has Gerrit AI code review feature been discussed? or any interest | 16:02 | |
| vhari | though it is not fool proof, there's been early adopters | 16:02 |
| fungi | vhari: yes, there was some conversation about it at the summit last year, sean mooney had a poc he was toying with | 16:03 |
| carloss | > that way teams can have their own team-spoecific information posted in the initial comment to every change | 16:03 |
| carloss | ++ - I think this can be a good thing to raise awareness of contributors | 16:03 |
| vhari | fungi, good to know, will check it out | 16:03 |
| fungi | julia also brought that up in the context more of implementation details for integrating it into the workflow | 16:03 |
| vhari | afaik it may require work from maintainers and training etc. | 16:04 |
| fungi | i think sean's poc was just something running locally to give feedback on personal diffs before pushing them to gerrit | 16:04 |
| fungi | anyway, i went way over time, i don't want to hold the meeting up | 16:04 |
| vhari | fungi++ | 16:05 |
| carloss | alright, I can take the AI to update our doc and share where we keep the reviews list and where we prioritize. I can also revamp the review focus etherpad to make it display priorities | 16:05 |
| carloss | I think this is a step in the right direction | 16:05 |
| carloss | fungi: thanks for bringing this up | 16:05 |
| fungi | sounds great | 16:05 |
| fungi | my pleasure, as always! | 16:05 |
| carloss | really appreciate the discussion | 16:05 |
| carloss | and the thoughts | 16:05 |
| carloss | feedback, etc :) | 16:05 |
| vhari | AI as in Action Item :) | 16:05 |
| carloss | haha, yeah, that has a double meaning now :) | 16:06 |
| carloss | alright, let's continue in #openstack manila | 16:06 |
| carloss | gouthamr++ fungi++ vhari++ thanks for sharing your thoughts | 16:06 |
| carloss | s/#openstack manila/#openstack-manila | 16:06 |
| carloss | thanks for participating everyone | 16:06 |
| carloss | have a great day | 16:07 |
| carloss | #endmeeting | 16:07 |
| opendevmeet | Meeting ended Thu Jan 29 16:07:08 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:07 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/manila/2026/manila.2026-01-29-15.00.html | 16:07 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/manila/2026/manila.2026-01-29-15.00.txt | 16:07 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/manila/2026/manila.2026-01-29-15.00.log.html | 16:07 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!