15:00:28 <gouthamr> #startmeeting manila
15:00:30 <openstack> Meeting started Thu Feb 18 15:00:28 2021 UTC and is due to finish in 60 minutes.  The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:31 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:33 <openstack> The meeting name has been set to 'manila'
15:00:38 <carloss> o/
15:00:44 <ecsantos> o/
15:00:45 <almir-okato> hi
15:00:53 <disap> o/
15:01:00 <vhari> hi
15:01:09 <dviroel> o/
15:01:10 <gouthamr> courtesy ping: ganso vkmc dviroel lseki andrebeltrami felipe_rodrigues
15:01:23 <gouthamr> heh, beat you by a few microseconds
15:01:32 <dviroel> =)
15:01:46 <vkmc> o/
15:01:48 <gouthamr> hello everyone o/ thank you for joining
15:02:41 <kiwi_36> o/
15:02:54 <jinyuanliu> o
15:02:58 <gouthamr> lets get started
15:03:03 <gouthamr> #topic Announcements
15:03:34 <carthaca> Hi
15:03:39 <gouthamr> a lot's going on currently, as we approach m-3 and the final leg of this release cycle
15:03:53 <gouthamr> #link: https://releases.openstack.org/wallaby/schedule.html
15:04:02 <gouthamr> we have 3 weeks to feature freeze
15:04:34 <gouthamr> so thanks everyone that's getting their code changes in shape and for doing code reviews!
15:04:52 <gouthamr> i don't have any other announcements for today
15:04:55 <gouthamr> anyone else got any?
15:05:47 <gouthamr> alright lets dive right in
15:05:51 <gouthamr> #topic Zadara Manila driver(rratnaka)
15:06:01 <gouthamr> hey there rratnaka!
15:06:08 <rratnaka> Hi gouthamr..
15:06:19 <rratnaka> Hope everyone is doing good!
15:07:11 <rratnaka> I am here to check with the reviewers about mine: https://review.opendev.org/c/openstack/manila/+/768590
15:07:41 <rratnaka> I resolved all the comments and currently my Zadara CI has got a failure and we are resolving that
15:08:12 <rratnaka> Just wanted to close in with review folks, if all comments are done? Except for my CI failure job
15:08:37 <rratnaka> If not, I thought I would like to bring their attention as part of todayś meeting
15:09:04 <gouthamr> thanks, i haven't had a chance to review your latest change, but dviroel has
15:09:25 <rratnaka> yes gouthamr.
15:09:39 <dviroel> yep, my last comment was about the CI only
15:09:51 <dviroel> didn't took a deep look in units yet
15:10:00 <dviroel> which shouldn't be a problem too
15:10:15 <carloss> same as gouthamr... I haven't looked at the current PS but intend to do that soon :)
15:10:40 <rratnaka> Thanks dviroel, carloss, gouthamr
15:11:28 <rratnaka> Please take a look to provide comments
15:11:38 <dviroel> gouthamr: is expected to add documentation update in the same change?
15:11:43 <gouthamr> rratnaka: will do, def get the CI working soon, and let us know if you hit any roadblocks
15:12:16 <gouthamr> dviroel: not expected, preferred perhaps
15:12:29 <gouthamr> rratnaka: do you intend to add documentation ^
15:12:34 <gouthamr> with the same patch?
15:13:29 <rratnaka> Current priority is getting the CI get ready
15:14:03 <rratnaka> Will add doc. on the best case and if timelines are feasible
15:14:22 <dviroel> rratnaka: make sense, if you get some time after, include documentation too
15:14:53 <rratnaka> Could you please help me with deadline for my driver changes to get in before?
15:14:59 <gouthamr> rratnaka: two places where your driver needs docs: https://docs.openstack.org/manila/latest/admin/index.html#supported-share-back-ends and https://docs.openstack.org/manila/latest/configuration/shared-file-systems/drivers.html
15:15:16 <gouthamr> rratnaka: we'll have to get it merged by feature freeze, that's in 3 weeks
15:15:28 <gouthamr> the sooner the better ofcourse
15:16:09 <rratnaka> definitely gouthamr.
15:16:32 <rratnaka> I see that falls between Mar 08 - Mar 12
15:16:55 <rratnaka> I am hopeful that our CI jobs will be done in a few days time
15:17:32 <gouthamr> good stuff.. anything else regarding $topic?
15:17:38 <rratnaka> I am sure you guys might caught up with many stuff. Will be really helpful if you guys take a look for review before that
15:17:48 <dviroel> +1
15:17:52 <rratnaka> Thats ir from my end gouthamr
15:17:59 <gouthamr> thanks, rratnaka
15:18:00 <rratnaka> Thanks again guys!!
15:18:13 <vkmc> +1
15:18:17 <gouthamr> #topic Share resize in Manila UI (disap/vkmc)
15:18:32 <gouthamr> disap/vkmc: o/
15:18:40 <vkmc> disap, wanna share your findings?
15:18:51 <disap> yes
15:19:34 <vkmc> #link https://review.opendev.org/c/openstack/manila-ui/+/767017
15:19:35 <disap> When share with files in it shrinked to a samller size then volume of files
15:19:46 <disap> It doesn't shrinked
15:19:56 <disap> But doesn throe any Exception
15:20:02 <disap> *throw
15:20:42 <gouthamr> disap: yes, that was a recent change - you must see a user message indicating what happened
15:20:53 <disap> Response is "Accepted" 202
15:21:04 <disap> Yes user message is there
15:21:31 <disap> But share_shrink function is goes through as successful
15:22:06 <gouthamr> disap: yeah, this is an asynchrous failure - and in the past, we'd set the share state to "share_shrinking_possible_data_loss"
15:22:25 <disap> Status first is "shrinking"
15:22:31 <disap> then becomes available
15:22:48 <disap> but size is not changed
15:23:18 <gouthamr> disap: yes - perhaps you should detect that scenario and show a helpful message in the UI?
15:23:29 <vkmc> we were wondering, is the behavior the same for most drivers? the shrink operation is not fulfilled and the response is not different from a successful shrink
15:23:48 <vkmc> or is there a driver in which the shrinking process will be done even though there is data loss?
15:24:20 <gouthamr> vkmc: yes, we modified this across drivers
15:24:31 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/724128 (Update share-manager behavior for shrink share operation)
15:24:58 <vkmc> gouthamr, so for all drivers, when you cannot shrink the share because there is a possibility of loosing data, then a 202 is returned and no shrinking is done
15:25:32 <gouthamr> vkmc: the shrink API returns with 202 if the request is valid
15:25:32 <vkmc> (ok, we need to update the api ref to remove the share_shrinking_possible_data_loss status)
15:25:39 <gouthamr> ^ +1
15:26:03 <vkmc> gouthamr, yeah, the request is valid but the operation doesn't succeed
15:26:46 <vkmc> the concern here is that it's a silent failure
15:27:03 <gouthamr> vkmc: yes, so i'm hoping you could check the share size, and indicate in the UI that the share wasn't shrunk
15:27:10 <dviroel> ^
15:27:19 <vkmc> yes, that's the solution that disap proposed
15:27:42 <vkmc> get share size, perform shrink operation, get share size again, compare sizes and then show result
15:27:56 <carloss> +1
15:28:05 <gouthamr> vkmc: yes
15:28:08 <vkmc> but... we do have the same issue with the python-manilaclient
15:28:43 <vkmc> (not the discussion topic for today, but maybe we want to do something alike)
15:29:26 <vkmc> ok, disap ^
15:29:27 <vkmc> :D
15:29:33 <gouthamr> vkmc: good point - if the user used a "--wait" option on shrink, we could react the same way as the UI
15:29:50 <vkmc> ++
15:30:13 <vkmc> ok, we will file a bug for the python-manilaclient
15:30:30 <vkmc> and... we can proceed with the ui change as disap suggested
15:30:44 <gouthamr> thanks, add "manila" as an affected project as well so we can make any necessary doc changes on manila
15:30:50 <gouthamr> s/on/in
15:30:55 <vkmc> sounds good
15:30:57 <vkmc> thanks
15:31:02 <vkmc> disap++ good job
15:31:07 <disap> thanks
15:31:42 <gouthamr> yeah, good find, and thanks for bringing that up here!
15:32:13 <gouthamr> anything else regarding this?
15:32:21 <vkmc> nothing else from me, disap?
15:32:31 <disap> nothing from my side
15:32:48 <gouthamr> #topic Reviews needing feedback
15:33:02 <gouthamr> just advertising the etherpad out here :)
15:33:03 <gouthamr> #link https://etherpad.opendev.org/p/manila-wallaby-review-focus (Wallaby cycle review focus etherpad)
15:33:27 <gouthamr> we're making slow but decent progress through the items on the etherpad
15:33:45 <gouthamr> but there's a lot
15:34:31 <gouthamr> if there's something missing on there, please do tack it on - if you intend to review something, add your nick
15:34:51 <gouthamr> if you've signed up to review, please add a status for the changes you've signed up
15:35:40 <gouthamr> we could use some collab reviews
15:36:36 <gouthamr> dviroel carloss andrebeltrami ecsantos: what about a session to go over the security services changes
15:36:57 <dviroel> yes, we could do a session for this one
15:36:58 <carloss> that'd be great!
15:37:00 <ecsantos> sounds good to me
15:37:23 <vkmc> sounds good!
15:37:55 <gouthamr> alright, we'll need to find a good time, and put it out on the ML
15:38:06 <dviroel> +1
15:38:40 <gouthamr> i'll like one for the secure-rbac changes - i'll run a poll for date/times and send out a note to the ML
15:38:56 <gouthamr> vkmc would like to have one for all the cephfs driver changes
15:39:48 <vkmc> yes please :)
15:40:13 <gouthamr> lets talk after this meeting and get these collab review meetings set up
15:41:25 <gouthamr> anything else about reviews/pending changes?
15:41:50 <carthaca> I created/copied a blueprint https://blueprints.launchpad.net/manila/+spec/affinity-antiaffinity-filter and proposed spec + code change.
15:41:50 <carthaca> Is it okay to put both up for review already?
15:43:10 <gouthamr> carthaca: we're past the deadline for the spec reviews for wallaby
15:44:05 <gouthamr> carthaca: can this wait until Xena? there's a lot of code to review, not enough bandwidth...
15:45:16 <carthaca> Sure
15:45:27 <carthaca> Deadlines are to be kept :)
15:46:00 <gouthamr> great thanks! we did miss a few things - but we always plan optimistically
15:46:19 <gouthamr> its always good to have code merge very early in a cycle too!
15:46:54 <carthaca> The good thing for the community then will be that we already tested in production
15:47:03 <gouthamr> haha :D
15:47:20 <gouthamr> i like how bleeding edge your cloud is
15:47:53 <gouthamr> alright, lets move on to our next section
15:48:04 <gouthamr> #topic Bugs (vhari)
15:48:12 <gouthamr> vhari: o/ floor's yours..
15:48:19 <vhari> gouthamr, \o
15:48:35 <vhari> no new bugs to discuss this week :)
15:48:44 <vhari> #link https://bugs.launchpad.net/manila/+bug/1904746
15:48:46 <openstack> Launchpad bug 1904746 in OpenStack Shared File Systems Service (Manila) "share server is failing to delete using kerberos with NetApp driver" [Medium,In progress] - Assigned to Felipe Rodrigues (felipefutty)
15:49:00 <vhari> fix merged .. need to update status
15:49:21 <vhari> if  all looks good ^^
15:49:39 <gouthamr> yes, i think it's good to tag as "Fix released"
15:49:51 <vhari> gouthamr, k moving on
15:49:54 <vhari> #link https://bugs.launchpad.net/manila/+bug/1893718
15:49:57 <openstack> Launchpad bug 1893718 in OpenStack Shared File Systems Service (Manila) "Fixed the logic that determines whether a share exists before manage a share" [Medium,In progress] - Assigned to haixin (haixin77)
15:50:15 <vhari> fix released in several manila releases
15:50:21 <gouthamr> this one too!
15:50:22 <gouthamr> yes
15:50:29 <vhari> cool :)
15:50:31 * gouthamr misses the bot
15:50:49 * vhari vhari too !
15:50:56 <vhari> #link https://bugs.launchpad.net/manila/+bug/1883506
15:50:57 <openstack> Launchpad bug 1883506 in OpenStack Shared File Systems Service (Manila) "delete manage_error share will lead to quota error" [Medium,In progress] - Assigned to haixin (haixin77)
15:51:08 <vhari> looking for some eyes on this one
15:51:43 <vhari> if anyone gets a chance to review would be great
15:52:11 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/741588/
15:53:17 <gouthamr> cool, i've added it to the review etherpad
15:53:40 <gouthamr> lets see if we can get some eyes here, the fix has been up for a while
15:53:51 <vhari> gouthamr, ty .. that's a wrap for today
15:54:09 <gouthamr> thank you vhari
15:54:14 <gouthamr> #topic Open Discussion
15:54:43 <vhari> gouthamr, yw
15:56:49 <gouthamr> great, lets wrap up - thank you all for attending!
15:56:58 <gouthamr> see you on #openstack-manila
15:57:06 <gouthamr> #endmeeting