15:00:22 #startmeeting manila 15:00:22 Meeting started Thu Feb 13 15:00:22 2025 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:22 The meeting name has been set to 'manila' 15:00:42 courtesy ping: dviroel vhari gouthamr carthaca msaravan pulluri ashrodri 15:00:48 hi 15:01:14 hi 15:01:26 o/ 15:04:25 alright, let's get started 15:04:42 more people will likely join as the meeting goes 15:04:51 hi 15:04:59 o/ hello everyone 15:05:05 hi 15:05:09 the meeting agenda for today: 15:05:11 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:05:20 #topic Announcements 15:05:40 Schedule and Deadlines 15:05:47 #link https://releases.openstack.org/epoxy/schedule.html (Epoxy release schedule) 15:06:10 Feature freeze is in two weeks 15:08:05 we currently don't have many major features targeted to this cycle 15:08:13 we've covered a couple of changes in the mid cycle last week 15:08:21 we can get to the changes in a bit 15:08:37 the other piece of announcement is: 15:08:43 Removal of the NFS Ganesha Standalone protocol helper is postponed 15:09:15 following the discussions in the openstack-discuss mailing list and during our mid-cycle 15:09:25 ashrodri: kindly drafted this update email: 15:09:27 #link #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/DRGEQ6VMM5YMEYIC6MPG3IW6IRQE2KQL/ 15:09:37 #undo 15:09:37 Removing item from minutes: #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/DRGEQ6VMM5YMEYIC6MPG3IW6IRQE2KQL/ 15:09:45 #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/DRGEQ6VMM5YMEYIC6MPG3IW6IRQE2KQL/ 15:10:11 that will buy people more time to react to this 15:10:45 and last but not least 15:11:09 the videos from the last week's mid cycle are already available in the OpenStack Manila Youtube channel 15:11:26 #link https://www.youtube.com/watch?v=u-TdVvn_q0g&list=PLnpzT0InFrqBSfadG3r47Dznu2doNa1so 15:12:35 that's all I had for announcements 15:12:41 is there an announcement you'd like to share? 15:13:29 taking silence as no 15:13:33 on to the next topic... 15:13:37 #topic Unmaintained to EOL transitions 15:14:06 this was me, an informational topic 15:14:35 gouthamr: thanks for adding it to the agenda 15:15:34 we had a change around the way we’d keep older git branches around in 2023; instead of having really old branches be called “stable/“ - when the community can’t maintain them adequately, they would transition to “unmaintained” 15:16:26 this means, patches are still welcome; however, the branch doesn’t get the same kind of test or code review scrutiny as “stable” branches do 15:16:56 there’s a global “unmaintained-core” group that assists in the upkeep of these unmaintained branches 15:17:24 however, over time these branches need to head to retirement too 15:19:16 that’s what happened with the “unmaintained/victoria” branch last week: 15:19:24 #link https://review.opendev.org/c/openstack/releases/+/937515 15:20:19 the same thing is being done with the “unmaintained/wallaby” branch now: 15:20:47 #link https://review.opendev.org/c/openstack/releases/+/941458 15:21:17 and xena, yoga, zed would be next 15:22:42 so at the end, the unmaintained branches would have a smaller lifecycle as a part of this, right? 15:22:54 doing these transitions will help clean up the proliferation of branches on our git repos, along with reducing confusion and reduce review burden 15:23:06 s/part/result 15:23:35 carloss: not really, these branches are now several years old, and hopefully no longer relied upon 15:24:04 but, as a side effect of the SLURP model 15:24:30 we decided that only SLURP releases can go from stable to unmaintained 15:25:54 right now, there’s an “unmaintained/2023.1” branch - and it could remain open a little beyond when we transition “stable/2024.1” to unmaintained 15:26:24 “stable/2023.2” (Bobcat) on the other hand will be retired directly 15:26:31 since it’s not a SLURP release 15:27:01 #link https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html 15:28:46 gouthamr: ack, thank you 15:30:53 great topic to bring up 15:30:58 thanks for that too 15:31:06 is there something else you'd like to add? 15:31:30 ++ that’s all I had, if anyone needs these branches living longer, do let us know 15:32:04 there’s a way to object to the change, and retain these branches for a little while longer 15:32:25 but it would mean signing up to have a working CI on the branch 15:32:44 and doing code reviews when patches need to land 15:34:29 ++ 15:34:33 thank you! 15:35:58 #topic Bug Triage (vhari ) 15:36:04 #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) 15:36:18 ty carloss :) 15:36:30 lets dive in with 1st bug of the week 15:36:32 #link https://bugs.launchpad.net/manila/+bug/2098090 15:37:31 ah, I should've reported this too :/ 15:37:34 ah, someone is deploying the “master” branch 15:37:38 I am addressing this at 15:37:40 #link https://review.opendev.org/c/openstack/manila/+/940334 15:37:49 still wip, I have to go and fix it 15:37:55 https://review.opendev.org/c/openstack/manila/+/940464 15:38:14 yep, the change kpdev mentioned is also addressing it for other drivers 15:38:48 I'll update the cephfs change today... Initially I thought only CephFS NFS was affected, but cephfs native also was 15:39:01 thanks, I’d set this to high, and edit both commit messages to include the bug ID 15:39:34 ++ 15:39:39 ack, ty for a quick turn on this ++ 15:39:48 vhari: please assign this to me 15:39:57 should we .. haha ^^ 15:39:59 will do 15:40:16 next up #link https://bugs.launchpad.net/manila/+bug/2098181 15:42:16 carthaca: thanks for the report 15:42:36 makes sense; if “size” is in the filter string, we should look at the size_increase parameter as well 15:44:07 ++ 15:46:16 maybe medium prio would fit it? 15:47:56 carthaca: are you/kpdev planning on working on the fix? 15:48:42 I'm not planning to work on this 15:48:59 carthaca: ack, thanks 15:50:02 if someone feels inclined to work on it, please pick it up :) 15:50:19 I chose to do filtering via share type extra specs instead, but thought I could report the bug anyway 15:50:51 yeah, the report is very useful for reference and would be nice to have the fix in place 15:51:10 thanks for working on it 15:51:25 ack, good catch carthaca++ 15:51:51 so if not other concerns.. lets wrap up bugs to this week folks 15:52:00 vhari: thank you very much! 15:52:15 ty for pitching in as always :) 15:52:38 #topic Open Discussion 15:52:46 so bringing up feature freeze related changes 15:53:03 I believe we currently have only one change that is targeted to this cycle and is making changes to the API 15:53:10 #link https://review.opendev.org/c/openstack/manila/+/929091 (Pass share network subnet metadata updates to backend drivers) 15:53:10 #link https://review.opendev.org/c/openstack/manila/+/921831 (Dell PowerScale: Rename Isilon to PowerScale in Manila Driver) 15:53:10 #link https://review.opendev.org/c/openstack/manila/+/934676 ([Netapp] Add support for prune deleted volumes) 15:53:10 #link https://review.opendev.org/c/openstack/manila/+/940464 (Fix access rule update) 15:53:18 this is a list of some changes 15:53:21 but most are driver related 15:54:01 so I'd like to ask: is there a feature that is already proposed to gerrit and you think you'll need extra time for it? 15:54:08 I'm referring to feature freeze exceptions 15:54:54 I am working on one feature and will push the patch by 18th Feb 15:56:55 gireesh: ack, thanks! as the change is going to be proposed to gerrit 1 week before feature freeze, it gets complicated. If we can't make it, we can merge earlier in the next cycle 15:57:47 thanks caloss, changes will be less and related to netapp driver only 15:58:24 ack :) 15:58:26 alright, that's all I had for this meeting 15:58:45 we're at the top of the hour, so let's wrap up 15:58:52 thanks for participating 15:58:59 let's get back to #openstack-manila 15:59:03 have a great day! 15:59:04 #endmeeting