16:00:36 <jgriffith> #startmeeting cinder
16:00:37 <openstack> Meeting started Wed Feb 27 16:00:36 2013 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:40 <openstack> The meeting name has been set to 'cinder'
16:00:50 <thingee> o/
16:00:53 <jgriffith> Hey everyone, sorry I literally just walked in
16:00:57 <xyang> hi
16:01:15 <guitarzan> literally!
16:01:19 <guitarzan> (morning folks)
16:01:25 <avishay> hi all
16:01:26 <rushiagr> hi!
16:01:28 <smulcahy> hello
16:01:38 <jgriffith> guitarzan: yes, literally :)
16:01:53 <jgriffith> Alright, let's get started
16:01:56 <jgriffith> First things first
16:02:00 <jgriffith> #topic reviews
16:02:24 <jgriffith> Don't forget, just because the push for G3 is done we should still be seeing bug fixes and such coming in
16:02:42 <jgriffith> enough said there
16:02:47 <jgriffith> #topic bugs
16:03:16 <jgriffith> Our list is growing rapidly https://bugs.launchpad.net/cinder
16:03:34 <jgriffith> I started triage and target last night and should get back to it today
16:03:45 <avishay> s/Our/NetApp's/ :P
16:03:45 <jgriffith> rushiagr: Looks like you've got a lot on your plate
16:03:48 <smulcahy> I'm tackling the ones I opened yesterday
16:04:10 <rushiagr> jgriffith: I see. Already started swallowing pieces in :)
16:04:11 <jgriffith> smulcahy: awesome, can you assign them to yourself if you haven't already?
16:04:26 <jgriffith> :)
16:04:34 <smulcahy> yup, did so already
16:04:35 <jgriffith> rushiagr: That's the down side of actually testing your code :)
16:04:40 <jgriffith> smulcahy: excellent
16:05:00 <bswartz> hi
16:05:01 <jgriffith> eharney: around?
16:05:05 <eharney> yep
16:05:05 <jgriffith> bswartz: morning
16:05:22 <jgriffith> eharney: any updates on the rtslib issue?
16:05:37 <eharney> i think i saw an update related to the pkg-info part of it
16:06:01 <rushiagr> jgriffith: agree. many drivers == increased chances of bugs
16:06:03 <eharney> but i haven't gotten too far into it yet
16:06:43 <jgriffith> eharney: Ok, so what do you think about removing rtslib from pip-requires for now?
16:07:03 <jgriffith> eharney: well more accurately "for now" would be for Grizzly
16:07:18 <jgriffith> eharney: We can wait before being drastic
16:07:29 <bswartz> rtslib is needed by the 3par driver, right?
16:07:35 <jgriffith> bswartz: no
16:07:38 <jgriffith> bswartz: LIO driver
16:07:44 <bswartz> oh I'm mixed up
16:07:47 <jgriffith> or "iSCSI target"
16:07:48 <eharney> i can look into it and see... that was kind of my original intent a while back
16:07:50 <jgriffith> bswartz: you and I both
16:08:04 <eharney> let me see what this pkg fix brought in and where things stand now
16:08:17 <jgriffith> eharney: cool
16:09:06 <jgriffith> winston-d_: any luck on stevedoore and errors/exceptions?
16:10:05 <jgriffith> Fort thos who don't know:
16:10:08 <winston-d_> jgriffith: i'm working on a patch for OSLO
16:10:31 <jgriffith> winston-d_: great, did you open an OSLO bug on that?
16:10:49 <jgriffith> sorry.. to keep buggin ya :)
16:10:53 <avishay> jgriffith: for those who don't know: ...
16:10:56 <avishay> ?
16:11:05 <jgriffith> avishay: Yeah... trying to find the bug now :)
16:11:12 <winston-d_> jgriffith: not yet.
16:11:21 <avishay> jgriffith: OK, thought you forgot :)
16:11:48 <jgriffith> So there are cases where the filter scheduler will say like "Unable to find filter-scheduler, capacity-weigher" etc etc
16:12:09 <jgriffith> Turns out if there's package conflicts in the pip requires or issues with loading them
16:12:28 <jgriffith> SteveDoore (which loades them, and the filter scheduler settings) pukes
16:12:34 <kmartin> this one https://bugs.launchpad.net/cinder/+bug/1131322
16:12:35 <uvirtbot> Launchpad bug 1131322 in cinder "Cinder service not logging exceptions from stevedore library" [High,Confirmed]
16:12:36 <jgriffith> but it doesn't use the Cinder log
16:12:45 <jgriffith> kmartin: is my hero
16:12:46 <jgriffith> :)
16:13:21 <jgriffith> anyway, so far it's only seen on > Precise
16:13:33 <jgriffith> So Quantal and Raring set-ups
16:13:53 <avishay> Got it
16:14:13 <jgriffith> So final thing on bugs from me...
16:14:29 <jgriffith> If you have bugs that you're working on PLEASE be sure to update the bug and assign it to yourself
16:14:40 <jgriffith> Also if you want to talk to me about targetting ping me on IRC
16:15:03 <jgriffith> If you have a bug you want targetted for RC1 and I haven't done it by the end of the day I likely missed it so hit me up
16:15:05 <thingee> jgriffith: is the force delete volume even with snapshots associated worth it?
16:15:13 <thingee> the one gabriel made
16:15:14 <jgriffith> Or target it yourself
16:15:22 <jgriffith> thingee: link?
16:15:45 <jgriffith> thingee: I'm not inclined to allow delete of volume with snapshot still/yet
16:15:52 * guitarzan sighs
16:16:14 <thingee> jgriffith: launchpad is not loading for me. well he wouldn't be able to make the experience better on horizon at this point anyways
16:16:16 <jgriffith> guitarzan: we can look at it if it's really a problem for folks, but it is a bigger change than I'd like to put in at this point
16:16:25 <jgriffith> thingee: booo Luanchpad
16:16:39 <jgriffith> thingee: true-dat
16:16:39 <guitarzan> yeah, the "at this point" totally makes sense
16:16:59 <jgriffith> thingee: I'd rather see jdurgin's boot from image patch go into horizon before anything else anyway
16:17:19 <jgriffith> IMO it's a bug that horizon doesn't have the cinder functionality in it
16:17:29 <jgriffith> guitarzan: k... cool
16:17:44 <jgriffith> Ok... anybody else with input/updates regarding bugs?
16:17:49 <avishay> Horizon is missing lots of Cinder stuff
16:17:49 <thingee> jgriffith: +1
16:17:54 <jgriffith> avishay: Yes
16:18:06 <avishay> jgriffith: Can we discuss this: https://bugs.launchpad.net/cinder/+bug/1131553
16:18:07 <uvirtbot> Launchpad bug 1131553 in cinder "SolidFire driver hasn't been updated to use self.configuration" [High,In progress]
16:18:09 <thingee> jgriffith: jdurgin had the patch done, but no one to review it
16:18:29 <jgriffith> avishay: sure
16:18:40 <jgriffith> avishay: what would you like to discuss?
16:19:00 <avishay> jgriffith: where did this self.configuration thing come from and how did i miss it and what do i need to do :)
16:19:12 <rushiagr1> avishay: with multi backend
16:19:19 <jgriffith> avishay: multi-back-end and filter scheduler
16:19:27 <jgriffith> avishay: don't feel bad, we all missed it :(
16:19:32 <jgriffith> avishay: well not all of us
16:19:34 <winston-d_> avishay: multi-back-end
16:19:54 <jgriffith> avishay: So hub_cap updated most of the drivers for folks, but a few us were left behind
16:20:24 <avishay> jgriffith: OK, I'll take another look at it
16:20:32 * hub_cap is sorry
16:20:34 <jgriffith> avishay: so it's not a tough patch, but if you don't have time I plan to have a general bug for all the drivers
16:20:40 <jgriffith> and I'll update it for you if you don't get to it
16:20:51 <jgriffith> Just won't be until end of next week
16:21:07 <avishay> jgriffith: OK no problem, I'll do it
16:21:18 <jgriffith> avishay: cool... let me know if you have any questions on it
16:21:19 <avishay> Just wanted some background info
16:21:23 <avishay> Thanks
16:21:23 <jgriffith> avishay: it's pretty straight forward
16:21:24 <kmartin> We are getting ready to submitted a patch for the 3PAR drivers today
16:21:29 <avishay> jgriffith: yea i saw
16:22:06 <jgriffith> kmartin: cool, I think that'll get everybody caught up, but I'll double check Nexenta and Zadara next week
16:22:19 <jgriffith> anybody else?
16:22:26 <smulcahy> in terms of submitting bug fixes, jenkins was blowing up on a pyparsing issue earlier - has that been fixed now or is it still in a non-functional state?
16:22:29 <kmartin> Do we still need to reference the FLAG = flags.FLAGS or can all that go away?
16:22:44 <xyang__> jgriffith: I'll be submitting a patch for my driver soon as well
16:22:50 <smulcahy> and when its fixed, can I retrigger a review to jenkins or do I need to submit a patch to cause that to happen?
16:22:50 <jgriffith> smulcahy: Yeah, I just started looking at that but like I said I got a late start this morning :(
16:23:21 <smulcahy> jgriffith: np, just wonder. there seemed to be a discussion on openstack-dev mailing lists but didn't fully understand what the solution was from it.
16:23:21 <jgriffith> smulcahy: Should be able to recheck, I'll scrub those when I get updated on the CI status this morning
16:23:25 <avishay> smulcahy: just leave a comment with "recheck"
16:23:45 <rushiagr1> I see the latest jenkins build managed to pass
16:23:46 <jgriffith> smulcahy: avishay yes, but don't forget to assign bug to the recheck please
16:24:23 <avishay> jgriffith: yep
16:24:28 <jgriffith> alrighty...
16:24:33 <smulcahy> jgriffith: "assign bug to the recheck" - don't fully grok that, is it documented in the wiki or can someone explain further?
16:24:50 <jgriffith> smulcahy: Yeah... so under the jenkins fail entry
16:24:57 <avishay> smulcahy: https://wiki.openstack.org/wiki/GerritJenkinsGithub#Test_Failures
16:25:01 <jgriffith> smulcahy: There's a link to a wiki with instructions
16:25:11 <jgriffith> teamwork rocks!
16:25:16 <jgriffith> avishay: thx :)
16:25:19 <avishay> jgriffith: google rocks :P
16:25:36 <smulcahy> awesome! ;)
16:25:38 <jgriffith> Oh... one other thing
16:25:54 <jgriffith> On bugs, make sure you use tags where appropriate
16:26:03 <jgriffith> ie Driver, SolidFire etc etc
16:26:25 <jgriffith> Also if you think it's backport potential mark that as well, although most of what i'm seeing so far is "new" code
16:26:46 <jgriffith> Ok, any final discussions WRT bugs?
16:26:55 <xyang__> jgriffith: do we have to open a bug for every submit now?
16:27:11 <jgriffith> xyang__: technically yes, you should
16:27:23 <jgriffith> xyang__: but what did you have in mind?
16:27:48 <jgriffith> xyang__: So for things like updating the Flags usage I don't really care personally
16:27:50 <xyang__> jgriffith: It is a fix for my driver.  has to do with attach
16:28:03 <jgriffith> xyang__: yes, you should log a bub please
16:28:13 <xyang__> jgriffith: sure, will do
16:29:02 <jgriffith> k
16:29:11 <jgriffith> #topic open discussion
16:29:17 <jgriffith> So for those that don't know
16:29:25 <jgriffith> There's been funny stuff going on in the gates
16:29:45 <jgriffith> One of the issues I've been looking at is "services not starting"
16:30:03 <jgriffith> So when you look at that bug list for jenkins jobs you have to be pretty thorough
16:30:19 <jgriffith> You'll notice a lot of things get marked as "cinder fails to create volume" etc etc
16:30:42 <jgriffith> But if you dig in you'll notice in reality it might be things like compute instance never started
16:30:49 <jgriffith> cinder-vol service never started
16:30:51 <jgriffith> etc etc
16:31:11 <jgriffith> My point is just if you do log a bug against a jenkins recheck try to be thorough if you can
16:31:16 <jgriffith> nuff said
16:31:38 <jgriffith> Also keep in mind DOCS!
16:31:59 <jgriffith> We need to make sure Grizzly goes out in better shape than Folsom did in terms of Docs
16:32:11 <jgriffith> I know a lot of folks are already working on this but just wanted to mention it again
16:32:40 <avishay> jgriffith: any administration stuff about the summit?  suggesting topics, etc.?
16:32:41 <jgriffith> and with that I'm done, anybody else have anything?
16:33:00 <jgriffith> avishay: submit your topics/suggestions to the website
16:33:26 <jgriffith> avishay: Once we get our time slots we'll start going through them and prioritizing based on time constraints
16:33:58 <avishay> jgriffith: where on the website?
16:34:06 <jgriffith> avishay: http://summit.openstack.org/
16:34:12 <avishay> not summit presentations, right?
16:34:33 <jgriffith> avishay: Yeah, that's confusing... the link I just posted is "design summit" session proposals
16:34:50 <jgriffith> Not the general "summit sesssions" for the foofy business folks and such :)
16:34:58 <avishay> jgriffith: :)
16:35:18 <avishay> so we can move those topics that were on the cinder wiki to here
16:35:25 <jgriffith> yeppers
16:36:12 <jgriffith> anyone else?
16:36:35 <avishay> (BTW looks like I will be there)
16:37:07 <jgriffith> avishay: I had assumed, didn't know there was a chance you wouldn't
16:37:19 <kmartin> avishay: :)
16:37:21 <avishay> jgriffith: it's far and expensive - had to get approval
16:37:32 <jgriffith> avishay: well glad you'll be there
16:37:48 <avishay> thanks, looking forward to meeting everyone
16:38:05 <jgriffith> ditto
16:38:52 <winston-d_> hopefully i can get my approval as well.
16:39:00 <jgriffith> winston-d_: you better!
16:39:08 <jgriffith> winston-d_: If not we'll take up a collection :)
16:39:21 <winston-d_> :)
16:39:27 <jgriffith> winston-d_: let us know if we need to harass your boss!
16:39:51 <winston-d_> haha, sure. thx!
16:40:06 <jgriffith> Ok, anybody else?
16:40:19 * jgriffith is thinking we might finish early for the FIRST TIME EVER
16:40:33 <jgriffith> at least the first time while he's been chairing :)
16:40:39 <bswartz> jgriffith: +1
16:40:46 <kmartin> speaking of the summit...is Stefano going to send out free registration codes to G-3 technical contributors
16:41:01 <bswartz> kmartin: that happened weeks ago
16:41:02 <xyang__> kmartin: I've got a free pass
16:41:15 <jgriffith> kmartin: bswartz There was supposed to be another round after G3
16:41:19 <avishay> I got mine a long time ago
16:41:20 <xyang__> kmartin: for being a contributor for the 1st time
16:41:24 <jgriffith> kmartin: There was something on the ML about that
16:41:38 <jgriffith> kmartin: I'd send an email IIWY
16:42:01 <kmartin> jgriffith: OK will do..I submitted late in G-3 but happen received mine yet
16:42:18 <jgriffith> kmartin: Yeah, I seem to recall there was a plan for that
16:42:25 <xyang__> jgriffith: do they usually give out free pass to every contributors?
16:42:33 <jgriffith> xyang__: yep
16:42:42 <xyang__> jgriffith: cool!
16:43:17 <jgriffith> alright, bswartz and I would like to finish early at least once!
16:43:25 <avishay> +1 for early
16:43:27 <jgriffith> #openstack-cinder of course
16:43:32 <jgriffith> #endmeeting cinder