15:00:53 <gouthamr> #startmeeting manila
15:00:53 <opendevmeet> Meeting started Thu Jan 27 15:00:53 2022 UTC and is due to finish in 60 minutes.  The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:53 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:53 <opendevmeet> The meeting name has been set to 'manila'
15:00:58 <felipe_rodrigues> o/
15:01:02 <fabiooliveira> o/
15:01:02 <vhari> o/
15:01:08 <andrebeltrami[m]> hello!
15:01:12 <haixin> o/
15:01:20 <caiquemello[m]> o/
15:01:55 <carloss> o/
15:01:59 <gouthamr> courtesy ping: ganso vkmc dviroel carloss tbarron ecsantos
15:01:59 <gouthamr> small crowd today :)
15:02:00 <archanaserver> o/
15:02:06 <vkmc> o/
15:02:10 <nahimsouza[m]> o/
15:02:12 <LeoCampelo> o/
15:02:39 <gouthamr> or not; hello all o/
15:02:39 <ecsantos[m]> o/
15:02:42 <gouthamr> lets get started
15:02:50 <gouthamr> #topic Announcements
15:03:07 <gouthamr> lets start with the deadlines
15:03:19 <gouthamr> Feature Proposal Freeze deadline is this week
15:03:41 <gouthamr> and Yoga-3 milestone and Client Library Freeze
15:03:46 <gouthamr> is on Feb 25
15:04:17 <gouthamr> unlike FPF, the client release is expected to occur on or before thursday/Feb 25th
15:04:51 <gouthamr> FPF - please use the weekend as the deadline, since we're not shipping anything
15:05:35 * gouthamr isn't suggesting making zuul work on weekends - you don't want to anger him
15:05:40 <gouthamr> #link https://releases.openstack.org/yoga/schedule.html
15:06:13 <gouthamr> per that ^
15:06:20 <gouthamr> FPF = All new Manila features must be proposed and substantially completed, with unit, functional and integration tests by the end of the week.
15:07:01 <sfernand> about that folks
15:07:01 * gouthamr checks calendar for real, Feb 25th is a Friday
15:07:25 <gouthamr> sfernand: lets dig in about that in a few
15:07:33 <sfernand> ok
15:08:44 <gouthamr> just a call out that release deadlines are usually the Thursday of the week, so the M3 deadline is really Feb 24th
15:09:31 <gouthamr> at the M3 deadline, we'll be shipping the final python-manilaclient for the yoga cycle
15:09:52 <gouthamr> and placing a feature freeze on manila and manila-ui (alongside a soft string freeze for this repo)
15:10:49 <gouthamr> between M3 and the RC1 target week (Mar 07-Mar 11), we will only be making bugfixes in manila and manila-ui
15:11:36 <gouthamr> at RC1, per usual, we'll transition the main branch to the zorilla cycle
15:11:40 <gouthamr> and features can merge
15:12:19 <gouthamr> however, we'd be conservative until March 30th when the final yoga release is expected to be; only in case we'd have to release a further release candidate
15:13:30 <gouthamr> that's all the release announcements
15:13:50 <gouthamr> #link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026916.html (help jungleboyj decide to vote for Zorilla)
15:14:09 <gouthamr> ^ :) just lobbying for our favorite name
15:14:42 <gouthamr> in other news
15:14:52 <gouthamr> #link http://lists.openstack.org/pipermail/openstack-discuss/2022-January/026922.html (2021 OpenInfra Foundation Annual Report Now Available)
15:15:06 <gouthamr> many a mention to the manila team in this report
15:15:48 <gouthamr> kudos archanaserver kafilat and ashrodri for being featured (alongside our other interns)
15:16:31 <gouthamr> 't was a great year as any to be a zorilla
15:17:10 <jungleboyj> He he he.
15:17:37 <gouthamr> o/ jungleboyj
15:17:41 <jungleboyj> o/
15:17:54 <dviroel> o/
15:18:04 <gouthamr> that's all the announcments i had today, any other announcements, folks?
15:18:28 <gouthamr> ooh yes, congratulations on becoming tripleo-ci core dviroel!
15:18:47 <dviroel> gouthamr: yey thanks o/
15:19:06 <andrebeltrami[m]> dviroel++
15:19:18 <ashrodri> dviroel++ congrats!
15:19:36 <sfernand> congrats :D
15:19:40 <vhari> dviroel++
15:19:51 <fabiooliveira> congrats o/
15:19:58 <vkmc> congrats dviroel o/
15:20:26 <felipe_rodrigues> dviroel++
15:20:44 <gouthamr> awesome, lets move on :D
15:20:47 <carloss> dviroel++ :D
15:20:50 <gouthamr> #topic FFE requests for drivers and FPF
15:21:08 <dviroel> ty all o/
15:21:36 <gouthamr> let me pause here, and ask you folks if there are any questions regarding the release timeline
15:23:18 <gouthamr> alright, time to discuss the feature proposal freeze
15:24:05 <gouthamr> i think we have a bunch of patches being worked on at the moment, lets cycle through them and understand what stage they're at
15:24:38 <gouthamr> 1) Scheduler stats changes
15:24:47 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/817379 (Add support of scheduler_hints in share replica create)
15:25:11 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/824726 (onlyHostFilter: Fix follow-up suggestions)
15:25:29 <gouthamr> #link https://review.opendev.org/c/openstack/manila-ui/+/814694 (Api 2.65, Add Share Affinity/Anti-Affinity Scheduler hints when create share)
15:25:54 <gouthamr> #link https://review.opendev.org/c/openstack/manila-tempest-plugin/+/816168 (Add tests for only_host scheduler hint(
15:26:11 <gouthamr> #link https://review.opendev.org/c/openstack/python-manilaclient/+/817739 (Add --scheduler_hints to share replica create command)
15:26:54 <gouthamr> ^ and some prior patches have merged
15:27:07 <gouthamr> s/stats/hints
15:27:21 <gouthamr> any concerns with this turning out to be a risk?
15:27:27 <gouthamr> grr
15:27:34 * gouthamr frames a leading question
15:27:52 <gouthamr> does anyone think this is risky to get done for this cycle?
15:29:23 <sfernand> should I include netapp patches to the list now, maybe? :P
15:29:51 <gouthamr> oh, i was going to pick on those next sfernand
15:30:08 <gouthamr> unless there's a related scheduler stats/replication patch?
15:30:09 <sfernand> ok great
15:30:20 * gouthamr s/stats/hints :|
15:30:47 <sfernand> we don't have any
15:30:48 <gouthamr> we'll keep this on the review focus etherpad
15:30:55 <gouthamr> next up
15:31:10 <gouthamr> 2) Multiple Subnets per AZ
15:31:19 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/825110 ([WIP]: add multiple subnets per AZ support)
15:31:41 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/826462 (Container: Multiple subnets per AZ)
15:32:00 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/825155 (NetApp ONTAP: Add support to multiple subnets per AZ)
15:32:32 <gouthamr> ^ am i missing any patches here?
15:32:51 <sfernand> no
15:33:08 <andrebeltrami[m]> we will include the manila-tempest soon
15:33:08 <felipe_rodrigues> btw, we need to set a topic
15:33:10 <carloss> any tempest change planned?
15:33:14 <carloss> oh, thanks andrebeltrami[m]
15:33:15 <carloss> :)
15:33:28 <gouthamr> felipe_rodrigues: yes, please do
15:33:34 <gouthamr> andrebeltrami[m]: ack
15:33:46 <gouthamr> will this require any client changes?
15:33:51 <sfernand> yep I didn't submmited any patch but this shall be done soon
15:34:23 <felipe_rodrigues> small.. just bump API version.. the REST calls are the same
15:34:31 <gouthamr> i see
15:34:32 <felipe_rodrigues> I'll submit the client changes soon
15:34:38 <sfernand> yep also we should submit a patch to the cli by tomorrow
15:35:24 <gouthamr> ack; would be you dropping the WIP by tomorrow as well?
15:36:10 <sfernand> yes we will, our only concern is that may be we wont have enough time to fix all tempest tests by the end of the week
15:36:13 <felipe_rodrigues> I think so..
15:36:39 <felipe_rodrigues> sfernand +1
15:36:52 <sfernand> so we would like to ask for a few days to have all patches passing in tempest and with the proper unit test coverage
15:37:10 <gouthamr> okay; if that's just it, i don't think it'll hurt to push this out till next thursday, would that be okay?
15:37:24 <sfernand> that would be ok
15:37:41 <felipe_rodrigues> +1
15:38:16 <andrebeltrami[m]> +1
15:38:52 <ecsantos[m]> +1
15:38:58 <sfernand> we will be dropping WIP for our patches by the end of the week so if someone have time to take a look at the core patch and give first impressions that would be nice
15:39:50 <gouthamr> ack
15:39:57 <gouthamr> thanks for the updates
15:40:08 <sfernand> and we should also be able to work on reviews starting next week
15:40:12 <sfernand> :)
15:40:32 <gouthamr> yes please; feel free to put all of these onto the review focus etherpad
15:40:39 <gouthamr> and sign up for reviews there
15:40:46 <sfernand> maybe helping reviewing the scheduler stats of something you guys thinks that require attention
15:40:58 <gouthamr> 3) Share Transfer between projects
15:41:07 <gouthamr> #link https://review.opendev.org/c/openstack/manila-specs/+/818854 (share transfer between project)
15:41:25 <haixin> The company has been a little busy recently, so it will take some time to develop this
15:41:33 <gouthamr> ah thanks haixin
15:41:42 <gouthamr> so we can push this one out to zorilla?
15:42:23 <gouthamr> the next one is yours as well
15:42:25 <gouthamr> 4) Manila share support recycle bin
15:42:33 <gouthamr> #link https://review.opendev.org/q/topic:bp%252Fmanila-share-support-recycle-bin
15:42:44 <gouthamr> this one's been ready for a while
15:42:44 <haixin> this need review
15:43:13 <haixin> it's micversion 2.66 has change to 2.68 :|
15:43:20 <gouthamr> yes, sfernand and team, this could use help :)
15:43:36 <sfernand> ack
15:43:38 <felipe_rodrigues> I'm having a look
15:44:29 <gouthamr> okay, with the review attention, i feel this isn't risky - as long as you can keep the review comments addressed haixin
15:45:06 <haixin> :) ok
15:45:35 <gouthamr> thanks!
15:45:46 <gouthamr> 5) Metadata APIs
15:45:58 <gouthamr> #link https://review.opendev.org/q/topic:bp%252Fmetadata-for-share-resources (Metadata for share resources)
15:46:35 <ashrodri> thats me!
15:46:41 <gouthamr> ashley is meta
15:47:06 * gouthamr doesn't know what that means, but says it to sound cool
15:47:16 <ashrodri> haha
15:47:20 <ashrodri> I've got some good progress this cycle. The metadata api ive been implementing has been whittled down to just two resources, it proved too big a beast to get all the resources in now.
15:47:30 <ashrodri> Was looking at tempest tests and found this one that tests a weird behavior regarding key values with ‘.json’ or ‘.xml’ in it:
15:47:38 <ashrodri> #link https://opendev.org/openstack/manila-tempest-plugin/src/branch/master/manila_tempest_tests/tests/api/test_metadata_negative.py#L117
15:47:49 <ashrodri> Basically such keys are allowed to be set, but not deleted. i was hoping to strike a quick discussion about this behavior and how to move forward with it.
15:48:26 <ashrodri> though that can wait til Open Discussion if needed. Besides that, i do have some changes gearing up for the CLI ill need review before the M3 deadline to make sure that ships out, does anyone want to be pinged for that?
15:49:13 <gouthamr> from the code, you're looking to modify the share metadata -- but there're no behavior changes really
15:49:32 <gouthamr> (except the tempest test failure you're citing)
15:49:37 <ashrodri> yep
15:49:43 <gouthamr> and you're adding metadata apis for snapshots
15:50:06 <gouthamr> so the real change here is the latter, and the former is mostly a code refactor
15:50:10 <gouthamr> ?
15:50:52 <ashrodri> sounds about right, though regarding shares theres also the admin-only metadata changes in a separate patch
15:51:01 <gouthamr> ah
15:51:27 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/806647 (Add admin only keys to share metadata(
15:51:36 <gouthamr> ^ this one's ready for review
15:52:12 <gouthamr> ashrodri: when do you think you can drop the WIP on the other patches?
15:52:47 <ashrodri> on the api changes probably by tomorrow, pending the tempest test failures and how to address it
15:52:57 <gouthamr> yes, lets talk about those
15:53:14 <gouthamr> we're short of time today
15:53:55 <gouthamr> can you bring it up on #openstack-manila, or here during the next meeting?
15:54:10 <ashrodri> lets talk on #openstack-manila
15:54:19 <ashrodri> id rather address it sonner than later
15:54:23 <gouthamr> it = the tempest test, if you need folks' take on what to do here
15:54:34 <ashrodri> yeah
15:55:30 <gouthamr> thanks, alright... this will require some review attention, do we consider this a risk if we provide time to wrap stuff up?
15:56:57 <gouthamr> okay...
15:57:12 <gouthamr> same thing as to sfernand and party, ashrodri -- don't work over the weekend or something.. but, if things have to slip - its not a problem, let us know
15:57:22 <ashrodri> +1
15:57:36 <gouthamr> we'll hope to see this complete by next week's meeting though, and discuss any fall out
15:57:48 <ashrodri> i think i can manage that
15:58:03 <gouthamr> alright
15:58:19 <gouthamr> am i missing any other feature change?
15:59:54 <gouthamr> sounds like none
16:00:03 <gouthamr> we're short of time to discuss reviews and bugs today
16:00:11 <gouthamr> so lets wrap up here
16:00:39 <gouthamr> in the next meeting, we'll discuss any critical client changes and follow up on these items
16:01:02 <gouthamr> if you have anything to bring up, please feel free to add it to the agenda: https://wiki.openstack.org/wiki/Manila/Meetings
16:01:15 <gouthamr> thank you all for attending, and for pushing patches, and reviewing :)
16:01:31 <gouthamr> see you on #openstack-manila now, and here next week
16:01:37 <gouthamr> #endmeeting