18:00:53 #startmeeting 18:00:54 Meeting started Thu May 3 18:00:53 2012 UTC. The chair is jgriff. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:10 Hi 18:01:13 Hi 18:01:46 hey 18:01:54 Let's hope my internet connection doesn't die this week and lock up the channel :( 18:02:06 :) 18:02:20 rnirmal: Sorry I didn't get your pull request last night before migration started back into gerrit 18:02:36 np send the PR thru gerrit 18:02:44 send/ will send 18:02:51 rnirmal: :) 18:03:18 shall we start the meeting 18:03:23 Ok, so you've probably all noticed a flury of activity :) 18:03:35 Thanks especially to anotherjesse !!! 18:03:38 jgriff: #startmeeting 18:03:47 I did 18:03:58 oops my bad.. 18:04:04 :> 18:04:20 I think it just cleared off my screen.. n/m 18:04:24 Ahhh 18:04:39 so, there is an official openstack/cinder repo now 18:04:43 hi 18:04:58 vladimir3p: yes has been for about a week now 18:05:34 #link https://github.com/openstack/cinder 18:05:53 yeah, just for some reason my git shows that it was created 15 min ago 18:06:03 so anyway... I'd suggest everybody take a look at the wiki page if you haven't: http://wiki.openstack.org/Cinder 18:06:09 vladimir3p: we just pushed a squash to it 15 minutes ago 18:06:22 Most importantly check out the etherpad 18:07:09 vladimir3p: Also I was convinced (fortunatley) that the way I was going about it wasn't so great so we did a reset 18:07:23 Instead we just pulled in all of nova and culled 18:07:49 ok, great 18:07:59 dtroyer is working on getting cinder support into devstack - https://review.openstack.org/#/c/7042/ 18:08:23 and vishy is working on the first item in the decoupling section 18:08:39 we need to get vishy's python-cinderclient moved to official repo this week as well 18:09:05 anotherjesse: ahhh.. I'll hit up mtaylor about that, assuming keep it in it's current form 18:09:27 jgriff: that's ok, I think it bit rotted though 18:10:08 anotherjesse: still could use as a baseline yes? 18:10:08 so is the cinder repo setup with gerrit now? 18:10:13 yup 18:10:16 rnirmal: yep 18:10:20 jgriff: yeah 18:10:29 cool thanks 18:10:29 jgriff: let me know when it's there and I'll get cinderclient added 18:10:55 mtaylor: assuming just pull in vish's version 18:11:04 yeah, prolly so 18:11:21 mtaylor: guess I'll need to do LP pages again 18:11:48 we actually just use the cinder pages for cinderclient if we're following the model of the other projects 18:11:58 mtaylor: yes please 18:12:16 mtaylor: thanks, wasn't sure on that one 18:12:24 #topic next-steps 18:12:52 So I'd like to propose continuing the usage of the etherpad for starters 18:13:11 if anybody sees something inparticular they'd like to tackle it would be good to keep this record up to date 18:13:14 jgriff: it probably works for another week, but we will want to move to blueprints once we figure out what we don't know ;) 18:13:30 I'd like to start opening up bugs/blueprints for anything new that's going to get merged in... easier to figure out what's getting worked on 18:14:07 rnirmal: fair 18:14:09 rnirmal: I think limiting to things we know need done - such as prototype http API extensions (#4 in decoupling work) 18:14:26 My proposal is this: 18:14:29 http://etherpad.openstack.org/cinder-worksheet 18:14:39 decoupling work, general structure etc is still in flux 18:14:46 use etherpad 18:14:57 building on top of what's there, features etc need bp 18:15:13 jgriff: I started outlining the basic flow of attaching a volume in nova 18:15:27 jgriff: in the etherpad, and how it 'should' work in the future 18:15:45 jgriff: it is a little complex and weird right now 18:16:02 vishy: I saw that, was thinking that's where I should probably copy it into a bp once it's a bit settled 18:16:15 like anotherjess mentioned, maybe another week of etherpad 18:16:22 Maybe a little less 18:16:46 also I don't think that precludes anybody from submitting bp's 18:18:03 it's probably worthwhile to hold off on new code submissions, till we get a base working copy with nova 18:18:24 I mean new features 18:18:24 rnirmal: I actually don't know if getting it working with nova is #1 goal 18:18:31 rnirmal: I think I agree but it's "all" new code :) 18:18:35 I would like it to work on its own 18:18:41 and expose the APIs nova would need 18:18:59 So I believe we are all on the same page 18:19:00 but the code changes to nova will be more complicated, so lets not block on them 18:19:13 We agreed previously, get nova functionality working before anything else 18:19:15 ok 18:19:24 in other words, existing nova-volume functionality 18:19:42 jgriff: define "nova functionality" - being able to do the functions or having nova actually using cinder? 18:20:03 I'd like to have nova actually use cinder before going into "new" features 18:20:10 mimic nova-volumes in current functionality 18:20:28 jgriff: let's start with operating cinder without nova 18:20:32 yeah, granted it might not be perfect but focus efforts on just getting it usable 18:20:35 like with some externall app 18:20:41 cinder is a service, having cinder do the right thing and having nova integrate well with cinder are different problem sets 18:21:05 vladimir3p: yep! we have python-cinderclient which we can make work with all the changes needed in the API to support volumes 18:21:12 (without a shared queue/db) 18:21:18 yeah, it will be the 1st step 18:21:29 nova tune-up will be a big step by itself 18:21:37 anotherjess: yeah, the nova side complicates 18:22:02 attach/detach first 18:22:07 if cinder could handle APIs properly and expose iSCSI devices - it is a good 1st milestone, IMHO 18:22:14 and then we can move into reserve/init connection if we want 18:22:20 I would like to try and get attach/detach working in F1 if possible 18:22:26 jgriff: agreed 18:23:21 so does anybody have time to dedicate/commit to some of these items? 18:24:26 hmm... ok, maybe that's to vague or commital 18:24:42 does everybody like what they see so far and agree with the direction still? 18:24:53 actually looks like initialize/terminate are more important 18:24:59 I just asked vishy what those where 18:25:08 that is how you actually get the iscsi connection information 18:25:26 initialize/terminate is what provides the connection info 18:25:27 anotherjesse: guess you can't attach/detach without that 18:25:38 attach/detach is just metadata 18:25:39 jgriff: yes 18:25:47 no it's the other way round 18:25:54 jgriff: I like it :-) can't commit for next couple of weeks. I would prefer to see more stuff in common rather copy/pasting to cinder 18:26:02 initialize/terminate is metadata that the volume service provides 18:26:19 vladimir3p: there should be a blueprint of blueprints to common-ize stuff 18:26:35 anotherjesse: ok 18:26:42 I'm starting to look at cinder, but can't commit this week. Might get chance to make some progress 18:26:50 vladimir3p: I started using the approach but was educated by anotherjess and vishy 18:26:57 :-D 18:27:12 vladimir3p: I think it's a good idea to work on this after getting goals for F1 and F2 18:27:18 vladimir3p: we can move things towards common, but don't block on it landing in common 18:27:27 anotherjess: exactly 18:27:28 yeah it's a nice to have at this point 18:27:39 anotherjesse: makes sense 18:27:52 I think nova will be striving for the same thing as well during Folsom 18:28:32 Does anybody see any glaring holes or things we didn't think of? 18:28:51 goal: (in a user story): a user can use python-cinderclient to create a volume, and get the iscsi attach info, then manually attach to their system (this assumes networks are accessible), then store things, dettach, move it to another server and see the info written in the first server, then detach and delete 18:29:40 +1 18:29:45 anotherjess: I plan to write something like that up and post on the wiki... 18:29:51 +1 18:29:57 +1 18:30:06 Also break it out and have stories per Folsom milestones 18:30:27 does that seem worthwhile/useful? 18:31:37 if I understand correctly this user story - the main functionality here is create/expose/delete. 18:31:38 Definitely. Helps have everybody pulling in a similar direction 18:31:50 the entier attach/detach is kind of optional metadata update within cinder 18:31:51 vladimir3p: create / use outside nova / delete 18:32:15 anotherjesse: use outside nova == any host with iSCSI init 18:32:27 #action also to vladimir3p's point we should create a blueprint about openstack common - and start creating child blueprints for subcomponents - a blueprint for scheduler, a blueprint for service.py, ... 18:32:35 vladimir3p: yep 18:32:51 anotherjesse: that should be in openstack-common right? 18:32:59 the blueprints.. cos it pertains to nova too 18:33:21 we can move blueprints around, and they can point to things in other projects 18:33:27 the important thing is to start writing them ;) 18:34:02 given that we deleted ~100k lines in nova to make cinder, it might be easier for us to look at things in cinder repo and see what shouldn't be there. 18:34:02 ok cool.. there's one for rpc already.. we'll just have to get the other ones out 18:34:31 rootwrap - https://github.com/openstack/cinder/tree/master/cinder/rootwrap 18:34:50 ... 18:35:46 rpc, notifier, some more of the wsgi and extensions functionality, not sure how much of that is in common already 18:38:25 rnirmal: probably about half I believe 18:38:45 k 18:39:04 alright, no reason to keep people hanging around for nothing.... 18:39:29 rnirmal: I know you started working on some things, antyhing you want to go on record with right now? 18:39:42 well I just have that one commit I need to make 18:40:04 ok 18:40:09 that removes the compute/versions stuff from the api... added the missing pieces into the volume api code 18:40:50 I'll just open a bug for it and submit it.. easier to do it that way for me 18:40:57 #action rnirmal submit his compute tear out and api work 18:41:51 jgriff: do we have jenkins setup to run the unit tests to gate commits? 18:42:00 rnirmal: yes 18:42:49 thanks to mtaylor for the infra setup 18:43:11 rnirmal: Yes, big thanks to mtaylor as well as jeblair !!! 18:43:44 all thanks should really go to jeblair - I'm just here to sign his paycheck... 18:43:46 :) 18:44:30 Ok, going forward: 18:44:45 Keep an eye on the etherpad for updates over the next few days 18:45:03 Keep an eye open for reviews needed in gerrit 18:45:25 Feel free to use email: [Openstack][Cinder] in the subject line 18:45:52 If you want to pick something up let folks know either IRC or ehterpad or both 18:46:03 (preferrably both) 18:46:11 Anybody have anything else? 18:47:52 alrighty.. thanks everyone, and HUGE thanks to anotherjesse vishy mtaylor and jeblair 18:47:55 #endmeeting