22:01:11 <gabrielhurley> #startmeeting horizon
22:01:12 <openstack> Meeting started Tue Apr 23 22:01:11 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:01:13 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:15 <openstack> The meeting name has been set to 'horizon'
22:01:17 <gabrielhurley> #topic overview
22:01:24 <gabrielhurley> Hi folks!
22:01:31 <david-lyle> Hello
22:01:32 <lcheng> hello
22:01:37 * kspear waves
22:01:37 <gabrielhurley> Welcome to the first Horizon meeting of the Havana cycle. :-)
22:01:49 <gabrielhurley> It was great seeing most of you at the summit last week
22:02:03 <gabrielhurley> I think we got some great work done, and generally I've tried to capture all the outcomes into blueprints
22:02:24 <gabrielhurley> just to recap for anyone that wasn't listening in on the meeting before this:
22:02:51 <gabrielhurley> the goal for this week is to get all the havan blueprints laid out, and to get them targeted to milestones and (if possible) assign them to people responsible for them
22:03:02 <gabrielhurley> At the very least I'd like to get H1 mostly accounted for.
22:03:09 <gabrielhurley> to that end
22:03:14 <gabrielhurley> #topic blueprints and bugs
22:03:33 <gabrielhurley> There's been good work happening on gerrit. I did a bunch of reviews today, and will continue to keep an eye on them.
22:03:40 <gabrielhurley> but blueprints are the larger issue currently
22:03:43 <gabrielhurley> https://blueprints.launchpad.net/horizon/havana
22:03:49 <gabrielhurley> there's what's targeted to Havana currently
22:04:05 <gabrielhurley> it should encompasse most of what we talked about at the summit, plus a few that continue to be important
22:04:36 <gabrielhurley> I'm gonna tackle the API version and extension detection, and hopefully have that done ASAP. My goal is to have that in the next two weeks.
22:04:53 <gabrielhurley> That one's the blocker for most other work in H, so the sooner the better
22:05:17 <gabrielhurley> I'd also like to see to it that we get D3 in place so everyone can start building with it ASAP
22:05:25 <gabrielhurley> doesn't mean everything has to be refactored in one go
22:05:38 <gabrielhurley> just progress on it
22:06:22 <gabrielhurley> There are a few BPs that trickled over from Grizzly which are targeted to H1 and even have reviews up already, so those are good
22:06:43 <gabrielhurley> the two large remaining themes I think are urgent for the early part of this cycle are:
22:07:07 <gabrielhurley> keystone domain work (blocked by the API version detection)
22:07:10 <gabrielhurley> and
22:07:22 <gabrielhurley> the basics of the realtime communication stuff
22:07:58 <gabrielhurley> that includes exploring python-based websocket solutions, dropping in socket.io, and investigating the RPC listener on Oslo
22:08:16 <gabrielhurley> of those, I've got the RPC listener assigned to me
22:08:31 <gabrielhurley> and a couple people have claimed other peices
22:08:50 <gabrielhurley> but anyone who'd like to work on specific things is welcome to step up to them, and teamwork is encouraged. ;-)
22:09:09 <gabrielhurley> for example i'll definitely work closely with whoever works on the websocket stuff
22:09:20 <gabrielhurley> but I don't think it'd be wise for me to own that one given my usual schedule
22:09:33 <gabrielhurley> so let me open it up a little
22:09:45 <gabrielhurley> does anyone want to argue for specific things they think should be in H1? or *not* in H1?
22:09:54 <gabrielhurley> or blueprints they're interested in/concerned about?
22:11:17 <kspear> i'd love to help with the websocket stuff but i don't have a lot of time in H1 since we're also upgrading our cloud to grizzly
22:11:32 <gabrielhurley> my hope is that it actually won't be much work
22:11:39 <kspear> everything else looks good to me
22:11:39 <gabrielhurley> it's one of those "if it goes right it's easy"
22:12:06 <kspear> can we come up with some design doco so we can better coordinate?
22:12:30 <gabrielhurley> sure. suggestions?
22:13:18 <kspear> at least an etherpad with a description of each component and how things will fit together?
22:13:27 <kspear> i realise some of this is still to be discovered
22:13:36 <gabrielhurley> sounds good. create one, jot down any thoughts, and link it into the BP?
22:13:48 <kspear> will do
22:14:04 <david-lyle> Lin and I are interested in working on keystone v3 support as it closely relates to the system we currently use and we would like to transition to v3
22:14:16 <gabrielhurley> yep. I'd love for y'all to own all of that
22:14:58 <gabrielhurley> I do have some concerns about the big reorganization that was in the wireframes at the summit, so don't start moving things until we can get a bit more consenus around that
22:15:34 <gabrielhurley> but otherwise let's follow up about how best to organize the API code and then you should be able to work more-or-less in parallel
22:15:46 <gabrielhurley> with what I need to do to support v2 and v3 side-by-side
22:16:21 <david-lyle> that's fine, we'll make it work in the existing layout unless we can generate some consensus
22:16:28 <gabrielhurley> cool
22:16:51 <gabrielhurley> so yeah, let's agree on what the interface for "switching" versions looks like, and then you can just stub in a hardcoded "use v3" and work forward from there until I get my end done
22:17:43 <david-lyle> is that a settings level item or are we looking for an UI element?
22:18:33 <david-lyle> settings would be use v3 is available type setting
22:19:07 <david-lyle> because it hits at login time too
22:19:09 <gabrielhurley> ultimately there will be something in the openstack_dashboard.api code that will know which versions are available and hand you back the appropriate client when you call it.
22:20:05 <gabrielhurley> it will probably get it's data from the APIs with an optional settings override
22:20:10 <gabrielhurley> but this is all just off the top of my head
22:20:24 <david-lyle> well work it out
22:20:26 <gabrielhurley> yep
22:21:08 <gabrielhurley> For anyone else who hasn't spoken up, I encourage you to look at the remaining blueprints targeted to H1 (and the ones that aren't) and figure out what you'd like to work on. Feel free to assign them to yourself if they're unclaimed. If there are things you think are important and should be in H1 feel free to email me.
22:21:37 <kspear> whatever happened to chunked/direct image upload?
22:21:56 <gabrielhurley> not targeted to Havana currently 'cuz nobody's stepped up to own it
22:22:07 <gabrielhurley> it's a big/tough problem
22:22:13 <gabrielhurley> and I don't want to force somebody to tackle it
22:22:22 <kspear> yep, fair enough
22:22:24 <gabrielhurley> if anyone *wants* it, I'm more than happy to bring it in
22:22:34 <kspear> it'd be very nice to have
22:22:38 <gabrielhurley> totally agreed
22:22:42 <kspear> i might look into it later in the cycle
22:22:46 <gabrielhurley> cool
22:22:53 <david-lyle> there doesn't seem to be a self assign for blueprints, is there a mechanism I'm missing?
22:23:08 <gabrielhurley> right now there are about the same number of BPs targeted to H as we completed in G, but I'm hoping we may actually be able to do more.
22:23:27 <gabrielhurley> david-lyle: if you can't do it just bug me or any of the other core folks and we can assign it for you
22:23:36 <david-lyle> ok, thanks
22:23:36 <gabrielhurley> launchpad has wacky permissions
22:23:46 <lcheng> can you this to either or Dave
22:23:48 <lcheng> https://blueprints.launchpad.net/horizon/+spec/multiple-service-endpoints
22:23:48 <lcheng> https://blueprints.launchpad.net/horizon/+spec/login-domain-support
22:23:48 <lcheng> https://blueprints.launchpad.net/horizon/+spec/rbac
22:24:04 <gabrielhurley> sure
22:25:25 <gabrielhurley> done.
22:25:30 <gabrielhurley> I divided them up randomly between you two
22:25:32 <gabrielhurley> ;-)
22:26:00 <gabrielhurley> ooookay
22:26:05 <lcheng> thanks!
22:26:07 <gabrielhurley> #topic open discussion
22:26:14 <gabrielhurley> Anybody got other things they're interested in talking about?
22:27:14 <kspear> the first grizzly stable release isn't far away iirc
22:27:24 <kspear> so if people could think about backports
22:27:45 <kspear> and either propose reviews or tag them that'd be good
22:27:55 <gabrielhurley> ah, that's a good point
22:27:58 <gabrielhurley> yes
22:28:12 <gabrielhurley> particularly some of the Load Balancer bugfixes would be great to backport
22:28:40 <kspear> yeah definitely
22:30:47 <gabrielhurley> okay, well, if anyone has other thoughts feel free to bring 'em up on the mailing list.
22:30:50 <gabrielhurley> good meeting folks
22:30:55 <gabrielhurley> same time next week!
22:30:57 <gabrielhurley> #endmeeting