15:00:38 #startmeeting manila 15:00:38 Meeting started Thu Jun 30 15:00:38 2022 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:38 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:38 The meeting name has been set to 'manila' 15:01:15 o/ 15:01:15 courtesy ping: ganso vkmc dviroel felipe_rodrigues ecsantos vhari fabiooliveira gouthamr 15:01:16 o/ 15:01:24 o/ 15:01:56 o/ 15:02:00 oi 15:02:28 o/ 15:03:10 o/ 15:03:18 o/ 15:04:19 o/ hi all 15:04:24 great to have you here today 15:04:35 let's get started with our meeting agenda 15:04:40 o/ 15:04:42 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:05:29 #topic Announcements 15:05:40 Schedule and Deadlines: 15:05:44 #link https://releases.openstack.org/zed/schedule.html 15:06:13 we are ~1 month away from our driver deadline 15:07:20 and we have one candidate for this release: 15:07:34 #link https://review.opendev.org/c/openstack/manila/+/825429 15:08:18 fzzf[m] has been working on the driver and the CI 15:09:31 the CI seems to be reporting success and the logs are posted there, but apparently the tests are being skipped 15:09:35 I'll ask the author 15:10:09 but it would be nice if we could start giving some attention to this driver now, to have some anticipated feedback 15:10:31 +1 15:11:49 ++ 15:12:37 I have added it to our review focus etherpad 15:12:46 can I have some eyes on this? 15:13:03 I can be one of the reviewers 15:13:38 gouthamr, dviroel_ 15:13:51 also would be nice to have some NetAppers eyes 15:14:01 to help with other third party driver being added 15:14:13 felipe_rodrigues ecsantos[m] sfernand 15:14:39 carloss: ack, can do 15:14:46 ack 15:16:37 me too 15:18:06 thank you folks 15:18:45 that's all I had for announcements 15:18:55 is there any other announcement you would like to share with us today? 15:20:27 * carloss will take that as a no 15:20:39 #topic Rechecks without reason/comments 15:21:10 I briefly talked about this over the PTG where in a call the TC was chatting with the community about some rechecks without further comments 15:21:44 they were trying to get us to spread with the community that it is important to add a comment to our rechecks 15:22:30 it helps to make a bit more understandable why we are doing some rechecks 15:23:18 and thinking more before actually triggering it 15:23:55 this surfaced because we have lots and lots of jobs being run for every repository and sometimes our jobs fail due to lack of memory 15:24:23 lack of memory which causes rabbit and mysql to fail as side effect 15:24:56 so the whole point is to try to reduce the amount of jobs being run so everyone can get clean runs and CI won't have that many jobs running at the same time 15:25:29 you may have seen an email from the openstack-discuss mailing list earlier today 15:25:33 the stats are interesting 15:25:34 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-June/029342.html 15:25:41 they shared some stats with us :) 15:25:53 apparently we had 160 rechecks in the last 30 days 15:27:12 and 108 of them we didn't provide a reason.. 15:27:13 yep - that leaves us with a 67.5 rate of what they call "bare rechecks" 15:28:01 i doubt this number a bit, but a bunch of this is probably our current issues with the stable branches 15:29:27 but, point taken - we should triage the failure and recheck with reason 15:29:48 I have never added the reason, btw :/ 15:30:01 fire this guy ^ 15:30:11 lol 15:30:25 sorry 15:30:31 hahaha 15:31:32 no problem, felipe_rodrigues - I have to confess that I used to do not add messages to the rechecks 15:31:37 I've been doing it lately 15:32:04 the only type of rechecks with messages that won't work are the experimental ones (I hit that issue some times) 15:33:01 but yeah, only wanted to bring that up today to talk a bit again about those stats and the reasons why people are caring about those rechecks 15:33:51 on to the next topic... 15:33:57 #topic Review Focus 15:34:02 #link https://etherpad.opendev.org/p/manila-zorilla-review-focus (Review Focus Etherpad) 15:34:19 one of the changes of the review focus we have already talked about (the new driver) 15:34:45 we have recently merged some code for OSC functional tests as well, so other changes may need a rebase 15:36:01 we also have ashrodri's metadata api changes 15:36:22 #link https://review.opendev.org/c/openstack/manila/+/825008 (Metadata for Share Snapshots Resource) 15:36:35 thank you for the reviews felipe_rodrigues 15:36:46 felipe_rodrigues++ thanks; /me will review this one today 15:36:50 I will get back to that change, but as far as I've seen, it was looking good on the last time 15:37:02 hey! yeah the snapshots metadata changes are still up for review. I recently added some share access rules ones im working though test failures on 15:37:21 I promise review until Friday 15:37:42 felipe_rodrigues: https://review.opendev.org/c/openstack/manila-tempest-plugin/+/827925 -- you asked about the tests on your review; they're here 15:37:56 all.. that's too long away 15:38:18 I thought is another patch 15:39:09 I already gave my +1.. I just asked to know 15:39:22 it's fine to me! 15:39:28 cool :) 15:39:37 thanks 15:39:47 is there any other change you would like to highlight? 15:39:55 yes 15:40:09 i wanted to see if we could review-jam some of the OSC changes 15:40:28 #link https://review.opendev.org/c/openstack/python-manilaclient/+/836239 15:40:28 #link https://review.opendev.org/c/openstack/python-manilaclient/+/838233 15:40:28 #link https://review.opendev.org/c/openstack/python-manilaclient/+/802791 15:40:28 #link https://review.opendev.org/c/openstack/python-manilaclient/+/816401 15:40:28 #link https://review.opendev.org/c/openstack/python-manilaclient/+/805107 15:41:23 and ashrodri carloss maaritamm ecsantos[m] felipe_rodrigues, fix the merge conflicts here: https://review.opendev.org/q/topic:osc-functional-tests+status:open 15:42:25 ack 15:42:40 sure gouthamr 15:42:56 will do :) 15:44:05 awesome 15:44:29 ++ thank you 15:44:39 thanks for sharing these, the OSC parity is quite close, let's make this final push to get the remaining commands 15:44:46 i guess we spoke about co-authors and reviewers for the code patches above 15:44:59 ++ - we have that on the PTG notes 15:46:01 ah true 15:46:10 thanks for the pointer, i'd forgotten where we'd noted these 15:46:12 #link https://etherpad.opendev.org/p/zorilla-ptg-manila-osc 15:46:33 yep, this one 15:46:34 thanks 15:46:39 so its mostly myself, carloss vkmc and maaritamm 15:47:00 guess we certainly could use some help! 15:47:33 so if you've some bandwidth this week, please help.. 15:49:08 ++ 15:50:06 that's all i wanted to highlight 15:50:10 thanks gouthamr :D 15:50:16 nope, thanks for the reviews! 15:50:57 #topic Bug Triage 15:51:05 I think we still have some minutes for some bug triage 15:51:20 #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) 15:51:37 vhari couldn't be here with us today, but kindly gathered the list for us to talk 15:51:44 we have two stale bugs to talk about today 15:51:46 #1 15:52:06 #link https://bugs.launchpad.net/manila/+bug/1585241 (Share Replication: File-based locks don't provide concurrency control in multi-node/multi-AZ deployments Edit) 15:52:28 * carloss : please ignore the edit at the end of the title 15:53:07 this has been up for a while - is this in your future plans gouthamr? 15:53:38 ah, this one is still an issue … we could bump down the importance; the fix is relatively simple but hasn’t been a priority 15:54:19 We need to switch out the Oslo concurrency locks in the share manager with tooz locks (which we have the code for) 15:54:37 hasn’t been a user concern though - just tech debt 15:55:10 let’s bump this down to low and set a target - perhaps z3 15:55:20 sure gouthamr - thanks 15:55:34 done 15:55:41 agree with you on that 15:56:06 cool, bug #2 15:56:26 #link https://bugs.launchpad.net/manila/+bug/1866951 ([db] default value for project_only allows non-secure access ) 15:57:51 haha - both that im procrastinating on 15:58:40 So this is a wishlist bug … we had a CVE that allowed cross project resource access; and someone suggested this as an alternative 15:59:24 we could change the default and see if any existing regression tests catch anything 16:00:09 anyone interested in picking this up as a low-hanging-fruit? 16:00:32 cool one to work on :) 16:01:15 * carloss checks time 16:01:45 thanks for mentioning the context on the issue gouthamr 16:01:51 we can link the minutes of this call to the bug too 16:02:01 and if there is someone willing to pick it up, pleas let us know 16:02:07 ++ 16:02:10 or just update the assignee on launchpad :p 16:02:15 alright, we are 2 minutes over 16:02:21 thank you all for joining this meeting today 16:02:33 let's continue on #openstack-manila 16:02:35 o/ 16:02:39 thanks carloss 16:02:41 #endmeeting