15:00:32 <tbarron_> #startmeeting manila
15:00:33 <openstack> Meeting started Thu Dec 19 15:00:32 2019 UTC and is due to finish in 60 minutes.  The chair is tbarron_. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:34 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:37 <openstack> The meeting name has been set to 'manila'
15:01:00 <tbarron_> courtesy ping: xyang toabctl bswartz ganso erlon tpsilva vkmc amito jgrosso dviroel lseki carloss
15:01:04 <dviroel> o/
15:01:05 <lseki> o/
15:01:06 <carloss> hi :)
15:01:12 <cmurphy> o/
15:01:40 <tbarron_> Note that you can edit the courtesy ping list yourselves, so pls. update if you want to be on or off of it.
15:02:10 * tbarron_ waits a couple
15:02:20 <vkmc> o/
15:02:51 <andrebeltrami> o/
15:03:02 <tbarron_> Hi all!
15:03:23 <tbarron_> gouthamr is travelling today so I am guest chair as emeritus ptl
15:03:41 <tbarron_> Agenda: https://wiki.openstack.org/wiki/Manila/Meetings
15:03:51 <tbarron_> #topic Announcements
15:04:03 <tbarron_> We will not meet next week.
15:04:22 <tbarron_> Next meeting is 2 January at this time.
15:04:33 <tbarron_> I will send a note to openstack-discuss ...
15:04:55 <tbarron_> I don't have other announcments today.  Anyone?
15:05:48 <tbarron_> OK, let's switch  up the order a bit in case maaritamm can join us later on ...
15:06:08 <tbarron_> #topic Policy Popup team
15:06:14 <tbarron_> cmurphy: Hi!
15:06:18 <cmurphy> hi o/
15:06:43 <tbarron_> cmurphy: I don't think all of us have full background, so please feel free to fill in ...
15:07:10 <cmurphy> oh sure, some background:
15:07:28 <cmurphy> #link https://governance.openstack.org/tc/reference/popup-teams.html#secure-default-policies
15:08:00 <cmurphy> we started a new popup team to get a head start on fixing the default policy rules across openstack, manila volunteered to be a part of it
15:08:30 <cmurphy> the popup team was approved by the tc last week, so i'm going around to each team's meeting this week to kick things off before the holidays
15:08:45 <cmurphy> mostly i'd just like to get you thinking about how you want to organize and track the work
15:08:47 <tbarron_> cmurphy: gouthamr volunteered us but several of  us were in sync with him on this :)
15:09:31 <maaritamm> tbarron, I sneaked in already, hi :)
15:09:36 <tbarron_> In general we're trying to get manila better integrated with the rest of OpenStack, give users consistent experience, etc.
15:10:06 <tbarron_> maaritamm: hi, and speaking of which we'll talk about manila OSC integration as next  agenda item
15:10:50 <cmurphy> tbarron_: :)
15:11:02 <tbarron_> cmurphy: we're starting to track our work with taiga and probably can make tasks there for policy rule work for manila
15:11:38 <cmurphy> tbarron_: great! if you could create links under the progress section here https://wiki.openstack.org/wiki/Consistent_and_Secure_Default_Policies_Popup_Team that would help me a lot
15:12:27 <cmurphy> i'm also available if you have any questions about the implementation
15:12:30 <tbarron_> cmurphy: No problem, we can do that.
15:13:00 <tbarron_> Let"s see if anyone in this meeting today is  particularly interested in participating.
15:13:58 <tbarron_> I think the first step will be to read the keystone design doc from the link cmurphy just posted, and see what we can crib from other projects there.
15:14:37 <tbarron_> And we should think about whether there's anything "special" about manila that would lead to a need for new policy roles, etc.
15:14:53 * tbarron_ doesn't know of anything like that, but we should check
15:15:47 <tbarron_> Anything else on this topic today?  cmurphy?  others?
15:16:51 <cmurphy> mostly the things to think about are whether the apis are specific to a project (things that are owned by a tenant/customer) or specific to the whole system (things that an administrator would do for the whole deployment)
15:17:14 <cmurphy> that's all i had, i can circle up with gouthamr after the holidays
15:17:24 <tbarron_> cmurphy: Thanks for adding this to our agenda!  We'll get started and may invite you back again if needed ...
15:17:41 <cmurphy> tbarron_: great! any time
15:17:56 <tbarron_> #topic: tracking our work
15:18:18 <tbarron_> #link https://review.opendev.org/#/c/642222
15:18:41 <tbarron_> This is the foundational review for our OSC integration work.
15:19:08 <tbarron_> vkmc has been driving this and maaritamm is going to be adding onto her work.
15:19:44 <tbarron_> We've had quite a bit of review of 642222 and I"d like to check if there are any objections to moving ahead and
15:19:47 <tbarron_> merging it.
15:20:25 <dviroel> Not at all. I'm in the middle of reviewing it. Look good.
15:20:26 <tbarron_> It just adds basic CRUD for shares to the OSC client, using a plugin from python-manilaclient.
15:21:01 <tbarron_> But it provides the design pattern that we should follow as we add more manila commands to OSC.
15:21:08 <tbarron_> dviroel: thanks
15:21:26 <tbarron_> Anyone have concerns?  Discussion points?
15:21:52 <carloss> Not from my side as well, tbarron_
15:22:51 <tbarron_> OK, I think we have consensus.  dviroel if you are reviewing anyways and expect to finish today, plese just W+1 assuming you still approve.
15:23:16 <dviroel> tbarron_ ok, will do
15:23:43 <tbarron_> I want to get lots of "soak time" in U for this stuff and have enough implemented by code freeze for this to be actually useful.
15:24:04 <tbarron_> maaritamm: vkmc: do you want to say something about what is being impmented next?
15:24:33 <tbarron_> implemented
15:25:24 <maaritamm> tbarron_, currently working on share types
15:25:57 <vkmc> tbarron_, not much actually... just that there are some patch for review already
15:26:19 <vkmc> the initial implementation, which is the plugin creation and the share crud commands
15:26:23 <tbarron_> maaritamm: good choice, cause it's a pain to have to use the manila cmd to create the share type you need before using OSC command to create the share referencing the share type :)
15:26:27 <vkmc> 642222
15:26:43 <vkmc> also the share set/unset, which might require some feedback from you
15:27:03 <vkmc> (you === all reviewers :)
15:27:22 <vkmc> https://review.opendev.org/#/c/698848/
15:28:02 <vkmc> in that command we are unifying the manila update and manila metadata commands into share set and share unset
15:28:07 <tbarron_> vkmc: maaritamm We'll rely on you two to prioritize our review cycles.  Assuming we merge 64222 today, which one is up next?
15:28:17 <vkmc> set and unset
15:28:24 <vkmc> then we continue with share types
15:28:34 <vkmc> and we also have acls and quotas coming up next
15:29:13 <vkmc> tbarron_, ^
15:29:14 <tbarron_> ok, I'm adding these into my devstack one by one and exercising them as we go along ...
15:29:29 <vkmc> nice, thx
15:29:45 <vkmc> it would be nice to get the reviews from operators
15:29:49 <tbarron_> Let's try to get another chunk merged the first week of January or so.
15:30:05 <vkmc> cool
15:30:37 <tbarron_> vkmc: yes, but failing up front reviews from operators the best thing we can do is get the commands out there early in the release cycle.
15:30:50 <tbarron_> so we can adjust as required.
15:30:58 <tbarron_> we're so agile :)
15:31:03 <vkmc> haha
15:31:09 <vkmc> ok, we can do that
15:31:48 <tbarron_> OK, moving along ...
15:32:16 <tbarron_> Any other reviews that need attention before 2020?   specs?
15:32:38 <carloss> Specs I think there is only the haixin's one
15:32:47 <carloss> Which I currently don't know the status
15:32:55 * carloss goes to check the patch
15:33:42 <carloss> we have a tbarron_  +2 and some +1s on that patch
15:33:46 <tbarron_> #link https://review.opendev.org/#/c/692330/
15:34:00 <tbarron_> yeah, it has my support and there was no controversy
15:34:06 <carloss> thanks tbarron_ :)
15:34:13 <tbarron_> others please review
15:34:39 <tbarron_> we won't hold up this one over milestone technicalities, but please review
15:35:10 <tbarron_> We'll wait to merge it though until after gouthamr is back.
15:36:08 <tbarron_> #topic Bugs
15:36:17 <tbarron_> jgrosso: you here?  vhari?
15:36:33 <jgrosso> I am here having some technical difficulties
15:36:59 <tbarron_> jgrosso: tecnical difficulties == Xmas cookies?
15:37:08 <jgrosso> lol I wish
15:37:11 <jgrosso> https://bugs.launchpad.net/manila/+bug/1850626
15:37:11 <openstack> Launchpad bug 1850626 in neutron "neutron-dynamic-routing: TypeError: bind() takes 4 positional arguments but 5 were given" [Critical,Fix committed] - Assigned to Slawek Kaplonski (slaweq)
15:37:17 * tbarron_ sends jgross some
15:37:29 <jgrosso> just had a question is this done for manila
15:37:45 <jgrosso> looks like it was merged and waiting on neutron correct?
15:38:19 <jgrosso> I was about to set fix -released for manila
15:39:26 <jgrosso> sorry not sure if you fot any of that info :(
15:39:50 <jgrosso> got not fot
15:39:54 <jgrosso> :)
15:40:24 <jgrosso> Issue my be Pebkac :)
15:40:35 <tbarron_> jgrosso: i think we need to check whether we have a workaround in place that we can un-do now
15:40:47 <jgrosso> ack tbarron_
15:40:55 <jgrosso> last bug
15:40:56 <tbarron_> jgrosso: and whether there is an issue in any of the stable/.. branches
15:41:05 <jgrosso> tbarron_ ok
15:41:22 <tbarron_> jgrosso: the lvm and cephfs IPv6 jobs may be relevant
15:41:24 <jgrosso> https://bugs.launchpad.net/manila/+bug/1848278
15:41:24 <openstack> Launchpad bug 1848278 in Manila "tempest extend/shrink tests may use wrong share export location" [Undecided,New]
15:41:38 <jgrosso> tbarron_ ack
15:41:47 <tbarron_> since they use bgp to propogate return routes to the tenant IPv6 networks
15:42:11 <jgrosso> border gateway protocol?
15:42:26 <jgrosso> been a while and I am rusty on networking :0
15:43:01 <tbarron_> I just assigned that one to myself jgrosso, you can ping about it again in the new year if it's not getting fixed.
15:43:18 <jgrosso> ok thanks tbarron_
15:43:23 <jgrosso> all I had thanks
15:43:27 <tbarron_> The issue there is simply that when there are multiple export locations the code is selecting the first one
15:43:36 <jgrosso> tbarron_: ack
15:43:50 <tbarron_> which may not be appropriate if IPv6 and IPv4 are both deployed
15:44:02 <tbarron_> so we need to loop and match
15:44:07 <jgrosso> understood
15:44:07 <tbarron_> address family
15:45:01 <tbarron_> targeted to U-2
15:45:23 <jgrosso> tbarron_: thanks for setting all of that
15:45:32 <jgrosso> for 1848278'
15:46:43 <tbarron_> jgrosso: w.r.t. 'border gateway protocol' yeah, that's what BGP is
15:46:52 <jgrosso> tbarron_: ack
15:47:08 <tbarron_> we don't need it for IPv4 tenant networks because they are NATed
15:47:42 <tbarron_> but IPv6 tenant networks are not, so they have to be routed, i.t. everyone outside that network needs to learn how to get to it.
15:47:58 <tbarron_> and BGP is one way to propogate that info.
15:48:07 <jgrosso> cool
15:48:10 <tbarron_> and it's what our CI uses.
15:48:57 <tbarron_> jgrosso: moar bugs?
15:49:06 <jgrosso> no I am set thanks tbarron_
15:49:22 <tbarron_> #topic Open Discussion
15:50:30 <tbarron_> Looks like we can close this year's Manila meetings down now.
15:50:45 <carloss> yes, tbarron_ :)
15:50:55 <tbarron_> Thanks all!  See you in #openstack-manila, and in this spot in 2020 on 2 January!
15:51:03 <carloss> Thanks tbarron_
15:51:07 <dviroel> Thanks tbarron_
15:51:08 <jgrosso> happy holidays all ! thank tbarron_
15:51:26 <tbarron_> #endmeeting