16:05:55 <david-lyle_afk> #startmeeting Horizon
16:05:55 <openstack> Meeting started Tue Nov 11 16:05:55 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle_afk. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:05:57 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:05:59 <openstack> The meeting name has been set to 'horizon'
16:06:52 <akrivoka> hello :)
16:07:04 <david-lyle> anyone here for the Horizon meeting? or did the time change in the US confuse people?
16:07:07 <tmazur> hello o/
16:07:14 <pkarikh> Hi. :)
16:07:15 <wchrisj> hello
16:07:21 <mwhagedorn> I am here @david :)
16:07:58 <john-davidge> I am here, but perpetually confused
16:08:14 <sanjay> Hi David
16:08:21 <ericpeterson> hey all
16:08:30 <mwhagedorn> hey ericpeterson
16:08:35 <pkarikh> david-lyle, if you hadn't said in the horizon channel, I 'd be confused
16:09:11 <kanchan> Hi all
16:09:38 <crobertsrh> Hello/
16:09:45 <david-lyle> I don't have a whole lot for today, mostly post summit catch up
16:09:57 <david-lyle> but a couple of items are on the agenda
16:10:55 <david-lyle> For those that were able to make the summit, thank you for your attendance
16:11:04 <david-lyle> I think it was a very productive time
16:11:37 <david-lyle> For those that weren't able to attend, links to the etherpads for the sessions can be found
16:11:43 <david-lyle> #link https://wiki.openstack.org/wiki/Summit/Kilo/Etherpads#Horizon
16:12:16 <david-lyle> Buried in the end of the Contributors meetup is an outline of the prioritized features for Kilo
16:13:45 <david-lyle> Those will shortly end up as blueprints scheduled for the milestones in the Kilo release
16:14:02 <john-davidge> Would just like to say that the Horizon contributors meeting was definitely one of the most productive of the day, so thanks David for chairing that.
16:14:15 <david-lyle> Other items will be able to be added, but those will be the priority
16:15:13 <david-lyle> john-davidge: I agree that it was very productive
16:16:02 <david-lyle> There is interest in having a mid-cycle meet up
16:16:32 <david-lyle> I think the proposed local would be somewhere on the East coast of the US and probably in January
16:16:41 <david-lyle> still trying to nail down specifics
16:16:51 <david-lyle> so keep that in mind
16:17:27 <david-lyle> Any one have anything to add or clarify around the summit?
16:17:53 <david-lyle> I will also be typing up a more formal summit report and post that
16:18:49 <david-lyle> alright on to the agenda
16:18:57 <jpich> mrunge posted a summary as well at http://www.matthias-runge.de/2014/11/10/horizon-kilo-summit/ FYI
16:19:33 <jpich> (The more reports the better though!)
16:20:16 <david-lyle> The agenda can be found https://wiki.openstack.org/wiki/Meetings/Horizon
16:20:44 <david-lyle> #topic What is Horizon's accessibility statement? (asahlin)
16:21:17 <david-lyle> doh
16:21:40 <david-lyle_afk> #topic What is Horizon's accessibility statement? (asahlin)
16:21:55 <akrivoka> heh...
16:21:56 <jpich> It's ok to also ask these questions directly on list rather than wait for Tuesdays
16:22:26 <david-lyle_afk> forgot I started the meeting with a different nick
16:22:44 <david-lyle_afk> asahlin not around?
16:22:59 <david-lyle_afk> I believe the author was doug-fish
16:23:02 <jpich> doug-fish was looking into it and created the web page linked in the agenda ( https://wiki.openstack.org/wiki/Horizon/WebAccessibility ), my understanding of the current situation would be that we want to do better but no one has had time to work on it so far
16:23:22 <david-lyle_afk> That's my understanding as well
16:24:23 <david-lyle_afk> let's have asahlin follow up with specific questions/concerns when he's around
16:24:48 <asahlin> Hey all sorry,  didn't realize the meeting time changed..    Or my calendar entry changed ;-)
16:24:50 <jpich> There was a strategy discussed at the last-last summit too -> see "Help! I found a bug" in https://etherpad.openstack.org/p/Dashboard_Accessibility (filing bugs for each problem found, then fixing them)
16:25:15 <david-lyle_afk> asahlin: confusing time of year as all meeting times are in UTC
16:25:38 <asahlin> The question arose from  a code review I was doing and realizing Horizon has a larger accessibility issue.   Which brought me to what is Horizon statement on accessibility, is there anything being done / in plan
16:26:07 <asahlin> Since then I exchanged emails with Doug Fish and situation is as jpich just posted
16:26:16 <john-davidge> Pro-Tip: Put the meeting times into your calendar on Iceland (Rekyjavik) time if it doesn't have a UTC option :)
16:26:38 <jpich> asahlin: Feel free to ask this kind of question on list directly, that way the answers can be more easily referenced as well :)
16:27:01 <asahlin> jpich: sure that makes sense, will do that.
16:27:11 <david-lyle> asahlin: mainly we need someone to pick this up and make progress
16:27:15 <jpich> Just for next time
16:27:56 <david-lyle> there is no argument around the need
16:28:18 <asahlin> david-lyle:  And currently no one is driving it... so its just report defect and fix in pieces,   Is that correct?
16:28:32 <david-lyle> asahlin: yes
16:29:08 <jpomero> asahlin, i think you should talk to doug-fish, accessibility is one of his goals iirc
16:29:18 <asahlin> david-lyle:  ok, at this point that's all I wanted to know.
16:29:49 <asahlin> jpomero: yeah, will follow up with Doug
16:30:02 <david-lyle> asahlin, sounds good
16:30:23 <david-lyle_afk> #topic Lock instance [akrivoka]
16:30:38 <akrivoka> so, one of the pain points that came up in the operators session was the lack of lock instance functionality in Horizon
16:30:53 <akrivoka> we have a blueprint for it here https://blueprints.launchpad.net/horizon/+spec/lock-unlock-server
16:31:22 <akrivoka> so I started looking into it and discovered that there is a missing piece of functionality related to the lock instance feature in nova itself - namely the ability to get lock status of an instance
16:31:46 <akrivoka> simply said, there is no way to tell, by looking at an instance, if it's locked or not
16:32:02 <david-lyle> well that's a bit of a hole, even for command line users
16:32:08 <jpich> Is there an open bug in Nova to track this?
16:32:10 <akrivoka> there seems to be a patch currently on review in nova, which is adding this missing part: https://review.openstack.org/#/c/131094/
16:32:23 <akrivoka> but that patch doesn't look ready to merge
16:32:28 <jpich> Cool! Should be referenced in the horizon bp too
16:32:46 <david-lyle> Yeah that BP needs an update
16:32:51 <akrivoka> my question to you guys is, considering this drawback, do we want to add the lock instance feature to Horizon now?
16:32:57 <akrivoka> no probs, I will update the bp
16:33:08 <akrivoka> so, we would be able to lock/unlock, but lock-status would not be visible
16:33:31 <akrivoka> (the same fucntionality as the command line has now)
16:33:56 <david-lyle> akrivoka: is locking an instance driver specific?
16:34:09 <david-lyle> is there another tool reporting this status
16:34:18 <akrivoka> david-lyle: I don't know...
16:34:37 <akrivoka> not as far as I've been able to find out
16:34:47 <david-lyle> I just find it odd that this would be a useful feature that operators would want unless there was
16:35:05 <david-lyle> maybe just all instances are locked upon creation in certain environments
16:35:57 <david-lyle> If that is a normal use case, I would be ok with adding the controls to lock and unlock and later improve with current status
16:37:03 <akrivoka> david-lyle: thanks! I will investigate more and see what I come up with
16:37:05 <david-lyle> maybe make two work items in the blueprint to address the first pass at functionality and then the improved functionality once the nova change merges
16:37:10 <david-lyle> akrivoka: thanks!
16:37:32 <akrivoka> david-lyle: sounds good - will do that!
16:37:47 <david-lyle_afk> #topic Open Discussion
16:38:24 <sanjay> hi david
16:38:27 * david-lyle notes starting the meeting with afk in your nick is not ideal
16:38:34 <david-lyle> sanjay: hello
16:38:38 <sanjay> regarding bp Add User "Role" field to Update User Form
16:39:04 <sanjay> https://blueprints.launchpad.net/horizon/+spec/add-user-role-field
16:39:33 <sanjay> do you see this as useful feature ?
16:39:53 <david-lyle> isn't the role expressed in the drop down in that view
16:39:54 <david-lyle> ?
16:40:50 <david-lyle> oh, not the assignment view, but the update user view
16:41:19 <david-lyle> what's on that view is the default project, not all projects IIRC
16:41:32 <sanjay> kanchn please explain
16:41:47 <david-lyle> The default project bit is likely going to go away
16:41:52 <jpich> Seems a role is only useful in the context of a project, it seems to me that's well covered already by the Projects view
16:42:16 <kanchan> Hi David
16:42:24 <david-lyle> once the default project part goes away, the need is eliminated
16:42:28 <david-lyle> hello
16:42:40 <kanchan> role will be added in Update user form
16:43:00 <kanchan> and by default _member_ will be added
16:43:42 <kanchan> just to maintain the consistency with CreateUserForm
16:44:25 <sanjay> so what I understand is once default project is gone we don't need to update role here and we can do this from project tab
16:44:26 <sanjay> right
16:44:26 <sanjay> ?
16:45:25 <ericpeterson> not exactly.  default project is one thing, which is largely just confusion
16:45:25 <david-lyle> was looking at form and code
16:45:44 <ericpeterson> you could see a need for select a user and add role assignments to them
16:45:59 <david-lyle> but that's covered in a different form
16:46:19 <jpich> can roles be added without a reference to a specific project though?
16:46:21 <ericpeterson> I could see an argument to make that feature available from either spot, but yes
16:46:45 <david-lyle> but the update user form as is would not be that location
16:46:50 <ericpeterson> roles can exist without anything else..... a role assignment is the combination of a user, a role, on a project
16:47:10 <ericpeterson> role assignments is what makes the roles show up in your token
16:47:27 <david-lyle> yes you can't grant a role without a project
16:47:39 <jpich> So are you suggesting adding the whole membership widget to the user form, with the list of the existing projects?
16:47:57 <jpich> kinda like the reverse of what we have on the projects list, with the list of existing users?
16:48:05 <ericpeterson> yes, that *could* be something that people might want
16:48:23 <ericpeterson> not advocating that, but I could see a use case for it
16:48:43 <sanjay> yes some sort of reverse of what we have on the projects list
16:48:45 <david-lyle> I could see that use case as well, but that's not what's in the blueprint
16:48:50 <jpich> Ok, just making sure I understood since it's not about adding a single field anymore
16:49:13 <ericpeterson> yep.  once again I think I have derailed this train of thought.  sorry
16:50:16 <david-lyle> So the bp referenced as is should be obsolete, another blueprint to cover this other use case would be appropriate
16:51:11 <david-lyle> kanchan: default project is going away due to changes in keystone and more integration with ldap
16:51:19 <david-lyle> should have led with that :)
16:51:48 <david-lyle> default === primary
16:51:53 <kanchan> ok
16:52:23 <david-lyle> if default projects were going to still exist, the blueprint would make sense
16:52:45 <david-lyle> randomly picking a role for the user in the background doesn't make sense
16:53:10 <david-lyle> but, let's just remove the Primary Project selection
16:53:31 <sanjay> ok
16:54:27 <kanchan> ok
16:56:12 <sanjay> so should be log this as wishlist in launchpad (remove the primary project)
16:57:11 <david-lyle> Since the DST change was already confusing... we're also going to look to stagger that meeting times going forward to make sure that folks in Japan, China and Australia can attend
16:57:36 <david-lyle> There will be a survey on times coming up
16:57:38 <jpich> See the thread at http://lists.openstack.org/pipermail/openstack-dev/2014-November/050095.html
16:58:21 <jpich> Alternate meeting times to include more people sounds great to me!
16:58:28 * david-lyle didn't check openstack-dev before meeting
16:58:44 <jpich> No doodles yet, but disagreements already. Finding the new time(s) should be fun ;)
16:58:53 <david-lyle> always is
16:59:35 <david-lyle> no two times will work perfectly for anyone, so be flexible people :)
16:59:52 <david-lyle> sanjay: not sure it's wishlist, but a bug
17:00:12 <david-lyle> primary project has never really worked
17:00:17 <david-lyle> times up
17:00:25 <david-lyle> Thanks everyone, have a great week!
17:00:27 <akrivoka> thanks everyone!
17:00:32 <akrivoka> \o
17:00:36 <david-lyle_afk> #endmeeting