| carloss | #startmeeting manila | 15:00 |
|---|---|---|
| opendevmeet | Meeting started Thu Jul 16 15:00:21 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 carthaca Sai ashrodri gireesh Kumar_T | 15:00 |
| carloss | Anoop_Shukla dari-c Silvia-Wachira | 15:01 |
| vhari | hi | 15:01 |
| Kumar_T | Hi | 15:01 |
| Sai | I/ | 15:03 |
| Sai | o/ | 15:03 |
| carloss | o/ | 15:03 |
| carloss | smaller quorum today | 15:03 |
| carloss | let's get started | 15:03 |
| carloss | and we'll likely wrap up early and get back to our bugs! | 15:03 |
| carloss | #link https://wiki.openstack.org/wiki/Manila/Meetings (Meeting) | 15:03 |
| carloss | #undo | 15:04 |
| opendevmeet | Removing item from minutes: #link https://wiki.openstack.org/wiki/Manila/Meetings | 15:04 |
| carloss | #link https://wiki.openstack.org/wiki/Manila/Meetings (Meeting agenda) | 15:04 |
| carloss | our meeting agenda for today | 15:04 |
| carloss | let's get started | 15:04 |
| carloss | #topic Announcements | 15:04 |
| itaiweismanweka | ם/ | 15:04 |
| itaiweismanweka | o/ | 15:04 |
| carloss | Schedule and Deadlines | 15:04 |
| carloss | o/ itaiweismanweka | 15:04 |
| carloss | welcome | 15:04 |
| kpdev | hi | 15:05 |
| carloss | o/ kpdev | 15:05 |
| carloss | #link https://releases.openstack.org/hibiscus/schedule.html (Hibiscus Schedule) | 15:05 |
| sakumbha_ | o/ | 15:05 |
| carloss | hey there sakumbha_ | 15:05 |
| carloss | so this is our bugsquash week | 15:05 |
| carloss | and we've been firing on all cylinders on bug fixes reviews and pushing patches | 15:05 |
| carloss | thank you everyone that is participating | 15:06 |
| carloss | we'll focus more on that towards the second part of this meeting | 15:06 |
| vhari | ++ | 15:06 |
| carloss | feature proposal freeze and new driver deadlines are in two weeks | 15:06 |
| carloss | for feature proposal freeze: 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 will happen in the mid cycle, in order to speed up the review process. | 15:07 |
| carloss | for 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:07 |
| carloss | these two deadlines are two weeks from now | 15:07 |
| carloss | just a reminder: features and drivers must be proposed to gerrit | 15:07 |
| carloss | but they have until feature freeze to merge | 15:07 |
| carloss | i think we're in a good position at the moment, considering all features and so on | 15:08 |
| carloss | that's all I had in terms of our schedule | 15:08 |
| carloss | if you have any questions about such deadlines or need more time, please let me know in advance in #openstack-manila | 15:08 |
| carloss | that said | 15:08 |
| carloss | I don't have anything else to share for our schedule | 15:09 |
| carloss | I have one other announcement for today that I did not add to the agenda but I think it's worth sharing | 15:09 |
| carloss | I'd like to introduce you to sakumbha_ | 15:09 |
| carloss | Sahil is joining our team at Red Hat and will be focusing in Manila | 15:09 |
| carloss | you've seen Sahil active in the bugsquash changes and chatter already | 15:10 |
| carloss | so welcome sakumbha_, the zorilla team is lucky to have you and we're sure you'll have fun with us | 15:10 |
| sakumbha_ | Hey everyone, happy to join zorillas ! | 15:11 |
| Anoop_Shukla | O/ | 15:12 |
| * vhari brb | 15:12 | |
| carloss | alright, that's all I had for $topic. is there an announcement you'd like to share with us today? | 15:14 |
| carloss | taking silence as no | 15:16 |
| carloss | let's leave our bugsquash for the last slot | 15:17 |
| carloss | #topic Review Focus | 15:18 |
| carloss | #link https://etherpad.opendev.org/p/manila-hibiscus-review-focus (Hibiscus Review Focus etherpad) | 15:18 |
| carloss | itaiweismanweka thanks for adding a topic to the agenda | 15:18 |
| carloss | Weka share driver PS12 — re-review request on change 989998, CI green | 15:18 |
| itaiweismanweka | o/ yes, that's me! PS12 addresses all PS11 feedback — eventlet replaced with native threads, CI green (903 tests, 0 failures). Would appreciate a re-review from gouthamr or Stig. We're tracking toward the July 30 deadline. | 15:19 |
| carloss | that's awesome progress | 15:20 |
| carloss | I haven't looked yet but I am planning too | 15:20 |
| carloss | I had a quick exchange with gouthamr about it | 15:20 |
| itaiweismanweka | thanks carloss! much appreciated. Any timeline in mind, given the July 30 deadline? | 15:20 |
| carloss | where we also discussed limitations for some types of access control | 15:20 |
| carloss | > thanks carloss! much appreciated. Any timeline in mind, given the July 30 deadline? | 15:21 |
| carloss | I think you folks are good honestly. Code is proposed, CI passing | 15:21 |
| carloss | unit tests implemented | 15:21 |
| carloss | that's all we'd expect for the upcoming July 30th deadline | 15:21 |
| itaiweismanweka | great to hear, thank you! You mentioned limitations for some types of access controlת could you elaborate? We want to make sure we address any concerns. | 15:23 |
| carloss | yeah, so iirc, it's harder to place access control to shares with WEKA protocol | 15:24 |
| carloss | or I am confusing things with LUSTRE | 15:24 |
| carloss | nvm I think I am mixing things up | 15:25 |
| carloss | we intend to add this topic as part of the future weekly meetings, likely the next one | 15:25 |
| carloss | HPE folks might be interested on the discussion as well | 15:25 |
| carloss | yeah, I got it right, it's related to access rules | 15:26 |
| carloss | so we can discuss this in the upcoming weekly meetings | 15:27 |
| carloss | is there something else you folks would like to add for $topic? | 15:28 |
| itaiweismanweka | just to clarify, for WekaFS protocol, access rules being no-ops is by design, not a limitation. Access control is handled natively at the Weka cluster level. Happy to discuss further in future meetings if helpful! | 15:28 |
| carloss | we'll cover bug reviews in the bugsquash topics :) | 15:28 |
| carloss | > just to clarify, for WekaFS protocol, access rules being no-ops is by design, not a limitation. Access control is handled natively at the Weka cluster level. Happy to discuss further in future meetings if helpful! | 15:28 |
| carloss | yep, that's the thing we'd like to expand on | 15:28 |
| carloss | #topic Hibiscus Bug Squash | 15:31 |
| carloss | #link https://etherpad.opendev.org/p/manila-hibiscus-m1-bugsquash (Hibiscus bug squash) | 15:31 |
| carloss | we are making decent progress on the bugsquash | 15:32 |
| carloss | vhari: was telling me at the beginning of the meeting that we already managed to get in progress bugs from 89 to 70, which means 19 bugs closed in ~2 days | 15:32 |
| carloss | not bad at all D: | 15:32 |
| carloss | :D * | 15:32 |
| carloss | thank you everyone for reviewing the changes and uploading patches where needed | 15:33 |
| vhari | ++ mid-point check progress | 15:33 |
| Anoop_Shukla | Great! | 15:33 |
| vhari | ty for everyone who is pitching to make a dent in quality | 15:33 |
| gouthamr | ++ | 15:34 |
| carloss | we've quite a few bugs to close still - it's a long list | 15:34 |
| carloss | but I like the focus and the dedication of the reviewers | 15:34 |
| carloss | so let's keep it up | 15:34 |
| carloss | even if the changes don't merge, if they get traction is still good progress | 15:35 |
| carloss | and that happened for a lot of changes | 15:35 |
| carloss | is there a change you'd like to add to the bugsquash list or bugs you'd like to have our eyes on? | 15:35 |
| vhari | ack, and some merge conflicts have been resolved, helping with reviews | 15:36 |
| carloss | kpdev just linked https://review.opendev.org/c/openstack/manila-tempest-plugin/+/973489 and https://review.opendev.org/q/topic:%22bug/2081827%22 | 15:37 |
| kpdev | yes | 15:38 |
| carloss | the former is not a bug but important to be closed. I acked gouthamr's comment in the channel about having some comments as draft. I'll try reviewing the tests too | 15:38 |
| carloss | and I'll get to the latter changes | 15:38 |
| gouthamr | wow, bug 2081827 is serious | 15:40 |
| carloss | indeed | 15:40 |
| gouthamr | im not at my computer today, but thanks for patching that up | 15:40 |
| gouthamr | will take a look when I get in front of a bigger screen | 15:40 |
| carloss | thanks gouthamr | 15:41 |
| carloss | any other bugs you'd like to bring up as part of this meeting | 15:42 |
| carloss | ? | 15:42 |
| carloss | discussions are going pretty well in the changes | 15:43 |
| carloss | alright | 15:44 |
| carloss | #topic Open Discussion | 15:44 |
| Anoop_Shukla | Will take a look as well. | 15:44 |
| gouthamr | itaiweisman carloss o/ on the access control discussion, we have an expectation that access control is mandatory, and driven by tenants through Manila. This expectation becomes more of a concern in multi-tenant clouds and, in single tenant clouds, we have a secure-by-design stance by enforcing that each share is inaccessible when it is created - that’s the “deny by design” at play. So, if we’re allowing a different | 15:45 |
| gouthamr | design, I think we owe it to tenants that it not be the default and there are big flags to indicate that we have no way in ensuring that their shares are secured against unauthorized access. | 15:45 |
| gouthamr | just this cycle we’ve heard that wekafs, DDN’s LUSTRE driver, a new/planned HPE driver can’t map to the established model | 15:46 |
| gouthamr | im thinking we make this super obvious through our share types and tenant visible extra specs mechanism | 15:47 |
| Anoop_Shukla | Update : on the security issue https://bugs.launchpad.net/ossa/+bug/2157914 we are having internal discussion on how to tacle that. We will be defaulting to https transport type by default and a patch should follow soon. | 15:47 |
| gouthamr | good stuff | 15:47 |
| Anoop_Shukla | For NetApp Manila driver | 15:47 |
| carloss | > Update : on the security issue https://bugs.launchpad.net/ossa/+bug/2157914 we are having internal discussion on how to tacle that. We will be defaulting to https transport type by default and a patch should follow soon. | 15:50 |
| carloss | good stuff Anoop_Shukla, thanks for sharing the progress | 15:50 |
| carloss | gouthamr: yes on the access control stuff... hoping we can get all interested parties in the room next week? | 15:51 |
| carloss | or maybe in the mid cycle | 15:52 |
| Anoop_Shukla | Deny by design is correct stance IMO | 15:52 |
| Anoop_Shukla | Most storages follow that practice | 15:52 |
| carloss | agreed | 15:53 |
| Anoop_Shukla | Should we docu | 15:53 |
| gouthamr | when’s our midcycle? | 15:53 |
| Anoop_Shukla | Should we document this in the maintainers guide? | 15:53 |
| carloss | Aug 10 - Aug 14 | 15:53 |
| carloss | 2 weeks before feature freeze | 15:53 |
| carloss | but a month from now is little time to react | 15:54 |
| carloss | if the decisions taken from the discussions mean some refactoring happening | 15:54 |
| carloss | maybe we can have the mid cycle 1 week earlier? | 15:55 |
| gouthamr | I guess so | 15:55 |
| carloss | that could help... would be the week that follows the fpf and new driver deadline | 15:55 |
| gouthamr | it would allow maintainers to make changes if we decide one way or another | 15:55 |
| carloss | or we could have it at the feature proposal freeze week | 15:55 |
| gouthamr | I can write up our current stance if it’s missing from docs | 15:55 |
| carloss | that means more time to react | 15:55 |
| carloss | > I can write up our current stance if it’s missing from docs | 15:56 |
| carloss | ++, thank you! | 15:56 |
| Anoop_Shukla | We shiuld also have operators opinion on this | 15:56 |
| carloss | Anoop_Shukla++ | 15:56 |
| carloss | so everyone okay with having the mid cycle at the feature proposal freeze week? | 15:58 |
| Anoop_Shukla | ++ | 15:58 |
| carloss | awesome... we can make it "later" in the week | 15:58 |
| carloss | so that contributors have the first two or three days of the week to propose the features they didn't propose yet | 15:58 |
| carloss | and then do the mid cycle on thursday/friday or wednesday/thursday | 15:59 |
| carloss | on the good side, there's more time to react to the discussions | 15:59 |
| carloss | alright, let's wrap up the meeting | 16:00 |
| carloss | thanks for the input | 16:00 |
| carloss | let's get back to our days | 16:00 |
| carloss | hope you have a great day | 16:00 |
| carloss | see you in #openstack-manila | 16:00 |
| carloss | #endmeeting | 16:00 |
| opendevmeet | Meeting ended Thu Jul 16 16:00:42 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/manila/2026/manila.2026-07-16-15.00.html | 16:00 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/manila/2026/manila.2026-07-16-15.00.txt | 16:00 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/manila/2026/manila.2026-07-16-15.00.log.html | 16:00 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!