22:01:25 <gabrielhurley> #startmeeting horizon
22:01:26 <openstack> Meeting started Tue May 28 22:01:25 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:01:27 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:01:29 <openstack> The meeting name has been set to 'horizon'
22:01:37 <gabrielhurley> #topic overview
22:01:46 <gabrielhurley> Hello folks
22:01:55 <lcheng> hey
22:02:00 <david-lyle> hello
22:02:12 <jpich> hey
22:02:23 <gabrielhurley> The H1 milestone will be cut roughly 10 hours from now. I'd consider things pretty much locked down for H1 now.
22:03:08 <gabrielhurley> All-in-all I believe 3 out of 11 blueprints for H1 made it on time.
22:03:42 <gabrielhurley> Per-project flavors, login with domains, and Heat integration being the main ones.
22:04:07 <gabrielhurley> whoops, 8 out of 11 made it on time
22:04:09 <gabrielhurley> 3 did not
22:04:24 <gabrielhurley> way to start a sentence counting one way and end it counting another way.
22:04:31 <gabrielhurley> lol
22:05:13 <gabrielhurley> Process-wise, once the milestone-proposed branch is cut then any critical bugs we find in the next couple days has to be specifically backported to that branch
22:05:20 <gabrielhurley> fixes should land in master first, as usual
22:05:40 <gabrielhurley> Also, once that branch is cut then anything for H2 is fair game
22:06:05 <gabrielhurley> before we take a look at specific blueprints I want to generally call out one larger topic
22:07:02 <gabrielhurley> There are three fairly interesting integration efforts going on which have code available to check out...
22:07:19 <gabrielhurley> Realtime/socket.io communication proof-of-concept:   https://review.openstack.org/30462  https://review.openstack.org/30463
22:07:50 <gabrielhurley> Heat integration: https://review.openstack.org/#/c/29478/
22:08:12 <gabrielhurley> and ceilometer: https://github.com/yuanotes/horizon/tree/ceilometer
22:08:44 <gabrielhurley> I'd like to get lots of eyes and thoughts on those to ensure we're not only getting good code, but getting the right kind of user experience we want too
22:09:07 <gabrielhurley> All of these are H2 priorities, for what it's worth.
22:09:29 <gabrielhurley> okay, let's talk specific blueprints for a minute
22:09:32 <gabrielhurley> #topic blueprints
22:09:41 <gabrielhurley> looking at https://launchpad.net/horizon/+milestone/havana-2
22:09:50 <gabrielhurley> we've got way too many blueprints, first off
22:10:41 <gabrielhurley> priorities are the three large areas mentioned above, and finishing the keystone v3 work
22:11:05 <gabrielhurley> lcheng: can you give a quick update on https://blueprints.launchpad.net/horizon/+spec/login-domain-support
22:11:49 <lcheng> gabrielhurley: it is still blocked by the implementation of keystoneclient v3 auth.
22:11:58 <lcheng> I am going to take over the implementation of it.
22:12:08 <gabrielhurley> that's what I thought. looking like that'll land in H2 keystone/keystoneclient?
22:12:26 <lcheng> yes.
22:12:28 <gabrielhurley> great
22:12:44 <gabrielhurley> the rest of the keystone v3 stuff is coming along great
22:13:02 <gabrielhurley> I'd like to keep the momentum there, for sure
22:13:11 <gabrielhurley> cody-somerville: what are your thoughts about working on https://blueprints.launchpad.net/horizon/+spec/building-on-openstack-dashboard in H2?
22:13:19 <lcheng> There not a lot of work left on our side, once that is ready it won't take that long to have our code ready.
22:13:41 <gabrielhurley> lcheng: yep, I've been checking in occasionally. I just wanted to make sure you were feeling the same way. :-)
22:16:49 <lcheng> gabrielhurley: we're good. :-) Btw, I registered another bp for keystone v3: https://blueprints.launchpad.net/horizon/+spec/group-role-assignment
22:16:57 <gabrielhurley> I'm inclined to push smaller features out of the H2 milestone in the interesting of getting the big stuff done earlier. On the chopping block would be things like availability zones ( https://blueprints.launchpad.net/horizon/+spec/show-zone-for-admin and https://blueprints.launchpad.net/horizon/+spec/show-zone-for-admin ) and the instance actions extension in nova ( https://blueprints.launchpad.net/horizon/+spec/instanc
22:17:08 <gabrielhurley> lcheng: cool. I'll take a look at that blueprint
22:17:27 <lcheng> gabrielhurley: thanks!
22:17:29 <gabrielhurley> Does anyone want to argue in favor of the blueprints on the list above, that they really really must be in H2?
22:19:00 <gabrielhurley> It's very hard to gauge how much will actually get done in this next milestone when there's an inordinately high number of blueprints and almost each one has a different assignee.
22:19:12 <gabrielhurley> but I figure it's better to start with a more conservative list.
22:19:21 <kspear> it sounded like work was going to happen on that bp soon, but it's hard to say
22:19:33 <gabrielhurley> kspear: which BP?
22:19:40 <kspear> it's assigned to me, but i actually wanted to take over this one
22:19:42 <kspear> https://blueprints.launchpad.net/horizon/+spec/select-zone-when-creating-instance
22:19:48 <gabrielhurley> gotcha
22:19:48 <kspear> gabrielhurley: show-zone-for-admin
22:19:56 <gabrielhurley> neither are terribly difficult
22:20:04 <gabrielhurley> if you wanna keep 'em in that's cool
22:20:19 <kspear> can't speak for show-zone-for-admin
22:20:31 <kspear> but i will have code up for select-zone within a couple of weeks
22:20:36 <gabrielhurley> got it
22:21:23 <gabrielhurley> let's see. I'm definitely inclined to bump the keystone v3 policy/role-based access control stuff since it doesn't even have an assignee and it's a very difficult one: https://blueprints.launchpad.net/horizon/+spec/rbac
22:21:47 <jpich> David seems to be assigned?
22:21:59 <david-lyle> I have that one.
22:22:12 <gabrielhurley> oh
22:22:16 <gabrielhurley> I can't read today
22:22:18 <david-lyle> might be big enough to slip, but I plan to start on it in H2
22:22:25 <gabrielhurley> got it
22:22:32 <gabrielhurley> I will leave it in H2 for now then
22:22:42 <gabrielhurley> lemme do this a different way
22:22:49 <gabrielhurley> since I'm failing at this so far ;-)
22:23:03 <gabrielhurley> does anyone have a blueprint assigned to them that they feel they will not complete in H2?
22:23:40 <david-lyle> I have https://blueprints.launchpad.net/horizon/+spec/centralized-color-palette assigned to me, but it's fallen in my priority list
22:24:02 <david-lyle> I'd be happy to free it up for someone else to look at, or keep it on the back-burner
22:24:12 <gabrielhurley> sounds good
22:24:21 <gabrielhurley> for now I'll leave it assigned to you but bump to H3
22:24:26 <david-lyle> ok
22:24:29 <gabrielhurley> if anyone else wants to pick it up we can reassign
22:27:29 <gabrielhurley> okay. if you refresh on https://launchpad.net/horizon/+milestone/havana-2 we're now down to 17 blueprints, all with assignees, and david-lyle is the only individual with more than 2 blueprints assigned to them.
22:27:54 <gabrielhurley> that seems like a good place to start the H2 cycle, I think. Thoughts on what we've got there from anyone else?
22:28:54 <gabrielhurley> I'll open it up for discussion then...
22:28:57 <gabrielhurley> #topic open discussion
22:29:06 <gabrielhurley> comments, questions and concerns are welcome
22:29:30 <kspear> looks good to me
22:29:41 <lcheng> gabrielhurley: Question on https://bugs.launchpad.net/horizon/+bug/1166794
22:29:41 <kspear> are we going to see quantum security group support soon?
22:29:43 <uvirtbot> Launchpad bug 1166794 in horizon "Project creation fails if the current user is added to it" [High,Confirmed]
22:30:20 <gabrielhurley> kspear: last I heard it was still pending some work in Quantum, but I think we're getting closer. I'm a little out of the loop on that one.
22:30:27 <gabrielhurley> lcheng: what's the question?
22:30:34 <lcheng> gabrielhurley: The token gets revoked whenever a user is added to a project. Same thing happening when a user is added/removed from a group.
22:31:04 <gabrielhurley> yep. there's about 4 iterations of this bug
22:31:15 <lcheng> Just wondering what would the fix for this issue, is it dependent on keystone not revoking the unscoped tokens?
22:31:21 <gabrielhurley> I'm not sure why none of them have been traiged/acknowledged by the keystone team
22:31:53 <gabrielhurley> I will bother dolphm next week if they're still not triaged on keystone's side
22:32:08 <gabrielhurley> an email to the -dev mailing list on the topic also wouldn't be a bad idea
22:32:24 <gabrielhurley> though the behavior is a breaking change on keystone's end I suspect it's not gonna be something they can easily fix
22:32:48 <gabrielhurley> due to the way token ids are generated in terms of hashing the token itself, etc.
22:32:55 <gabrielhurley> we may have to work around it on our end
22:33:31 <gabrielhurley> that's about as much as I've got on that bug right now
22:34:02 <gabrielhurley> anything else?
22:34:27 <lcheng> okay, I was hoping that you can get keystone team to fix this. :-)  But definitely, we can workaround the issue if needed.
22:34:46 <gabrielhurley> yeah, we shall see
22:35:12 <gabrielhurley> okay... I think that's about it for today. great work on H1 everyone, and we'll talk more about H2 next week!
22:35:16 <gabrielhurley> #endmeeting