15:01:09 <carloss> #startmeeting manila
15:01:09 <opendevmeet> Meeting started Thu Aug  1 15:01:09 2024 UTC and is due to finish in 60 minutes.  The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:09 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:09 <opendevmeet> The meeting name has been set to 'manila'
15:01:21 <carthaca> hi
15:01:21 <vhari> o/
15:01:55 <haixin> o/
15:01:57 <carloss> courtesy ping: dviroel gouthamr  msaravan pulluri ashrodri
15:02:09 <gouthamr> o/
15:02:11 <ccokeke[m]> hello
15:02:32 <gireesh> hi
15:03:36 <msaravan> Hi
15:04:06 <carloss> o/ hello everyone
15:04:23 <carloss> let's get started with our meeting agenda for today
15:04:32 <carloss> #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting (Meeting agenda)
15:04:42 <carloss> #topic Announcements
15:04:49 <carloss> Schedule and Deadlines
15:05:03 <carloss> #link https://releases.openstack.org/dalmatian/schedule.html (Dalmatian release schedule)
15:05:19 <carloss> so this week is our feature proposal freeze
15:05:57 <carloss> and it means: all new Manila features must be proposed and substantially completed, with unit, functional and integration tests by the end of the week. Collaborative review sessions must be proposed at this timeline, in order to speed up the review process
15:06:56 <carloss> on the collaborative review sessions: as we discussed in the last week, we will be covering them during the mid cycle
15:08:49 <carloss> for feature proposal freeze, I see a couple of features submitted already:
15:10:03 <carloss> - Share encryption
15:10:03 <carloss> - Pass metadata updates to the share drivers
15:10:03 <carloss> - Export location metadata
15:10:03 <carloss> - Ensure shares APIs
15:10:03 <carloss> - Manage/unmanage for cephfs drivers
15:10:04 <carloss> - [NetApp] Custom storage efficiency policy support for Manila share
15:10:12 <carloss> am I missing a feature in this list?
15:10:26 <carloss> and is there a feature you are still willing to propose that would qualify for feature proposal freeze?
15:10:45 <carloss> I'd recommend pushing the code to gerrit by tomorrow, but if you'd like some time, please let me know and we can talk exceptions
15:11:37 <msaravan> Yes, support for backup_types via API
15:12:02 <carloss> I think most of the features on this list (except for APIs ensure shares) already have some unit tests. I am willing to update unit tests for that change by tomorrow
15:12:12 <msaravan> carloss : We need some time for this, and I'll ping you and provide updates
15:13:13 <gireesh> Snaplock support for Manila, I am working on that and will raise the patch by next week
15:13:37 <carloss> msaravan, gireesh: thank you
15:14:47 <gouthamr> gireesh msaravan: we have a feature proposal freeze to estimate review bandwidth that's necessary during these last few weeks
15:15:17 <gouthamr> are these two features you mention small/well-tested?
15:15:50 <gouthamr> the list carloss shared is pretty large
15:16:03 <gireesh> Snaplock support is small and will be well tested
15:16:15 <gouthamr> if we can defer anything meaningfully to Epoxy, i'd encourage it
15:16:21 <gouthamr> Epoxy is a SLURP release
15:16:41 <msaravan> Ack, @gouthamr : we understand that. Yes, it would be well tested. We all are working closely on the design part and testing part.. to make sure we are not missing anything.
15:17:18 <msaravan> @gouthamr : We understand your point.. if it takes more time, and if we find it complex, we'll update you and we can take a call as you suggested.
15:18:17 <gouthamr> sure, I don't mean to sound like a stuck tape - these deadlines have existed for a while :) am not in favor of a feature freeze exception..
15:18:38 <gouthamr> (feature freeze is Milestone-3)
15:19:11 <ashrodri> for export location metadata, will push up tempest patch soon for functional testing.
15:19:20 <msaravan> Ack..
15:22:13 <carloss> ++ on the measuring the review bandwidth and the importance to have the features on gerrit
15:23:05 <carloss> thanks for sharing your thoughts
15:25:40 <carloss> agree with deferring something to Epoxy in case we need, as it is a SLURP release
15:26:18 <carloss> and for the amount of features we already have, we'll need as many reviewers as possible
15:28:52 <carloss> so please submit the code to gerrit as soon as you can
15:30:08 <carloss> and ++ on trying to avoid feature freeze exceptions on this cycle
15:31:56 <carloss> still on announcements, and something similar
15:32:05 <carloss> our mid-cycle
15:32:12 <carloss> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/5UMH5BI55STHTMEV4W7JHWAOTURFMX3U/ (Mid-cycle announcement)
15:32:19 <carloss> I sent the email announcing it to the mailing list
15:32:45 <carloss> and it will be as we spoke in the last week: two days, two hours each day
15:32:52 <carloss> Aug 12 and 13
15:33:07 <carloss> from 14 to 16 UTC
15:33:36 <carloss> on the first day we will focus on updates from what we discussed on the PTG
15:33:45 <carloss> and the second one we will use for collab review sessions
15:34:20 <carloss> I believe that due to the amount of features we currently have, we will need more time to collab reviews, so maybe we can get started with them on the first day, in case we have some time
15:34:36 <carloss> #link https://etherpad.opendev.org/p/manila-dalmatian-mid-cycle-notes (Mid cycle etherpad)
15:34:56 <carloss> please add a topic for the feature you are proposing under the collaborative reviews topic
15:35:40 <carloss> is there something else you'd like to add?
15:35:48 <carloss> or an announcement to share with us today?
15:37:29 <carloss> taking silence as no
15:38:34 <carloss> #topic Review focus
15:38:55 <carloss> #link https://etherpad.opendev.org/p/manila-dalmatian-review-focus (Review focus etherpad)
15:39:06 <carloss> Please add all the features and patches you are proposing to the review focus etherpad
15:39:29 <carloss> and let's try to get back using it again. It can be a great source of identifying changes that can use your eyes
15:40:37 <carloss> so I'll get back to updating it daily, and would be nice if all reviewers could look at it a couple of times every week
15:40:46 <carloss> and check if there's a change you can help with reviews
15:41:06 <carloss> for now, the review focus will naturally be shifting to features, because we are getting close to the feature freeze :)
15:41:29 <carloss> that's all I had for $topic ... Is there a change you'd like to ask for our attention today?
15:43:10 <kpdev> for feature freeze I would like to review and merge two things ;; deferred deletion and passing metadata to backend
15:45:31 <carloss> ack, thanks kpdev - I think we got a couple of reviews on deferred deletion already, so seems closer
15:45:55 <carloss> the metadata one seems close too. can you do the collab review session for it?
15:46:50 <kpdev> ok, will add for metadata
15:47:37 <carloss> thank you!
15:47:52 <carloss> #topic Bug Triage (vhari)
15:48:08 <vhari> o/ all
15:48:17 <vhari> let's dive in
15:48:18 <vhari> #link https://bugs.launchpad.net/manila/+bug/2073883
15:49:39 <carloss> we discussed something similar lately
15:49:45 <carloss> let me refresh my memory :)
15:50:14 <carloss> that's a different thing: allow scheduling to disabled manila-share host Edit
15:50:17 <vhari> ack, and force delete option
15:50:48 <carloss> tricky one because host down is different from disabled, and we might not be able to reach it
15:51:00 <carloss> not sure if we had someone looking into it in the past though
15:52:06 <gouthamr> we did i think
15:53:23 <gouthamr> sorry; my search-fu isn't working
15:56:32 <gouthamr> https://bugs.launchpad.net/bugs/1867030
15:57:06 <gouthamr> so we created this fix:
15:57:16 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/911694
15:57:27 <gouthamr> ccokeke[m] worked on this during his internship application
15:57:52 <carloss> ah, nice
15:57:56 <carloss> so it's a duplicated bug
15:58:02 <gouthamr> this was reported against yoga
15:58:21 <carloss> yep... we would need to start backporting it
15:58:30 <carloss> this feels a lot like an RFE
15:58:33 <gouthamr> it is
15:58:53 <ccokeke[m]> gouthamr: yes i did
15:59:29 <ccokeke[m]> during my contribution stage
16:00:17 <vhari> ccokeke[m]++
16:00:21 <carloss> the fix apparently doesn't show any risks of regression, so I believe we should be safe to backport
16:00:22 <vhari> gouthamr, good find
16:00:51 <carloss> nothing related to API versions or changing returns
16:01:08 <carloss> so I'd say: let's close this bug and say the fix is already in and add some links
16:01:25 <carloss> and we can start with the backports
16:01:39 * carloss time check
16:02:24 <carloss> let's wrap up
16:02:30 <carloss> thank you for participating
16:02:38 <carloss> let's get back to #openstack-manila
16:02:40 <carloss> #endmeeting