15:01:22 <bswartz> #startmeeting manila
15:01:23 <openstack> Meeting started Thu Nov 20 15:01:22 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:24 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:26 <openstack> The meeting name has been set to 'manila'
15:01:36 <bswartz> hello all
15:01:37 <cknight> Hi
15:01:37 <rushil> \o
15:01:40 <vponomaryov> Hi
15:01:40 <vvechkanov> Hi
15:01:40 <toabctl> hi
15:01:41 <rraja_> hi
15:01:43 <xyang1> hi
15:01:49 <jasonsb> gi
15:01:53 <csaba> hi
15:02:22 <bswartz> so the agenda today is light
15:02:37 <bswartz> good to see a bunch of people here, last week was lightly attended
15:02:47 <bswartz> #agenda https://wiki.openstack.org/wiki/Manila/Meetings
15:03:21 <bswartz> I think mainly we are getting down to work and implementing new things for Kilo
15:03:32 <bswartz> so there's not much to discuss unless anyone wants to
15:03:40 <bswartz> #topic dev status
15:03:47 <vponomaryov> Dev status for last week:
15:03:48 <bswartz> vponomaryov: we missed you last week\
15:04:07 <vponomaryov> 1) Functional tests in manilaclient
15:04:11 <vponomaryov> BP: #link https://blueprints.launchpad.net/python-manilaclient/+spec/functional-tests
15:04:18 <vponomaryov> status: added gate job, it is being tested already. Work in progress on new tests.
15:04:38 <vponomaryov> 2) Driver modes:
15:04:38 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/driver-modes
15:04:38 <vponomaryov> status: work has been started
15:04:46 <vponomaryov> 3) Network helper
15:04:46 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/network-helper
15:04:46 <vponomaryov> status: work in progress
15:04:51 <vponomaryov> 4) devstack enhancements
15:04:55 <vponomaryov> BP: #link https://blueprints.launchpad.net/manila/+spec/enhance-devstack-plugin
15:04:55 <vponomaryov> gerrit: #link https://review.openstack.org/135953
15:04:55 <vponomaryov> status: work in progress
15:05:09 <vponomaryov> That's the main
15:05:18 <bswartz> thanks vponomaryov
15:05:31 <bswartz> anyone have any questions about what we're working on?
15:05:49 <bswartz> I've bee doing pretty minimal reviews -- is anyone looking for code reviews on new stuff?
15:06:21 <toabctl> I'm trying todo reviews now frequently. but I'm on vacation for the next 3 weeks.
15:06:27 <jasonsb> I hope soon but im stuck on somerhing
15:06:43 <bswartz> thanks toabctl -- enjoy your vacation :-)
15:06:47 <jasonsb> neutron thing
15:07:06 <bswartz> vponomaryov: what is julia's IRC handle?
15:07:21 <vponomaryov> we have two Julias
15:07:28 <bswartz> Julia Varlamova
15:07:39 <vponomaryov> jvarlamova
15:07:39 <bswartz> she's listed at assignee for driver modes on LP
15:07:47 <bswartz> okay I should have guessed
15:07:52 <vponomaryov> =)
15:07:58 <bswartz> is she on the same timezone as you?
15:08:05 <vponomaryov> no
15:08:10 <vponomaryov> +1 from me
15:08:13 <bswartz> okay
15:08:25 <bswartz> well thanks for the update
15:08:28 <bswartz> #topic open discussion
15:08:35 <bswartz> does anyone else have a topic they wanted to discuss today?
15:08:50 <vponomaryov> one thing
15:09:15 <bswartz> go ahead
15:09:23 <vponomaryov> deepakcs proposed to use same storage for our current service image as for modified cirros image
15:09:38 <vponomaryov> csaba is using it
15:09:48 <bswartz> you mean the dropbox account?
15:09:52 <vponomaryov> no
15:09:59 <bswartz> where then?
15:10:09 <csaba> bswartz: my red hat personal webpage
15:10:23 <bswartz> csaba: can that site handle high bandwidth?
15:10:54 <vponomaryov> csaba: also is there traffic limit?
15:11:01 <bswartz> vponomaryov: is there any reason to not continue using dropbox?
15:11:04 <lpabon> hi
15:11:06 <vponomaryov> or treshold for download speed?
15:11:07 <lpabon> sorry im late
15:11:09 <bswartz> I thought that we had upped the traffic limit and it was okay now
15:11:10 <csaba> bswartz: we have to check it to make sure, allegedly others use people.redhat.com to storeimages too
15:11:28 <vponomaryov> bswartz: it still has limit
15:11:36 <vponomaryov> bswartz: we just do not reach it
15:11:39 <bswartz> yes but the limit is way higher than we need
15:11:42 <rushil> but people.redhat.com is much slower than dropbox images
15:12:00 <bswartz> if we get close to the limit again, then we should just engage with the infra folks and have them host it
15:12:12 <bswartz> we could have infra do it now -- I know they're okay with it
15:12:20 <bswartz> but the current situation seems to be working
15:12:44 <vponomaryov> bswartz: are you ok that is my own personal storage?
15:13:10 <vponomaryov> bswartz: I mean I am the bottleneck
15:13:10 <bswartz> vponomaryov: in the short term yes -- it's been this way for several months and we've been okay
15:13:32 <vponomaryov> ok
15:13:33 <bswartz> the long term plan is for infra to do it but I'd rather focus on a manila-image project first
15:13:58 <bswartz> but all of that is lower priority than the BPs we have targetted for kilo-1
15:13:59 <toabctl> bswartz: what is "manila-image project" ?
15:14:14 <bswartz> I want to get those new feature merged because they will affect new driver writers
15:14:28 <vponomaryov> toabctl: planned project to handle our service image
15:14:30 <bswartz> #topic manila-image project
15:14:44 <bswartz> okay so for those who missed the discussion in paris (this was at the manila team meetup)
15:15:14 <bswartz> I'm proposing that we start a new project to build the glance image that manila's generic driver currently uses
15:15:40 <bswartz> currently the image we use is built in a way that not everyone can reproduce
15:15:56 <bswartz> so I'd like to have this team create and own the build scripts for that image
15:16:00 <toabctl> bswartz: should that be based on diskimage-builder?
15:16:11 <toabctl> i.e. the sahara project has something similar
15:16:29 <toabctl> the project there is called sahara-image-elements
15:16:32 <bswartz> toabctl: I'm not sure, I'm not familiar with that project
15:16:36 <bswartz> #link https://github.com/openstack/diskimage-builder
15:16:37 <csaba> toabctl: it's open what to base on, suggestions are welcome
15:16:57 <toabctl> #link https://github.com/openstack/sahara-image-elements
15:17:05 <csaba> toabctl, bswartz : I plan to start on with yocto
15:17:33 <bswartz> the main requirements for the image (from my perspective) is that it needs to be small and the build scrips need to be apache licensed
15:17:36 <csaba> https://www.yoctoproject.org/
15:17:50 <vponomaryov> we have here two directions - way of maintenance and source for image itself
15:17:50 <bswartz> the image needs to support SSH, NFSv3 and NFSv4, as well as Samba
15:18:23 <bswartz> several people (including me) are investigating approaches to achieve those goals
15:18:34 <bswartz> by the end of kilo I'd like to have something usable
15:18:48 <toabctl> csaba: hm. I suggest to first have a look at diskimage-builder. That's used by tripleo, sahara and maybe some other projects.
15:18:50 <bswartz> it's not a high priority
15:19:02 <csaba> toabctl: as of diskimage-create: they say "This script builds Ubuntu, Fedora, CentOS cloud images for use in Sahara." -- we'd prefer smaller images than general purpose distro based ones tend to be
15:19:03 <bswartz> toabctl: where are docs for that project?
15:19:05 <toabctl> is there already a blueprint for that?
15:19:06 <bswartz> is there a wiki?
15:19:48 <csaba> toabctl: source is https://github.com/openstack/sahara-image-elements/blob/master/diskimage-create/README.rst
15:19:48 <toabctl> bswartz: wiki for diskimage-builde?
15:20:33 <toabctl> csaba: why do we want to have smaller images? imho what people want is a image based on there already supported distro they use anyway. no?
15:20:59 <bswartz> the main motivation for the small image is that this image is actually used as part of our gate tests
15:21:21 <bswartz> we want to minimize stress on the gate test servers and we also want our gate to run as fast as reasonably possible
15:21:22 <vponomaryov> toabctl: gate tests and to have only "required" things within
15:21:44 <bswartz> actual deployers are welcome to build their own larger images
15:22:03 <bswartz> that's why this is not a high priority
15:22:17 <nileshb> would the smaller image help CI for manila in future?
15:22:28 <vponomaryov> nileshb: yes
15:22:31 <bswartz> yeah
15:22:41 <vponomaryov> we had timeouts of image downloadings
15:22:51 <rushil> I thought we were supposed to base it out of cirros images
15:23:15 <bswartz> rushil: it can be based on anything, so long as it meets the requirements of SSH, NFSv4, and Samba
15:23:26 <bswartz> currently we use an ubuntu-based image that's 305 MB
15:23:45 <bswartz> I would like to see an image in the 10-50MB range
15:23:51 <rushil> bswartz: We can modify that. My local.conf uses a significantly smaller cirros image
15:24:02 <csaba> rushil: there might be licensing problems, this is something that bswartz raised at summit but has not been completely cleared AFAIC feel
15:24:15 <csaba> rushil: *licensing with cirros
15:24:21 <bswartz> rushil: I'd love to see what you have if it actually works
15:24:49 <rushil> bswartz: Sure.
15:24:53 <bswartz> also as csaba mentions, we can't fork cirros because it's license is not compatible with apache
15:25:18 <csaba> bswartz: I gave it a thought though
15:25:22 <bswartz> but I'll take something non-apache-licensed if it's small and it works
15:25:33 <csaba> an image builder is something like a compiler
15:25:48 <csaba> you are not worried by gcc being gpl, right?
15:26:03 <csaba> so why worry about license of the image builder?
15:26:26 <bswartz> if it's going to be an openstack or stackforge project, one of the requirements is that it's apache licensed
15:26:27 <csaba> images, like with compiler, won't be a derivate work of builder
15:27:03 <bswartz> yes I'm not worried about usage of GPL stuff, as long as nothing we distribute is GPL
15:27:18 <clarkb> bswartz I dont think that is a requirement for stackforge
15:27:38 <bswartz> clarkb: interesting -- are you aware of GPL projects on stackforge?
15:28:04 <bswartz> if they exist, then perhaps a cirros-derivative image is the easier path to follow
15:28:13 <clarkb> not off the top of my head but I dont see why that would be prevented
15:28:23 <bswartz> okay that's something we can look into
15:28:37 <bswartz> any more questions on manila-image?
15:29:47 <bswartz> okay that's everyone
15:29:49 <bswartz> I think we're done
15:30:15 <bswartz> *thanks everyone
15:30:16 <bswartz> #endmeeting