22:03:00 <gabrielhurley> #startmeeting horizon
22:03:01 <openstack> Meeting started Tue Feb 12 22:03:00 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:03:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:03:04 <openstack> The meeting name has been set to 'horizon'
22:03:30 <gabrielhurley> #topic Status and Overview
22:03:42 <gabrielhurley> Coming into the final week of real activity
22:03:45 <gabrielhurley> lots of reviews up
22:03:51 <gabrielhurley> lots of blueprints with reviews up particularly
22:03:58 <gabrielhurley> I've commented on almost all of 'em
22:04:08 <gabrielhurley> got my own BP review up
22:04:14 <gabrielhurley> (I wrote code, yay!)
22:04:26 <gabrielhurley> In general everything's looking good and going the right direction
22:04:34 <gabrielhurley> just need everyone to be really active and diligent for this week
22:04:44 <gabrielhurley> I will do reviews every day
22:05:02 <gabrielhurley> I don't see anything that's got a review up there that can't make it though.
22:05:06 <gabrielhurley> #topic Blueprints
22:05:29 <gabrielhurley> davidlenwell seems to have escaped me
22:05:45 <gabrielhurley> was ginna grill him on the file upload UI blueprint
22:05:47 <gabrielhurley> *gonna
22:06:18 <cody-somerville> I'll ping him.
22:06:29 <gabrielhurley> cody-somerville got up a review for the Glance image upload which may have to suffice for Grizzly. It gets the job done, but I was hoping to have things be cool/fancy. Thanks to Cody for getting that far though,
22:06:52 <gabrielhurley> In Havana we can work with the Glance team to think about direct upload mechanisms with pretty progress indicators and such
22:07:23 <gabrielhurley> amotoki doesn't seem to be around currently either, but I'll follow up with him on the Quantum Security Groups blueprint.
22:07:28 <gabrielhurley> I'm not worried there, though.
22:08:03 <gabrielhurley> cody-somerville: if you could tell davidlenwell that my inclination is to drop that blueprint from Grizzly unless there's a review in the next two days I'd appreciate it.
22:08:12 <cody-somerville> Will do.
22:08:26 <gabrielhurley> anybody else got blueprints they want to discuss?
22:08:45 <kspear> gabrielhurley: other than pleading for a review? :)
22:09:00 <gabrielhurley> I'm gonna go through 'em all again today
22:09:13 <gabrielhurley> #topic Bugs
22:09:27 <gabrielhurley> I narrowed down the bug list to close out G3.
22:10:04 <gabrielhurley> There's also one new one for enabling the XFrameOptionsMiddleware byu default
22:10:16 <gabrielhurley> it's a termendously simple change but it's a good security practice
22:10:21 <gabrielhurley> *tremendously
22:10:31 <gabrielhurley> I wanna make sure that's merged for Grizzly
22:10:50 <gabrielhurley> #topic General Discussion
22:11:02 <gabrielhurley> I've got one topic for general discussion today
22:11:21 <mrunge> I have met one bug
22:11:34 <gabrielhurley> go ahead
22:11:35 <mrunge> how do we handle backwards compatibilty?
22:11:47 <davidlenwell> gabrielhurley: have you looked at / played with Thermal? the heat plugin someone wrote?  or did you already talk about that and I missed it.
22:12:06 <mrunge> I had one bug, where grizzly horizon don't works with folsom keystone
22:12:34 <gabrielhurley> mrunge: in general Grizzly Horizon should work with Folsom. If that's not the case why should figure out what introduced the incompatibility and either address it in code or address it via a setting as a last resort.
22:12:45 <gabrielhurley> is there a bug filed for it?
22:12:49 <mrunge> gabrielhurley, https://bugs.launchpad.net/horizon/+bug/1121975
22:12:51 <uvirtbot> Launchpad bug 1121975 in horizon "original_ip keystone parameter not compatible with folsom keystone" [Undecided,New]
22:13:01 <gabrielhurley> ah
22:13:03 <gabrielhurley> great
22:13:05 <gabrielhurley> let's fix that
22:13:08 <gabrielhurley> should be easy to fix in code
22:13:21 <mrunge> that change in keystone was introduced in mid october
22:13:29 <mrunge> yeah
22:13:30 <gabrielhurley> yep
22:13:36 <gabrielhurley> triaged into the list with High priority
22:13:42 <dolphm> keystoneclient then? not keystone folsom
22:13:42 <gabrielhurley> cool
22:14:00 <mrunge> dolphm, exactly
22:14:37 <gabrielhurley> davidlenwell: I haven't looked at Thermal in quite some time, why do you ask?
22:15:23 <davidlenwell> gabrielhurley: I was reviewing it last week because a few members of our team are putting a lot of effort into using heat
22:16:18 <davidlenwell> wondered if you had seen the interface and if you had any opinions about it.
22:16:40 <gabrielhurley> I'm not gonna offer an opinoin 'cuz my opinion would be out of date
22:16:44 <gabrielhurley> *opinion
22:17:10 <mordred> gabrielhurley: I've heard that, pending heat's acceptance, just merging the work into horizon might be an option?
22:17:20 <gabrielhurley> if Heat graduates then we'll get all the details sorted
22:17:29 <gabrielhurley> and yes, it'll absolutely be the starting point
22:17:44 <gabrielhurley> if/when
22:17:48 <gabrielhurley> not trying to sound negative
22:18:00 <davidlenwell> I think it will need a lot of work before its ready to merge into horizon.. some of the ui is very out of place
22:18:11 <gabrielhurley> I think that's likely
22:18:28 <davidlenwell> for one its got its own tab in the left nav .. with project and admin ..
22:18:34 <gabrielhurley> but the UI is easier to sort out than the API stuff, so the work they've done to get it functional will be valuable
22:18:49 <gabrielhurley> it won't be a wholesale merge by any means
22:18:55 <davidlenwell> okay
22:19:06 <gabrielhurley> I've been taking a "cross that bridge when we get there" approach
22:19:19 <gabrielhurley> same with ceilometer
22:19:25 <gabrielhurley> they've been developing things in the wings
22:20:35 <gabrielhurley> The one topic I'd like to discuss real quick: In the spirit of continuing to expand horizon core, I'd like to propose amotoki (who's not present) for Horizon Core. He's done a ton of work over the last two release cycles and has really stepped up his reviewing in the last few months. Anyone object before I send something to the ML?
22:22:04 <gabrielhurley> great
22:22:26 <gabrielhurley> Also, a quick reminder for the current core folks: if something already has a +2 and you feel it's ready as well, feel free to +2 *and* approve the review. You have to do both. I've seen a few reviews that had a +2 from me and either a +1 or a +2 but no "approve" from other core folks.
22:22:59 <gabrielhurley> anyo other questions or topics?
22:23:58 <jpich> when should code be up at the latest for bug fixes?
22:24:24 <gabrielhurley> bug fixes can go straight to the release being cut, but make sure you file bugs in launchpad so they can be tracked by release management
22:24:54 <jpich> Ok! cheers
22:24:57 <gabrielhurley> great. thanks everyone, and do all you can on reviews! have a great week!
22:25:07 <gabrielhurley> #endmeeting