15:00:08 <bswartz> #startmeeting manila
15:00:14 <openstack> Meeting started Thu Aug 17 15:00:08 2017 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:17 <openstack> The meeting name has been set to 'manila'
15:00:23 <bswartz> hello all
15:00:24 <cknight> Hi
15:00:25 <ganso> hello
15:00:30 <zhongjun> Hi
15:00:32 <jprovazn> hi
15:00:36 <tbarron> hi
15:00:44 <xyang1> Hi
15:00:46 <dustins> \o
15:01:09 <raissa_> hi
15:01:26 <bswartz> vponomaryov toabctl markstur gouthamr: courtesy ping
15:01:51 <bswartz> #topic announcements
15:02:10 <bswartz> RC1 happened last week -- 1 day later than we'd aimed for
15:02:55 <bswartz> This week is R-2, so if any showstopper bugs are found, we have 2 weeks to fix them before the final release
15:03:14 <bswartz> so far I'm not aware of any critical bugs
15:03:34 <bswartz> I'm spending my time on addressing some issues for queens
15:04:00 <bswartz> which is actually a good segue into my only agenda item
15:04:09 <bswartz> #agenda https://wiki.openstack.org/wiki/Manila/Meetings
15:04:15 <bswartz> #topic PTG
15:04:24 <bswartz> #link https://etherpad.openstack.org/p/manila-ptg-queens
15:04:46 <bswartz> I created an etherpad for the PTG
15:04:55 <bswartz> and started adding topics
15:05:24 <bswartz> just a reminder that the Manila PTG will be a virtual event, and we agreed to hold it the week following the Denver event
15:05:50 <vkmc> o/
15:06:14 <bswartz> I expect some new things to come up in denver, and we can add them to our PTG agenda, but most of the stuff we should already know about now
15:06:36 <bswartz> so please go ahead and starting adding topics of your own
15:07:02 <bswartz> I am working on the stuff there with my name on it already
15:07:28 <bswartz> trying to take advantage of the relative quiet between RC1 and release
15:08:35 <bswartz> oops I just noticed the got the dates wrong on the etherpad and fixed them
15:08:44 <bswartz> :-[
15:09:19 <bswartz> nobody has anything on this topic?
15:09:31 * bswartz can tell it's going to be a short meeting
15:09:40 <bswartz> #topic open discussion
15:09:46 <bswartz> any other topics for today?
15:09:54 <bswartz> I saw tbarron pushing up all kinds of docs patches
15:09:56 <tbarron> need to think before we add stuff, for us Queens will be a stabilization release, much work in tripleo
15:10:16 <tbarron> b/c of 'containerized deployment', TLS everywhere, etc.
15:10:17 <bswartz> tbarron are you looking for reviews on those?
15:10:31 <tbarron> bswartz: I think they are close to being ready to merge
15:10:32 * bswartz likes the sound of TLS everywhere
15:10:51 <tbarron> and doesn't-happen-in-devstack bugs
15:11:07 <tbarron> like one dustin just found
15:11:11 <bswartz> link?
15:11:22 <tbarron> bswartz: he's got to file it
15:11:52 <bswartz> hey, if it works in devstack, then clearly any problems are user errors right?
15:11:52 <tbarron> on the doc subject, i need to do a bit more cleanup, they should be ready by the end of the week
15:12:19 <tbarron> if it's a user error to deploy on multiple nodes and fail over :D
15:12:31 * bswartz </sarcasm>
15:12:37 <toabctl> hi
15:12:37 <tbarron> bswartz: understood
15:13:09 <tbarron> bswartz: on the doc issue, do you know if we just get those into master or whether we need them in pike?
15:13:40 <bswartz> I don't know
15:13:49 <bswartz> and I'm not sure how we find out
15:14:03 <tbarron> bswartz: ok, I'll ask on #openstack-doc or something and get back to you
15:14:16 <bswartz> the relevant question is whether there are any automated build processes that pull docs content from stable branches and puts it up on docs.o.o
15:14:31 <tbarron> right
15:14:37 <bswartz> My expectation would be that the install guide would do that, but the rest of the guides would not
15:14:47 <bswartz> but my expectations are often wrong
15:15:27 <tbarron> also, like cinder, we are just importing tables for e.g. backend configuration options from openstack-manuals (before-migration tag)
15:15:38 <tbarron> and are not regenerating them dynamically
15:15:49 <tbarron> b/c it is not obvious how to do this
15:16:04 <tbarron> only cinder and manila have this issue so far as i can tell
15:16:10 <bswartz> hopefully the cinder guys have a plan to solve that which we can copy
15:16:12 <tbarron> because we have lots of driver config
15:16:18 * bswartz looks around for jungleboyj
15:16:22 <tbarron> neutron has drivers out of tree
15:16:31 <tbarron> bswartz: they don't yet
15:16:57 <tbarron> so we're likely to incur tech debt on that front
15:17:01 <bswartz> well I'll be in Denver and I can bug him about it
15:17:14 <jungleboyj> I am traveling today.
15:17:28 <bswartz> no worries jungleboyj
15:17:35 <tbarron> i'll probably ask on openstack-dev , tried in #openstack-doc but no results yet
15:17:55 <bswartz> the whole docs situation is just annoyingly subpar
15:18:00 <tbarron> on the reviews, the aim is just to get material imported and not introduce new problems
15:18:17 <bswartz> hopefully this is the last time we have to go through a "transition" with our documentation
15:18:25 <tbarron> so if I add a file (like a README) and something is wrong (or it should be removed) then -1
15:18:47 <tbarron> but don't -1 because of poor wording in the original file, fix it in a followup patch
15:18:59 <bswartz> yeah agreed
15:19:01 <tbarron> which can be submitted as soon as you want
15:19:11 <bswartz> it's more important to get the migration done
15:19:45 <bswartz> alright anything else for this week?
15:19:59 <jungleboyj> I think Doug Hellman had some code out there that was a proof-of-concept for how to do a dynamically. I haven't had a chance to take a look at it yet. Hope to do that after Queens opens up more.
15:20:40 <bswartz> thx jungleboyj, if dhellmann is working on it we'll definitely have a solution soon
15:20:49 <tbarron> jungleboyj: +1, pleasure working with you, and thanks for your help on this
15:21:14 <bswartz> I guess one last thing -- if anyone finds a critical bug that needs fixing in an RC2 release, please come hunt me down and let me know
15:21:27 <tbarron> we have warnings-as-error = 1 btw and the patches pass with it
15:21:33 <vkmc> READMES are just for the repo... right? shouldn't be included on the indexes
15:21:33 <bswartz> because I'll need to create an RC2 target in launchpad and target the bug
15:21:40 <vkmc> I was hesitant on reviewing it
15:22:06 <tbarron> vkmc: I'll probably just remove them, they were useful for the original change-layout patch
15:22:13 <jungleboyj> True. Glad to help out Tom. Always a pleasure to work with you as
15:22:28 <tbarron> but kinda interrupt the flow of reading for manila content
15:22:48 <tbarron> i'll leave them in any empty dirs if we have them
15:23:07 <bswartz> tbarron: they won't cause any web content to generate will they?
15:23:26 <bswartz> as long as they don't affect the build they're probably harmless
15:23:28 <tbarron> I get warnings (as errors) if I leave them un-indexed
15:23:43 <tbarron> there might be a way around that, I'm no sphinx expert
15:24:05 <bswartz> can the content be moved to a place where it doesn't make sphinx unhappy?
15:24:20 <bswartz> if it's just aimed at developers then some parent directory would probably work
15:24:28 <tbarron> probably
15:24:49 <tbarron> i think they were mostly just placeholders anyway though
15:24:55 <bswartz> k
15:25:15 <bswartz> alright I think we're done for today
15:25:19 <bswartz> see you next week
15:25:29 <bswartz> #endmeeting