| carloss | #startmeeting manila | 15:00 |
|---|---|---|
| opendevmeet | Meeting started Thu Aug 27 15:00:40 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 |
| gouthamr | o/ | 15:01 |
| carloss | courtesy ping: dviroel vhari carthaca Sai ashrodri gireesh Kumar_T Anoop_ShuklaSilvia-Wachira | 15:01 |
| carthaca | hi | 15:01 |
| Sai | o/ | 15:02 |
| vhari | hi | 15:02 |
| manideep | o/ | 15:02 |
| itaiweismanweka | o/ | 15:02 |
| Kumar_T | Hi | 15:03 |
| srinesh[m] | Hi | 15:04 |
| medha_ | Hi | 15:04 |
| gireesh | hi | 15:04 |
| carloss | alright, good quorum... let's get started | 15:04 |
| carloss | our meeting agenda for today: | 15:05 |
| carloss | #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting (Meeting agenda) | 15:05 |
| carloss | #topic Announcements | 15:05 |
| carloss | Schedule and deadlines | 15:05 |
| carloss | #link https://releases.openstack.org/hibiscus/schedule.html (Hibiscus Schedule) | 15:05 |
| carloss | so this is feature freeze week | 15:05 |
| carloss | and also client release week - all client changes that don't make it today, will need to ship as part of the next release we tag, which can be as early as we can in the upcoming release cycle | 15:06 |
| carloss | considering feature freeze is also review focus today, let's talk bugsquash briefly and get back to feature freeze and review focus :) | 15:07 |
| carloss | as we agreed, we'll be having the bugsquash async again, starting from next Monday, at 14:00 UTC | 15:09 |
| carloss | we'll talk in #openstack-manila about the list of bugs | 15:09 |
| Anoop_Shukla_ | O/ | 15:09 |
| carloss | #link https://etherpad.opendev.org/p/manila-hibiscus-m2-bugsquash (Hibiscus bugsquash) | 15:09 |
| carloss | we're targeting in progress bugs | 15:09 |
| carloss | vhari: thank you for putting the list together | 15:10 |
| carloss | any considerations on this list? | 15:10 |
| vhari | yw carloss | 15:10 |
| carloss | what we did last time: we asked contributors to go through the bugs assigned to themselves and update the changes and tag reviewers | 15:11 |
| carloss | I think we can use the same approach | 15:11 |
| carloss | we do have a bunch of changes to get in as part of this cycle | 15:11 |
| carloss | I think it will be busy, but we have a good opportunity ahead of us to tackle many bugs | 15:11 |
| carloss | any other thoughts on bugsquash? | 15:11 |
| carloss | is there an announcement you'd like to make? | 15:12 |
| carloss | alright, let's talk review focus and feature freeze | 15:12 |
| carloss | #topic Review Focus and Feature Freeze | 15:12 |
| carloss | #link https://etherpad.opendev.org/p/manila-hibiscus-review-focus (Hibiscus review focus etherpad) | 15:13 |
| carloss | I've been trying to keep the etherpad up to date considering the reviews people are receiving | 15:13 |
| gouthamr | hey we moved on quite quickly from announcements | 15:13 |
| itaiweismanweka | o/ on the weka driver (989998): PS19 went up earlier today addressing all 47 of gouthamr's review comments — config defaults moved into option definitions, comment/docstring cleanup, dropped logic manila core already handles. zuul and weka CI running now | 15:13 |
| gouthamr | quite quickly: my fingers are still waking up | 15:13 |
| itaiweismanweka | the new PS reset the votes including carloss's +2 from yesterday. given freeze is today — is a re-review possible once CI reports? and if timing is tight, what would you need from us for an FFE? | 15:13 |
| carloss | gouthamr: my bad, sorry :D | 15:13 |
| gouthamr | alright, not an announcement, but, reflecting on one from yesterday: | 15:14 |
| gouthamr | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/JQCWZP4BJOMQNGIK5WMTGPVWRAFGLJX3/ ([all][elections][ptl] 2027.1 Project Team Lead Election Conclusion and Results) | 15:14 |
| kpdev | hi | 15:14 |
| gouthamr | i wanted to take a moment to congratulate your election, carloss and thank you for nominating yourself | 15:15 |
| Anoop_Shukla_ | Congratulations carloss | 15:15 |
| itaiweismanweka | Congrats Carloss! | 15:16 |
| gouthamr | i'm very glad to see your continued vigor and care for this project team.. knowing first hand how much workload this is, i'll say we're lucky to have you | 15:16 |
| gireesh | Congrats Carloss ..! | 15:16 |
| gouthamr | thanks for all the things we don't thank you enough for :) | 15:16 |
| carthaca | Thanks carloss ! | 15:16 |
| Kumar_T | Congrats Carloss! | 15:17 |
| Sai | Ah, thanks for everything and congratulations carloss !! | 15:17 |
| sailaja | Congratulations Carloss | 15:17 |
| vhari | thank you carloss for all your contributions and big congrats :) | 15:17 |
| manideep | congratulations Carloss! | 15:18 |
| medha_ | Congratulations Carloss! | 15:18 |
| srinesh[m] | congrats carloss! | 15:19 |
| carloss | Thank you very much folks, your support means a lot. It's a pleasure to work with this team and contribute as a PTL. I appreciate all of you :) | 15:19 |
| gouthamr | ++ thanks, now let's get back to work :) | 15:20 |
| carloss | xD | 15:20 |
| carloss | itaiweismanweka: yep, we can discuss the change and I think it's close | 15:21 |
| carloss | so let's start with new drivers and then dive into features | 15:22 |
| gireesh | Goutham and Carloss, can I talk about share server replica core related changes, once itaiweismanweka done | 15:23 |
| carloss | gireesh: yep, | 15:23 |
| carloss | so Lustre merged and we're now working on on DDN Exascaler and WEKA | 15:23 |
| carloss | on DDN Exascaler: we've posted review comments and have been waiting on updates to the patch. I tried following up yesterday but we have not heard back | 15:24 |
| carloss | the driver was proposed early enough in the cycle. My feedback is more on the coding rather than the functionality not working | 15:25 |
| carloss | so things seem to be working and that is great. At this point, I'd be okay with merging and requesting a follow-up, based only on my comments. | 15:25 |
| carloss | other reviewers might feel differently. We'd need to hear from the maintainers though | 15:26 |
| Anoop_Shukla_ | Are they not active? | 15:26 |
| carloss | they have been until 2 weeks ago | 15:26 |
| Anoop_Shukla_ | Ok | 15:27 |
| carloss | but for the past two weeks, no | 15:27 |
| carloss | so I'll reach out via email | 15:27 |
| carloss | and ask | 15:27 |
| Anoop_Shukla_ | I see a pure driver as well..is it targetted for I release? | 15:27 |
| gouthamr | > so things seem to be working and that is great. At this point, I'd be okay with merging and requesting a follow-up, based only on my comments. | 15:29 |
| gouthamr | i think the issue with DDN is the lack of access control | 15:29 |
| carloss | Anoop_Shukla_: we dropped it from the list - the pure driver is a multi-cycle (or year) effort at this point and we haven't heard much | 15:29 |
| Anoop_Shukla_ | Okay | 15:29 |
| carloss | > i think the issue with DDN is the lack of access control | 15:30 |
| carloss | ah, ack - I see that interaction happening earlier in the comments. Maybe they're waiting on the readiness of the new APIs now? | 15:30 |
| gouthamr | so i wouldn't merge it without some bells and whistles, or diluting our driver minimunm required features: https://docs.openstack.org/manila/latest/contributor/driver_requirements.html#access-rules | 15:30 |
| Anoop_Shukla_ | ++ | 15:31 |
| carloss | gouthamr: yeah, that makes sense. if we do, the limitations should be written in lots of places and people should be aware of it | 15:31 |
| gireesh | carloss and gouthamr, both the patches (core and python manila client) for share server replica are in good shape, what do you think, we can merge those in this release ..? | 15:32 |
| carloss | itaiweismanweka: responding to your questions on WEKA - if we need more time based on reviews, yes, I'll be happy to grant an FFE. You guys have been super responsive and the driver was submitted within the deadlines | 15:33 |
| itaiweismanweka | that's great to hear, thank you! we'll keep the fast turnaround on any remaining review comments | 15:34 |
| itaiweismanweka | and since access control came up for DDN ; after the mid-cycle we implemented ip-based access rules for WEKAFS (plus policy groups), so the driver meets the access-rules requirement | 15:35 |
| carloss | if we need the FFE, we'll need to make it publicly through openstack-discuss mailing list | 15:35 |
| carloss | gireesh: for python-manilaclient is a more difficult conversation... we must merge it by today to tag the release. We can't hold back on client releases | 15:35 |
| carloss | In fact, I am a bit late to update the release | 15:35 |
| carloss | and for the client to make it, the core also must be merged because they have a dependency on each other and the client bumps the API version | 15:36 |
| gireesh | python manila client changes are dependent on core changes, core changes should go first | 15:36 |
| gouthamr | gireesh: i've failed to complete a review on the server patch in several passes that i've taken at it | 15:36 |
| Anoop_Shukla_ | Do we see any blockers for share server replica that cannot be addressed in a follow up? | 15:37 |
| gouthamr | yes - its just a painful read, and a reference driver implementation, i don't know if that just stalled? i don't have a way to test this stuff | 15:37 |
| gouthamr | i reviewed both patches from the netapp driver code that followed, and i am still unsure | 15:38 |
| Anoop_Shukla_ | I think there is a thorough test cycle that we are following on NetApp side.. | 15:39 |
| itaiweismanweka | gouthamr: once CI is green on PS19, would you have bandwidth for another pass today or tomorrow? happy to address anything else same-day | 15:39 |
| Anoop_Shukla_ | For both core and driver patches | 15:39 |
| Anoop_Shukla_ | There are some issues which are also being addressed.. | 15:39 |
| gireesh | We have tested all the code, we have tempest for the same and all the share server replica test are passing | 15:40 |
| Anoop_Shukla_ | How do we move forward on this? | 15:40 |
| gouthamr | Anoop_Shukla_: did you folks address the reference driver question somewhere? | 15:40 |
| Anoop_Shukla_ | Yes. I think kiran has a patch for that as well | 15:41 |
| carloss | yep, I saw that patch - did you guys also enable tempest to run on it? | 15:42 |
| gouthamr | #link https://review.opendev.org/c/openstack/manila/+/999135 ([WIP] container driver: add share server replica support) | 15:43 |
| Anoop_Shukla_ | Tempest is also being worked upon and mostly done..3rd party ci as well | 15:43 |
| carloss | and yes, it is difficult to test - I see the functional tests being run for NetApp here https://netappopenstacklogserver.s3-us-west-1.amazonaws.com/logs/60/998360/24/upstream-check-manila-smas-nas/manila-tempest-plugin-ontap-smas-nas-dhss-rest/6681746/testr_results.html - Kumar_T gireesh manideep any reason why only the share server replica tests are enabled on CI? | 15:44 |
| carloss | also, did you guys stop testing DHSS=False? | 15:44 |
| manideep | @carl | 15:44 |
| Anoop_Shukla_ | Share server replica is not supported for dhss=false | 15:45 |
| carloss | yes, but we need to test the whole driver | 15:45 |
| carloss | I mean, share server encryption is changing a lot of the basic workflows | 15:45 |
| carloss | on lib_multi_svm, lib_base in some cases | 15:45 |
| carloss | this is a huge change and for the tests being run using NetApp, they should be enabled for this change https://review.opendev.org/c/openstack/manila/+/991844 as well, right? | 15:45 |
| manideep | @carloss: We created a separate pipeline for share replication tests due to ONTAP hardware limitations. But the other tests are also being run on the manila patches using the existing pipeline. | 15:47 |
| carloss | ^ I mean the share server replica tests enabled in this change | 15:47 |
| carloss | manideep: ack, thanks for explaining | 15:48 |
| gouthamr | we're at the date where we need to make a call about the client/sdk. we've been at this situation before.. honestly, reviewer bandwidth as limited as it always was. one way we could go about this is to fix the deficiencies and target early Indri. However, if you have concerns with that, an FFE is a choice | 15:49 |
| gouthamr | but it'll be a huge bar to meet to get the reference driver whipped into shape and tested on the CI with tempest tests added for it | 15:49 |
| gouthamr | s/added for it/run against it | 15:49 |
| gouthamr | but, note that the SDK/CLI (python-manilaclient) change will not land in this release.. | 15:50 |
| Anoop_Shukla_ | I concur with taking the fixes as priority in Indri. | 15:50 |
| gouthamr | the deadline for that is today, and we've a "depends-on" to server side patches | 15:50 |
| manideep | The share server replica tempest run which Carlos’s referred has all the share server manila patches added as Depends-on. | 15:51 |
| gouthamr | gireesh: have you considered marking this API stack experimental? so we can make incremental progress on it | 15:52 |
| gireesh | hmm, please add this comment | 15:53 |
| Kumar_T | Share server replica driver patches has Depends on core patch and both Zuul and NetAPPCI passed recently which ensures the existing functionality is in good shape and no issues | 15:53 |
| carloss | Kumar_T: yep, the test run on 991844 indicate that too, but it still lacks testing for dhss=false and in the runs in the netapp driver with all the changes, we're lacking the share server replication tests enabled in that change, which is where things are actually implemented | 15:56 |
| carloss | would be nice to have it testing the whole stack with that | 15:56 |
| carloss | or is that the limitation you guys mentioned? you're not being able to test the share server replica alongside the rest of the tests? | 15:57 |
| Kumar_T | https://www.irccloud.com/pastebin/n1Y5cUhC/ | 15:58 |
| carthaca | if we have the API experimental, do we have to apply the same strictness or could an experimental API land even today? | 15:58 |
| carloss | Kumar_T: https://netappopenstacklogserver.s3-us-west-1.amazonaws.com/logs/44/991844/40/upstream-check-manila/manila-tempest-plugin-ontap-dhss/aee1eb4/testr_results.html | 15:58 |
| carloss | doesn't run share server replication as part of this suite - this is what I'm referring to | 15:59 |
| Kumar_T | got it, manideep had clarified on that | 15:59 |
| itaiweismanweka | noted zuul -1 on PS19 — single voting job failure (dummy-dhss, looks unrelated to the driver), weka CI passed both protocols. we'll recheck and investigate | 16:00 |
| carloss | carthaca: I think it helps a bit, but would be nice if we could get the reference driver | 16:00 |
| gouthamr | carthaca: i wouldn't rush it even after that transition... an FFE would help it get past today being a blocker for a decision, and i'd be more comfortable if we have an FFE on an experimental API than one that is fully baked | 16:01 |
| gouthamr | how important is it to have the client implementation land in Hibiscus | 16:01 |
| carloss | gouthamr++ | 16:01 |
| carloss | vhari: thanks for the bug list today, sorry we couldn't cover it :/ | 16:03 |
| carloss | we're over the scheduled time for the meeting - let's continue this discussion in #openstack-manila | 16:03 |
| gouthamr | ack | 16:03 |
| carloss | thanks for participating, see you in #openstack-manila | 16:03 |
| carloss | #endmeeting | 16:03 |
| opendevmeet | Meeting ended Thu Aug 27 16:03:43 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:03 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/manila/2026/manila.2026-08-27-15.00.html | 16:03 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/manila/2026/manila.2026-08-27-15.00.txt | 16:03 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/manila/2026/manila.2026-08-27-15.00.log.html | 16:03 |
| *** bauzas1 is now known as bauzas | 18:07 | |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!