15:01:51 <tbarron> #startmeeting manila
15:01:52 <openstack> Meeting started Thu Mar  7 15:01:51 2019 UTC and is due to finish in 60 minutes.  The chair is tbarron. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:53 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:55 <openstack> The meeting name has been set to 'manila'
15:01:58 <bswartz> .o/
15:02:20 <carlos_silva> hi :)
15:02:27 <tbarron> chair bswartz
15:02:30 <tbarron> in case
15:02:41 <vkmc> o/
15:02:44 <tbarron> i'm going to try the courtesy ping the old way
15:02:46 <amito> o/
15:02:50 <tbarron> courtesy ping: gouthamr zhongjun xyang toabctl bswartz ganso erlon tpsilva vkmc amito jgrosso
15:02:57 <bswartz> I have a conflict at 10:30 unfotunately, so I can only stat half the meeting
15:02:59 <tbarron> bot didn't kill me
15:03:05 <bswartz> You need the hashtag to make the chair command work
15:03:06 <toabctl> hey
15:03:09 <lseki> hi
15:03:14 <jgrosso> hey all
15:03:15 <tbarron> bswartz: oh yeah
15:03:17 <bswartz> s/stat/stay/
15:03:27 <tbarron> ganso has a conflict
15:03:34 <tbarron> gouthamr is taking PTO
15:03:36 <tbarron> slacker
15:03:43 <jgrosso> :)
15:03:43 <bswartz> PTO? what's that?
15:03:50 <bswartz> >_<
15:04:15 <tbarron> ok let's get started
15:04:30 <tbarron> Agenda: https://wiki.openstack.org/wiki/Manila/Meetings#Weekly_Manila_team_meeting
15:04:39 <tbarron> #topic Announcements
15:04:56 <tbarron> It is Feature Freeze
15:05:25 <tbarron> if you have any other non-bug fix, non-test-only, non-doc fixes for Stein
15:05:37 <tbarron> you need to request a Feature Freeze Exception
15:05:54 <bswartz> Today is feature freeze in Kubernetes too
15:05:59 <tbarron> Fortunately the big manage share servers stuff merged
15:06:04 <bswartz> I wonder if that's a coincidence or good planning?
15:06:13 <tbarron> bswartz: got your raw block discovery working?
15:06:19 * tbarron digresses
15:06:31 <bswartz> It merged in the dark of night
15:06:40 <tbarron> cool
15:07:17 <tbarron> Thanks to ganso, his team, and reviewers, especially gouthamr for their work on the manage share servers feature
15:07:46 <tbarron> It's also time to release the version of python-manilaclient that we're shipping for Stein.
15:08:06 <tbarron> So I've submitted a review for that and it will presumably merge today or tomorrow
15:08:34 <tbarron> It's also the deadline to submit topics for the Summit Forum.
15:08:40 <tbarron> I plan to do these later today,
15:08:52 <tbarron> You still have a little bit of time to add your ideas to
15:09:00 <tbarron> our brainstorm etherpad
15:09:58 <tbarron> #link https://etherpad.openstack.org/p/DEN-train-forum-manila-brainstorming
15:10:08 * tbarron pauses to fix the agenda there
15:11:12 <tbarron> That's all I have for announcements,
15:11:20 <tbarron> anyone else?
15:11:50 <tbarron> #topic Bugs
15:12:06 <tbarron> OK it's time in the release schedule to pivot
15:12:13 <tbarron> from development to
15:12:21 <tbarron> bug detection and fixes
15:12:33 <tbarron> of course that should be ongoing but now it should
15:12:44 <tbarron> be exclusive focus for stein work
15:13:08 <tbarron> (doesn't mean you can't work on stuff for train but we won't merge it till then)
15:13:13 <tbarron> jgrosso: you are up
15:13:17 <jgrosso> ok
15:13:44 <jgrosso> well question about https://bugs.launchpad.net/manila/+bug/1817316
15:13:45 <openstack> Launchpad bug 1817316 in Manila "security service password is stored in plaintext" [Undecided,New]
15:14:18 <jgrosso> have we  found out the best practice as a baseline and go from there, we were thinking this was not a "manila" issue but across the board??
15:14:28 <jgrosso> I know we talked about this last meeting
15:14:54 <tbarron> well I asked on the discuss list and bnemec from oslo and joasorio from security replied
15:15:15 <tbarron> There is a new oslo capability to leverage castellan to
15:15:30 <tbarron> keep service passwords and the like  in a vault rather than
15:15:32 <tbarron> plaintext
15:15:52 <tbarron> That doesn't address the security-service password directly b/c
15:16:14 <tbarron> it is entered by a cloud-operator via the api
15:16:20 <tbarron> and stored in the database
15:16:30 <tbarron> So I've added this as a PTG topic
15:16:46 <jgrosso> ok great
15:16:48 <tbarron> one possibility is that we can use standard (i think ??) DB
15:16:56 <jgrosso> is this a medium?
15:17:05 <tbarron> AES encryption or some such to store the password in the DB
15:17:15 <tbarron> and add configuration for the encryption key
15:17:31 <tbarron> and then use castellan for the encryption key and
15:17:36 <tbarron> for service passwords
15:17:51 <tbarron> so I'll float that idea now and we can talk about it at PTG
15:17:55 <bswartz> When was the last time we added a dependency on an outside service?
15:18:06 <bswartz> We need a checklist of things that need updating when we do that
15:18:10 <tbarron> yeah
15:18:19 <bswartz> For example all the test jobs need to install that service
15:18:26 <bswartz> The developer docs need to tell developers to install it
15:18:27 <tbarron> bswartz: we could make it a soft dependency of course
15:18:39 <tbarron> still need the checklist
15:18:44 <bswartz> Deployers will have to do whatever they do
15:19:14 <tbarron> but operator would set an option to encrypt service passwords and sec service p/w
15:19:15 <bswartz> It's a nontrivial change to make
15:19:16 <tbarron> or not
15:19:25 <bswartz> But I agree it does make sense in this context
15:19:40 <tbarron> bswartz: right, it's non-trivial and that's why I think it's a PTG topic
15:19:50 <tbarron> would need a spec and work plan
15:20:23 <tbarron> jgrosso: so medium is fine but add wish-list and note that we'll discuss it at PTG
15:20:35 <jgrosso> got it
15:20:38 <jgrosso> https://bugs.launchpad.net/manila/+bug/1818569
15:20:39 <openstack> Launchpad bug 1818569 in Manila "access rule apply races allow duplicates" [Undecided,New]
15:21:12 <tbarron> we have api races when applying access rules
15:21:25 <tbarron> I think this one is also a PTG topic
15:21:38 <tbarron> b/c the best way to fix it
15:21:43 * tbarron brainstorms
15:22:02 <tbarron> involves some ING DB states and locking around the transition to them
15:22:25 <tbarron> I think I made this point back when gouthamr was doing the last access rule changes
15:22:48 <tbarron> and people said that it might be true but didn't want to hold up all the other improvements he was making
15:23:16 <tbarron> so jgrosso i think this is MEDIUM at least and it's not goign to be a quick fix
15:23:17 <bswartz> Is the problem that the user asks for duplicate rules and we don't prevent it?
15:23:21 <tbarron> hope I'm wrong
15:23:28 <jgrosso> ok wil make a note this is PTG topic as well
15:23:28 <bswartz> Or that the user doesn't ask for it and we do it anyways?
15:23:44 <tbarron> bswartz: we try to prevent it but the prevenetion is subject to race problems
15:23:49 <tbarron> and doesn't always  work
15:23:56 <tbarron> so the real issue is the races
15:24:02 <tbarron> this is just one manifestation
15:24:22 <bswartz> I see
15:24:35 <tbarron> that's my *opinion* -- others should investigate and form their own
15:24:47 <tbarron> but I'm putting it as a PTG topic
15:25:04 <jgrosso> ok
15:25:12 <tbarron> if someone comes up with a clean fix that's simpler than what I'm thinking in the mean time then
15:25:21 <tbarron> I'd *love* to be wrong
15:25:31 <jgrosso> :)
15:25:55 <jgrosso> https://bugs.launchpad.net/manila-ui/+bug/1584145
15:25:56 <openstack> Launchpad bug 1584145 in manila-ui "Wrong handling of errors updating share type extra specs" [Medium,In progress]
15:26:18 <jgrosso> can some explain to me what we do with abandoned stuff :)
15:26:41 <jgrosso> I am on a mission to clean everything up
15:26:43 <jgrosso> :)
15:27:10 <vkmc> it gets back to the queue so other contributor can work on it?
15:27:17 <tbarron> yeah
15:27:34 <tbarron> this is an old bug report though and a lot has changed in horizon and manila-ui
15:27:49 <jgrosso> ok so we just leave it there?
15:28:05 <vkmc> yeah, somebody needs to verify what is the status for it
15:28:18 <tbarron> do we understand how to reproduce this?
15:28:22 <jgrosso> ok https://bugs.launchpad.net/python-manilaclient/+bug/1712835
15:28:23 <openstack> Launchpad bug 1712835 in python-manilaclient "shell client completion cache not working" [Undecided,In progress] - Assigned to Eric Harney (eharney)
15:28:37 <tbarron> jgrosso: so back to the other one
15:28:47 <jgrosso> oh ok
15:28:52 <tbarron> we need to get an owner to try and see if it's still valid
15:29:05 * tbarron thinks he sees vkmc waving her hand
15:29:15 <vkmc> \o)
15:29:17 <vkmc> (o/
15:29:28 <jgrosso> I will add a comment
15:29:30 <tbarron> awesome
15:29:43 <tbarron> jgrosso: assign to vkmc
15:29:50 <jgrosso> ok
15:30:01 <vkmc> just grabbed it
15:30:02 <tbarron> vkmc: it's perfectly fine if you can't reproduce to say that and close it
15:30:03 <vkmc> thanks jgrosso
15:30:14 <tbarron> vkmc thank you!
15:30:53 <vkmc> thanks tbarron!
15:31:19 * bswartz sneaks out of the room to his 10:30 meeting
15:31:26 <jgrosso> the next bug it looks fixed in Cinderclient
15:31:32 <tbarron> bswartz: see you later, thanks!
15:31:48 <tbarron> jgrosso: and it's in review in manila, right?
15:32:10 <jgrosso> yes
15:32:34 <jgrosso> ok sorry did not see that
15:32:35 <jgrosso> :)
15:32:52 <tbarron> jgrosso: i'd say the importance is LOW if you want to set that
15:32:58 <jgrosso> ok
15:33:11 <tbarron> it's a convenience
15:33:25 <jgrosso> got it
15:34:35 <jgrosso> https://bugs.launchpad.net/manila/+bug/1816939
15:34:36 <openstack> Launchpad bug 1816939 in Manila "Tempest test test_create_sg_and_share_specifying_az fails sporadically" [Undecided,New]
15:35:09 <jgrosso> reported by Goutham
15:35:49 <tbarron> looks like someone needs to investigate where the races are
15:35:53 <tbarron> in which service
15:36:28 <jgrosso> is this a dev or could QE help out ?
15:36:46 <tbarron> of course QE can help out
15:37:02 <jgrosso> ok I will assign it to me
15:37:04 <tbarron> there are no you're a DEV or you're a QE rules upstream
15:37:13 <tbarron> jgrosso: terrific
15:37:19 <jgrosso> great!
15:38:51 <jgrosso> sorry for the delay system is slow at home
15:39:05 <tbarron> no prob
15:40:37 <jgrosso> https://bugs.launchpad.net/manila/+bug/1811943
15:40:38 <openstack> Launchpad bug 1811943 in Manila "limit max share size" [Undecided,New]
15:41:17 <tbarron> this is a wishlist item
15:41:30 <tbarron> we can have it as a PTG topic
15:41:41 <jgrosso> ok
15:41:46 <jgrosso> how bout this https://bugs.launchpad.net/manila/+bug/1811336
15:41:48 <openstack> Launchpad bug 1811336 in Manila "Manila snapshot create method doesn't support "force" attribute" [Undecided,New]
15:42:36 <tbarron> we need someone to investigate it
15:43:16 <tbarron> does anyone kknow right off what 'force' is supposed to do when creating a snapshot?
15:43:50 <tbarron> jgrosso: maybe bring this one up again next week when we have more people here with
15:43:55 <tbarron> history in manila
15:43:59 <jgrosso> got it
15:44:15 <tbarron> bswart or ganso or gouthamr may know
15:44:32 <jgrosso> got it
15:45:04 <jgrosso> https://bugs.launchpad.net/manila/+bug/1804239
15:45:06 <openstack> Launchpad bug 1804239 in Manila "NetApp utilization metrics slow" [Undecided,New]
15:45:40 <tbarron> any netappers want to take this?
15:46:28 <tbarron> jgrosso: see if you can get ganso to take this one and
15:46:38 <tbarron> have his team work it
15:46:40 <tbarron> now that
15:46:44 <jgrosso> sounds good
15:46:49 <tbarron> the manage share servers stuff is merged
15:46:58 <jgrosso> ok I have one more
15:46:59 <jgrosso> https://bugs.launchpad.net/manila/+bug/1804208
15:47:01 <openstack> Launchpad bug 1804208 in Manila "scheduler falsely reports share service down" [High,New]
15:47:11 <jgrosso> its marked as High
15:48:13 <tbarron> well that's probably defensible
15:48:27 <tbarron> for big deployments like the reporter's
15:48:33 <tbarron> he's at SAP
15:48:43 <jgrosso> ahh
15:49:28 <lseki> netapper here o/, we'll decide between us regarding 1804239 who will work on it
15:49:28 <jgrosso> so your saying this can be expected in large deployments?
15:49:31 <tbarron> I don't see anyone raising their hands to say they'll work on it immediately so it will just be in our high prio baclog for now
15:49:44 <jgrosso> ok
15:49:59 <tbarron> lseki: awesome, would you assign it to yourself and then
15:50:08 <tbarron> re-assign as appropriate?
15:50:12 <jgrosso> lseki: thanks
15:50:20 <lseki> tbarron: sure, I will
15:50:28 <tbarron> lseki: thanks
15:51:34 <jgrosso> tbarron: that is all I have for now
15:51:44 <tbarron> jgrosso: cool, and thanks
15:51:51 <tbarron> #topic Open Discussion
15:51:53 <jgrosso> your welcome
15:52:30 * tbarron waits a couple minutes
15:53:47 <tbarron> OK, thanks everyone, let's go fix bugs!  See you on #oopenstack-manila!
15:53:54 <tbarron> #endmeeting