12:12:48 <mrunge> #startmeeting Horizon
12:12:50 <openstack> Meeting started Wed Jul  8 12:12:48 2015 UTC and is due to finish in 60 minutes.  The chair is mrunge. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:12:51 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:12:53 <openstack> The meeting name has been set to 'horizon'
12:12:53 <mrunge> :D
12:12:56 <mrunge> hello
12:13:05 <tsufiev> o/
12:13:08 <doug-fish> hi!
12:13:12 <r1chardj0n3s> o/
12:13:16 <neillc> hello
12:13:21 <zhenguo> o/
12:13:24 <rdopiera> hi
12:13:57 <ddomingo> hi
12:14:12 <mrunge> it looks like david-ly_ couldn't make it for todays meeting.
12:14:24 <mrunge> let's have a more informal meeting then
12:14:45 <mrunge> #topic open discussion
12:15:04 <mrunge> Agenda for today: https://wiki.openstack.org/wiki/Meetings/Horizon
12:15:07 <mrunge> (empty)
12:15:16 <mrunge> do you have anything to discuss?
12:15:53 <kzaitsev_mb> late o/
12:16:11 <mrunge> o/
12:16:16 <zhenguo> mrunge, about volume migration bp https://review.openstack.org/#/c/186810/, can you help to review :)
12:17:25 <mrunge> zhenguo, will have a brief look at that, thanks!
12:17:37 <ddomingo> also, next steps for https://blueprints.launchpad.net/horizon/+spec/context-sensitive-help ?
12:17:43 <zhenguo> mrunge, thanks
12:18:41 <tsufiev> I'd like to come up with the question I was going to raise in a ML several days ago (well, I'm procrastinating): 'region' entity naming in Horizon and Keystone
12:19:28 <tsufiev> so, the problem here IMO is that the name is the same for 2 different entities - service regions (inside keystone catalog) and AVAILABLE_REGIONS setting inside Horizon
12:19:37 <tsufiev> that's a great source of confusion
12:19:46 <doug-fish> tsufiev: agreed!
12:20:15 <mrunge> yes, tsufiev
12:20:16 <tsufiev> especially when there is some bug - we had such situation recently and I had great challenge in explaining what part is actually broken
12:20:25 <mrunge> that's right
12:20:34 <doug-fish> I just went through the same experience recently
12:20:52 <doug-fish> I think the "AVAILABLE_REGIONS" related usage of regions is incorrect.
12:20:56 <doug-fish> is that agreed on?
12:21:06 <mrunge> yepp. even within this community this is quite unclear
12:21:11 <mrunge> doug-fish, yes!
12:21:36 <mrunge> tsufiev, since that touches horizon and keystone, you should take it to ML
12:21:59 <tsufiev> mrunge okay, I'll start a thread then so we could agree on a better naming
12:22:10 <tsufiev> will add [docs] to subj as well
12:22:20 <mrunge> tsufiev, yes, please do
12:23:14 <mrunge> I was just fiddling with the region/project/whatever selector a few mins ago
12:23:28 <mrunge> this is quite unclear, what this really does
12:23:47 <mrunge> as one could even have combinations of regions/projects etc.
12:24:25 <mrunge> ddomingo, last week, we briefly discussed https://blueprints.launchpad.net/horizon/+spec/context-sensitive-help
12:24:44 <ddomingo> mrunge, thanks. sorry I missed it
12:24:50 <mrunge> there were a few thoughts, but not that much has been added to the whiteboard
12:25:20 <doug-fish> I added a couple of comments to the blueprint - but there was some discussion about comparing it to the existing help capabilities in the new launch instance wizard too
12:25:28 <mrunge> IIRC, lots of us were really looking forward to have context sensitive help
12:25:33 <mrunge> ah yes, right doug-fish
12:25:36 <ddomingo> i responded to the reply in the whiteboard
12:25:47 <doug-fish> yeah it was well received
12:26:25 <ddomingo> thanks. i'd do the patch myself if i could, but my skills are pretty limited to documentation
12:26:47 <mrunge> ddomingo, maybe the next step would be to provide a proof of concept to share
12:26:56 <ddomingo> if you guys could finalize how the HELPLINKS.json syntax should go, i can get started on it
12:27:36 <ddomingo> ie. the mapping of pages to contextual links, i mean
12:28:13 <mrunge> it would be great, if that could be pluggable
12:28:28 <mrunge> i.e. add another file/directory and help would be extended
12:28:48 <mrunge> that would go well with any extension mechanism
12:29:39 <mrunge> ddomingo, I *think*, we could start with a more static version
12:29:52 <ddomingo> static version?
12:29:58 <mrunge> i.e. just a single .json file
12:30:21 <doug-fish> yeah - if there are limited developer resources for this, that would make it simpler
12:30:31 <mrunge> the syntax even be WIP
12:30:57 <mrunge> changing that later should be fine
12:31:02 <ddomingo> ok
12:31:22 <mrunge> ddomingo, you had a proposal in the bp. that's something where I would start from
12:32:48 <ddomingo> mrunge: yeah, I actually noted in the BP that we use a single file to specify mappings between contexts (ie. pages) and related links. the reason for this was to make it easy for upstream tech writers to help maintain it
12:33:11 <mrunge> ddomingo, yes, sure. I got that.
12:33:36 <^Gal^> Hi, would like to disscuss upon my blueprint: https://blueprints.launchpad.net/horizon/+spec/stack-add-additional-files
12:33:56 <mrunge> as second step I could imagine, horizon to be extended by some plugin.
12:34:09 <mrunge> the plugin should get a context help, too
12:34:39 <mrunge> but a plugin mechanism could append HELPLINKS.json to provide that
12:34:40 <ddomingo> ok
12:34:59 <ddomingo> ah ok
12:35:20 <mrunge> it still should be pretty straightforward
12:36:04 <mrunge> ^Gal^, what would you like to discuss there?
12:38:12 <^Gal^> just to know what do you guys think about it
12:39:11 <doug-fish> ^Gal^: it seems reasonable - I don't know that much about extra files and heat templates ... is it not possible to parse the template and determine what additional files might be needed?
12:40:51 <^Gal^> not at the moment
12:41:47 <doug-fish> maybe that can be something for phase 2.  :-)
12:42:53 <^Gal^> @doug-fish what do you mean by phase 2? :)
12:43:36 <doug-fish> thinking about it more ... it's a nice capability the way you've defined it. phase 2 = improvements to be made at some undefined point in the future when we all have free time or our employers and/or customers demand it.
12:43:58 <^Gal^> oh ok
12:44:15 <^Gal^> tnx
12:45:09 <mrunge> ^Gal^, I'd say, come up with a proposal then
12:46:08 <mrunge> ^Gal^, uhm can't those files reference each other?
12:46:53 <mrunge> and if yes, how would one visualize that?
12:47:30 <doug-fish> mrunge: that's even harder than the phase 2 I was thinking of!
12:47:45 <^Gal^> thats the first idea i had
12:47:50 <doug-fish> now you want to parse them all! not just the template
12:47:51 <^Gal^> having the files relate to each other
12:47:53 <^Gal^> but
12:48:23 <^Gal^> not all heat users are happy with that
12:48:46 <^Gal^> it's to change the way they write templates
12:48:54 <mrunge> yes, it's a bit hard to understand
12:49:08 <mrunge> on the other side, it makes templates reusable
12:49:16 <^Gal^> I agree
12:49:23 <tsufiev> ^Gal^, that (how templates are written) sounds like the issue that Merlin is trying to solve
12:51:18 <mrunge> is there anything else to discuss?
12:51:28 * tsufiev is advertising topology graph patch https://review.openstack.org/#/c/199063/ once again, this time for the record :)
12:51:41 <mrunge> tsufiev++
12:51:57 <mrunge> ah, we don't have a karma bot here ;-)
12:52:04 <tsufiev> just in case some Angular.js-oriented guys from the PST would like to join the effort :)
12:52:26 <mrunge> it's still a bit early for them, tsufiev
12:52:43 <tsufiev> mrunge, yep, I know, I just hope they will read the logs
12:53:03 <mrunge> uhm, before I'll leave you, I would like to advertise to UPDATE YOUR FLASH PLUGINS
12:53:06 <mrunge> https://helpx.adobe.com/security/products/flash-player/apsa15-03.html
12:53:17 <^Gal^> i'm an angular guy :)
12:53:31 <r1chardj0n3s> so'm I :)
12:53:41 <mrunge> ^Gal^, you might want to have a look at tsufiev s patch
12:53:50 <^Gal^> yep i'm looking at it now
12:53:56 <mrunge> cool
12:53:57 <^Gal^> :D
12:53:59 <tsufiev> ^Gal^, r1chardj0n3s so welcome in the patch :)
12:54:12 <r1chardj0n3s> (but it's time for sleep here now, sorry - patch tomorrow!)
12:54:21 <mrunge> thanks for coming here
12:54:23 <tsufiev> r1chardj0n3s, np )
12:54:41 <mrunge> sorry I wasn't better prepared
12:54:47 <mrunge> #endmeeting