15:00:46 <bswartz> #startmeeting manila
15:00:47 <openstack> Meeting started Thu Mar 26 15:00:46 2015 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:50 <openstack> The meeting name has been set to 'manila'
15:00:51 <bswartz> lol
15:00:54 <lpabon> o/
15:00:57 <xyang2> hi
15:01:04 <bswartz> hey guys
15:01:15 <bswartz> I'm running this meeting from a bus on my cellphone
15:01:22 <vponomaryov> nice =)
15:01:24 <bswartz> so I might get dropped
15:01:29 <lpabon> wonders of the internet
15:01:33 <bswartz> this is just in case I get lost
15:01:49 <bswartz> #chairs cknight
15:01:57 <bswartz> #chair cknight
15:01:57 <openstack> Current chairs: bswartz cknight
15:02:09 <bswartz> cknight takeover if I get dropped
15:02:13 <cknight> bswartz: ok
15:02:20 <bswartz> #agenda https://wiki.openstack.org/wiki/Manila/Meetings
15:02:34 <bswartz> #topic Kilo-RC1 status
15:02:51 <bswartz> #link https://launchpad.net/manila/+milestone/kilo-rc1
15:03:12 <bswartz> so we still have a bunch of open bugs
15:03:30 <cknight> bswartz: I have several bugs in progress that should be targeted to RC1
15:03:33 <bswartz> we've got about 1 more week before we start kicking non-essential bugs out of the release
15:03:53 <bswartz> cknight can you email me a list and I'll target them when my plane lands?
15:03:59 <cknight> bswartz: yes
15:04:03 <xyang2> bswartz: when are you planning to cut RC1
15:04:19 <bswartz> xyang2: the target is next week, but that's a soft target
15:04:30 <bswartz> we will have to judge based on the bugs that are still open
15:04:38 <bswartz> we will hold the RC for a critical bug
15:05:04 <bswartz> non-critical bugs will simply get retargetted to liberty though
15:05:19 <bswartz> so don't wait to get bugfixes in
15:05:31 <cknight> xyang2: will your team be fixing https://bugs.launchpad.net/bugs/1434817 ?
15:05:32 <openstack> Launchpad bug 1434817 in Manila "EMC VNX driver should return CIFS export with with backslashes" [Medium,In progress] - Assigned to Ben Swartzlander (bswartz)
15:05:45 <xyang2> cknight: we can
15:05:47 <bswartz> xyang2: I have  fix for it, but my management won't let me submit it
15:05:57 <xyang2> bswartz: :(
15:06:01 <bswartz> that's a funny story
15:06:05 <xyang2> bswartz: we can do it
15:06:15 <bswartz> xyang2: go ahead and fix it yourself -- it's fine with me
15:06:26 <xyang2> bswartz: I thought you are doing it so I didn't take it
15:06:34 <xyang2> bswartz: ok
15:06:35 <bswartz> yeah I thought I was too
15:06:45 <vponomaryov> bswartz: what about the one about generic CIFS fix?
15:06:54 <bswartz> that fix should be submitted soon
15:07:05 <vponomaryov> ok
15:07:05 <bswartz> in fact I don't know what's holding it up
15:07:10 <bswartz> when my plane lands I'll look into it
15:07:39 <bswartz> my vacation is just ending so I'll be getting caught up on stuff that I ignored last few days
15:07:48 <toabctl> hi
15:08:11 <bswartz> any quesitons about RC1?
15:08:23 <bswartz> or open bugs?
15:08:36 <bswartz> I'll review everything in the queue soon
15:08:58 <bswartz> #topic open discussion
15:09:04 <bswartz> so that was the only "topic" I had for today
15:09:05 <cknight> I'd encourage everyone with multi-share-server drivers to test the new network plug-ins.
15:09:11 <bswartz> oh except 1 announcement
15:09:15 <lpabon> of all the bugs, i only see one high that is in progress
15:09:21 <lpabon> most have fixes commited
15:09:25 <bswartz> welcome u_glide to the manila core team!
15:09:37 <vponomaryov> for all: We have fork Horizon with support of latest Manila: #link https://github.com/NetApp/horizon/tree/manila_kilo , if some issues found, please file them at #link https://github.com/NetApp/horizon/issues/
15:09:38 <xyang2> congrats u_glide!
15:09:59 <bswartz> also some previews
15:10:12 <bswartz> in the next weeks we'll start to talk about vancouver design summit topics
15:10:19 <markstur> congrats Igor
15:10:33 <bswartz> and I'll present my plan for vendor CI
15:10:49 <bswartz> the CI discussion should be extra interesting given the recent events in the cinder project
15:10:57 <xyang2> vponomaryov: why is that only under NetApp github?
15:11:12 <lpabon> ^^ and why fork?
15:11:22 <vponomaryov> xyang2: it is temporary solution
15:11:28 <bswartz> xyang2: that's where it's been in the past, and it's a fork lpabon because we didn't have another option
15:11:38 <lpabon> weird
15:11:41 <bswartz> starting in liberty horizon will offer a real plugin solution we can use
15:11:49 <lpabon> ah
15:11:51 <gary-smith_> work on that is underway :-)
15:11:52 <xyang2> bswartz: I thought it was some other location, but I haven't tried with horizon for a while
15:11:58 <bswartz> so the netapp github repo approach will die with kilo
15:12:01 <cknight> bswartz: will it be ready for us to use in Liberty?
15:12:11 <cknight> bswartz: or ready by the end of Liberty?
15:12:21 <bswartz> cknight: hopefully early -- maybe not day 1
15:12:29 <gary-smith_> bswartz: +1
15:12:43 <markstur> 1+1 = day 2?
15:12:51 <lpabon> ok, just my question on bugs.. looks like only one HIGH bug is in progress and others are in gerrit... should we be looking adt medium bugs also?
15:12:54 <bswartz> we can hope
15:12:59 <david-lyle> plugin mechanism in horizon currently exists, since late juno, been improving since then
15:13:08 <cknight> lpabon: yes, let's fix everything we can
15:13:15 <lpabon> cknight: cool
15:13:26 <david-lyle> just moving to have projects use it rather than fully integrating into the horizon source tree
15:13:46 <bswartz> david-lyle: thanks
15:14:09 * david-lyle goes back to lurking
15:14:11 <lpabon> Another question:  Bug https://bugs.launchpad.net/manila/+bug/1434076 is medium but the patch is on hold
15:14:11 <openstack> Launchpad bug 1434076 in Manila "requires ddt >= 0.7.0" [Medium,Confirmed]
15:14:54 <lpabon> should it be lower than medium? moved to liberty-1?
15:15:08 <bswartz> vponomaryov: ?
15:15:11 <bswartz> you're the ddt expert
15:15:21 <vponomaryov> bswartz: it is only about tests
15:15:22 <lpabon> this is just an example, i'm just trying to gage what goes into RC1
15:15:33 <vponomaryov> bswartz: nothing critical, no relation to production at all
15:15:46 <vponomaryov> bswartz: so, we can wait with it to liberty
15:15:51 <bswartz> lpabon: for the next week we can accept any bug fix that's low risk
15:16:00 <lpabon> cool thanks
15:16:19 <bswartz> we will tighten starting next Thursday and starting kicking out stuff that hasn't merged
15:16:35 <xyang2> bswartz: about the summit, will you be able to join remotely?
15:16:50 <bswartz> xyang2: that depends on my unborn daughter
15:16:55 <bswartz> I will definitely try
15:17:02 <xyang2> bswartz: :)
15:17:10 <cknight> bswartz: +1
15:17:15 <bswartz> but if she decides to be born and an inconvenient time then I'm out of luck
15:17:24 <lpabon> bswartz: congratulations!
15:17:36 <bswartz> lpabon: ty
15:17:40 <markstur> baby Liberty!
15:17:47 <bswartz> lol
15:17:52 <bswartz> that name is _not_ on the list
15:18:00 <markstur> better than Lizard
15:18:12 <cknight> markstur: :-)
15:18:15 <xyang2> bswartz: maybe a nick name:)
15:18:51 <bswartz> okay so we might be able to cut this meeting short
15:18:57 <bswartz> unless anyone has something else to discuss
15:19:10 <markstur> Will Manila docs get into official docs for Kilo?
15:19:14 <vponomaryov> bswartz; csaba's changes?
15:19:16 <mkoderer> I will push a new version of the scenario test soon
15:19:24 <mkoderer> I hope it will be finished today :)
15:19:25 <bswartz> vponomaryov: link?
15:19:44 <csaba> yes I just wanted to ask that ..
15:19:50 <vponomaryov> bswartz: #link https://review.openstack.org/162542
15:20:03 <bswartz> markstur: good question -- I think no but I will double check
15:20:25 <markstur> that's what I thought.  Would be a good goal for Liberty if we can't somehow do it sooner
15:21:01 <bswartz> yikes! +518, -439
15:21:44 <bswartz> so on the plus side the impact is contained to the glusterfs driver
15:21:51 <bswartz> but it's a big change
15:22:05 <bswartz> and without actually reviewing it right now it sounds like a new feature is being added
15:22:15 <bswartz> is that the concern>
15:23:09 <bswartz> did my wireless drop?
15:23:15 <lpabon> no
15:23:18 <csaba> no
15:23:35 <bswartz> I'll take a closer look
15:23:47 <lpabon> csaba what would be the result of not having this fix?
15:24:00 <vponomaryov> lpabon: maturity
15:24:19 <vponomaryov> lpabon: kind of
15:24:19 <markstur> I removed my -1.  That was mainly a question of FFE.  Not sure about the other -1 and discussions.
15:24:26 <bswartz> csaba we'll need to know the risks of not fixing this vs the risks of fixing this in kilo
15:24:28 <lpabon> vponomaryov: yeah, i agree, but I mean what would be the impact to glusterfs w/o the fix
15:24:50 <csaba> having gluster-native at PoC quality..
15:25:10 <bswartz> if others feel that this is a new feature, then csaba should formally request a FFE and we can handle it that way
15:25:39 <bswartz> csaba: FFE requests go to the ML
15:25:59 <bswartz> I'll make this change top priority after I land
15:26:12 <csaba> bswartz: yes I know the procedure
15:26:17 <bswartz> okay
15:26:18 <xyang2> bswartz: does it need a bp as well?
15:26:35 <vponomaryov> xyang2: =)
15:26:40 <bswartz> make sure you justify it with a statement of risks of not fixing it
15:26:47 <bswartz> no there's no point
15:26:58 <bswartz> BPs are just for tracking and if we have a bug to track it then it's okay
15:27:11 <xyang2> right now it doesn't have a bp nor a bug fix
15:27:15 <bswartz> !!!
15:27:16 <openstack> bswartz: Error: "!!" is not a valid command.
15:27:18 <csaba> bswartz: is there a conventional subject format for FFEs?
15:27:21 <bswartz> well that is a problem
15:27:29 <lpabon> Error: "!!" is not a valid command -- lol
15:27:42 <bswartz> csaba: check the ML -- there are examples of other requests
15:27:49 <csaba> bswartz: OK
15:28:07 <bswartz> it needs either a bp or a bug
15:28:32 <bswartz> anything that's not pure docs or contrib changes need a tracking item in launchpad
15:29:15 <bswartz> either a bp or a bug
15:29:24 <bswartz> so we can "target" it to a milestone
15:29:42 <bswartz> that's how release management sees what's going into each milestone
15:29:56 <bswartz> okay enough on that topic
15:30:00 <bswartz> anything else for today?
15:30:08 <csaba> bswartz: what's the deadline for doc changes?
15:30:17 <lpabon> that's all from me
15:30:31 <vponomaryov> bswartz: is there some docs with meetup topics proposals?
15:30:48 <vponomaryov> bswartz: therpad link?
15:30:49 <bswartz> docs can be changed at any time except right around the actual release
15:31:10 <bswartz> vponomaryov: nothing exists yet
15:31:25 <mkoderer> bswartz: I can give a short update on manila scenario tests
15:31:43 <bswartz> we'll start with that next week
15:31:48 <bswartz> mkoderer: go ahead
15:32:11 <mkoderer> I will push a new version of the inital scenario test tomorrow
15:32:12 <mkoderer> https://review.openstack.org/#/c/162628/
15:32:27 <mkoderer> current state: we have a experimental test run for scenario tests
15:32:36 <mkoderer> I will release the WiP flag tomorrow
15:32:57 <mkoderer> it will launche a vm, create a share, allow access and ping the share service
15:33:12 <mkoderer> that's the inital setup
15:34:12 <bswartz> mkoderer: I look forward to checking those out
15:34:25 <mkoderer> bswartz: should we put a new milestone for L-1? or is kilo still ok?
15:34:51 <bswartz> hmm
15:35:05 <mkoderer> I mean it's just qa and no actual code is changed within manila
15:35:09 <bswartz> as long as it's nonvoting there's no risk to putting it in kilo really
15:35:21 <mkoderer> bswartz: yep exactly
15:35:30 <bswartz> but also I'm not sure it adds a ton of value either
15:35:47 <bswartz> compared to just putting it in liberty
15:36:04 <bswartz> we can use the tests to find bugs now, but not make it stardard for every patch until liberty
15:36:30 <mkoderer> bswartz: yep that's the thing.. so it won't be voting during kilo
15:36:53 <mkoderer> bswartz: so we can move https://blueprints.launchpad.net/manila/+spec/scenario-tests to L-1
15:37:07 <bswartz> yeah I'm okay with that
15:37:16 <mkoderer> bswartz: ok
15:37:21 <mkoderer> that's all from my side
15:37:45 <bswartz> thanks mkoderer
15:37:52 <bswartz> anything else before we wrap up?
15:38:17 <bswartz> thanks all
15:38:28 <lpabon> bye
15:38:36 <bswartz> #endmeeting