15:00:02 <vkmc> #startmeeting manila
15:00:03 <openstack> Meeting started Thu Mar  5 15:00:02 2020 UTC and is due to finish in 60 minutes.  The chair is vkmc. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:06 <openstack> The meeting name has been set to 'manila'
15:00:09 <vkmc> o/
15:00:11 <amito> o/ hello
15:00:13 <lseki> o/
15:00:14 <maaritamm> o/
15:00:14 <vkmc> hello zorillas
15:00:16 <carloss> hi
15:00:19 <andrebeltrami> hello
15:00:22 <danielarthurt> Hello
15:00:26 <vhari> hi
15:00:36 <dviroel> hi
15:00:51 <ganso> hello
15:01:08 <vkmc> Agenda: https://wiki.openstack.org/wiki/Manila/Meetings
15:01:19 <vkmc> #link https://wiki.openstack.org/wiki/Manila/Meetings
15:01:26 <vkmc> there is no much in the agenda... but, following processes
15:01:42 <vkmc> :D
15:02:02 <vkmc> you might be aware that gouthamr couldn't make it today, so I will (try) to fill in for him
15:02:22 <vkmc> courtesy ping: xyang toabctl
15:02:34 <vkmc> all right...!
15:02:39 <vkmc> let's start with
15:02:44 <vkmc> #topic Announcements
15:02:52 <vkmc> #link https://releases.openstack.org/ussuri/schedule.html
15:03:30 <vkmc> nothing much this week... except that we are one week away from the manila's feature proposal freeze
15:03:59 <tbarron> \o
15:04:00 <vkmc> that means that we expect that features are completed or nearly completion by that deadline
15:04:14 <vkmc> tbarron, o/ oh heyy, thought you were away for today as well
15:04:22 <tbarron> not really here -- multitasking and I'm slow -- but saying 'hi'
15:04:45 <vkmc> cool, a very polite zorilla :)
15:06:16 <vkmc> all right, wrt the feature proposal freeze, make sure to notify the team if you have any blocker and reaching the deadline gets complicated
15:06:25 * gouthamr sneaks in
15:06:30 <vkmc> gouthamr, !
15:06:44 <gouthamr> o/ vkmc - please continue :)
15:06:49 <vkmc> sure thing
15:07:07 <vkmc> that's about it with the schedule
15:08:06 <vkmc> I want to add an extra announcement... since we mentioned when she started and also I believe is good to mention the current status
15:08:27 <vkmc> our dear intern maaritamm is finishing her internship this week
15:08:39 <vkmc> that makes me quite sad because I would love to have her in our team for longer
15:08:40 * gouthamr applause
15:08:47 * gouthamr sad face
15:08:50 <dviroel> =(
15:08:51 <carloss> :/
15:08:55 <lseki> :-(
15:08:58 <vhari> vhari, =(
15:09:06 <vkmc> but I want to say thanks to her for all the great work she did
15:09:24 <vkmc> and also let you know that she is pursuing a career in openstack
15:09:34 <vkmc> so... definitely we want to keep her in our team
15:09:44 <gouthamr> ++ maaritamm: great going and thank you for all your hard work here... we're too slow to review your changes, but we'll keep up :)
15:09:45 <maaritamm> This is the best and the coolest team I have ever worked with so big thanks to all, it was awesome!
15:10:09 <gouthamr> also, congratulations vkmc for being a successful mentor (again) :)
15:10:14 <vkmc> thanks gouthamr!
15:10:23 <maaritamm> I will definetly be around as much as possible and keep contributing :)
15:10:26 <gouthamr> maaritamm: you bet, we'll fund a zorilla tattoo :P
15:10:27 <carloss> thanks, maaritamm! You have done a great job in the project
15:10:43 <vkmc> with some luck we get her in our community and she can continue with her contributions :D
15:11:02 <gouthamr> ++
15:11:07 <vkmc> and... also... with some (more) luck... we also get her to join us in the OpenDev next June
15:11:32 <vkmc> so... I cannot stress how much I'm crossing my fingers for all this to happen
15:11:58 <maaritamm> same!
15:11:59 <vkmc> all right, that's everything I had on that topic
15:12:24 <gouthamr> #success  maaritamm finishes her successful #outreachy internship with #openstack-manila and is geared to work on OpenStack for the long haul! that's the kind of success we want with these internships!
15:12:31 <vkmc> do somebody else have any announcement for today?
15:12:38 <vkmc> hehe nice usage of bot commands
15:12:39 * gouthamr looks around of the success bot
15:12:46 * gouthamr fail
15:14:26 <vkmc> ok, I'll take that as a no
15:14:51 <vkmc> so, moving on...
15:15:08 <vkmc> it's a good moment to talk about bugs
15:15:28 <vkmc> #topic Bugs (vhari)
15:15:37 <vhari> o/
15:15:46 <vkmc> vhari, do we have any bugs to triage this week?
15:15:53 <vhari> sure, have a couple to look at
15:15:57 <vhari> https://bugs.launchpad.net/manila/+bug/1861959
15:15:58 <openstack> Launchpad bug 1861959 in Manila "CephFSDriver type error" [Undecided,New]
15:16:26 <vhari> let's take a look - needs early triage
15:16:46 <vkmc> checking it out
15:17:21 <vkmc> I have been working on the ceph drivers lately
15:17:26 <vkmc> so I'm wondering
15:17:38 <vkmc> which ceph version is the reporter using?
15:17:46 <vkmc> I'll ask that question for them
15:17:49 <gouthamr> good question ^
15:18:03 <gouthamr> wonder if this is the mimic/nautilus issue that was reported a while ago
15:18:07 <vkmc> there are slight differences in latest ceph versions so we might be hitting some error related to that
15:18:53 <gouthamr> https://bugs.launchpad.net/manila/+bug/1838936
15:18:54 <openstack> Launchpad bug 1838936 in kolla-ansible ussuri "manila-share not working with ceph mimic (13.2) nor ceph nautilus (14.2)" [Undecided,Triaged]
15:19:09 <gouthamr> ^ this is the other bug, but it seems unrelated
15:19:54 <vkmc> #link https://bugs.launchpad.net/manila/+bug/1861959
15:19:55 <openstack> Launchpad bug 1861959 in Manila "CephFSDriver type error" [Undecided,Incomplete]
15:20:08 <vkmc> #link https://bugs.launchpad.net/manila/+bug/1838936
15:20:09 <openstack> Launchpad bug 1838936 in kolla-ansible ussuri "manila-share not working with ceph mimic (13.2) nor ceph nautilus (14.2)" [Undecided,Triaged]
15:20:14 <vkmc> checking...
15:20:21 <gouthamr> vkmc: good to check, wrt LP 1838936, i couldn't reproduce it with a TripleO deployed OpenStack using Red Hat packaged ceph - it's possible we may have some missing patches in the package used in the other OSes
15:20:24 <vkmc> I just ask the reporter some questions and set the bug to incomplete
15:20:34 <vkmc> yes
15:20:34 <gouthamr> vkmc: +1
15:20:56 <vhari> vkmc+1 ty
15:20:56 <vkmc> ok, I believe we need to wait for them to provide more info
15:21:13 <vkmc> so, we can move on to the next bug
15:21:25 <vhari> https://bugs.launchpad.net/manila/+bug/1799742
15:21:26 <openstack> Launchpad bug 1799742 in Manila "Wrong segmentation ID sent to drivers when using multi-segments" [Medium,In progress] - Assigned to Sneha Prasad (snpd)
15:22:01 <vhari> ^^ looking for next steps
15:22:30 <vkmc> yes... I can see JSON asked for some updates
15:22:48 <vkmc> this was reported by ganso
15:23:16 <vkmc> and there is a proposed fix
15:23:19 <vkmc> https://review.opendev.org/#/c/648755/
15:25:49 * vkmc got distracted reviewing the proposed fix
15:26:04 <gouthamr> hmm, i'll need to dig in, but, the fix doesn't appear to be addressing the issue of the last segment being updated in the share network
15:26:11 <vkmc> no
15:26:46 <gouthamr> do you folks use multi segment neutron networks?
15:26:47 <vkmc> I see that ganso pointed out where the bug is, but the proposed fix is not addressing that directly
15:26:55 <gouthamr> carthaca: do you folks use multi segment neutron networks?
15:27:11 <gouthamr> carloss dviroel ^
15:27:55 <gouthamr> if yes, can you please take a look at this bug and confirm if it's valid?
15:28:20 <dviroel> gouthamr: will subscribe to this one
15:28:23 <vkmc> *still* valid
15:28:27 <vkmc> it's two years old
15:28:41 <ganso> I don't remember for what reason I tested that. I remember it was relevant for what we were implementing or testing, but I don't remember what it was exactly
15:28:43 <carthaca> I’m not sure if we are affected, but I will check
15:28:49 <vkmc> and the last update for the proposed fix is one year ago
15:28:59 <gouthamr> thank you dviroel ganso carthaca
15:29:08 <vkmc> thanks folks
15:29:20 <ganso> perhaps it was for designing the spec, I'm not sure. But I was studying how the network plugins and share networks behaved on multi-segment, since it was possible anyone in production could use that
15:29:21 <gouthamr> vkmc: +1, we did change share networks quite a bit now with subnets
15:29:27 <carloss> gouthamr will subscribe as well
15:29:34 <vkmc> gouthamr, yes, I was seeing that
15:29:36 <gouthamr> great thanks carloss ..
15:29:52 <ganso> I remember having a discussion with someone where I assumed every segment could only have 1 VLAN, and when I found out that it wasn't true, I started investigating and testing that, and found the bug
15:30:01 * ganso is in a meeting, sorry
15:30:40 <gouthamr> np thanks for the context ganso - i vaguely remember discussing part of this during the early implementation of subnets
15:31:20 <vkmc> ganso++
15:31:27 <vkmc> ok
15:31:31 <vhari> next we have https://bugs.launchpad.net/manila/+bug/1820933
15:31:32 <openstack> Launchpad bug 1820933 in Manila "There is no way to select neutron subnet while creating share network with Horizon" [Undecided,Incomplete]
15:31:43 <vkmc> uh oh horizon
15:32:18 <vkmc> we would need to deploy manila with horizon in rocky and see if we can reproduce that
15:32:39 <vkmc> if not, I believe we can close it
15:32:53 <gouthamr> oh, we have a response that i didn't respond to
15:32:54 <gouthamr> :)
15:33:00 <vhari> :D
15:33:21 <vkmc> gouthamr, shall we ask the reporter to submit the git tag or hash?
15:33:28 <vkmc> or is it too late to ask for that?
15:33:39 <gouthamr> i recall testing it on the rocky release for the OP though i haven't mentioned that explicitly in my response..
15:33:54 <gouthamr> vkmc: perhaps too late, i'll still update the bug for completeness sake
15:34:05 <vkmc> sure
15:34:20 <gouthamr> it's possible there's some logging they can provide us *if* they're still on rocky, and seeing this issue
15:34:42 <vkmc> yes
15:34:54 <vkmc> we can try to reproduce in newer versions as well though
15:34:57 <vkmc> in master
15:35:07 <vkmc> hopefully it's not broken
15:35:11 <gouthamr> vkmc: yeah, problem doesn't exist - i use that quite a bit :)
15:35:19 <vkmc> cool
15:35:39 <vkmc> ok
15:35:46 <vhari> good to know ^^
15:35:58 <vhari> that's all bugs for today folks
15:36:07 <vkmc> yay, cool
15:36:10 <vkmc> thanks vhari
15:36:12 <vhari> ty all
15:36:31 <vkmc> last but not least
15:36:32 <vkmc> #topic Open Discussion
15:36:49 <vkmc> any topic for open discussion for today?
15:37:11 <gouthamr> yes
15:37:47 <gouthamr> this thing bothered me a lot, and i thought you guys might have some insight
15:38:02 <gouthamr> do wallabies like zorillas?
15:38:08 <vkmc> oh...
15:38:10 * gouthamr ducks
15:38:16 <lseki> lol
15:38:18 <dviroel> maybe
15:38:22 <carloss> haha
15:38:41 <vkmc> wallabies are vegetarian so there is no immediate risk
15:38:43 <vkmc> zorillas too
15:39:09 <vkmc> so they might be good friends
15:39:24 <gouthamr> awesome! i like your theory vkmc - now we just need to prove that in a safe lab environment, you know, for science.
15:39:27 <vkmc> we all know that sharing food interests is always a good way to make friends with anybody
15:39:37 <vkmc> sounds like a plan
15:39:42 <lseki> or they'll fight for the same food
15:39:50 <vkmc> lseki, also a good point
15:39:52 <gouthamr> lseki: hah!
15:40:19 <vkmc> lots of research to do before OpenStack Wallaby kicks in
15:40:44 <gouthamr> sorry for the goofiness, good to always have a laugh with you folks! great meeting, thank you vkmc!
15:40:48 <vkmc> fortunately we have like one full cycle xD
15:40:56 <gouthamr> lots of time!
15:41:03 <vkmc> gouthamr, you can do anything, you are our ptl
15:41:04 <vkmc> hahaha
15:41:06 <vkmc> gouthamr++
15:41:21 <vkmc> allright, anything else?
15:41:47 <vkmc> let's do a countdown
15:41:51 <vkmc> 5...
15:41:53 <gouthamr> 100...
15:41:54 <vkmc> 4...
15:41:56 <vkmc> lol
15:41:56 <gouthamr> oh
15:42:01 <vkmc> 3...
15:42:08 <vhari> 1..
15:42:09 <vkmc> 2...
15:42:13 <vkmc> 1...
15:42:22 <vkmc> ok, will take that as a no
15:42:33 <vkmc> and you get back roughly 13 minutes back
15:42:34 * gouthamr damn threading issues
15:42:39 <vkmc> use them wisely
15:42:42 <vkmc> thanks everybody!
15:42:44 <gouthamr> ++
15:42:47 <vhari> ++
15:42:51 <vkmc> #endmeeting