22:02:19 <gabrielhurley> #startmeeting horizon
22:02:20 <openstack> Meeting started Tue Mar  5 22:02:19 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:02:21 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:02:23 <openstack> The meeting name has been set to 'horizon'
22:02:27 <gabrielhurley> #topic General
22:02:35 <gabrielhurley> Hi everyone!
22:02:41 <gabrielhurley> Things are going very well with the RC
22:03:00 <gabrielhurley> I triaged the bugs this morning and there wasn't anything unexpected.
22:03:14 <gabrielhurley> What's on the current list is looking good.
22:03:24 <gabrielhurley> #topic Blueprints and Bugs
22:03:44 <gabrielhurley> the one remaining blueprint is cleared for merging, so I'm gonna give that a final review and merge it unless anyone objects.
22:04:04 <gabrielhurley> I would like to talk about this bug for a moment: https://bugs.launchpad.net/horizon/+bug/1060426
22:04:06 <uvirtbot> Launchpad bug 1060426 in horizon "Login screen doesn't show reason for being logged out" [High,Confirmed]
22:04:20 <gabrielhurley> This bug leads to more bug reports than anything else in Horizon
22:04:27 <gabrielhurley> It confuses people constantly
22:04:34 <gabrielhurley> And what I'm wondering is this:
22:05:18 <gabrielhurley> is it better to 1) show the "reason" (e.g. "Unauthorized, please try logging in again."). Or is it better to *not* log people out and let them see the unauthorized messages in the dashboard for the API requests that can't be completed.
22:05:33 <gabrielhurley> the latter being option 2, since I fail at numbering.
22:06:09 <gabrielhurley> From a faux-security perspective it feels more right to log them out, but I think the better UX is to let them be logged in and unable to act...
22:06:11 <gabrielhurley> thoughts?
22:06:17 <kspear> yeah, i was thinking about this when fixing another bug
22:06:18 <jpich> A clear error message in the dashboard would make more sense IMO
22:06:28 <jpich> Or be more user friendly
22:06:38 <kspear> i think a dashboard message plus a link to logout/login would be better
22:06:47 <gabrielhurley> As a caveat, fixing this by way of *not* logging them out is a lot easier to implement.
22:07:00 <gabrielhurley> Cool. I think that's the direction I'll take it then.
22:07:10 <kspear> is lin-hua's comment there correct?
22:07:14 <vkmc> I think that an error message will be great too
22:07:28 <kspear> i have seen permission denied messages on the login page before
22:07:50 <gabrielhurley> that should be investigated as a related (simple) fix
22:08:15 <gabrielhurley> which I'll do. since the ticket is assigned to me.
22:08:18 <gabrielhurley> lol.
22:08:32 <kspear> haha
22:08:33 <gabrielhurley> any other bugs folks want to talk about?
22:08:57 <kspear> i think the comment is saying it's already fixed
22:09:13 <gabrielhurley> Oh, just as a general note: I'm planning on doing a complete Django 1.5 compatibility pass as soon as the H cycle starts.
22:09:15 <kspear> but the change you suggested would be better
22:10:58 <kspear> i just have
22:10:59 <kspear> https://bugs.launchpad.net/horizon/+bug/1072848
22:11:01 <uvirtbot> Launchpad bug 1072848 in horizon "Switching projects sends user "home" inappropriately" [Low,Confirmed]
22:11:17 <kspear> i made some changes in openstack_auth to support a fix
22:11:25 <kspear> is it possible to cut a 1.0.7 release of that?
22:14:39 <gabrielhurley> oh, yes
22:14:41 <gabrielhurley> will do
22:15:06 <kspear> great
22:15:09 <gabrielhurley> #topic open discussion
22:15:10 <kspear> the horizon fix is one line
22:15:15 <gabrielhurley> sweet
22:15:36 <vkmc> gabrielhurley, jogo suggested to add tenant deletion on Keystone directly. How this impact my current work on the blueprint? https://blueprints.launchpad.net/horizon/+spec/tenant-deletion
22:15:56 <gabrielhurley> hard to say
22:16:27 <gabrielhurley> The Horizon BP is basically a stop-gap for keystone doing something about it
22:16:36 <gabrielhurley> and getting that into keystone may be a bit controversial
22:16:46 <gabrielhurley> so I'd proceed as planned but stay in the loop on that issue
22:17:20 <vkmc> gabrielhurley, Yeah I agree...
22:17:29 <jpich> Is there an existing bug or blueprint in keystone for this?
22:17:41 <vkmc> gabrielhurley, Currently I'm having some blockers, but overall progress is good
22:18:15 <gabrielhurley> vkmc: cool. do you know if there's a keystone BP for it? I'm not aware of one, but that doesn't mean it doesn't exist.
22:18:54 <dolphm> gabrielhurley: vkmc: bug 1129037 is one, but it's sort of a dupe... i swear we had another
22:18:55 <uvirtbot> Launchpad bug 1129037 in keystone "keystone tenant-delete" [Undecided,New] https://launchpad.net/bugs/1129037
22:19:11 <gabrielhurley> yeah. there oughta be one if there isn't
22:19:16 <gabrielhurley> then we could link the horizon and keysotne BPs
22:19:34 <vkmc> gabrielhurley, Saw the one shared by dolphm
22:19:37 <vkmc> dolphm, Thanks
22:20:46 <gabrielhurley> kspear: openstack_auth 1.0.7 is published to PyPI
22:21:01 <dolphm> last time it was discussed it was determined to be an orchestration issue, although there's probably some way for keystone to help with that, such as publishing a list of deleted projects, etc
22:21:17 <kspear> gabrielhurley: that was quick! thanks
22:21:17 <gabrielhurley> yeah. that's why I say that it's gonna be a while to get it into keystone
22:21:25 <gabrielhurley> so I think Horizon should go ahead with it
22:21:29 <gabrielhurley> s/it/our plan
22:22:04 <gabrielhurley> vkmc: make sense?
22:22:53 <vkmc> gabrielhurley, It does, yeah
22:23:12 <vkmc> gabrielhurley, And it's a relief to hear that :)
22:23:14 <gabrielhurley> cool
22:23:27 <gabrielhurley> other topics from folks?
22:23:49 <kspear> do we have a date for rc1?
22:25:35 <gabrielhurley> I heard March 12th
22:25:46 <dolphm> gabrielhurley: sorry, accidentally replied off list so i'm hitting you twice
22:25:47 <gabrielhurley> so, next week, roughly
22:25:54 <gabrielhurley> dolphm: no worries
22:26:14 <kspear> good to know
22:26:25 <gabrielhurley> kspear: yup. good question.
22:28:29 <gabrielhurley> cool. with that I think we'll call it a day.
22:28:42 <gabrielhurley> Great job everyone, same time next week!
22:28:52 <gabrielhurley> #endmeeting