15:00:29 #startmeeting manila 15:00:29 Meeting started Thu Mar 26 15:00:29 2020 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:33 The meeting name has been set to 'manila' 15:00:37 o/ 15:00:58 hey 15:01:02 o/ 15:01:17 courtesy ping: xyang toabctl ganso vkmc amito lseki carloss 15:01:29 o/ 15:01:30 hi :) 15:01:38 we'll be missing vhari likely today, i'll drive the bug triage 15:01:39 o/ 15:01:44 hi 15:02:05 hello 15:02:15 gouthamr, ack may need to step out for a bit, ty for driving the bugs on the list today 15:02:24 o/ 15:02:28 vhari: sure thing 15:02:39 agenda for this meeting: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:02:50 Thank you all for joining 15:03:40 Hope you're all doing well in these virulent times 15:03:49 #topic Announcements 15:04:03 First up, a release time line check 15:04:13 Ussuri-3/Feature Freeze is in 2 weeks 15:04:32 that deadline also includes Client Library Releases for Ussuri - python-manilaclient and manila-ui 15:04:36 #link: https://releases.openstack.org/ussuri/schedule.html#u-ff 15:05:25 So, please give features that touch CLI review preference and we'll discuss them in a bit 15:05:55 Does anyone anticipate anything to slip at this stage? Or any gotchas that we must be aware of? 15:06:20 hoping not :) 15:06:35 Please note two new stable branch updates for manila: 15:06:40 #link https://releases.openstack.org/train/index.html#train-manila (manila 9.1.1) 15:06:43 #link https://releases.openstack.org/stein/index.html#stein-manila (manila 8.1.1) 15:07:17 These were released this morning and include important bug fixes, so users are recommended to update to these versions at the earliest 15:08:02 continuing with release themes, i added manila project deadlines to the Victoria Release schedule 15:08:06 #link https://releases.openstack.org/victoria/schedule.html (Victoria cycle schedule + manila deadlines) 15:08:14 o/ 15:08:18 * vkmc sneaks in late 15:08:38 just as i said her name 15:08:50 haha 15:08:51 hehe 15:09:00 lol 15:09:16 please take a look at the deadlines added, and lets discuss them here - these are not set in stone 15:09:43 although i allowed the patch to merge before bringing your attention to it, my bad 15:10:05 so, before we move on to our next topic, i'd like to note some peculiarities with the upcoming release 15:10:31 If you missed this email on the ML: 15:10:37 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012735.html ([all] Proposed release schedule for Victoria) 15:11:14 * gouthamr Victoria will be a slightly shorter release cycle 15:11:25 "Part of the reason for the slightly shorter schedule was to wrap up prior to the Summit" 15:12:11 It's still not as short a cycle as Ocata was 15:12:29 but, i needed to adjust some deadlines 15:13:02 i'm proposing that Manila's spec freeze be three weeks before M-2 15:13:22 the new driver deadline remains M-2 15:13:42 feature proposal freeze is two weeks prior to feature freeze 15:14:01 gah, three weeks* 15:14:19 and you've four weeks between PTG and spec freeze 15:14:37 does anyone disagree with this proposal? 15:15:39 you don't have to - right now, please let me know if you think this can't work for any reason and we'll bring it up in an upcoming meeting and adjust timelines 15:16:40 My last announcement today is for the upcoming TC/PTL elections: 15:16:46 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013597.html ([all][elections][ptl][tc] Combined PTL/TC Nominations Kickoff) 15:17:26 dunno if you're shy or respectful, but, no-one reached out to me to attempt to be PTL :P 15:18:07 so i've a plan brewing to groom folks to step up 15:18:53 if no-one self-nominates to lead us, i'll seek self-nominations for the Wallaby release, and i'll mentor you through the Victoria cycle 15:19:12 *crickets* 15:19:57 anywho, it gives me time to document all things that one does being a project team lead and discuss how we can make things better 15:20:05 we are not yet done with gouthamr's ptlness 15:20:10 seems so 15:20:12 xD 15:20:12 vkmc ++ 15:20:14 :D 15:20:20 :) 15:20:34 <3 15:20:44 Any other announcements for today? 15:20:50 yes 15:20:59 go for it, dviroel 15:21:04 we have new manila contributor from our side 15:21:13 felipe_rodrigues, welcome! 15:21:17 🎉 15:21:20 welcome, felipe_rodrigues :D 15:21:31 Thank you! :) 15:21:36 Welcome! :p 15:21:45 wee, welcome! 15:21:51 felipe_rodrigues: welcome, thank you for joining us! 15:21:58 * gouthamr reaches for the zorilla stamp 15:22:46 hope to see lots of patches from felipe_rodrigues soon :) 15:22:54 felipe_rodrigues: are you sure your last name isn't viroel, because we just heard of another felipe around here and i'm always suspicious of dviroel 15:23:20 hahaha! 15:23:30 hehe 15:23:31 haha 15:23:34 never too young to be a zorilla 15:23:47 * dviroel dviroel already reserved fviroel id for the future 15:24:01 dviroel: hah! smart dad 15:24:05 ahahaha 15:24:28 cool, thank you for making the introduction dviroel 15:24:36 anything else before we move on? 15:24:51 #topic Tracking our work 15:25:03 #link https://etherpad.openstack.org/p/manila-ussuri-review-focus (Ussuri cycle review focus etherpad) 15:25:19 How're things looking here? lets do a rollcall 15:25:31 Support query user message by timestamp 15:25:39 #link https://review.opendev.org/#/c/706438/ (manila) 15:25:40 #link https://review.opendev.org/#/c/708807/ (python-manilaclient) 15:26:00 this has gotten some review attention - any reason to think we can't merge soon' 15:26:49 i'll take a look at both these today, i don't see any blockers 15:27:00 [Unity] Manage/unmanage share server/share/snap 15:27:07 #link https://review.opendev.org/#/c/688227/ 15:27:54 a number of us have taken a look at this code, couple of issues we've tried conveying to the author/s 15:28:06 their CI is currently broken, we'll discuss why in a second 15:28:17 ^ not sure why they don't want to enable manage/unmanage tests on their ci 15:29:15 should be possible just to enable them only for this change 15:29:16 yep, dviroel... i've asked that as well in my most recent comment 15:29:26 but didn't get any response yet 15:29:38 carloss: can you -1 with your comment, might get their attention 15:29:59 gouthamr ok 15:30:19 I don't see any reviewers added for the next one 15:30:20 Graduate share groups feature 15:30:24 #link https://review.opendev.org/#/q/topic:bp/graduate-share-groups-feature+(status:open+OR+status:merged) 15:31:29 ah ty dviroel 15:31:33 i've got a review from vkmc 15:31:39 on the manila change 15:31:45 * vkmc hides 15:31:45 cool, so it's moving fine 15:31:53 oh it's was a good thing 15:31:53 ok 15:31:54 Tenant based quotas for share replicas and replica sizes 15:31:54 :) 15:32:02 lol 15:32:04 #link https://review.opendev.org/#/q/topic:bp/graduate-share-groups-feature+(status:open+OR+status:merged) 15:32:16 gah 15:32:17 #link https://review.opendev.org/#/q/topic:bp/limit-share-replicas-per-share+(status:open+OR+status:merged) 15:32:33 this has been getting good reviewer attention too 15:32:43 and looks good for the most part, anything to add carloss? 15:32:47 ty for reviewing, gouthamr and ty for the review/QA, dviroel 15:32:57 didn't added my comments on that yet, but I'm working on QA'ing 15:33:03 awesome 15:33:04 Create share from snapshot in another pool or backend 15:33:11 #link https://review.opendev.org/#/q/topic:bp/create-share-from-snapshot-in-another-pool-or-backend+(status:open+OR+status:merged) 15:33:25 this is the most complicated set of changes in my view for our attention 15:33:34 i'd like some more eyes on it, if possible 15:33:53 including the driver patch from NetApp: 15:33:55 #link https://review.opendev.org/#/c/712642/ 15:34:33 carthaca: your review would be valuable too ^ 15:34:37 * carthaca bookmarks the 3 links above to do some review 15:34:55 * gouthamr notes how people are reading his mind today 15:35:06 thank you carthaca 15:35:17 andrebeltrami is working on QA NetApp driver also 15:35:32 so please andrebeltrami, post your comments there too 15:35:42 Sure! 15:35:44 alright, the rest of the reviews on that etherpad aren't really features, and we have some time to get to them 15:36:28 please correct me if that's not the case 15:36:56 agree 15:37:08 cool, anything else about these reviews before we move on? 15:37:27 #topic NetApp Share Server NFS modify implementation (carthaca) 15:37:33 #link: https://etherpad.openstack.org/p/manila-netapp-share-server-nfs-modify (NetApp Share Server NFS modify proposal etherpad) 15:37:38 carthaca: you're up 15:37:45 Hi, thanks 15:37:51 I hope it is okay I just put this very netapp specific topic on the agenda. 15:37:57 But I wanted to collect feedback before coding something that I would never be able to contribute back and had to maintain in my fork forever ^^ 15:38:05 Please have a look at my etherpad and comment, ask, discuss ;) 15:38:38 josecastroleon, o/ 15:38:40 hi 15:39:40 carthaca: is this entirely netapp specific? or did you intend on generalizing this solution? 15:39:41 i've a couple of questions 15:40:54 "give my customers the possibiility to select certain nfs vserver settings" 15:41:04 well not all of that options are netapp specific, but I'm not that familiar with the other back ends 15:41:29 carthaca: that isn't entirely congruent with the way share servers are designed 15:41:40 carthaca: users have no control over them 15:42:06 currently only via security services 15:42:34 carthaca: yes, those and share networks are the only aspects they can view/manipulate about their share servers 15:43:34 carthaca: and these server side settings may not make sense to share networks, security services or individual shares (as you noted) 15:43:56 carthaca: but, the netapp driver already handles something like this today 15:44:37 i forget how, but, nfs versions can be configured 15:44:56 yes, you can set this in the config 15:45:25 ah, so its not exactly defined per tenant then 15:45:36 but that would mean I would have to run multiple manila-share services for the same backend or something 15:45:48 true 15:46:28 hmmm, at the outset, it feels like you could define scoped share type extra-specs and set these options when the first share is created 15:46:58 this looks like qos, but for share-servers 15:47:11 could work in the same way, i guess 15:47:18 but, when the share type extra-specs are manipulated and the next share is created, the driver can choose to either manipulate the existing share server or create a new one 15:48:31 dviroel: true, or any other scoped extra-spec that we'd plumb directly to the driver 15:49:13 carthaca: i'm not against generalizing this solution, but we'll probably need to discuss the possibilities/merits in a longer meeting 15:49:31 might need a common capability also, to identify backends that support it and have it enabled 15:50:04 the rest is up to the driver 15:51:09 i recall a similar request to determine root squash and all squash nfs options 15:52:00 i can dig up that discussion from a past PTG to see what ideas were considered, a proposal was not made 15:53:55 sounds related, I think this option is called ignore-nt-acl-for-root at netapp nfs modify 15:54:10 ack 15:54:18 cool, i think we've some AIs on this carthaca - we'll see what was discussed earlier wrt share server side customizations, please explore if scoped extra-specs can be considered 15:54:37 if you're planning on a generalized implementation, a specification would be required 15:55:04 cool, thanks for the feedback 15:55:06 if it just pertains to netapp, a spec is not necessary, just file a bp for project tracking 15:55:27 cool, we only have 5 minutes 15:55:41 * gouthamr looks into the bug etherpad 15:56:03 dviroel: we might have to look at https://bugs.launchpad.net/manila/+bug/1868586 outside of this meeting 15:56:05 Launchpad bug 1868586 in Manila "tempest complains 'Share network xxx could not be found.' " [Undecided,New] 15:56:28 i want to skip bug triage today and give ~3 mins to open discussion 15:56:32 taht okay? 15:56:38 +1 15:56:40 #topic Open Discussion 15:56:47 gouthamr: ok 15:56:59 gouthamr: you can take a bit more time if you need 15:57:26 ah, thank you priteau - you're kind :) we'll do the triage on our channel 15:57:49 anyone has anything to discuss? 15:57:52 yes 15:57:59 josecastroleon: o/ 15:58:47 we have just had a nasty behavior on our manila setup 15:59:03 we have 4 different cephfs backends behind 15:59:11 each of them mapped to a share type 15:59:21 so scheduling should be easy right? 15:59:41 we were seeing a continuous increase of scheduling time 16:00:16 josecastroleon: oh, weird - do you mind us moving over to #openstack-manila 16:00:21 sure 16:00:41 josecastroleon: thank you, lets continue there 16:01:04 thanks all for attending, we'll discuss this scheduling issue on #openstack-manila, please join us there if you can 16:01:08 thanks! 16:01:10 #endmeeting