15:00:46 <bswartz> #startmeeting manila
15:00:47 <openstack> Meeting started Thu Sep  4 15:00:46 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:51 <openstack> The meeting name has been set to 'manila'
15:00:56 <bswartz> hello all
15:00:58 <cknight> Hi
15:01:01 <deepakcs> Hi, bswartz, will be meeting be here or openstack-manila given we are incubated now
15:01:02 <deepakcs> :)
15:01:03 <vponomaryov> hi
15:01:19 <deepakcs> *openstack-meeting i meant
15:01:19 <bswartz> deepakcs: nobody meets in the project channels
15:01:35 <xyang2> hi
15:01:41 <bswartz> no, we use this channel because the other one is taken during this time
15:01:46 <deepakcs> ok
15:02:16 <bswartz> with so many projects it's inevitable that there will be conflicts
15:02:22 <bswartz> I'm aware of a #openstack-meeting-3 too
15:02:33 <deepakcs> ah i wasn't aware.. news to me :)
15:02:41 <bswartz> someday probably a 4 and a 5
15:02:51 <bswartz> #agenda https://wiki.openstack.org/wiki/Manila/Meetings
15:03:07 <bswartz> #topic J-3
15:03:22 <bswartz> So J-3 was completed yesterday
15:03:45 <bswartz> the EMC driver was merged and the Glusterfs "native" driver as well
15:04:03 <bswartz> at this point I believe we're done with new features for Juno
15:04:14 <bswartz> did anyone have something they still hoped to land?
15:04:40 <deepakcs> bswartz, the manilaclient patch (its waiting jenkins +1) - its a dep for the glusterfs native driver
15:05:04 <bswartz> deepakcs: I know about that -- the gate is super backed up and it will take a while
15:05:16 <deepakcs> bswartz, ok, but i hope it gets into juno as well
15:05:19 <bswartz> python-manilaclient is not part of J-3 though so it's not a big deal
15:05:29 <deepakcs> oh ok, didnt knew that
15:05:41 <deepakcs> i thot the J-3 applied to all projects equally
15:05:57 <bswartz> We don't do milestones for the client
15:06:24 <deepakcs> ok
15:06:25 <bswartz> we'll do a release for the client but it will be a lot more casual than the manila release itself
15:06:47 <deepakcs> ok
15:06:49 <bswartz> so overall I'm pleased with J-3
15:06:55 <deepakcs> Yo!
15:07:03 <deepakcs> kudos to all!
15:07:12 <bswartz> thanks especially to the efforts of xyang and vponomaryov and everyone else who helped out with reviews
15:07:20 <deepakcs> bswartz, =1
15:07:22 <deepakcs> *+1
15:07:32 <bswartz> #topic dev status
15:07:41 <xyang2> thanks everyone
15:07:46 <vponomaryov> dev status is not big today
15:07:50 <vponomaryov> 1) Big part of efforts was directed to bugfixing.
15:08:04 <vponomaryov> 2) Default share-network for multitenant drivers (planned for K)
15:08:08 <vponomaryov> bp: #link https://blueprints.launchpad.net/manila/+spec/default-network-for-multitenant-drivers
15:08:08 <vponomaryov> gerrit: #link https://review.openstack.org/114258
15:08:17 <vponomaryov> status: available for testing
15:08:28 <vponomaryov> other mentioned stuff:
15:08:40 <vponomaryov> 3) Manila has new driver - EMC VNX.
15:08:40 <vponomaryov> 4) Manila has possibility to provide GlusterFS shares using appropriate driver.
15:09:03 <vponomaryov> that's the main update for a week
15:09:11 <bswartz> thanks vponomaryov
15:09:26 <bswartz> btw it looks like jenkins isn't happy with the default network change
15:09:35 <bswartz> but I'm glad it's avialable for review
15:10:01 <bswartz> just because it won't merge until Kilo doesn't mean we can't keep reviewing/testing it now
15:10:32 <bswartz> I spent some time cleaning up LP yesterday before publishing the J-3 tag for manila
15:10:53 <bswartz> please target your bugs in LP to a milestone
15:10:59 <deepakcs> bswartz, can u pls approve the cert-based-access-type bp.. given that most of the code is merged
15:11:14 <bswartz> deepakcs: oh yeah I never went back and did that
15:11:15 <deepakcs> bswartz, i put target as J-3 for the above cert bp
15:11:38 <bswartz> but this feed into my next topic
15:11:46 <bswartz> #topic J-4 plans
15:11:54 <xyang2> bswartz: is there a guideline on what can still be approved for Juno?  Any bug fixes with J-3 tag?
15:12:09 <vponomaryov> xyang2: https://wiki.openstack.org/wiki/Release_Cycle
15:12:22 <bswartz> so we have several bugs targetted at juno-rc1 now
15:12:24 <vponomaryov> xyang2: bug fixies with bug id
15:12:56 <xyang2> vponomaryov: thanks
15:13:00 <bswartz> please make sure anything you want fixed in juno has a target of juno-rc1
15:13:22 <bswartz> we will review that list and try to get it to zero as fast as possible
15:13:50 <bswartz> anything that can wait should be targetted to kilo-1 or later
15:14:42 <xyang2> bswartz: I'll only approve bugs with the juno-rc1 tag then
15:15:04 <bswartz> yes thanks
15:16:04 <bswartz> I need to double check that not just anybody can target a bug to a milestone
15:16:39 <bswartz> but assuming we to the right targeting in LP we should have a smooth release
15:17:15 <bswartz> so the other thing (other than bugs) we should focus on during J-4 is reviewing and updating docs
15:17:32 <vponomaryov> bswartz: docs on wiki?
15:17:36 <bswartz> now that we're incubated we have a chance to get into the integrated docs
15:18:16 <bswartz> so some of the docs will need to migrate from wiki to docs.openstack.org
15:18:31 <bswartz> and we'll need to review them for content, especially for stuff that's changed
15:18:34 <vponomaryov> bswartz: if you mean docs in manila project, then it does not satisfy criteria "only dugfixies"
15:18:47 <deepakcs> bswartz, Is J-4 same as juno-rc1 ? (https://wiki.openstack.org/wiki/Juno_Release_Schedule doesn't talk abt J-4, hence the Q)
15:19:31 <bswartz> J-4 is the period from now until Oct 16 (Juno Release)
15:20:12 <vponomaryov> bswartz: what about horizon extension?
15:20:20 <vponomaryov> bswartz: it is incompatible now
15:20:34 <bswartz> vponomaryov: by docs I was referring to http://git.openstack.org/cgit/openstack/openstack-manuals/
15:20:55 <vponomaryov> bswartz: API and client changes affected our horizon with manila support
15:21:00 <bswartz> we will have to do some work for horizon, tempest, and devstack, and I believe all of that work can wait until K-1
15:22:07 <bswartz> so priorities should be:
15:22:25 <bswartz> #1 find critical bugs / fix bugs for juno-rc1
15:22:38 <bswartz> #2 update docs and move them to openstack-manuals
15:22:56 <bswartz> #3 get back to work on new features aimed at kilo-1
15:23:47 <bswartz> any comments/questions?
15:24:15 <bswartz> with any luck we will be able to cut RC1 early in the J-4 cycle
15:24:40 <deepakcs> bswartz, what about the cirros image issue... we hold it till K-1 as well ?
15:25:12 <bswartz> deepakcs: that's outside the manila team's control right now so work can continue on that on whatever schedule
15:25:29 <deepakcs> ok
15:25:41 <bswartz> that's another issue we should tackle in kilo-1 though -- how to get a reference image controlled by the manila team
15:26:08 <bswartz> we'll need to create a new project most likel
15:26:38 <bswartz> #topic open discussion
15:26:45 <bswartz> so does anyone have anything else?
15:26:51 <csaba> bswartz: yes
15:26:59 <csaba> terminology question
15:27:19 <bswartz> for those of you who don't know, we will almost certainly get some official time on the design summit schedule, but I don't know how much
15:27:36 <bswartz> so think about topics to discuss in paris
15:28:06 <deepakcs> bswartz, is there a place where we can post the potential topics ?
15:28:14 <deepakcs> or see who has proposed what
15:28:15 <bswartz> csaba: go ahead
15:28:37 <bswartz> deepakcs: http://summit.openstack.org/
15:28:58 <csaba> so as we discussed last time, insteaad of single vs multi-tenant drivers we'll prefer to speak of  flat-network vs ... kind of drivers?
15:29:00 <bswartz> as you can see, it's not open yet
15:29:13 <bswartz> csaba: oh yes
15:29:13 <deepakcs> bswartz, got it
15:29:27 <csaba> "bloated network drivers"? :)
15:29:37 <bswartz> lol
15:29:39 <bswartz> I like it
15:29:51 <bswartz> seriously though
15:30:33 <bswartz> we have "flat-network" and "secure multitenancy" or "segmented-network" drivers
15:30:42 <deepakcs> how abt neutron-network based drivers ?
15:30:49 <bswartz> I guess we don't have an agreed-upon name for the non-flat-network drivers
15:31:05 <vponomaryov> this is it - non-flat-network drivers
15:31:12 <bswartz> deepakcs: we can't reference neutron because we're trying to eliminated that dependency
15:31:21 <csaba> it's just comes up when I'm to word my thougths
15:31:26 <xyang2> bswartz: what is segmented-network?  is this the gateway-assisted?
15:31:43 <vponomaryov> xyang2: vlan, vxlan usage, etc
15:32:02 <deepakcs> bswartz, i think we need to conclude on the right terminologies and put them for good in the manila wikipage, so that we can all talk the same lingo
15:32:03 <bswartz> xyang2: by segmented we just mean the tenants are on something like VLANs or VXLANs
15:32:05 <xyang2> vponomaryov: ok, thanks
15:32:16 <bswartz> okay these are all good points
15:32:35 <xyang2> bswartz: ok
15:32:43 <bswartz> let's plan to make decisions on terminology by next week
15:32:49 <bswartz> I'd like to think over the options and write some stuff down
15:33:27 <bswartz> I think I know what I mean when I talk about this stuff but if people don't understand it then it's no good
15:33:28 <csaba> bswartz: OK cool that's also good as base effort for outlined doc effort
15:33:55 <csaba> s/base effort/base/
15:34:03 <bswartz> yeah the front page of our manual needs to have a glossary section where we explain our manila-specific terminology
15:34:51 <bswartz> okay looks like we're done early today
15:35:01 <bswartz> going once....
15:35:11 <bswartz> twice....
15:35:20 <deepakcs> The terminology should go not just into manuals, but also in wikpage and hacking.rst too, so that developers, people googling and customers reading manuals all can read the same
15:35:33 <bswartz> deepakcs: good points
15:35:58 <bswartz> I'll make a note on the agenda for next week
15:36:05 <bswartz> okay thanks everyone
15:36:08 <deepakcs> bye
15:36:16 <bswartz> #endmeeting