15:00:49 <tbarron> #startmeeting manila
15:00:51 <openstack> Meeting started Thu Feb  7 15:00:49 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:52 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:54 <openstack> The meeting name has been set to 'manila'
15:00:57 <tbarron> ping ganso
15:00:58 <vkmc> o/
15:01:01 <gouthamr> o/
15:01:03 <ganso> hello
15:01:21 <tbarron> ping bswartz
15:01:25 <tbarron> ping amito
15:01:29 <tbarron> ping toabctl
15:01:36 <carthaca> Hello
15:01:38 <tbarron> ping xyang
15:01:50 <bswartz> .o/
15:01:54 <tbarron> ping erlon
15:01:58 <tbarron> ping tpsilva
15:02:21 <tbarron> Hi all!
15:02:39 <tbarron> #topic Announcements
15:03:03 <tbarron> I don't really have any except schedule stuff, which is our next topic.
15:03:10 <tbarron> Anyone else have some?
15:03:22 <tbarron> 3
15:03:28 <tbarron> 2
15:03:30 <amito> hey o/
15:03:51 * tbarron pretends not to notice amito coming in
15:03:53 <tbarron> 1
15:04:01 <tbarron> #topic Schedule reminders
15:04:03 <gouthamr> #LINK https://wiki.openstack.org/wiki/Manila/Meetings
15:04:11 <bswartz> Only 3 minutes late isn't terrible
15:04:17 <tbarron> gouthamr: thanks!
15:04:28 <amito> sorry :P
15:04:40 <tbarron> bswartz: and he's usually driving home about now too ...
15:04:52 <tbarron> amito: not a problem, I'm just messing with you
15:05:16 <tbarron> so as a reminder, here is the Stein schedule:
15:05:30 <tbarron> #link https://releases.openstack.org/stein/schedule.html
15:05:49 <tbarron> Of note: feature proposal freeze is 21 February.
15:06:26 <tbarron> code for new features should be posted in gerrit with unit tests passing
15:06:47 <tbarron> Then Feature Freeze and client library freeze are 7 March.
15:07:22 <tbarron> There is no guarantee that your feature will be merged just because you make these deadlines, but if you don't
15:07:27 <tbarron> well you know the rest.
15:07:46 <tbarron> And as I was discussing with some folks earlier in #openstack-manila, your
15:07:58 <tbarron> odds are better if you can get review eyeballs early.
15:08:17 <tbarron> Put your work up, get review eyeballs on it early.
15:08:34 <tbarron> Ideally break it into relatively managable reviews.
15:09:22 <tbarron> We don't have a lot of reviewer bandwidth so if you wait till deadlines and drop one huge review then it's tougher to get the job done.
15:09:33 <tbarron> questions?  comments?
15:10:10 <tbarron> Also please remember that reciprocity makes openstack go around.
15:10:31 <tbarron> When you *do* reviews people want to review your own submissions.
15:10:31 <toabctl> hi
15:10:39 <tbarron> toabctl: Hi!
15:10:56 <tbarron> k, nuf said I guess
15:11:07 <tbarron> #topic Bugs
15:11:26 <tbarron> jgrosso is on PTO today but I want to call attention to an email
15:11:37 <tbarron> he sent to #openstack-discuss recently
15:11:58 <tbarron> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002404.html
15:12:41 <tbarron> We're lucky to have a bug czar who brings brand new energy and "beginner's mind" to our bug backlog
15:12:55 <tbarron> Please read this email and respond.
15:13:18 <tbarron> gouthamr: I see you replied already and I know you worked a little bit
15:13:20 <tbarron> :)
15:13:27 <tbarron> with jgrosso on this
15:13:35 <bswartz> What is the purpose of the discuss ML?
15:13:39 <bswartz> I don't subscribe to it
15:13:41 <tbarron> do you have anything to say?
15:13:49 <tbarron> bswartz: it is everything now!
15:13:55 <tbarron> no more dev list
15:13:56 <toabctl> bswartz, discuss is the replacement of dev
15:14:01 <bswartz> Oh...
15:14:06 * bswartz missed the memo
15:14:08 <tbarron> it replaces dev, ops, etc.
15:14:19 <toabctl> bswartz, there is *only* discuss now. no dev, no ops, no docs, no infa, ...
15:14:26 * tbarron reminds himself to cover changes like that in this meeting
15:14:30 <bswartz> Did my subscription automatically migrate over?
15:14:34 <toabctl> no
15:14:58 <bswartz> Ok
15:15:00 * gouthamr slaps bswartz with a large trout
15:15:07 <gouthamr> \m/
15:15:08 <tbarron> bswartz: we forgot to tell fungi to ping you about it personally on irc b/c you have too much email to read it
15:15:09 * bswartz sticks tongue out at gouthamr
15:15:42 <bswartz> Okay cool
15:16:12 <tbarron> gouthamr: did you have anything you wanted to say about the email thread or should we just carry forward
15:16:23 <tbarron> this topic to next week's meeting
15:17:16 <gouthamr> tbarron: nothing more
15:17:21 <tbarron> gouthamr: k
15:17:32 <gouthamr> tbarron: we can discuss the initial bug triage when jason's around
15:17:47 <tbarron> #topic tracking our work
15:17:57 <tbarron> #link https://wiki.openstack.org/wiki/Manila/SteinCycle
15:18:05 <tbarron> please take a look
15:18:32 <tbarron> First section is work associated with approved specs for stein
15:18:34 <fungi> tbarron: bswartz: i sent numerous announcements to the old dev ml before it was eventually deleted
15:18:41 <fungi> over the course of months
15:18:47 <tbarron> fungi: we know :)
15:19:11 <tbarron> fungi: sorry to raise you -- we were just giving some folks @#$@4 for not knowing
15:19:30 <fungi> okay, just making sure. if anyone has ideas for how to more effectively reach subscribers of a mailing list rather than sending e-mail to that mailing list, i'm interested to hear them ;)
15:19:48 <fungi> er, other than
15:19:52 <tbarron> fungi: people will suggest #slack :)
15:20:12 <tbarron> or worse
15:20:20 <fungi> touché
15:20:41 <tbarron> fungi: the zorillas aren't really complaining
15:20:53 <bswartz> fungi: if it didn't say [manila] it was autodeleted -- my fault for aggressive filtering
15:21:04 <tbarron> ok, back on topic
15:21:14 <fungi> no worries
15:21:31 <tbarron> I've marked each of the work items associated with approved specs red, yellow, or green.
15:22:07 <tbarron> depening on whether they are likely not to make it in this cycle, in the middle, or in good shape
15:22:32 <tbarron> If you disagree with any of these markers let me know!
15:23:02 <ganso> tbarron: can one item that is already yellow become green? :)
15:23:17 <bswartz> What does the yellow in the py3 section indicate?
15:23:20 <tbarron> ganso: yes, it can, when it's ready
15:23:34 <tbarron> bswartz: that we've done some of the work but not enough
15:23:50 <bswartz> Please not slack for openstack. Slack is terrible
15:24:07 <tbarron> bswartz: I want us to get the lvm job and some of the dhss=true jobs with real back ends running tempest with py3
15:24:19 <tbarron> otherwise I don't think we have sufficient coverage
15:24:41 <tbarron> Also I haven't heard that any of the third party jobs are running with py3
15:24:48 <tbarron> And grenade is still py2
15:24:58 <tbarron> bswartz: make sense?
15:24:58 <bswartz> ganso: are we moving our CI to py3?
15:25:13 <ganso> bswartz: we are in progress of moving
15:25:24 <tbarron> ganso: that's good news
15:25:55 <tbarron> This is a wiki so I'm not supposed to be the only updater.
15:26:09 <tbarron> gouthamr just updated the active-active section with tasks
15:26:24 <tbarron> amito has promised an update to the sdk section
15:26:37 <bswartz> On systems I administer, python2 is symlinked to a shellscript that writes a message to syslog at level LOG_EMERG, lowers your disk quota by 10%, and runs python3
15:26:39 <amito> I posted an update yesterday
15:26:51 <tbarron> amito: awesome, thx
15:27:02 <tbarron> gouthamr updated the osc section
15:27:46 <gouthamr> bswartz: :D haha, okay, i'd add a smug/sad smiley and also "P.S: you're what's wrong to the world"
15:27:51 <tbarron> vkmc - looks like you updated uwsgi and UI
15:28:12 <tbarron> e0ne: thanks for your help with UI testing ^^^
15:28:32 <e0ne> tbarron: hi. you're welcome!
15:28:42 <tbarron> bswartz: that's awesome!
15:29:25 <tbarron> I'll mention also that the os-ansible folks are making good progress on a manila role there
15:29:36 <tbarron> first iteration will deploy manila with lvm back end
15:31:06 <tbarron> Lots of these areas have owner/coordinators who have defined some tasks to do but
15:31:21 <tbarron> that does not mean they are doing the whole thing themselves.
15:31:41 <tbarron> So if you have any interest in helping even with a small piece please do step up.
15:32:06 <tbarron> That's all I have on this one today.  Anyone else?
15:32:23 <e0ne> tbarron: FYI, I failed to setup tls proxy with manila on gates, so I disabled it in my patch
15:32:50 <tbarron> e0ne: kk
15:33:01 <tbarron> e0ne: one step at a time :)
15:33:07 <e0ne> :)
15:33:38 <bswartz> What's tlsproxy for?
15:33:38 <tbarron> e0ne: do you want to briefly tell folks what your change does? or if you are busy with midcycle that's ok too
15:34:06 <e0ne> bswartz: it's to enable  ssl/https for endpoints
15:34:26 <e0ne> I pushed small patch to test manila-ui with the current horizon
15:34:35 <bswartz> Oh you mean do the HTTPS stuff outside of the server?
15:34:38 <bswartz> Ok
15:34:54 <e0ne> the jobs setups devstack environment with manila and manila-ui
15:35:14 <e0ne> I added a few simple tests to verify that manila ui could be opend
15:35:34 <e0ne> these tests are based on horizon selenium integration tests
15:35:55 <e0ne> it's up to you if you want to add more tests
15:35:55 <tbarron> should help us with issues like those we had b/c our plugin was using private unstable "interfaces" (not) in horizon and we broke
15:36:24 <vkmc_> right now its the gate and the horizon selenium suite, right?
15:36:40 <e0ne> tbarron: I'll add this job to horizon experimental queue letter
15:36:51 <e0ne> vkmc_: correct
15:36:53 <tbarron> e0ne: nice, thanks
15:37:06 <vkmc_> cool
15:37:18 <e0ne> so, it will be some kind of verification that plugins are working with a current horizon
15:37:38 <e0ne> #link https://review.openstack.org/635112
15:39:09 <tbarron> e0ne: thanks again!
15:39:39 <tbarron> we have quite a bit of work to do with our plugin, it's quite behind the api and the client on microversions
15:39:53 <tbarron> and we need to build on what e0ne has put in place
15:40:08 <vkmc_> e0ne++
15:40:28 <tbarron> so get your django liking friends over here, it's fun to be a zorilla!
15:40:48 <tbarron> I think we're ready for
15:40:54 <tbarron> #topic Open discussion
15:41:36 <tbarron> talkative bunch today ...
15:42:11 <tbarron> OK, let's pick up here again next week.  Thanks everyone!
15:42:15 <tbarron> #endmeeting