16:00:12 #startmeeting cinder 16:00:13 Meeting started Wed Oct 16 16:00:12 2013 UTC and is due to finish in 60 minutes. The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:14 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:16 The meeting name has been set to 'cinder' 16:00:20 hey everyone 16:00:22 o/ 16:00:29 hi 16:00:33 hello folks 16:00:34 hi~ 16:00:42 agenda is here: https://wiki.openstack.org/wiki/CinderMeetings 16:00:44 hello all 16:00:52 hi 16:00:59 I'll open it up for folks after we get through the basics real quick 16:01:21 #topic status for Havana 16:01:39 You may have noticed we did an RC3 last night/this morning 16:01:56 good work jgriffith, two fixes. 16:01:57 This hopefully will address the upgrade issues with mysql migrations 16:02:12 zhiyan: yeah, the other one was fortuitous :) 16:02:30 jgriffith: Saw that. 16:02:38 For anybody that didn't see: https://launchpad.net/cinder/havana/havana-rc3 16:02:54 hopefully no rc4? 16:02:57 The thin LVM fix and the i8n fix I pushed to master didn't warrant IMO 16:03:05 winston-d: please no 16:03:06 :) 16:03:18 it's time we move on and say good by to RC's for Havana 16:03:31 besides the distro folks will murder me if I do another RC :) 16:03:38 jgriffith: kudos on the release! 16:03:49 avishay: +2 16:03:53 avishay: thanks, and kudos to everyone for pitching in!! 16:04:06 hopefully you've all got some testing in on the RC bits 16:04:29 I dont' really have much else on RC, just wanted to give that update incase folks didn't see it 16:04:32 what? test? :) 16:04:37 anybody have any questions about RC? 16:04:40 winston-d: haha!!! 16:04:52 winston-d: just wait for bug reports from the field ;) 16:05:05 avishay: hah! 16:05:06 avishay: winston-d I thought that's what the field was for "test" 16:05:07 LOL 16:05:09 just kidding 16:05:14 haha 16:05:22 alright... moving along 16:05:29 #topic release-notes 16:05:43 https://wiki.openstack.org/wiki/ReleaseNotes/Havana#OpenStack_Block_Storage_.28Cinder.29 16:06:10 I've takena stab, but there's a good bit probably missing 16:06:27 it would be great if you have a feature that you worked on/added if you put something in the release notes about it 16:06:34 also eharney I think that TODO is from you 16:06:38 volume migration :( 16:06:46 eharney: you want me to write something or shall you? 16:06:46 Yes, there are a fair number of drivers that had config options deprecated. Please note these in the release notes. your users will love you. 16:06:54 oh, yes, it is 16:06:58 avishay: yes I didn't forget, I just went to bed when I got to it 16:07:06 jgriffith: :) 16:07:14 avishay: if you want to add something that woudl be fantastic 16:07:21 i can 16:07:23 jgriffith: will do 16:07:26 winston-d: your qos changes should have some detail there as well 16:07:57 jgriffith: yep, and i still own everybody the doc. 16:08:00 I'd like to have the fairly well buttoned up by the end of today if we can 16:08:10 winston-d: Ohh yeahh!! Thanks for reminding me :) 16:08:15 s/me/us/ 16:08:39 winston-d: you're docs/comments in code and commit messages is great BTW 16:08:46 much appreciated 16:09:39 jgriffith: thx, still working on doc for qos, should be ready tomorrow 16:09:59 winston-d: great 16:10:23 anything on Release Notes? 16:10:41 cool 16:10:46 #topic summit 16:10:56 Ok, we've got a good list: http://summit.openstack.org/cfp/topic/14 16:11:05 now it's time to start figuring out what stays, what goes 16:11:24 I plan to finally get around to working on this a bit today 16:11:39 jgriffith: link is 'forbidden' 16:11:49 so fair warning, if you have things in mind that you haven't proposed, it would be really good to get them up 16:11:57 avishay: say whaaa 16:12:00 OHHH 16:12:09 hehe 16:12:21 http://summit.openstack.org/ 16:12:23 sorry about that 16:12:32 I gave you the link to my "special" page 16:12:34 ctrl-f , search for cinder :) 16:12:53 how to group-by-cinder... 16:13:01 you can just order by topic 16:13:01 avishay: you an also sort by cliking on topic 16:13:05 thingee: +1 16:13:13 oooh 16:13:15 fancy 16:13:18 thingee: cool 16:13:21 thanks 16:13:30 thanks 16:13:31 So... if anybody sees anything here they don't want to talk about :) let me know 16:13:46 or if you want to volunteer to combine some sessions that would be great as well 16:14:01 else I'll do it myself, and who knows how messed up it will be :) 16:14:09 22 topics, 11 slots? 16:14:15 avishay: yeup 16:14:17 yup 16:14:22 the math doesn't quite work :) 16:14:34 each one have 22.5 mins, done 16:14:43 s/have/has 16:14:50 winston-d: interesting idea 16:14:52 :) 16:14:56 lighting rounds for summit sessions 16:14:57 LOL 16:15:06 Taskflow and ollie/my state taslk might be combinable 16:15:31 DuncanT-mob: yeah, I would like to explore that 16:15:49 think it would be good to have those talks simultaneously, just worried about fitting it all in time wise 16:15:55 I've been talking to harlowja and combining ideas 16:16:07 yeah, that's awesome! 16:16:25 I don't know how much additional harlowja has there 16:16:33 but there are other topics that overlap as well 16:16:50 like where do we go next (ie delete, backup etc) for taskflow 16:16:54 who proposed this topic? http://summit.openstack.org/cfp/details/212 Is he/she asking for a Q&A session or what? 16:16:56 anyway... there's a lot there I think 16:17:09 My proposal slightly overlaps with Avishay's 16:17:22 winston-d: I was wondering the same thing 16:17:57 winston-d: thingee good question 16:17:58 http://summit.openstack.org/cfp/details/212 might be talking about per-volume settings .v. per volume type settings... 16:17:58 doesn't seem appropriate for the summit 16:18:05 caitlin56: your proposal is great and i'm really interested in it, but not sure how much overlap there is with replication 16:18:06 I don't know who Alex Jauch is either 16:18:45 hmmm... he has a couple proposals that don't really *fit* 16:19:06 seems to be a lack of understanding of existing architecture/purpose 16:19:18 anyway... I'll see if I can track him down and clear some of those things up 16:19:34 anything anybody kicking around that they want to get on the list quickly? 16:19:36 Unconference sessions are always a poossibility 16:20:03 DuncanT-mob: yeah, that worked really well in SanDiego 16:20:15 DuncanT-mob: didn't have quite as good a luck with them in Portland 16:20:32 ie don't think we really had them in Portland :( 16:21:05 How much time is there for unconference sessions that don't conflict with Cinder sessions? 16:21:13 Ok, not much else to say here, unless yall want to start going through these as a group effort? 16:21:30 caitlin56: unconf sessions are the same length/duration 16:21:32 jgriffith: lets move it to #openstack-cinder 16:21:37 after meeting 16:21:41 caitlin56: it's just a matter of getting a room 16:21:48 thingee: +1 16:21:48 and coordinating everyone 16:21:53 thingee: +2 16:22:14 Ok, I had state machine on the agenda, but I think that's premature to open up in meeting time 16:22:28 DuncanT-mob: ollie and harlowja are all working on things here 16:22:39 so that's likely enough for now 16:22:52 Indeed, I've nothing much to say on the subject orther than I've been working on it and talking to harlowja about geting it into taskflow 16:23:06 fair enough 16:23:07 (sorry, lagged) 16:23:15 Okie Dokie 16:23:20 #topic open-mic 16:23:22 DuncanT-mob: any design draft can share with me? 16:24:05 zhylan: When I'm not mobile, yes. There's an etherpad and some scratch code 16:24:30 I have a general question/concern and wanted to understand the history. A lot of nova people seem to think of cinder as "external storage" and prefer "native" hypervisor based storage. 16:24:42 DuncanT-mob: cool. can you ping the link to me? thanks 16:24:51 caitlin56: yes they do 16:25:08 What can we do to discourage this. It can be wasteful, like they were talking about authenticating glimpse clones totally independent of cinder's existing cloning capabilities. 16:25:38 caitlin56: keep providing and improving things like boot from volume for starters 16:25:53 Code was written by me so ugly as sin, just so you're wared ;-) 16:26:13 Is cinder ready to state "you should be using Cinder for all volume services" if not, what is lacking? 16:26:45 caitlin56: I don't think that's something that would work 16:26:50 caitlin56: not that I would mind 16:27:01 caitlin56: but it's just not realistic 16:27:09 jgriffith: would't work politically or wouldn't work technically? 16:27:13 cinder is all for volume, nova folks even want cinder to manage native local disks during last summit 16:27:19 both, but mostly politically 16:27:26 winston-d: +1 16:27:34 DuncanT-mob: actually i'm interested in what's your plan for taskflow-statemachine 16:27:44 caitlin56: I think we're getting there, and will continue to make progress 16:28:05 but you'll never convince everybody that they don't *need* some on-server disk storage 16:28:09 DuncanT-mob: if you have any design doc/wiki, it will be great. 16:28:24 that by the way was the whole idea that started brick 16:28:32 before it got horribly side-tracked 16:28:43 * jgriffith apologizes for that 16:28:45 jgriffith: I was more thinking of opposing enhanciung non-cinder storage -- such as the "certified clone" feature being discussed. 16:29:00 caitlin56: I'm not familiar with that 16:29:12 jgriffith and hemnafk and eharney did great job on brick during H 16:29:33 They want to check out clones directly from glimpse and effectively sign them for the hypervisors to use. 16:29:34 winston-d: yeah... kudos to hemnafk eharney and everyone who worked on it 16:29:42 I just didn't manage/communicate things well 16:30:15 caitlin56: hmm... not sure about that. But the work zhiyan has been doing should help get that sort of thing going in Cinder 16:30:15 caitlin56: do you have a link to a blueprint or something? i'm not aware of this 16:30:16 jgriffith: I'll forward it to you. 16:30:29 caitlin56: but they'll still want the locality feature of the image 16:30:45 caitlin56: if you have a link post it here or in cinder later 16:30:51 I'm sure others are interested as well 16:31:18 You can never get anything to retreat, but keeping it from growing may be doable. 16:32:05 caitlin56: yeah... sometimes just go with the flow though :) 16:32:19 Ok, anybody have anything else? 16:32:27 caitlin: Somebody needs to code up the cinder-equivilant 16:32:35 DuncanT-mob: +1 16:32:48 which I'm sure we can do if we understand what they're tryign to accomplish 16:33:02 I suspect it's part of the glance/cinder/RO work 16:33:12 or they should just code it in cinder to begin with? 16:33:20 avishay: well there's that :) 16:33:37 let's not get too anxious on this since none of us seem to be familiar with it 16:33:43 we'll figure it out 16:33:56 all valid points though 16:34:07 jgriffith: +1 16:34:12 silos versus project 16:34:21 ok... that's all I've got 16:34:29 * jgriffith is on a mission to have shorter meetings :) 16:34:42 jgriffith: stable/havana tomorrow? 16:34:57 avishay: not sure if it'll be tomorrow or not 16:35:00 avishay: good point, i just want to raise this question :) 16:35:00 avishay: Good question. 16:35:13 i already have a backport :( 16:35:29 avishay: yeah, there are a few 16:35:40 avishay: just make sure you tag the bug so we can track it 16:35:43 Gotta draw the line at some point though. 16:35:49 avishay: and we'll get backports going asap when stable hits 16:36:00 jgriffith: yup it's tagged, sure thing 16:36:06 jungleboyj: +1, and it's been drawn 16:36:16 jungleboyj: although we use pencil so it can be erased 16:36:18 :( 16:36:21 jgriffith,avishay: Avoiding Image Copying from srujana_cp on Oct 16 at 2:58 AM. 16:36:22 jgriffith: and re-drawn, and re-drawn - but that's it! 16:36:41 caitlin56: ahh 16:36:48 caitlin56: that's somewhat different IIRC 16:37:54 Ok, let's move over to #cinder for folks that have more they want to talk about 16:37:58 thanks everyone! 16:38:02 #endmeeting