15:01:53 #startmeeting manila 15:01:54 Meeting started Thu Aug 13 15:01:53 2020 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:57 The meeting name has been set to 'manila' 15:02:03 o/ 15:02:08 hi 15:02:13 hi 15:02:15 hello! 15:02:20 hey, sorry to be late, it's early for me 15:02:23 :D 15:02:25 o/ 15:02:33 courtesy ping: ganso vkmc carloss danielarthurt 15:02:39 :P sorry carloss 15:02:44 np :) 15:02:46 Hello! 15:03:25 hey everyone o/ it is summer vacations time, at least in the northern hemisphere and many folks may be away from their computers for good reasons 15:03:38 so this is going to be a short meeting likely :) 15:03:46 Agenda is here: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:03:51 lets get started with 15:03:55 #topic Announcements 15:04:09 first and foremost, is our schedule - 15:04:19 our Feature Proposal Freeze is next week! 15:04:24 v 15:04:25 #link https://releases.openstack.org/victoria/schedule.html (victoria release schedule) 15:04:56 please have any patches polished up and uploaded, and passing CI by next week - so we can assess our feature review workload and catch things early 15:05:48 if there are any concerns with this deadline, as always, let's discuss it either via this meeting, or the ML 15:06:21 and a friendly reminder to register for the upcoming OpenInfra summit and the OpenDev PTG 15:06:44 #link https://www.openstack.org/summit/2020/?_eboga=1892306176.1579632769 15:07:04 #link https://www.openstack.org/ptg/ 15:07:26 the summit is oct 19-23, and the ptg is oct 26-30 15:07:33 so its back to back weeks 15:07:54 the venue i hear is a lovely place this time, quite comfortable i'd hope 15:08:35 sorry for the tease, but we'll hopefully adjust our schedules well so that we don't have meeting fatigue 15:09:26 both these events are virtual, registration is 0$, so no reason not to do it :) - the program committees for both events send announcements to registered users 15:10:03 voting for summit presentations is open 15:10:07 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016486.html 15:11:16 the last announcement today's a sad one, but not an unexpected one 15:11:41 xyang let me know (a while ago, my bad) that she cannot dedicate time to review patches 15:12:27 so she would like to be removed from the maintainers team - i conveyed our deep sense of gratitude for all the work she has done in the past to get manila up and running 15:12:43 =( 15:12:45 * vkmc sneaks in o/ 15:13:01 we'll see her around in the k8s community, and she's welcome here whenever 15:13:05 :( 15:13:57 as we've maintained, our objective is to continue to grow the number of responsible maintainers 15:14:41 we'll mentor folks that are willing, please get in touch with any of the existing maintainers! 15:14:58 that's all i had in terms of announcements today, does anyone else have anything? 15:15:40 #topic Doc-a-thon recap 15:16:14 so we had an impactful event last week! 15:16:31 thanks to vkmc and vhari for putting things together 15:16:36 (vhari is out for the day) 15:16:42 \o/ 15:16:48 #link https://ethercalc.openstack.org/ur17jprbprxx (doc-a-thon ethercalc) 15:17:20 i see a number of open doc reviews from that day 15:17:42 we've also gotten started on some hard ones 15:18:03 all of those bugs are targeted to milestone-3 15:18:23 but, a number of them are available to review right now - please take a look at the etherpad 15:18:28 and review these docs 15:19:28 doc changes to user/admin guides may even be backported - so lets get these merged in the main branch :) 15:19:42 any other feedback on the doc-a-thon? 15:19:54 how did everyone else feel? 15:20:41 i feel we ought to make this a regular thing at least once each release, given how enthusiastically we swarmed on the doc bug backlog 15:20:51 I think that it was productive and we had a chance to work in several bugs that were opened for a long time 15:21:11 agree with the idea of doing it more often 15:21:27 the synchronous triage session was helpful so we could dive into each of these as a group, rather than have a conversation on the bug reports 15:21:59 It was great to see everybody working together at that day 15:22:25 great! vkmc and vhari have plans for a bug-a-thon akin to this! 15:22:29 for sure we should do more often 15:22:38 we'll probably aim to do that one after feature freeze 15:22:52 cool 15:23:28 +1 15:23:28 thanks everybody for joining that effort 15:23:34 it was great .) 15:23:40 :) 15:23:43 bug-a-thon may also be a good time to mentor new contributors 15:23:47 I have to catch up with reviews now 15:23:59 yep, next one will be a bug-a-thon... this was a pilot test 15:24:38 vkmc: Feature freeze is the week of sep 07011 15:24:47 sep 07-11* 15:24:54 yes 15:25:03 gouthamr, I'm thinking after feature freeze 15:25:09 when we start working on stabilization 15:25:14 i was hoping it'd be after GHC so we have some enthusiastic newbies :) 15:25:33 gouthamr, that's a great idea 15:26:07 (backstory: vkmc enriquetaso and i are hoping to motivate some GHC attendees to get involved with manila - https://ghc.anitab.org/attend/) 15:26:24 big challenge :D 15:26:48 I'll wait for the open discussion to share more info on it, if you want to join us 15:27:21 vkmc: we can work out the details - we can do multiple days if we need to, one where we're swarming on the more complicated bugs and one specifically for new contributors 15:27:42 vkmc: ack, i'll roll on then.. 15:27:46 gouthamr++ 15:28:00 any other questions/concerns/feedback regarding $topic? 15:28:13 #topic Questions for the User Survey 15:28:17 #link https://etherpad.opendev.org/p/manila-zorilla-2021-user-survey-question (user survey candidate questions) 15:28:35 thank you for adding questions to that etherpad 15:29:00 we can pick two of these, and so i'd like for us to please vote against the questions submitted 15:29:28 just use +1 or -1 next to the question 15:30:38 we'll need to try and make these objective rather than subjective if possible, for a couple of reasons - survey fatigue, and for the reason that subjective answers are hard to parse and aggregate 15:31:06 but if we *must* use a subjective question, that's alright 15:31:48 so please vote, i'll take a look at this and compile, and ship it off to the foundation marketing team 15:32:12 any questions/concerns? 15:32:45 I've submitted a few :o 15:32:55 no questions on my side 15:32:58 vkmc++ ty :) 15:33:06 okay 15:33:13 #topic Reviews needing attention 15:33:26 i'll restart the etherpad after next week 15:33:39 but, are there any languishing changes that you'd like eyes on? 15:34:27 we found that the etherpad is helpful when we're facing a deadline :) but, if you have a review you're not getting attention on, you're welcome to bring it up to this meeting 15:34:55 edit the agenda on https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting and i'll know 15:35:10 hearing none, lets move on to some bug triage 15:35:16 #topic Bugs 15:35:24 #link https://etherpad.opendev.org/p/manila-bug-triage-pad-new 15:35:35 vhari farmed out a list for us to look at 15:35:45 #link https://bugs.launchpad.net/manila/+bug/1890537 15:35:46 Launchpad bug 1890537 in OpenStack Shared File Systems Service (Manila) "RHOSP16(Train) Unity manila NFS access-allow does not work for a specific IP, but it works for a subnet." [Undecided,New] 15:36:42 hmmm, i wonder if the IP without /32 will work on that driver 15:37:04 interesting bug nevertheless 15:37:22 we expect drivers to treat IPv4 /32 and IPv6 /128 as single IP addresses 15:38:24 we'll let the dell/emc folks take this bug, but i think its a "medium" (which is almost a "high" for a driver bug) 15:38:37 any disagreements? 15:38:43 no 15:39:05 okay next 15:39:05 #link https://bugs.launchpad.net/manila/+bug/1886904 15:39:06 Launchpad bug 1886904 in OpenStack Shared File Systems Service (Manila) "Access rule is not successfully applies to share" [Undecided,New] 15:40:21 an interesting one, it looks like we inadvertently factored out the reconciliation loop for service failures into the "ensure_shares" mechanism 15:40:51 what are the consequences when one hits this bug? 15:40:53 and "ensure_shares" will be called on service startup only if the driver needs it 15:41:01 for the user? 15:41:13 the user will see the rule never applied 15:41:24 teh state is correct "queued_to_apply" 15:41:30 can they delete it and reapply? 15:41:44 yes, or perform *any* further access rule operation on the share 15:41:50 right 15:42:01 agree with your analysis on likely fix 15:42:16 just trying to ask the triage question w.r.t. severity 15:42:28 ack, we can make this a medium too and note the workaround 15:42:50 we have a class of these service failure issues that lkuchlan's bringing up 15:43:01 like a share that gets stuck creating/deleting 15:43:12 we could brainstorm a common solution 15:43:32 +1 15:43:36 +1 15:44:00 any volunteers to take this bug/ 15:44:34 i'll assign it to myself, and get to it sometime-ish 15:44:35 #link https://bugs.launchpad.net/manila/+bug/1886690 15:44:36 Launchpad bug 1886690 in OpenStack Shared File Systems Service (Manila) "Misleading asynchronous user message when share services are down" [Low,New] 15:44:44 yay, my favorite one now 15:45:08 oh, i reported it too 15:45:13 xD 15:45:13 * gouthamr calms down 15:45:34 okay this is potentially a low hanging fruit, but also an opinion 15:45:54 gouthamr should have to be up before dawn more often 15:46:15 when the share service is down, the user message for failures ought to say something along the lines of 15:46:16 gouthamr: yeah, the thing on this one is to drive agreement on the right message 15:46:17 "No storage could be allocated for this share request. Share back end services are not ready yet, trying again after a while may succeed. Contact your administrator in case retrying does not help." 15:46:27 i think 15:47:14 any disagreements, or is that leaking the abstraction too much 15:47:18 I like it. 15:47:36 lgtm 15:47:40 makes sense to me 15:47:55 s/Share back end services/services -- if necessary 15:48:41 We're not disclosing back end details, that there is some back end that has to be ready is not a secret. 15:49:09 but the substitution is fine by me too 15:49:13 ack 15:49:24 any volunteers to fix this up 15:49:50 we could keep it around for ghc/new contributors - its a fairly easy bug fix 15:49:56 gouthamr, I can take this 15:50:01 I have a mentee starting up 15:50:02 :) 15:50:10 ooh, nice ty vkmc 15:50:11 lgtm as well :) 15:50:13 I'll grab it in the meantime 15:50:33 ... and set it to triaged 15:50:40 awesome, thank you 15:50:52 lets stop the triage for today with this 15:51:01 #topic Open Discussion 15:52:04 vkmc: tell us about GHC 15:52:32 o/ 15:52:48 so, GHC stands for Grace Hopper Celebration 15:53:02 it's a huge conference that has been ongoing for several years 15:53:07 and they have the "open source day" 15:53:20 we are participating as a community for this day 15:53:46 for this, we will be doing a hands on event in which we will help participants to make their first contribution 15:53:56 we expect to do some pair programming with them and work on some low hanging fruit bugs 15:54:16 as gouthamr mentioned, enriquetaso and him will be joining as mentors 15:54:38 spotz and I are coordinating 15:54:40 we do need more mentors though 15:54:52 we expect 30 participants to join and we expect to get at least 4 more people 15:54:58 if you are interested, please let me know 15:55:15 date? 15:55:16 also if you are hesitant on how is to mentor, also let me know 15:55:21 oct 1st 15:55:27 ty 15:55:34 from 8.30pm PT to 6.00pm PT 15:55:39 probably we will make it shorter 15:55:47 but initially that's the length 15:55:50 (full day) 15:56:11 #link https://ghc.anitab.org/ 15:56:24 * gouthamr an event in PT :) 15:56:31 #link https://ghc.anitab.org/get-involved/volunteer/ 15:56:52 also, it is worth mentioning, if you sign up as mentors for the open source day, you will get a full pass for the whole conference 15:56:53 :) 15:57:11 comments, questions? 15:58:24 thank you for sharing vkmc - its an awesome mentoring opportunity, and a way to promote openstack and manila among a great gathering 15:58:44 yaas, thanks you gouthamr for the broadcasting space and for joining us as mentor 15:59:04 always 15:59:34 we're close to the hour - let's take this to #openstack-manila - thanks for joining everyone 15:59:46 stay safe, and enjoy any time off you may have planned 15:59:55 #endmeeting