15:00:48 <bswartz> #startmeeting manila
15:00:48 <openstack> Meeting started Thu Oct 30 15:00:48 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:52 <openstack> The meeting name has been set to 'manila'
15:00:55 <bswartz> hello all
15:00:57 <rushil1> hi
15:00:58 <tbarron> hi
15:00:59 <ameade> o/
15:01:02 <xyang1> hi
15:01:04 <cknight> hi
15:01:07 <nileshb> hi
15:01:28 <bswartz> #agenda https://wiki.openstack.org/wiki/Manila/Meetings
15:01:51 * bswartz looks around for vponomaryov
15:02:40 <bswartz> okay we may rearrange the agenda
15:02:51 <bswartz> there he is
15:02:54 <vponomaryov> sorry for late
15:03:09 <bswartz> #topic dev status
15:03:23 <vponomaryov> Dev status for last week:
15:03:27 <vponomaryov> 1) Functional tests for manilaclient
15:03:31 <vponomaryov> BP: #link https://blueprints.launchpad.net/python-manilaclient/+spec/functional-tests
15:03:34 <vponomaryov> gerrit: #link https://review.openstack.org/132011
15:03:37 <vponomaryov> status: work in progress
15:03:42 <vponomaryov> 2) Enhancement of share manager
15:03:46 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/enhance-share-manager
15:03:51 <vponomaryov> gerrit:
15:03:51 <vponomaryov> #link https://review.openstack.org/129843
15:03:51 <vponomaryov> #link https://review.openstack.org/129844
15:03:51 <vponomaryov> status: ready for review
15:03:57 <vponomaryov> 3) Manila share-networks-list API filtering:
15:04:01 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/improve-share-network-list-filtering
15:04:05 <vponomaryov> gerrit, server: #link https://review.openstack.org/130147
15:04:09 <vponomaryov> gerrit, cleint: #link https://review.openstack.org/129849
15:04:09 <vponomaryov> status: ready for review
15:04:17 <vponomaryov> thats the main
15:04:29 <bswartz> vponomaryov: question about 129844
15:04:48 <bswartz> gerrit says it depends on an "outdated" change
15:05:00 <vponomaryov> yes, requires rebase
15:05:07 <bswartz> ok
15:05:14 <bswartz> also, 130147 is still failing tempest
15:05:16 <bswartz> :-(
15:05:39 <bswartz> will that be fixed by the change we merged this morning?
15:05:46 <vponomaryov> bswartz: you already has merged fix for it
15:05:51 <bswartz> okay good
15:05:53 <vponomaryov> gate tests just should be rerun
15:05:55 <bswartz> any questions on the above?
15:06:10 <bswartz> I'll do the recheck
15:06:25 <bswartz> okay
15:06:35 <bswartz> #topic design summit
15:06:43 <bswartz> #link https://etherpad.openstack.org/p/kilo-manila-summit-topics
15:07:01 <bswartz> I cleaned up and rearranged the etherpad for the design summit
15:07:14 <bswartz> we have 3 agreed upon design summit topics
15:07:24 <bswartz> and a bunch of stuff for the meetup, in a rough priority order
15:07:51 <bswartz> Please take a look at the meetup topics and post some comments if you think something needs to be moved up/down
15:08:21 <bswartz> I'm still unclear on exactly how much time we'll have when we get together in paris on Friday, but I want to work from this list for our discussions
15:08:38 <vponomaryov> bswartz: little update about integration with tempest
15:08:55 <bswartz> k
15:09:11 <vponomaryov> bswartz: tempest is going to be split up, and functional tests are going to be in each project that owns it
15:09:25 <xyang1> bswartz: will it be overlapping with cinder meetup on Friday?
15:09:30 <bswartz> vponomaryov: that is similar to what we already have, right?
15:09:39 <vponomaryov> bswartz: as final result htat is expected - tempest has only "integration" tests
15:09:45 <bswartz> xyang1: unknown
15:09:47 <ameade> vponomaryov, bswartz : there is a session about tempest-lib at some point
15:09:49 <vponomaryov> liek scenario tests, etc
15:10:12 <vponomaryov> bswartz: not similar
15:10:20 <vponomaryov> bswartz: now we use tempsest project
15:10:32 <vponomaryov> bswartz: will use "tempest-lib" library
15:10:37 <bswartz> xyang1: there's nothing official at all on the schedule which means we might have freedom to do whatever we want
15:10:47 <bswartz> xyang1: it could also mean they forgot us :-/
15:10:57 <vponomaryov> ameade: yes, I am aware of it
15:11:04 <bswartz> xyang1: however we will try to avoid overlapping with cinder because I'm sure people will want to attend both
15:11:55 <xyang1> bswartz: sure
15:12:15 <bswartz> vponomaryov: it sounds to me like the changes to tempest will ultimately be good for us
15:12:22 <bswartz> vponomaryov: are there any issues you foresee?
15:12:24 <vponomaryov> bswartz: учфседн
15:12:27 <vponomaryov> bswartz: exactly
15:12:49 <vponomaryov> bswartz: it for point from https://etherpad.openstack.org/p/kilo-manila-summit-topics
15:13:04 <vponomaryov> bswartz: we can remove it
15:13:25 <bswartz> well it's just a sub-bullet
15:13:35 <bswartz> we probably won't need much time on it, but I don't want to lose track of it in the notes
15:13:43 <bswartz> we should write down the official plan for integration along with everything else
15:14:00 <vponomaryov> щл
15:14:02 <vponomaryov> ok
15:14:45 <bswartz> does anyone want to comment on the priorities?
15:14:59 <bswartz> I didn't really have strong feelings when I put these in order
15:15:17 <bswartz> mostly I went with what I thought needed to be discussed in person
15:15:28 <bswartz> because I'm sure the discussions will continue after we go home
15:16:01 <bswartz> ok
15:16:38 <bswartz> #topic Kilo network changes
15:16:51 <bswartz> #link https://wiki.openstack.org/wiki/Manila/Kilo_Network_Changes
15:17:04 <bswartz> just wanted to give an update on what I've been working on
15:17:14 <bswartz> this is a preview to the talk next week
15:18:33 <bswartz> I think I finally have a solid grasp of what we need to change to make
15:18:52 <bswartz> so my proposals are in that wiki
15:19:06 <bswartz> I didn't delete the first draft, I just pushed it down
15:19:55 <bswartz> to give a brief summary, what I want to see is for manila to recognize different driver modes and to operate differently depending on which mode is selected
15:20:23 <bswartz> all of this would be hidden from the tenants, it's intended to give administrators more fine grained control for how they setup their backends and networks
15:20:42 <bswartz> and specifically to enable use cases which are currently impossible
15:20:54 <bswartz> while at the same time not breaking anything
15:21:21 <bswartz> existing drivers will need updates, but the goal is to make life easier for future driver authors
15:21:58 <bswartz> so you're all welcome to read the wiki and pre-load some questions or challenges before the talk at the design summit
15:22:08 <jasonsb> do you see enterprise private cloud using network segmentation?
15:22:28 <bswartz> jasonsb: I see both use cases
15:22:32 <jasonsb> (IE: hippa or PHI data, lets say)
15:23:06 <bswartz> if an enterprise private cloud uses network segmentation, then they're really just acting a little more like a public cloud, as far as we're concerned
15:23:29 <bswartz> as long as we cover both use cases well, then deployers are free to choose what works for them
15:23:35 <jasonsb> yes, with caveat of single LDAP (perhaps)
15:23:50 <bswartz> yeah I'm aware of that use case
15:24:12 <bswartz> I think my proposal will allow for that
15:24:22 <bswartz> VLAN-based segmentation with shared LDAP between tenants
15:24:57 <bswartz> I know it's a lot to read and even more to understand
15:25:15 <jasonsb> quite interesting
15:25:16 <bswartz> I spent a lot of time coming up with this
15:26:13 <jasonsb> i'm still working on getting an environment to start work on my manila driver
15:26:34 <jasonsb> so for me this is very timely
15:26:55 <bswartz> jasonb: one of the issues I'm trying to fix with these changes is make it easier to "get an environment"
15:26:57 <jasonsb> im also hoping to have an environment to test and do reviews :)
15:26:58 <bswartz> right now it's way too hard
15:27:25 <bswartz> I want to enable people to create much simpler environment, and help them scale up
15:27:34 <bswartz> rather than forcing them to start with the most complex
15:27:54 <jasonsb> i like the image you give in devstack
15:28:00 <jasonsb> but certainly you are correct
15:28:10 <jasonsb> im sure it would be well received
15:28:23 <bswartz> okay that's all from me
15:28:44 <bswartz> I'll be working on the design for my other presentation topic between now and Tuesday
15:28:59 <jasonsb> when are you presenting on this topic?
15:29:06 <bswartz> glad you asked!
15:29:15 <bswartz> #link http://kilodesignsummit.sched.org/
15:29:25 <bswartz> #link https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads#Manila
15:30:50 <bswartz> #topic open discussion
15:30:57 <bswartz> anything else?
15:31:07 <bswartz> next week's meeting is canceled (obviously)
15:31:19 <vponomaryov> bswartz: team meetup
15:31:26 <vponomaryov> where can we find info about it?
15:31:43 <bswartz> if you look at sched.org, on Friday
15:31:50 <bswartz> those are all the meetups
15:31:58 <bswartz> I'm hoping to get manila into that list
15:32:09 <bswartz> but we'll find out about what kind of space/time is available when we're in paris
15:32:14 <xyang1> I don't see meetup time for any incubated project on the schedule
15:32:28 <vponomaryov> so do I
15:32:49 <vponomaryov> bswartz: if not available - no meet up?
15:33:09 <bswartz> I've been told we will have space at our development team pod
15:33:17 <bswartz> we just need to designate a time to all be there
15:33:22 <bswartz> I'll be there when I'm not doing anything else
15:33:26 <bswartz> just to hang out
15:33:34 <bswartz> in case anyone wants to grab me
15:33:58 <bswartz> okay so just in case, let's PLAN on meeting up during the afternoon half of Friday at the manila team pod
15:34:03 <bswartz> so we can avoid conflicting with cinder
15:34:19 <bswartz> if I learn anything official or if we have to change the plan I'll use the ML
15:34:23 <xyang1> bswartz: +1
15:34:44 <vponomaryov> thanks
15:34:55 <bswartz> thanks everyone
15:35:00 <xyang1> who will be at the summit?
15:35:06 <jasonsb> me
15:35:06 <bswartz> .o/
15:35:07 <ameade> me
15:35:10 <vponomaryov> me
15:35:25 <xyang1> me too
15:35:47 <bswartz> I know a bunch of others who will be there -- they probably fell asleep at their keyboards
15:35:57 <xyang1> bswartz: :)
15:36:00 <vponomaryov> =)
15:36:03 <bswartz> #endmeeting