18:01:37 #startmeeting 18:01:38 Meeting started Thu May 10 18:01:37 2012 UTC. The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:01:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:01:54 Role call? 18:03:04 Wow.. nobody? 18:03:11 Present, couldn't possibly comment on being correct 18:03:43 DuncanT: pheww, just go with correct 18:04:10 Well I guess this might be rather short unless we get some folks late 18:04:21 #topic last weeks action items 18:04:53 rnirmal caught up with me this morning, and unfortunately didn't get much done last week 18:05:01 vladimir: you here? 18:05:46 Those were two we had, sounds like no updates 18:05:46 Sorry I'm late. 18:05:59 Mandell: no problem, glad you're here 18:06:42 So vladimir was going to work on openstack common, haven't seen anything there 18:07:03 rnirmal was working on some compute tear out and api work, but didn't get to it last week 18:07:38 I've pushed a change to drop the instance relationship from volumes, need review :) 18:07:46 Mandell: thanks! 18:07:59 Still needs approved etc 18:08:05 I saw that, haven't had time to look yet but will do tomorrow if not before 18:08:21 DuncanT: thanks! much appreciated 18:08:42 which brings me to the next topic... 18:08:50 #topic reviews 18:09:09 So there hasn't been a "ton" of activity but... 18:09:25 o/ 18:09:31 There are a couple items that have been submitted and just sit 18:09:38 vishy: Yo 18:09:56 Just want to make sure folks that signed up for core are able to help out here 18:10:19 Doesn't seem right for me to review, +1, +2 and A my own changes :) 18:10:32 We have out public-beta go-live today so it has been kind of hectic... will definitely make time to keep up 18:10:47 DuncanT: No worries, I understand 18:10:55 Just wanted to put a reminder out 18:11:16 #topic current status for cinder 18:11:30 Is there a dashboard for outstanding cinder reviews? 18:11:45 I've not used gerrit in anger all that much.... 18:11:51 DuncanT: Youre core so should be getting emails, else just look in gerrit 18:12:04 ok 18:12:06 Not a ton there but want to form good habbits :) 18:12:51 So I've been doing some work on seperating instance relationships and working on cinderclient 18:13:04 vishy: has been doing a bunch of work on the compute tear out 18:13:09 vishy: updates? 18:14:03 Or any updates on work other folks are doing/planning? 18:14:49 jgriffith: haven't been working on anything yet :( 18:15:05 I've only gotten as far as pulling the code and getting the unit tests working, and that was only today 18:15:10 jgriffith: but I still have plans to do step 3 on the blueprint 18:15:16 vishy: :) 18:15:39 DuncanT: unit tests should have already been working? 18:16:13 DuncanT: did you have an issue running them? 18:16:19 jgriffith: Yeah, I was getting them working without virtual env, so I can package cinder for our test infrastructure 18:16:25 Ahhh 18:16:43 virtual env worked out of the box, dpkg based run didn't take long 18:17:04 DuncanT: ok 18:17:16 I'll put some packaging files somewhere accessible once they are working 18:17:23 DuncanT: great 18:17:46 Also need volunteers from core to hit mtaylors change in gerrit as well 18:18:03 jgriffith: has anyone tried updating python-cinderclient yet? 18:18:08 Mine can wait until it hits nova 18:18:11 that should be a chunk of work 18:18:19 vishy: I started working on that about 30 minutes ago 18:18:30 and yes, it seems like a good chunk 18:18:42 nice, you probably need to pull in all of the changes from novaclient 18:18:50 and then we can reset the repo like we did for cinder 18:18:50 vishy: I'm currently putting in fakes for the delete/list/detail tests 18:19:01 vishy: Ahh... repo is set 18:19:11 vishy: Sorry, I should've mentioned 18:19:33 mtaylor apparently had the forethought to pull your version in as the base :) 18:20:06 vishy: Oh, I think I see what you're saying now. 18:20:22 jgriffith: i mean get rid of annoying history :) 18:20:28 Rather than use the base you had set up pull in novaclient and rip appart 18:20:35 Ohhh 18:20:41 jgriffith: no that is what i did 18:20:52 but there have been a number of fixes/changes to novaclient since i split 18:20:59 vishy: I'm with ya... take three or four tries but I catch up 18:20:59 which it would be nice to get in 18:21:51 vishy, jgriffith do you guys want/need to start the cinderclient repo over like we did for cinder? 18:22:00 vishy: I planned to work on that next assuming my instance ref's patch doesn't get rejected :) 18:22:16 jgriffith: i'm reviewing it now 18:22:17 mtaylor: Yes, but after I makes some changes today and tomorow 18:22:19 looking good so far 18:22:28 * jgriffith sigh of relief 18:23:00 mtaylor: BTW sorry about the "false" bug to set up the repo :( 18:23:52 #action jgriffith get cinderclient up to speed and ask mtaylor to reset repo when ready 18:24:22 anybody else looking for ways/places to help out? 18:24:58 Just a reminder we had a goal of having base functionality at F1 I think, which is approaching very quickly 18:26:04 ok, one more thing from my side no cinder... 18:26:07 All I can commit to for the next couple weeks is reviews, but I'll commit to one a day. 18:26:23 Mandell: Reviews are a huge help so that's great 18:26:59 So there was a submission for auto cleanup of orphaned volumes: 18:27:09 #link https://review.openstack.org/#/c/7314/ 18:27:26 I wanted to get other volume folks opinion... 18:27:42 I'd rather see this manual or configurable via conf file? 18:28:09 Agree/Disagree? 18:28:27 Definitely don't like it being manual 18:29:05 Just reading through the patch, but I can't see it being something we want turned on 18:29:18 DuncanT: You mean automatic? 18:29:39 Yeah 18:29:59 DucanT: Ahh ok 18:30:01 Possibly at all 18:30:24 If users want to keep volumes lying around, who are we to argue? 18:30:30 DuncanT: yeah, but I can see the desire to go through and do cleanup but I don't like the idea of having it take place on it's own 18:30:47 Providers may like that depending on how they do their billing :) 18:30:53 Possibly an api to list 'orphan' volumes? 18:31:10 I think that can be done purely in the client TBH 18:31:24 DuncanT: Actually that's a bette approach than what i had in mind, and yes it can 18:32:01 DuncanT: The needed functionality is already there, just query via the api and delete if you want 18:32:15 jgriffith: reviewed, have three extra chunks of code that can be deleted, otherwise looks great 18:32:30 vishy: awesome THANKS!!! 18:32:41 jgriffith: Agreed 18:33:12 autoclean is not good 18:33:17 DuncanT: Ok, I'll update my review and put our reasoning in 18:33:29 at least in nova. I don't mind a deployer doing it externally 18:33:42 vishy: I didn't think so... exactly, external is easy enough 18:33:49 if a user creates a volume and doesn't use it that is fine 18:34:06 a task to log a notification or something would make sense 18:34:07 Ok, I'll update my review of it accordingly but that's where I was headed with it 18:34:13 but deleting it seems really bad. 18:34:49 I thought it seemed really dangerous personally, especially if it's not at least configurable (on/off/interval) 18:35:06 but as DuncanT pointed out it's really not necessary to have in the code at all 18:35:24 Just external via the api can accomplish for somebody that wants it 18:35:58 rnirmal: you made it :) 18:36:22 well logged in..but still in another meeting 18:36:29 :) 18:36:47 Anybody else have anything they want to bring up? Questions/Concerns ? 18:37:02 Is this meeting worthwhile for you? 18:38:14 The nice thing about no response is I can interpret it any way I like :) 18:38:18 It's good to see progress, and also means there is at most a week between kicks, so yes 18:39:05 DucnanT: cool... I'll be here no matter what so just want to make sure folks don't want to see something different 18:39:19 or "need" something different 18:39:49 I do believe the pace will start picking up significantly with each week 18:40:11 vladimir3p: Hey there 18:40:25 hey 18:40:30 sorry :-) 18:40:38 vladimir3p: Any updates on openstack-common? 18:40:40 had couple customers meetings 18:40:48 nope :-) 18:40:51 vladimir3p: NP 18:41:05 vladimir3p: :) 18:41:25 Alright, well I was going to go ahead and wrap up if nobody has anything.... 18:41:46 vladimir3p: if you want to catch up we can do so offline or you can grab the minutes off of eavesdrop 18:42:12 jgriffith: it will be great to talk offline - might be faster 18:42:17 Oh... one other thing, I think the etherpad is probably not the place to add anything any longer 18:42:38 vladimir3p: sounds good 18:42:41 lets start opening blueprints and bugs to work on items 18:42:50 rnirmal: +1 18:43:24 the etherpad is still good reference for some stuff, but anything new anybody wants to grab we start using the formal process 18:43:41 Ok... well if there's nothing else? 18:44:20 Alright, thanks everyone. Ping me if you think of anything 18:44:24 #endmeeting