15:00:03 <bswartz> #startmeeting manila
15:00:03 <openstack> Meeting started Thu Apr  2 15:00:03 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:05 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:08 <openstack> The meeting name has been set to 'manila'
15:00:20 <bswartz> hello everyone
15:00:22 <lpabon> o/
15:00:22 <toabctl> hi
15:00:25 <u_glide> hello
15:00:30 <rraja> hi
15:00:31 <vponomaryov> hello
15:00:34 <bswartz> #agenda https://wiki.openstack.org/wiki/Manila/Meetings
15:00:54 <cknight> Hi
15:01:17 <bswartz> #topic Kilo-RC1 status (bugs)
15:01:27 <markstur> hi
15:01:29 <bswartz> so we will not meet our goal of releasing RC1 today
15:01:30 <tbarron> hi
15:01:30 <rushil> \o
15:01:35 <jvarlamova> hello
15:01:38 <csaba> hi
15:01:40 <ganso_> hello
15:02:00 <xyang1> Hi
15:02:04 <bswartz> at this point it's a day-by-day question when to make the RC
15:02:16 <bswartz> #link https://launchpad.net/manila/+milestone/kilo-rc1
15:02:36 <bswartz> when everything on this page is green, we will cut RC1
15:03:02 <vponomaryov> even #link https://bugs.launchpad.net/bugs/1356588 ?
15:03:03 <openstack> Launchpad bug 1356588 in Manila "manila: pylint wrong continued indentation issues" [Low,New] - Assigned to Danny Al-Gaaf (danny-al-gaaf)
15:03:03 <bswartz> Right now I'm hoping that day will be Tuesday 7 April or earlier
15:03:15 <bswartz> vponomaryov: I want to talk about that one
15:03:26 <bswartz> in fact we will talk about all of these
15:03:41 <bswartz> first, the blueprint
15:03:46 <bswartz> https://blueprints.launchpad.net/manila/+spec/automatic-cleanup-of-share-servers
15:04:01 <bswartz> This one looks good
15:04:13 <bswartz> thanks for helping out with this u_glide
15:04:15 <bswartz> and welcome back
15:04:33 <bswartz> https://bugs.launchpad.net/bugs/1356588
15:04:34 <openstack> Launchpad bug 1356588 in Manila "manila: pylint wrong continued indentation issues" [Low,New] - Assigned to Danny Al-Gaaf (danny-al-gaaf)
15:04:48 <bswartz> this one, I can't figure out if its' still a problem
15:05:03 <u_glide> bswartz: wellcome
15:05:37 <mkwiek> exit
15:05:39 <bswartz> some people are having trouble reading the channel -- maybe it's lagged?
15:05:51 <vponomaryov> ?
15:05:58 <cknight> bswartz: seems ok here
15:06:02 <lpabon> seems fine to me
15:06:04 <bswartz> okay I guess at least some people are okay
15:06:08 <toabctl> fine for me
15:06:11 <u_glide> cknight:+1
15:06:15 <markstur> me too
15:06:19 <bswartz> okay
15:06:24 <bswartz> so this pylint issue
15:06:41 <vponomaryov> I guess it should be postponed to Liberty
15:06:46 <bswartz> I haven't been ably to find dalgaaf
15:06:58 <lpabon> are other reviews having an issue with pylint?  I haven't seen the isue pop up
15:07:05 <bswartz> it's not essential for Kilo, but if it's actually fixed already I'd like to just close it
15:07:30 <lpabon> for example: review https://review.openstack.org/#/c/169917/ which is new, does not have an issue
15:07:30 <bswartz> we've been kicking it across milestones the whole release, and I can't find any evidence that there's any real problem
15:07:48 <lpabon> with pylint that is
15:07:58 <bswartz> so I'd like someone to take it over and verify if it's even valid anymore
15:08:10 <lpabon> i'll takeit
15:08:16 <bswartz> lpabon: thank you!
15:08:18 <lpabon> np
15:08:29 <tbarron> lpabon: well that review doesn't have any issues at all :-)
15:08:29 <bswartz> https://bugs.launchpad.net/bugs/1438893
15:08:30 <openstack> Launchpad bug 1438893 in Manila "NetApp cDOT driver is too strict in delete workflows" [Medium,Triaged] - Assigned to Clinton Knight (clintonk)
15:08:37 <lpabon> tbarron: ;-)
15:08:42 <bswartz> cknight you own this one
15:08:46 <cknight> bswartz: yep
15:08:54 <bswartz> estimate for when it will be ready for review?
15:09:20 <cknight> bswartz: a few days, there is some discovery on this one.  Valeriy had some input as well.
15:09:34 <bswartz> is merged by Tuesday a realistic goal?
15:09:40 <bswartz> or will it take longer than that?
15:09:50 <cknight> bswartz: I'll do my best!
15:10:06 <cknight> bswartz: In any case, it shouldn't be a large review.
15:10:08 <bswartz> okay -- my fear is that that bug might be the last one holding up RC1
15:10:16 <bswartz> because the rest look close to done
15:10:28 <cknight> bswartz: understood
15:10:29 <bswartz> https://bugs.launchpad.net/bugs/1438825
15:10:30 <openstack> Launchpad bug 1438825 in Manila "Creation of share server should fail early with VXLAN, GRE with NetApp cDOT driver" [Low,Triaged] - Assigned to Rushil Chugh (rushil)
15:10:44 <cknight> bswartz: This one is coded and in internal review.
15:10:44 <bswartz> rushil: this is the other one not ready for review yet
15:11:01 <bswartz> so perhaps upstream by later today?
15:11:05 <rushil> bswartz: I just pushed the fix to our internal CI
15:11:07 <lpabon> cknight: what does internal review mean?
15:11:24 <lpabon> cknight: company review?
15:11:32 <bswartz> lpabon: netapp runs a private gerrit where code is tested/reviewed before pushing upstream
15:11:37 <cknight> lpabon: Our internal CI system also uses gerrit, so by the time we push anything upstream, it has gone through extensive internal reviews.
15:11:56 <lpabon> that's pretty cool
15:12:02 <vponomaryov> not really =)
15:12:02 <bswartz> it's something our lawyers make us do, but it actually results in a lot of benefits for us quality-wise
15:12:07 <lpabon> lol
15:12:17 <tbarron> vponomaryov: :-)
15:12:18 <cknight> lpabon: Yes, it is!  But it introduces some delay as well.
15:12:37 <cknight> vponomaryov: :-)
15:13:12 <bswartz> okay so that one sounds like it's in okay shape
15:13:27 <bswartz> please push it upstream without delay
15:13:38 <cknight> bswartz: +1
15:13:47 <bswartz> there are 6 more bugs "in progress"
15:13:51 <bswartz> https://bugs.launchpad.net/bugs/1437509
15:13:53 <openstack> Launchpad bug 1437509 in Manila "cDOT driver can leave shares in world-readable state" [High,In progress] - Assigned to Clinton Knight (clintonk)
15:13:55 <bswartz> https://bugs.launchpad.net/bugs/1370761
15:13:55 <openstack> Launchpad bug 1370761 in Manila "NetApp cDOT driver uses a deprecated API for NFS export management" [Medium,In progress] - Assigned to Clinton Knight (clintonk)
15:13:59 <bswartz> https://bugs.launchpad.net/bugs/1420369
15:14:00 <openstack> Launchpad bug 1420369 in Manila "manila create from snapid fails to inherit share type" [Medium,In progress] - Assigned to Tom Barron (tpb)
15:14:03 <bswartz> https://bugs.launchpad.net/bugs/1434918
15:14:04 <openstack> Launchpad bug 1434918 in Manila "NetApp cDOT multi-SVM driver may choose unsuitable physical port for LIFs" [Medium,In progress] - Assigned to Clinton Knight (clintonk)
15:14:09 <bswartz> https://bugs.launchpad.net/bugs/1437176
15:14:10 <openstack> Launchpad bug 1437176 in Manila "glusterfs_native: Unable to create shares using newly available GlusterFS volumes without restarting manila share service" [Medium,In progress] - Assigned to Csaba Henk (chenk)
15:14:13 <bswartz> https://bugs.launchpad.net/bugs/1259988
15:14:15 <openstack> Launchpad bug 1259988 in Manila "NetApp cDOT driver should split clone from snapshot after creation" [Low,In progress] - Assigned to Clinton Knight (clintonk)
15:14:29 <bswartz> please prioritize these reviews
15:14:30 <cknight> bswartz: All of mine are in upstream review and are my highest priority to get merged.
15:15:08 <bswartz> csaba: yours appears to have a -1
15:15:18 <bswartz> actually 3 -1s
15:15:25 <bswartz> let's get those addressed
15:15:30 <csaba> bswartz: yes, we are fixing those
15:15:38 <bswartz> okay cool
15:15:50 <bswartz> does anyone have any other bugs that need targeted to RC1?
15:16:31 <bswartz> I see these 2 being worked on but not targeted:
15:16:32 <bswartz> https://bugs.launchpad.net/manila/+bug/1439030
15:16:33 <openstack> Launchpad bug 1439030 in Manila "config_group_name missing in NeutronNetworkHelper" [Undecided,In progress] - Assigned to li,chen (chen-li)
15:16:48 <bswartz> https://bugs.launchpad.net/python-manilaclient/+bug/1439683
15:16:49 <openstack> Launchpad bug 1439683 in python-manilaclient "Client fails with error instead of raising exception" [High,In progress] - Assigned to Igor Malinovskiy (imalinovskiy)
15:16:56 <bswartz> oh nevermind that second one -- it's a client change
15:17:28 <bswartz> chen12: you here?
15:18:21 <csaba> bswartz: I have two bugs for which I'm working on the fix and....  a third one that I have not yet even filed to launchpad as I was not sure about its scope (now I made sure, so I can go ahead with filing it)
15:18:32 <bswartz> csaba: !
15:18:55 <bswartz> please make sure you're filing bugs as you discover issues
15:18:55 <csaba> those two are:
15:19:14 <csaba> https://bugs.launchpad.net/manila/+bug/1439198
15:19:14 <openstack> Launchpad bug 1439198 in Manila "glusterfs_native corrupts GlusterFS backend" [Undecided,New]
15:19:16 <csaba> and https://bugs.launchpad.net/manila/+bug/1417352
15:19:17 <openstack> Launchpad bug 1417352 in Manila "Failed to allow-access for native_glusterfs" [Undecided,New] - Assigned to Csaba Henk (chenk)
15:19:27 <bswartz> and if they're critical, please find a bug supervisor to target it
15:20:06 <markstur> who are the bug supervisors?
15:20:14 <csaba> bswartz: whom are exactly bug supervisors/
15:20:21 <csaba> yeah same question :)
15:20:23 <bswartz> https://launchpad.net/~manila-bug-supervisors
15:20:36 <bswartz> right now it's the same members as the core reviewer team
15:21:08 <bswartz> but we will probably want to split those responsibilities later
15:22:01 * bswartz realizes he has too many browser tabs open
15:22:19 <bswartz> okay, so csaba are you asking for both of those bugs to be RC1-targeted?
15:22:41 <lpabon> they look pretty critical to me
15:22:44 <csaba> bswartz: if possible
15:23:09 <bswartz> okay I will follow up with both at the conclusion of this meeting
15:23:37 <bswartz> that's it for RC1
15:24:01 <bswartz> if we still have open bugs next week and I can't get solid commitments to finish them, we'll have to consider punting them to liberty
15:24:29 <bswartz> #topic Liberty design summit
15:25:06 <bswartz> The dates are May 19-22
15:25:26 <markstur> be there
15:25:28 <bswartz> so we've got a few weeks to propose topics and get a schedule together
15:25:38 <bswartz> #link https://etherpad.openstack.org/p/manila-liberty-proposed-sessions
15:25:45 <cknight> markstur: +1
15:25:46 <bswartz> I created this blank etherpad to collect the proposals
15:26:12 <bswartz> in future weeks we will discuss the proposed topics and find a way to make them fit into the time we get
15:26:19 <vponomaryov> bswartz: "Fishbowl" sessions?
15:26:23 <lpabon> quick question, what is meant by "fishbowl" ?
15:26:30 <bswartz> I haven't checked back yet, but it sounds like we are likely to get the session we asked for
15:26:30 <vponomaryov> lpabon =)
15:26:33 <bswartz> haha
15:26:41 <bswartz> there was a thread on this topic, late last year
15:26:43 <lpabon> lol
15:26:49 <bswartz> the design summit is changing formats again
15:27:07 <vponomaryov> nice
15:27:40 <bswartz> so fishbowl sessions are what we've done in the past -- with a large room and a area at the front where the chairs are arranged more or less in a semicircle
15:28:32 <bswartz> those are intended to present ideas, to have discussions at the front of the room, and for a large audience to be able to sit in an observe (as often happens)
15:29:07 <bswartz> working sessions are a new concept where the team can get together around a boardroom-style table and actually work on stuff
15:29:07 <vponomaryov> bswartz: can you please add description in etherpad?
15:29:18 <bswartz> there is less room for onlookers in the working sessions
15:29:25 <lpabon> ah
15:29:30 <bswartz> I'll provide links to the appropriate threads when I dig them up
15:30:34 <bswartz> we can get into more detail about this in coming weeks, but I wanted to provide a place to jot down ideas because we should start doing that now
15:30:42 <tbarron> http://lists.openstack.org/pipermail/openstack-dev/2015-January/054122.html
15:31:10 <bswartz> anyone who has ideas should be prototyping them and writing up designs/specs/blueprints this month
15:31:17 <bswartz> tbarron: thanks!
15:31:42 <bswartz> I guess it was early this year not late last year
15:32:23 <bswartz> that's all I'll say about the design summit for now
15:32:43 <bswartz> I'll add my own proposals soon and more info about the format and what we expect to get, space/time-wise
15:33:13 <bswartz> #topic Documentation
15:33:52 <bswartz> so as Kilo winds down and we fix the remaining bugs, we need to refresh our docs
15:34:05 <bswartz> a lot of docs haven't been touched since Juno!
15:34:42 <bswartz> people on my team are doing what they can, but it's a lot of work, and we're looking for people with spare cycles who can help with this
15:34:42 <vponomaryov> docs for network plugins are absent at all =)
15:35:37 <bswartz> We need to refresh: the admin guide, the user docs, the SDK docs, the developer docs, various driver docs, etc
15:36:50 <lpabon> i'm going to focus on developer docs
15:36:51 <bswartz> also, I've been talking with annegentle about the possibility of contributing our docs to the openstack-manuals project instead of what we've done in the past
15:37:30 <markstur> for Kilo? or L
15:37:33 <bswartz> there is a possible legal hurdle there, but if we can solve that issue I would prefer to migrate our docs to the official openstack-manuals project
15:37:42 <bswartz> possibly for Kilo
15:37:53 <markstur> nice
15:37:58 <markstur> if possible
15:38:19 <bswartz> it will happen eventually -- the sooner the better IMO
15:38:26 <lpabon> bswartz: do you mean "our docs" as NetApp or Manila?
15:38:35 <bswartz> Manila
15:38:41 <lpabon> ok
15:38:53 <bswartz> in this room I wear my manila hat and leave my netapp hat at the door
15:38:55 <vponomaryov> lpabon: which are in manila repo and http://docs.openstack.org/developer/manila/
15:39:55 <lpabon> All this time I didn't know about this: http://docs.openstack.org/developer/manila/devref/index.html !  I went to the wiki looking for this info
15:40:03 <bswartz> doh!
15:40:10 <bswartz> looks like we might need to add a link
15:40:14 <lpabon> we'll, that'll be my first fix ;-)
15:40:52 <bswartz> anyways, I'm coordinating the docs refresh, so if anyone has cycles, please reach out to me and I'll try to ensure we don't have duplication of effort
15:41:55 <bswartz> #topic open discussion
15:42:02 <bswartz> anything else for today?
15:42:41 <bswartz> oh, you may have seen I nominated cknight for the core reviewer team on the ML this morning
15:43:10 <toabctl> already added my +1 on the list. good nomination IMO
15:43:16 <bswartz> please offer support on the ML thread if you agree
15:43:28 <tbarron> toabctl: +1
15:43:36 <markstur> I thought only the core +1s actually count though.  Is that right?
15:44:00 <bswartz> well there is no official vote that occurs
15:44:14 <markstur> Oh.  +100 then
15:44:19 <bswartz> technically, the existing core team are the opinions that count
15:44:20 <ganso_> lol
15:44:29 <cknight> bswartz:  I appreciate the nomination.  The honor is to serve.  :-)
15:44:50 <markstur> Sir Knight
15:44:52 <bswartz> usually, core team additions are unanimous consent from among the existing core team, but feedback from others is welcome
15:45:18 <markstur> Good to know.
15:45:51 <bswartz> if anyone has concerns they're not comfortable sharing publicly, please reach out to individual core team members and share them
15:45:59 <bswartz> myself included
15:46:39 <lpabon> i do have one concern
15:46:43 <bswartz> that's all I've got
15:46:46 <lpabon> not a big one
15:47:10 <lpabon> ah nevermind.. no biggie
15:47:16 <bswartz> please share it
15:47:46 <lpabon> just from experience (for example Swift) it may be "interesting" to have multiple core members from the same company
15:48:08 <bswartz> if anyone is concerned about the balance of the core team, that goal has been to try to grow it to 6 people in the kilo timeframe
15:48:27 <bswartz> and I'm aware of worries about too many people from too few companies
15:48:27 <lpabon> what tends to happen is that core members from the same company tend to vote similarly
15:48:42 <lpabon> just my $0.02
15:48:48 <bswartz> my next nomination will be from a different company (not netapp or mirantis or EMC)
15:49:10 <bswartz> lpabon: thanks for sharing that -- it's a definite concern that I'm aware of
15:49:31 <bswartz> I've been talking to various candidates privately to gauge interest
15:49:36 <lpabon> bswartz: cool thanks
15:50:06 <bswartz> for those that don't know, what we look for is a history of consistent high quality code reviews over a period of 2 months or more
15:50:38 <cknight> lpabon: FWIW, Ben is spectacularly good at representing the Manila community's interests even when they don't align perfectly with NetApp's.  I don't see an issue in this case.
15:51:25 <cknight> lpabon: But thanks for raising the question.
15:51:37 <bswartz> other considerations for core reviewer membership include: code contributions (preferably to core), participation in meetings, IRC channel, mail list, and meetups
15:51:46 <lpabon> cknight: i agree, but my main concern is "the man" (the lawyers) behind the developers
15:51:54 <bswartz> but it's primarily a code REVIEWING job so that's that main requirement
15:53:05 <bswartz> my distaste for legal BS is well-known
15:53:11 <lpabon> lol
15:53:30 <lpabon> again, just my opinion
15:53:51 <bswartz> and I would hope that if anyone feels that I'm choosing netapp's interests over the interest of the community that you don't support me when I run for PTL
15:54:04 <bswartz> I try very hard to support the interests of the community first
15:54:13 <lpabon> bswartz: i think you are doing great, imho
15:54:55 <bswartz> anyways, we've veered off topic
15:55:01 <tbarron> fwiw, I see bswartz representing the community's interests within netapp, educating our company, regularly
15:55:08 <vponomaryov> yeah, we were having situation when vacations of cores were breaking possibility to merge changes with 2 +2
15:55:51 <bswartz> thanks vponomaryov, that was the motivation for growing the core team
15:56:06 <bswartz> my target number is 6, but we could continue to grow in liberty
15:56:08 <markstur> I having 2 from a company will actually be handy for you guys to cover each others gaps (vacations, etc)
15:56:40 <markstur> and representing at the summit
15:56:40 <bswartz> we have a lot of great candidates thanks to greatly increase participation during kilo
15:57:26 <Xyang2> This happened in other projects too.  Manila is not the only one with more than 2 cores from the same company
15:58:15 <bswartz> maybe we should adopt an informal rule that if there are 2 cores form the same company, we should not merge a change with only +2s from that company
15:58:52 <Xyang2> Then it doesn't help the vacation situation :)
15:58:53 <bswartz> that would prevent a single company from merging changes unilaterally, while still allowing us to expand the team to get more review bandwidth and to cover during vacations, etc
15:59:14 <cknight> bswartz: +1
15:59:16 <bswartz> it would help
15:59:19 <Xyang2> i think it depends on the patches
15:59:20 <lpabon> awesome
15:59:26 <bswartz> because cknight and I rarely take vacations at the same time
15:59:37 <bswartz> and the same is probably true of vponomaryov and u_glide
15:59:42 <cknight> bswartz: What is this "vacation" you speak of?
15:59:46 <bswartz> lol
15:59:46 <lpabon> lol
15:59:54 <markstur> lol
15:59:56 <Xyang2> with big patch, we should encourage more people to review before merge
15:59:58 <vponomaryov> cknight: workaholic? =)
16:00:05 <bswartz> xyang2: that too
16:00:10 <markstur> (I'm on vacation right now)
16:00:15 <bswartz> okay we're past our time
16:00:16 <cknight> vponomaryov: guilty  (but you are too!)
16:00:21 <bswartz> thanks everyone
16:00:26 <vponomaryov> thanks
16:00:31 <bswartz> #endmeeting