16:03:44 <jgriffith> #startmeeting cinder
16:03:44 <openstack> Meeting started Wed Sep  4 16:03:44 2013 UTC and is due to finish in 60 minutes.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:03:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:03:48 <openstack> The meeting name has been set to 'cinder'
16:03:55 <jgriffith> any cinder peoples about?
16:04:01 <bswartz> hi
16:04:03 <eharney> hello
16:04:04 * caitlin-nexenta waves
16:04:04 <DuncanT-> I'm here
16:04:06 <zhiyan> hello
16:04:07 <xyang_> hi
16:04:10 <kmartin> hi
16:04:11 <DuncanT-> Nothing on the agenda yet
16:04:16 <jgriffith> nope
16:04:23 <skolathu> Hello
16:04:29 <jgriffith> I'll just give some updates and open things up
16:04:43 <jgriffith> was hoping avishay would be around but apparantly he's off on vacation
16:04:50 <jgriffith> #topic reviews
16:04:53 <DuncanT-> Can I get a quick summary on where we are with the freeze and any exceptions please?
16:04:59 <jgriffith> DuncanT-: :)
16:05:05 <jgriffith> so on that....
16:05:12 <DuncanT-> (I've not been paying enough attention)
16:05:15 <jgriffith> everything that's been granted an exception thus far is in process
16:05:34 <jgriffith> there's nothing else that I'm planning on accepting especially at this point
16:05:41 <jgriffith> a few things were snuck in, but that's ok
16:05:43 <jjacob512> hi
16:06:08 <bswartz> what is the status of https://review.openstack.org/41868 ?
16:06:18 <jgriffith> https://launchpad.net/cinder/+milestone/havana-3
16:06:33 <jgriffith> So take a look at this list
16:06:46 <jgriffith> these are the items we should be focused on for reviews today
16:06:52 <zhiyan> jgriffith: do you like give some support for landing r/o-volume in nova side?
16:07:00 <jgriffith> zhiyan: I can try
16:07:01 <bswartz> okay cool
16:07:19 <zhiyan> jgriffith: cool
16:07:26 <eharney> what moves blueprints from "needs code review" to "implemented"?  is that a big red button jgriffith has on his desk or automatic?
16:07:36 * jgriffith currenlty
16:07:40 <jgriffith> eharney: ^^
16:07:51 <jgriffith> eharney: seems that the launchpad bot isn't very good lately
16:07:59 <jgriffith> eharney: I've been updating status
16:08:20 <jgriffith> eharney: it is supposed to be automagically picked up by the bots
16:08:52 <jgriffith> so any changes that are not in the 10 needed reviews on that LP page, please ignore for now :)
16:09:19 <skolathu> jgriffith: wanted to check on the FC plugin support..I had addressed pretty much all comments except the latest that came today morning from Navneet
16:09:19 <jgriffith> We need to focus on the NetApp and Dell EQL changes
16:09:34 <jgriffith> skolathu: I'm a bit concerned about your timing on that
16:10:39 <skolathu> jgriffith: Yeah, I know it got a little late. I had been working on the comments during last few days..
16:10:50 <skolathu> I am clearing the new comments also now
16:11:10 <skolathu> Hope there won't be any other gating issues
16:11:30 <jgriffith> Just a reminder today is the cut off for H3
16:11:46 <jgriffith> thus the concern with rushing something like that through
16:11:59 <jgriffith> skolathu: it doesn't seem like it's ready IMO
16:12:31 <jgriffith> anybody else have thoughts?
16:12:41 <jgriffith> hemna: DuncanT- eharney ?
16:13:18 <kmartin> hemna is driving into the office
16:13:20 <skolathu> jgriffith: I think I can clear all comments till now today. But are you suggesting there has to be more reviews?
16:13:20 <eharney> any h-3 bugs need attention?
16:13:35 <DuncanT-> It still seems to be getting a lot of feedback to me
16:14:14 <jgriffith> eharney: a few, however the priority is features
16:14:24 <jgriffith> eharney: we have milestones for bugs still :)
16:14:25 <DuncanT-> 56 comments on the latest review... that's enough to make me wary
16:15:02 <jgriffith> DuncanT-: ?
16:15:09 <eharney> jgriffith: we might as well punt that LVM volume clearing bug off of h-3 at least
16:15:11 <jgriffith> DuncanT-: NM
16:15:18 <DuncanT-> jgriffith: The FC stuff
16:15:26 <jgriffith> DuncanT-: yeah, I'm with ya
16:16:06 <jgriffith> skolathu: I'm willing to see how it plays out
16:16:14 <jgriffith> eharney: sure
16:16:47 <jgriffith> anyway... my whole point was:  The bp's that need review have to be priority today
16:16:56 <jgriffith> there's a lot of complaining lately about review tims
16:16:58 <jgriffith> times
16:17:16 <jgriffith> I want to remind that submitters are responsible for timely turn around as well
16:17:19 <jgriffith> it goes both ways
16:17:36 <jgriffith> and it will help your karma considerably to do reviews on other peoples code as well
16:17:43 <jgriffith> cinder is not a dumping ground for code/drivers
16:18:01 <jgriffith> any questions/concerns?
16:18:22 <jgriffith> # topic retype
16:18:27 <jgriffith> #topic retype
16:18:34 <skolathu> jgriffith, DuncanT: I think the new comments are pretty straightforward and should be easy..I'll address them shortly and will see how it goes.
16:18:41 <jgriffith> so I started working on retype command
16:18:55 <jgriffith> but there's some conflicting views on what this should be
16:19:01 <kmartin> will retype require driver changes?
16:19:07 <jgriffith> my thought was local retype, with no migration
16:19:30 <jgriffith> avishay however submitted a patch that copies that but also makes it do a migration
16:19:35 <jgriffith> kmartin: it would
16:19:42 <jgriffith> seems to me that it's too late in the game
16:19:56 <kmartin> I agree
16:19:58 <jgriffith> since there's disagreement on what it should do etc
16:20:20 <jgriffith> and I'm also not sure about migration functionality as it is
16:20:32 <kmartin> did the same thing last release with config and half the drivers were broke out of the gate
16:20:35 * DuncanT- wants it to do everything. With unicorns on top
16:20:53 <jgriffith> DuncanT-: quadricorns!!!
16:21:05 <jgriffith> kmartin: fair
16:21:10 * DuncanT- starts on a blueprint
16:21:13 <jgriffith> alright, I'm going to defer it
16:21:27 <kmartin> jgriffith: +1
16:21:56 <jgriffith> #topic other questionable bp's
16:22:01 <jgriffith> https://blueprints.launchpad.net/cinder/+spec/volume-acl
16:22:43 <jgriffith> Personally I feel this introduces a good deal of un-needed complexity
16:22:54 <jgriffith> I'd like to get other people to provide input and feedback
16:23:03 <kmartin> agree
16:23:15 <eharney> how many people have a good understanding of this work at this point?
16:23:24 * DuncanT- doesn't any more
16:23:29 <eharney> i know i don't
16:23:41 <kmartin> not me
16:23:43 <jgriffith> ok, sounds to me like this one's out
16:24:06 <jgriffith> agreed?
16:24:45 <jgriffith> TBH I'd much rather wait and do a proper/clean integration via keystone
16:24:53 <hemna> k
16:25:05 <DuncanT-> Makes sense to me
16:25:22 <zhiyan> jgriffith: sounds good to me
16:25:28 <caitlin-nexenta> Also makes sense to me. Let keystone/nova/whomever worry about this.
16:25:29 <kmartin> +1
16:25:48 <jgriffith> kk
16:26:01 <jgriffith> so from my perspective everything else on the list right now is a go
16:26:20 <jgriffith> That give us 9 patches as the priority
16:26:43 <jgriffith> anything people see missing from that list, or disagreements with what's there?
16:26:57 <jgriffith> keep in mind the "add tests in test_db api" can be late if need be
16:27:14 <jgriffith> changes to tests are part of feature freeze
16:27:21 <jgriffith> s/are/aren't/
16:28:39 <jgriffith> Ok... guess that it then :)
16:28:43 <eharney> one question
16:28:44 <jgriffith> #topic open-discussion
16:28:48 <jgriffith> eharney: go for it
16:28:55 <eharney> what's the schedule/policy/etc around cinderclient changes at this point?
16:29:06 <jgriffith> eharney: cinderclient is an open book :)
16:29:14 <jgriffith> eharney: it's not tied to milestones
16:29:16 <topshare> have someone use ceph?
16:29:22 <eharney> good, because i'm probably going to propose something soon
16:29:31 <eharney> thanks
16:29:39 <jgriffith> eharney: I'll do a tag to pypi later next week and then problem another before final release
16:29:44 <jgriffith> eharney: :)
16:29:49 <jgriffith> topshare: say what?
16:30:41 <jgriffith> so I want to spend today and the rest of the week just focusing on H3
16:30:59 <jgriffith> we'll start up on some other things like the driver qual etc first thing next week
16:31:11 <jgriffith> I'll get the code up and start talking to folks about some different ideas
16:31:22 <jgriffith> anybody have anything else?
16:31:48 * DuncanT- would like to know if anybody considers themselves well versed in policy stuff?
16:31:54 <jgriffith> DuncanT-: :)
16:32:09 <DuncanT-> (because I unserstand even less than I thought I did)
16:32:25 <jgriffith> DuncanT-: yeah... sadly I thought I knew more than I do there as well
16:32:31 <zhiyan> jgriffith: can you add this to you list: https://review.openstack.org/#/c/44455/
16:32:48 <jgriffith> For everybody's benefit the goal is to figure out how to disable extensions
16:33:11 <guitarzan> some way other than just manually enabling all the extensions you want?
16:33:39 <jgriffith> guitarzan: even that would be fine via policy file
16:33:51 <eharney> i'm not sure about the context here (something with extend volume right?)
16:34:02 <jgriffith> guitarzan: but I *thought* you could enable/disable specific actions in the volume_actions module
16:34:11 <DuncanT-> Specifically I want to disable extend and only extend
16:34:12 <guitarzan> ah, we disable entire extensions just via cinder.conf
16:34:13 <jgriffith> eharney: yes, be able to disable os-extend
16:34:19 <DuncanT-> I can't find a syntax to do it
16:34:25 <guitarzan> DuncanT-: let me look
16:34:33 <eharney> you may be able to do it via policy.json
16:34:39 <DuncanT-> Thanks all
16:34:41 <eharney> set rule is_admin etc
16:34:51 <DuncanT-> https://bugs.launchpad.net/cinder/+bug/1220752 is the bug
16:34:53 <uvirtbot> Launchpad bug 1220752 in cinder "Can't disable extend_volume call via policy" [Undecided,New]
16:34:58 <jgriffith> eharney: that's something I tried but didn't work out the way I'd hoped :)
16:35:08 <jgriffith> eharney: I set a new role "disabled_exts"
16:35:23 <jgriffith> eharney: and assigned that to the extension in the policy file
16:35:29 <jgriffith> eharney: I may have missed something
16:35:35 <eharney> jgriffith: some of the work we just did in Nova also tied whether the extension was enabled to whether you were coming in via publicURL API or adminURL
16:35:45 <eharney> maybe another thing to consider but i'm still kinda fuzzy there on the exact details
16:35:50 <guitarzan> nova's policy engine is smarter than cinders
16:35:53 <jgriffith> eharney: ahhh...
16:35:54 <eharney> ah
16:36:01 <jgriffith> guitarzan: :(
16:36:21 <eharney> there was a bug out there somewhere about porting Cinder to use oslo's policy code but i'm not sure where it ended up
16:36:21 <guitarzan> I saw some of the syntax the cloud servers guys use and it doesn't work in cinder
16:37:03 <jgriffith> eharney: it was a nightmare!
16:37:21 <jgriffith> eharney: I started working on it, then somebody said they wanted to take it..
16:37:21 <eharney> :)
16:37:33 <jgriffith> eharney: I think his name started with hem and ended with a
16:37:36 <jgriffith> :)
16:37:36 <guitarzan> it looks like you should be able to do policy out the volume api extend call...
16:37:55 <jgriffith> Ok, let's take that offline and see if we can get it to work as expected
16:38:02 <jgriffith> anything else?
16:38:05 <DuncanT-> Appreciated
16:38:18 <eharney> just thanks for everyone reviewing stuff
16:38:25 <jgriffith> indeed!
16:38:39 <jgriffith> big thank you to EVERYBODY!
16:38:52 <jgriffith> 3'rd milestone is always hectic
16:39:03 <jgriffith> but this one's going well I think with the soft freeze
16:39:20 <jgriffith> Ok.... one more day of review focus please :)
16:39:33 <jgriffith> remember turn around time on comments/feedback
16:39:59 <jgriffith> and don't be crazy about typos in comments and such at this stage if you can avoid it :)
16:40:03 <jgriffith> thanks everyone!
16:40:08 <jgriffith> #endmeeting cinder