22:00:43 <gabrielhurley> #startmeeting horizon
22:00:44 <openstack> Meeting started Tue Apr 30 22:00:43 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:00:45 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:00:47 <openstack> The meeting name has been set to 'horizon'
22:00:52 <gabrielhurley> #topic overview
22:01:06 <gabrielhurley> I'm pretty sure I change the name of this first topic every week...
22:01:09 <gabrielhurley> anyhow
22:01:13 <gabrielhurley> hello folks!
22:01:20 <lcheng> hello!
22:01:21 <david-lyle> hello
22:01:31 <vkmc> hii
22:01:43 <jpich> hey
22:01:49 <gabrielhurley> Lemme start off by saying I couldn't be mor pleased with how Havana is looking already!
22:02:04 <bradjones> hey
22:02:15 <gabrielhurley> We've barely started and we already have two dozen bugs fixed, blueprints in code review, and a great-looking plan
22:02:23 <gabrielhurley> that's just fantastic
22:02:57 <gabrielhurley> I finished doing a first pass at the full Havan roadmap today
22:03:04 <gabrielhurley> check out https://blueprints.launchpad.net/horizon/havana
22:03:09 <gabrielhurley> or any of the indvidual milestones
22:03:34 <gabrielhurley> I think that leads into the next topic
22:03:40 <gabrielhurley> #topic blueprints and bugs
22:03:55 <gabrielhurley> H1 has all it's blueprints assigned, so folks should just move forward on those
22:04:07 <gabrielhurley> and just 'cuz something may not be targeted to H1 doesn't mean you shouldn't work on it now
22:04:33 <gabrielhurley> the targets are rough measures of how much I think we can bite off in a set of time, and some idea of known blockers in other services, etc.
22:04:43 <gabrielhurley> but if you wanna work ahead I never mind bumping blueprints *up*
22:05:07 <gabrielhurley> For my part, I discovered an interesting quandary working on https://blueprints.launchpad.net/horizon/+spec/api-capability-detection
22:05:20 <gabrielhurley> which is that the keystone service catalog endpoints have hard-coded versions in them
22:06:01 <gabrielhurley> within the next week I'll have a proposal out to the mailing list to remove all version and tenant info from the service catalog endpoints, and instead to have the clients be able to construct the appropriate endpoints based on what's returned by keystone and what you pass in.
22:06:13 <gabrielhurley> so, progress there is good, but won't be done this week
22:06:13 <dolphm> (YAY!)
22:06:27 <gabrielhurley> in the interim I'm going to lay down some groundwork code for switching versions that'll hack around it
22:06:46 <gabrielhurley> I want to make sure all the v3 API work isn't blocked, so this'll be a stopgap measure
22:06:51 <gabrielhurley> I should have that up in the next week
22:07:07 <gabrielhurley> who else wants to discuss or report in on blueprints?
22:07:49 <david-lyle> to be clear, the v2/v3 toggle will work across horizon and django_openstack_auth?
22:08:46 <gabrielhurley> correct
22:09:46 <gabrielhurley> okay. I'm not worried about any of the BPs this week so I won't call for specific updates.
22:10:02 <gabrielhurley> just wanted to give people the opportunity in case anyone wanted to comment
22:10:19 <bradjones> I'll pitch in about d3 integration
22:10:35 <gabrielhurley> go for it
22:10:43 <bradjones> we are making good progress on reworking the quota graphics
22:11:01 <bradjones> Am looking into displaying the usage summary as some sort of graph over time
22:11:10 <lcheng> @gabrielhurlye: from openstack_auth, how can I determine the keystone version.. Are we going to explicitly set some parameter in settings file  to configure the KS version or I have to make a call on the api discovery function you're working on?
22:11:11 <gabrielhurley> very cool. fwiw, I could see those taking up a lot less space by being made into vertical bar graphs or something...
22:11:18 <gabrielhurley> usage-over-time would also be awesome
22:11:28 <gabrielhurley> ceilometer would help with that and there are future BPs to address that in more detail
22:11:47 <gabrielhurley> lcheng: in the short term (like for a couple weeks here) it's gonna be a setting
22:12:00 <gabrielhurley> it will later depend on version discovery
22:12:03 <bradjones> would it be a good idea to replace usage summary with graph or have it as an option to display either?
22:12:05 <gabrielhurley> see my comments about that above
22:12:14 <lcheng> okay
22:12:16 <gabrielhurley> bradjones: depends on the data source
22:12:41 <gabrielhurley> if you're pulling from ceilometer it probably has to be optional
22:12:57 <bradjones> ok will look into it further once the quota summary is finalised
22:13:03 <gabrielhurley> excellent
22:13:23 <jpich> bradjones: btw, there was a bug about consistency in the quota graphs, perhaps this can be tackled at the same time - https://bugs.launchpad.net/horizon/+bug/1102461
22:13:25 <uvirtbot> Launchpad bug 1102461 in horizon "Quota Summary graphs should be consistent in styling" [Low,Confirmed]
22:13:43 <bradjones> jpich: I'll look into it
22:14:26 <jpich> Cool
22:14:57 <gabrielhurley> great
22:15:02 <gabrielhurley> anyone else with blueprint comments?
22:15:41 <gabrielhurley> cool
22:16:01 <gabrielhurley> bug-wise we're doing fine. there are a couple that need triage, but nothing that looks dangerous/needs exceptional comment on.
22:16:09 <gabrielhurley> #topic open discussion
22:16:22 <gabrielhurley> Other things on people's minds?
22:16:33 <jpich> Grizzly stable: amotoki had raised the point before the summit that there had been a lot of improvements in the translations after they were pulled into grizzly
22:16:48 <jpich> should we open a bug to track this, is it possible to update the translations for a stable release?
22:17:10 <jpich> If yes it'd be cool to get it in for the first one
22:17:11 <dolphm> gabrielhurley: make sure you ping me when you have unversioned catalog code published
22:17:32 <dolphm> gabrielhurley: alternatively, i have a bunch of jumbled thoughts in my head on the topic if you'd like me to simply throw them at you
22:17:46 <gabrielhurley> dolphm: gonna be a bit for *actual* code. I wanna get pseudo-code reviewed by the community first.
22:17:56 <gabrielhurley> feel free to write 'em down and send 'em my way
22:18:06 <gabrielhurley> I don't think keystone needs to change *that* much, actually
22:18:12 <dolphm> gabrielhurley: on that thread or off list?
22:18:14 <gabrielhurley> it's mostly gonna be changes in the clients and devstack
22:18:24 <gabrielhurley> dolphm: that thread is good with me
22:18:27 <dolphm> will do
22:18:45 <gabrielhurley> jpich: backporting the translations is fine with me
22:18:53 <gabrielhurley> same process as any other backport
22:19:26 <jpich> gabrielhurley: I don't think we have pulled the latest ones from Transifex though, since the update was made
22:19:59 <gabrielhurley> it's not hard to do
22:20:08 <gabrielhurley> pip install the transifex client
22:20:18 <gabrielhurley> there's already a transifex dotfile committed to the horizon repo
22:20:41 <jpich> Ok, I'll look into it then
22:20:53 <gabrielhurley> cool
22:25:17 <gabrielhurley> well alright then
22:25:23 <gabrielhurley> good meeting folks
22:25:30 <gabrielhurley> have a good week and keep up the good work!
22:25:32 <gabrielhurley> #endmeeting