15:00:53 <tbarron> #startmeeting manila
15:00:54 <openstack> Meeting started Thu Feb 21 15:00:53 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:55 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:57 <openstack> The meeting name has been set to 'manila'
15:01:02 <tbarron> ping ganso
15:01:07 <tbarron> ping erlon
15:01:09 <ganso> hello
15:01:14 <tbarron> ping gouthamr
15:01:14 <gouthamr> o/
15:01:17 <tbarron> ping vkmc
15:01:23 <erlon_> hey
15:01:28 <tbarron> ping xyang
15:01:36 <tbarron> ping toabctl
15:01:44 <tbarron> ping tpsilva
15:01:48 <tbarron> ping amito
15:01:52 <vkmc> o/
15:02:03 <tbarron> bswartz has a conflict today
15:02:05 <carthaca> Hello
15:02:12 <tbarron> carthaca: hi!
15:02:25 * tbarron waits a couple minutes
15:02:52 <xyang> hi
15:04:00 <tbarron> ok let's get started
15:04:04 <tbarron> hi all!
15:04:21 <tbarron> Agenda: https://wiki.openstack.org/wiki/Manila/Meetings
15:04:41 <tbarron> if you add to it ping me so I refresh :)
15:04:50 <tbarron> #topic announcements
15:05:05 <tbarron> It's Technical Committee election time
15:05:29 <tbarron> There are threads on openstack-discuss with questions for the candidates
15:05:55 <tbarron> As OpenStack matures and moves into the more general world of Open Infrastructure there
15:06:13 <tbarron> are lots of important issues for the Technical Committee
15:06:40 <tbarron> so I encourage people to read the threads, participate, vote,, and follow up with the TC going
15:06:48 <tbarron> forwards on its work
15:07:06 <tbarron> We are working to position manila  as a vital project
15:07:41 <tbarron> both within OpenStack and in  the larger world outside it and interaction with TC will be there :)
15:08:11 <tbarron> The only other announcements I have are w.r.t. schedule, which is its own topic
15:08:20 <tbarron> Anyone else have announcements?
15:08:33 <carthaca> I want to let you know some personal information, if this is the right place.
15:08:45 <tbarron> carthaca: yes
15:08:45 <carthaca> In order to prevent you thinking: 'what happened to that SAP guy?'
15:08:49 <carthaca> Next week my family name will change from Schreiber to Escher.
15:09:18 <carthaca> And more dramatically I will stop doing manila work for this year soon, but care for my to be born offspring instead :)
15:09:34 <carthaca> I have a SAP internal successor, but I don't know when he will be at the point to start making upstream contributions..
15:09:57 <gouthamr> carthaca: Congratulations :)
15:10:02 <carthaca> Anyway I will return next year, and most likely I will return to manila as well.
15:10:05 <tbarron> carthaca: congratulations!!
15:10:12 <carthaca> thanks :)
15:10:25 <ganso> carthaca: congrats!
15:10:33 <tbarron> carthaca: we will welcome you back enthusiastically, you make great contributions.
15:10:55 <tbarron> carthaca: does your middle name begin with the letter 'C'?
15:11:12 <carthaca> no, but my nick does :D
15:11:15 * tbarron hopes to get M C Escher working on manila soon
15:11:51 <carthaca> Maurice Carthaca Escher will be at your service
15:12:00 <tbarron> https://www.mcescher.com/
15:12:12 <tbarron> carthaca: awesome, and thanks for sharing the news
15:12:21 <tbarron> Any other announcements?
15:12:52 <tbarron> #topic Schedule reminders
15:13:14 <tbarron> Feature Proposal Freeze is today.
15:13:35 <tbarron> "All new Manila features must be proposed and substantially complete, with unit tests by 21 February 2019 (23:59 UTC)."
15:14:01 <tbarron> Anyone have any features to propsose for whom that deadline is a problem?
15:14:21 <ganso> tbarron: our testing patch isn't passing CI yet
15:14:28 <ganso> tbarron: for manage-unmanage
15:14:39 <tbarron> ganso: that's ok, you have good unit test coverage
15:14:44 <ganso> tbarron: we are trying to get it fixed until midnight today
15:15:03 <ganso> tbarron: I meant functional tests #LINK https://review.openstack.org/#/c/638231
15:15:04 <tbarron> ganso: that's great but it's not required by this deadline
15:15:29 <tbarron> good idea anyways though, so pretend it's the deadline for functional tests too :)
15:15:30 <ganso> tbarron: great! I can go to bed slightly earlier tonight then haha
15:15:39 <ganso> tbarron: noooooooooooooooooooooo
15:15:57 <tbarron> ganso: it's all good ...
15:16:04 <ganso> tbarron: thanks =)
15:16:30 <tbarron> the *next* deadline is 7 March, feature freeze itself
15:16:53 <tbarron> so we need to get reviews done, tempest tests done and passing, and  merge by then
15:17:16 <tbarron> ganso: so get good sleep tonight so you can sprint fast tomorrow
15:17:26 <ganso> tbarron: =D
15:17:31 <tbarron> Anything else on schedule?
15:17:43 <tbarron> on the schedule topic, that is?
15:18:07 <tbarron> #topic tracking our work
15:18:22 <tbarron> #link All new Manila features must be proposed and substantially complete, with unit tests by 21 February 2019 (23:59 UTC).
15:18:27 <tbarron> woops
15:19:03 <tbarron> #link https://wiki.openstack.org/wiki/Manila/SteinCycle
15:19:21 <tbarron> you just never know what might be in your paste buffer :)
15:19:33 <tbarron> we just hit on one of the big ones here
15:19:45 <tbarron> we need review eyes on
15:20:01 <tbarron> #link https://review.openstack.org/#/q/topic:bp/manage-unmanage-with-share-servers+(status:open+OR+status:merged)
15:20:34 <tbarron> i'll be reviewing the container-driver patches today and then move to the core stuff
15:20:54 <ganso> tbarron: I gotta fix the topics, again
15:20:56 <tbarron> when I've got devstack working with container back end so that I can exercise it
15:20:57 <ganso> tbarron:  just a minute
15:21:20 <tbarron> carthaca: in your copious free time maybe take a look at the netapp patch in this series
15:21:26 <ganso> link https://review.openstack.org/#/q/topic:manage-unmanage-with-share-servers+(status:open+OR+status:merged)
15:21:47 <tbarron> carthaca: make sure SAP will still function in your absence after ganso does his thing
15:22:10 <tbarron> ganso: thanks for updating
15:22:35 <tbarron> Other work for this cycle that would be impacted by the 7 March deadline?
15:22:55 <tbarron> vkmc: uwsgi work seems to be progressing well
15:23:33 <tbarron> we can make progress on python3  functional jobs and stuff like osc client past that deadline
15:23:41 <erlon_> https://review.openstack.org/#/q/author:*%2540netapp.com+status:open+(project:openstack/manila+OR+project:openstack/manila-tempest-plugin+)
15:24:01 <ganso> I updated the topic for the patches, if you refresh the link above it should show a total of 7 patchess
15:24:36 <tbarron> erlon_ ganso -- thanks
15:25:37 <tbarron> I want to thank vkmc and enriquetasso for getting a lot of interest in manila from outreachy applicants
15:26:01 <tbarron> our hope is to get some outreachy folks working on the osc client for manila
15:26:04 <vkmc> :D
15:26:38 <tbarron> so if you see outreachy folks trying to figure out what to do in our channel do say hi and
15:26:56 <tbarron> facilitate getting them in touch with people who can help
15:27:13 <tbarron> vkmc: any advice on this topic?
15:28:02 <vkmc> sure... so, newcomers in this case may not have background on open source tools and processes... so try to be patient
15:28:33 <s0ru> :)
15:28:39 <vkmc> if they make questions that are not strictly related to manila, redirect them to #openstack-outreachy
15:28:50 <tbarron> s0ru: welcome!
15:28:55 <vkmc> if they make questions about manila... well, you know manila so you will be able to help them out
15:29:05 <tbarron> vkmc: perfect
15:29:12 <s0ru> o/ thanks!
15:29:20 <vkmc> if they ask you questions on private messages, tell them to ask here... they might not have netiquette and they might not know that usually asking in the open is better
15:29:44 <tbarron> also, remind people that we may not be in the same timezone but that lots of us have bouncers and will see the question later
15:29:59 <vkmc> and I think.. that's enough for tips today... let me or enriquetaso know if you have any question wrt the program
15:30:02 <tbarron> so they should stay in channel and not be frustrated by lack of immediate response.
15:30:06 <vkmc> yes, that's a good one tbarron
15:30:07 <tbarron> vkmc: thanks!
15:30:27 <tbarron> #topic Bugs
15:30:41 <tbarron> jgrosso is in Florida, poor man
15:30:52 <tbarron> but gouthamr may have some for us?
15:31:17 <gouthamr> there aren't any new/pressing ones that folks haven't looked at this week
15:31:25 <tbarron> he can at least tell us about manila tls ports though
15:31:32 <gouthamr> #link: https://bugs.launchpad.net/manila/+bug/1816640
15:31:34 <openstack> Launchpad bug 1816640 in Manila "[NetApp driver] Race condition between setup_server and teardown" [Undecided,New]
15:31:56 <gouthamr> ganso, i suppose you can triage and assign an owner on that? ^
15:32:02 <ganso> we have colleages working on that in parallel
15:32:27 <ganso> sure, I can change the status to triage, we've already had
15:32:37 <ganso> s/had/triaged
15:33:02 <gouthamr> ganso: sure.. thanks
15:33:08 <tbarron> ganso: and if there's someone working it maybe assign owner
15:33:23 <gouthamr> #link https://bugs.launchpad.net/manila/+bug/1815038
15:33:24 <openstack> Launchpad bug 1815038 in Manila "API is not reachable if manila is deployed with uWSGI and mounted in /share" [Medium,In progress] - Assigned to Victoria Martinez de la Cruz (vkmc)
15:33:30 <tbarron> ganso: and target for Stein3 if appropriate
15:33:49 <gouthamr> ^ this has a fix, but needs reviews
15:33:51 <gouthamr> #link: https://review.openstack.org/637057
15:34:42 <gouthamr> please review :) ^
15:34:56 <gouthamr> #link https://bugs.launchpad.net/manila/+bug/1806576
15:34:57 <openstack> Launchpad bug 1806576 in Manila "ERROR rabbitmq error code 108" [Undecided,New]
15:35:19 <tbarron> gouthamr: I need to look at that one, have shirked
15:35:30 <tbarron> gouthamr: see if I can reproduce
15:35:54 <gouthamr> "108, 'error in stat: /_nogroup/a746281c-66a9-453b-875f-033a60efa956: error code 108'"
15:36:14 <gouthamr> tbarron: should we change the title of the bug?
15:36:19 <tbarron> yes
15:36:38 <tbarron> but I need to understand better what the real problem is, do you?
15:37:01 <gouthamr> tbarron: nope, it looks like a problem with the "stat" call in the cephfs driver
15:37:24 <tbarron> ceph volume client can't make backing volume for manila share
15:37:26 <tbarron> perhaps
15:37:36 <tbarron> I suspect a ceph version mismatch
15:38:06 <tbarron> I put this on my todo list and took ownership of the bug
15:38:20 <tbarron> you or jgrosso can "bug" me about it next week
15:38:25 <gouthamr> tbarron: nice, ty.. i updated the title now..
15:38:33 <gouthamr> #link https://bugs.launchpad.net/manila/+bug/1811680
15:38:34 <openstack> Launchpad bug 1811680 in Manila "Manila allows share type deletion despite quota allocations" [Medium,New]
15:39:53 <tbarron> it seems like the foreign key checking on db purge didn't get updated when per-share-type quotas were introduced?
15:40:15 <gouthamr> could be..
15:40:57 <tbarron> but arnewielback is suggesting an api-time check on share-type-delete iiuc
15:40:58 <gouthamr> we might have not linked the quota and share type tables because quotas are meant to be free form
15:41:25 <gouthamr> i.e, you can set them against users and projects that manila doesn't really know about/manage
15:41:40 <gouthamr> so, we might have made the same assumption about share types
15:42:07 <gouthamr> that's my theory though, wonder how volume type quotas and volume type deletion is handled in cinder
15:42:33 <tbarron> yeah
15:43:18 <tbarron> oh, so you can *soft* delete them but can't purge them
15:43:45 <tbarron> arne would like to prevent the delete if you can't purge
15:44:36 <tbarron> i wonder if we have this situation for other resources
15:45:24 <gouthamr> ah, true..
15:45:53 <gouthamr> we need someone to look at this and reproduce it
15:46:26 <gouthamr> any volunteers?
15:47:06 <tbarron> note that one could implement #b in the near term and look at the deeper isue later
15:47:45 <gouthamr> *crickets* :)
15:47:46 <gouthamr> alright, we'll see if anyone picks it up, we can bring this up again...
15:47:46 <gouthamr> # link: https://bugs.launchpad.net/manila/+bug/1816420
15:47:47 <openstack> Launchpad bug 1816420 in Manila "[ceph-nfs-ganesha] Allow 'cephx' access to a NFS share type" [Undecided,New]
15:48:06 <tbarron> gouthamr: I don't see any volunteers right now, let's bubble this one up again when jgroso has his "system" going
15:48:18 <gouthamr> tbarron: ack
15:48:41 <tbarron> gouthamr: I can tak e that one
15:49:06 <gouthamr> cephfs <3 tbarron
15:49:59 <gouthamr> # link https://bugs.launchpad.net/manila/+bug/1816646
15:50:00 <openstack> Launchpad bug 1816646 in Manila "Infinidat driver fails pylint" [Undecided,New]
15:50:19 <gouthamr> amito: are you okay with me assigning that to you?
15:50:26 <amito> yes,
15:50:33 <gouthamr> amito: ty, done..
15:50:39 <amito> however, someone else from my team might do it, if that's the case I'll re-assign it.
15:51:01 <gouthamr> amito: sure thing
15:51:41 <amito> gouthamr: there's a simple solution to the 'capacity' issue, we implemented it in our Cinder driver before. I believe we'll solve it in the next few days.
15:52:25 <tbarron> amito: nice
15:53:21 <gouthamr> amito: my theory is that you can directly replace it's usage with oslo_utils.units
15:53:21 <gouthamr> amito: i couldn't find the source code to confirm...
15:53:21 <gouthamr> tbarron: okay, that's all from the the top of the stack
15:53:33 <tbarron> gouthamr: thanks!
15:53:40 <tbarron> #topic open discussion
15:54:22 <tbarron> Alright, see y'all on #openstack-manila
15:54:26 <tbarron> Thanks everyone!
15:54:31 <tbarron> #endmeeting