15:01:00 #startmeeting manila 15:01:00 Meeting started Thu Jan 13 15:01:00 2022 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:00 The meeting name has been set to 'manila' 15:01:07 o/ 15:01:10 o/ 15:01:15 o/ 15:01:16 o/ 15:01:18 o/ 15:01:20 o/ 15:01:38 o/ 15:01:38 courtesy ping: ganso dviroel tbarron felipe_rodrigues ecsantos 15:01:44 o/ 15:02:13 o/ 15:02:20 hi 15:02:28 o/ 15:02:42 hello everyone o/ 15:03:02 thank you for joining, here's our agenda for this meeting: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:03:15 lets get started 15:03:18 #topic Announcements 15:04:09 pretty silent second week of 2022 15:04:38 we're trying to name the Zorilla cycle if you missed the ML post: 15:04:54 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026620.html ([all] Nomination open for OpenStack "Z" Release Naming) 15:05:53 our new driver deadline for yoga is at the end of next week 15:06:04 #link https://releases.openstack.org/yoga/schedule.html 15:06:18 ++ whoever that proposed zorilla to the names 15:06:20 and the feature proposal freeze is in two weeks (Jan 28) 15:07:10 time's flying, so if you have featureful changes that you're working on that need to get merged in the yoga cycle, please pay attention to this deadline 15:08:04 two weeks of fun for some of you :) 15:08:53 mental exercise :) 15:09:03 this release is going so fast, just 2 weeks 15:09:42 :D 15:10:09 felipe_rodrigues: i know - its like we lost nov-dec; but the calendar in my head still thinks its 2019 15:10:36 anyone else got further announcements for today? 15:11:53 #topic Changes to manila-stable-maint 15:12:53 for a very long time, we've had a stable maintenance team that managed stable release branches 15:13:51 so we'd propose members and the team would vet these members whether they'd adhere to the stable branch maintenance procedures 15:14:20 before allowing them to +2/+W patches against stable branches of manila repositories 15:14:45 which meant that this was a subset of manila-core 15:15:42 there's a change that i'd like to discuss with this process: 15:15:49 #link https://governance.openstack.org/tc/resolutions/20210923-stable-core-team.html (2021-09-23 Stable Core Team Process) 15:16:36 given our proactive approach to backports, we need as many reviewers that we can use on stable branch changes 15:17:03 and in the recent past, i've considered +1s from non-stable cores to mean a +2 mentally because we were spread too thin 15:17:49 #link https://docs.openstack.org/project-team-guide/stable-branches.html#appropriate-fixes 15:18:09 i think at this point, everyone on manila-*-core has read these policies 15:18:24 and committed them to heart when reviewing/proposing changes to stable branches 15:18:49 i'd like to know if this is a good time to merge the core and stable-core teams... 15:19:10 i don't mean that we'd dissolve the manila*-stable-maint teams on gerrit 15:19:50 but, i'd like to add all members from the regular manila*-core groups to the respective manila*-stable-maint teams 15:20:53 that makes sense to me gouthamr... and we'd have more hands to get things moving on the stable branches 15:20:57 as we add new members to the core team, we can still take care to maybe take a cycle's worth of vetting if the person hasn't done enough core reviews or needs time to understand the stable branch process 15:21:36 I'm ok with that. As long they are aware with https://docs.openstack.org/project-team-guide/stable-branches.html#appropriate-fixes as you mentioned gouthamr 15:22:01 * dviroel sorry missing some stable reviews :( 15:22:24 dviroel you're not, i'm piling most reviews on you and carloss atm :D 15:23:05 dviroel++ carloss++ 15:24:01 thanks for your vote of confidence; any objections to this proposal? 15:25:24 * gouthamr *crickets*... ahem.. *zorillas* 15:27:05 alright :) i'll make these changes 15:27:54 any other thoughts about $topic? 15:28:25 #topic Reviews needing attention 15:28:32 #link https://etherpad.opendev.org/p/manila-yoga-review-focus 15:29:24 alright, i think a couple of the open specs merged 15:29:39 #link https://review.opendev.org/c/openstack/manila-specs/+/818854 (share transfer between project) 15:29:51 * dviroel fixes year :) 15:30:07 ^ this one is waiting on vkmc, sfernand 15:30:47 :P dviroel++ 15:30:51 hey sorry didn't have time to work on it yet 15:30:55 but I will prioritize this review for today 15:31:06 same, sorry about that 15:31:17 thanks sfernand vkmc 15:32:51 can i have some more eyes on a six removal patch? 15:33:02 #link https://review.opendev.org/c/openstack/manila/+/821162 (remove usage of six library in driver layer and the corresponding test) 15:33:35 i could take a look 15:33:39 me too :) 15:33:49 thanks fabiooliveira carloss 15:34:25 anytime gouthamr 15:34:52 need reviewers on a nondisruptive migration bugfix: 15:34:57 #link https://review.opendev.org/c/openstack/manila/+/820071 (Force share server selection on nondisruptive migration) 15:35:46 dviroel: can you help with this one in your copious free time? 15:36:24 gouthamr: sure, will do 15:36:33 thanks much :) 15:36:36 thanks dviroel :) 15:36:52 also, thanks felipe_rodrigues and gouthamr for the reviews there 15:37:31 #link https://review.opendev.org/c/openstack/python-manilaclient/+/788060 ([OSC] Add missing waiters) 15:38:14 ^ felipe_rodrigues we have you on this one... could you please re-review? 15:38:26 for sure! 15:38:32 vkmc: this could use your review as well ^ 15:39:21 kiwi_36: o/ i read your message on a related topic :) thanks for pushing to complete these 'waiters' -- sure maaritamm and i will appreciate the help! 15:39:31 ok :) 15:39:42 gouthamr, you welcome 15:40:22 thanks felipe_rodrigues vkmc 15:41:21 yw 15:41:32 vhari proposed spending some time doing a collab review - i think the time's ripe for one given we have this pad full at the moment 15:41:57 gouthamr, ty 15:42:09 lets look at this bug https://bugs.launchpad.net/manila/+bug/1920942 15:42:17 https://review.opendev.org/c/openstack/manila/+/820071 15:42:31 has +1 and +2s 15:42:43 could use extra eye 15:42:48 * gouthamr had thrown dviroel under this bus 15:42:53 :) 15:42:56 :) 15:43:22 * dviroel on it btw 15:43:35 gouthamr, hehe yeah we are in sync 15:43:57 should we work on it here or move on to another one? 15:44:26 yep - move on to the next one 15:44:42 https://bugs.launchpad.net/manila/+bug/1924230 15:44:50 https://review.opendev.org/c/openstack/manila/+/821753 15:45:43 and https://review.opendev.org/c/openstack/manila/+/817112 15:46:33 this is a two part fix, and these stable backports could use some reviews.. although here both changes have merged in the main branch 15:47:11 * gouthamr double checks https://review.opendev.org/c/openstack/manila/+/817112 --- seems like i've skipped stable/xena :( 15:48:08 gouthamr: merged in Sep 16 15:48:55 ah, so part of stable/xena 15:49:09 thanks :) panicked there for a moment 15:50:21 i'll review those replica update ones 15:50:28 thanks dviroel 15:52:47 thanks for bringing these up vhari 15:52:59 we can move https://bugs.launchpad.net/manila/+bug/1924230 to fix released 15:53:22 gouthamr, yw, ack 15:53:50 did you want to chat about any other changes 15:54:18 gouthamr, not atm .. almost out of time 15:54:38 ack, do we have any bugs to triage? 15:54:59 have one to share 15:54:59 #topic Bug Triage (vhari) 15:55:09 #link https://bugs.launchpad.net/manila/+bug/1957075 15:55:32 oh 15:55:38 we're looking for minor triage on this bug 15:57:04 felipe_rodrigues: what do you think? low? medium? 15:57:37 does the ONTAP driver support "grow_shrink"? 15:57:38 felipe_rodrigues: will you take this one? 15:57:52 how does that work with the "size" attribute from manila? 15:59:11 yeah, it is weird 15:59:31 it sounds like a medium 15:59:54 agree 16:00:19 the ontap driver lets the user grows more than manila size reports 16:00:59 if the user is using the default behavior (grows more than the manila size), the promoted replica will lose it 16:01:18 how could the user recover from it ? From manila it is not possible 16:01:36 the user must go driectly to ontap 16:02:04 i understand the issue, but don't understand why they let it grow over maniza share size 16:02:12 that'd be strange/unintended behavior felipe_rodrigues -- i recall thinking about autogrow when discussing "infinite" shares; but i thought the driver didn't "support" it 16:03:04 thats the idea of flexvols, it is flexible volumes.. we could remove this behavior though 16:03:59 I think that the default config 16:04:06 we don't change it when creating 16:04:15 alright, we can triage this further on #openstack-manila and offline; will you respond to the issue, felipe_rodrigues? 16:04:44 Yeah, I'll talk to the reporter and see what it's the expected behavior for default volumes 16:04:48 we can assign a priority, assignee and target if there's a confirmed bug here.. 16:04:51 awesome thank you 16:04:57 sorry we're over time.. 16:05:11 thanks for bringing this up vhari 16:05:21 and thank you all for attending! 16:05:30 lets wrap up and chat on #openstack-manila 16:05:34 #endmeeting