20:00:37 <ying_zuo> #startmeeting horizon
20:00:38 <openstack> Meeting started Wed Oct 25 20:00:37 2017 UTC and is due to finish in 60 minutes.  The chair is ying_zuo. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:41 <openstack> The meeting name has been set to 'horizon'
20:00:54 <ying_zuo> Hi everyone :)
20:00:57 <e0ne> hi
20:01:00 <gary-smith_> o/
20:01:02 <deshipu> o/
20:01:44 <lajoskatona_> o/
20:02:16 <Kvisle> o/
20:02:17 <ying_zuo> o/
20:02:22 <ying_zuo> #topic Notices
20:02:29 <ying_zuo> #info Queens-2 development cycle has started
20:02:34 <ying_zuo> #link https://review.openstack.org/#/c/513432/
20:02:40 <ying_zuo> once this patch is merged, Horizon Queens-1 will be released officially, which should happen anytime from now
20:02:56 <ying_zuo> #link https://launchpad.net/horizon/+milestone/queens-2
20:03:12 <ying_zuo> here's the list of tickets targetted for Queens-2 at the moment
20:03:31 <ying_zuo> we usually set the target milestone for critical issues or when the patch is in a good state
20:03:44 <ying_zuo> so the list will grow as the time progresses
20:04:20 <ying_zuo> #info Horizon Sessions at the Sydney Summit
20:04:28 <ying_zuo> The schedule has been posted
20:04:37 <ying_zuo> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/global-search?t=horizon
20:05:13 <e0ne> ying_zuo: why some of those bugs have 'fix released' status instead of 'fix commited'?
20:05:50 <deshipu> I think that may be because they have been backported and released
20:05:55 <ying_zuo> I think that's the status set by launchpad
20:06:06 <ying_zuo> if the patch is merged
20:06:20 <ying_zuo> I don't think I have seen "fix commited"
20:06:59 <ying_zuo> that would be a more appropriate status
20:07:52 <e0ne> ying_zuo: thanks. looks like it's set but bot or launchpad
20:08:01 <lajoskatona_> ying_zuo: trunk is intentionally missing from the blueprint list?
20:08:18 <lajoskatona_> I am not that familiar with the administration of the blueprints
20:08:28 <ying_zuo> e0ne: I will double check if it's configurable in launchpad
20:08:41 <e0ne> ying_zuo: thanks
20:08:56 <ying_zuo> lajoskatona_: I just moved the bug reports to this milestone
20:09:40 <ying_zuo> I will check the state of the patches for the blueprints targetted for queens-1 and to decide where they should be
20:09:53 <ying_zuo> either Queens-2 or next
20:10:03 <lajoskatona_> ying_zou: ok, thanks for clarification
20:10:31 <ying_zuo> cool
20:10:44 <e0ne> ying_zuo: e.g.  heat sets fix commited for bugs https://launchpad.net/heat/+milestone/queens-2
20:11:17 <ying_zuo> good to know so it's probably configurable
20:11:23 <ying_zuo> thanks e0ne
20:11:30 <e0ne> ying_zuo: np
20:11:55 <e0ne> we used this status (fix commited) for the cinder too
20:12:08 <e0ne> it's more clear for operators
20:12:08 <ying_zuo> cool
20:12:23 <ying_zuo> going back to the Sydney summit topic
20:12:44 <ying_zuo> I look forward to meeting everyone at the summit in less than two weeks!
20:13:00 <ying_zuo> there won’t be IRC meeting during the week
20:13:38 <e0ne> I'll miss the Summit this time :(
20:13:49 <ying_zuo> :(
20:14:12 <ying_zuo> anyone here is going?
20:14:52 <ying_zuo> yes, it's quite far this time
20:14:59 <lajoskatona_> Bence Romsics (rubasev) will join the summit
20:15:13 <ying_zuo> great!
20:15:39 <e0ne> ying_zuo: I would like to say, that it's too expensive this time
20:16:06 <ying_zuo> yes, that's what I meant by "far" :p
20:16:12 <e0ne> :)
20:16:42 <ying_zuo> #topic Bug Reports Review
20:16:49 <ying_zuo> #link https://etherpad.openstack.org/p/horizon-bug-review
20:17:02 <ying_zuo> #link https://bugs.launchpad.net/horizon/+bug/1723142
20:17:03 <openstack> Launchpad bug 1723142 in OpenStack Dashboard (Horizon) "network topology page doesn't scale" [High,Confirmed]
20:18:16 <ying_zuo> I am aware of the performance issue on topology panel
20:18:38 <ying_zuo> according to this ticket, it's just the console link
20:19:51 <ying_zuo> 20 seconds faster for an environment with 100 vms is awesome!
20:21:08 <ying_zuo> any thoughts on amotoki's suggestions?
20:21:19 <ying_zuo> comment #5
20:21:53 <e0ne> ying_zuo: I like an option "* Replace "Open Console" link with the URL of the console tab of the detail page"
20:21:53 <Kvisle> 'Replace "Open Console" link with the URL of the console tab of the detail page' sounds pretty decent to me
20:22:37 <ying_zuo> same here
20:22:41 <gary-smith_> +1
20:22:59 <ying_zuo> wonder if anyone opens console from the topology panel
20:23:07 <ying_zuo> I don't :p
20:23:36 <Kvisle> the part about auto-refresh sounds pretty reasonable too
20:24:33 <ying_zuo> probably a good question to ask in the user feedback session at the summit too
20:24:59 <ying_zuo> #link https://bugs.launchpad.net/horizon/+bug/1678204
20:25:00 <openstack> Launchpad bug 1678204 in OpenStack Dashboard (Horizon) "User logged out when transitioning to a project with non-admin role" [High,New]
20:25:40 <ying_zuo> e0ne: I think you mentioned a similar issue before?
20:26:07 <ying_zuo> is it this one or something else?
20:27:51 * e0ne_ had some issue with wi-fi:(
20:28:14 <ying_zuo> IIRC the discussion ended with trying to catch the exception and redirect to the login page
20:29:11 <ying_zuo> oh, just saw your comment there
20:29:11 <e0ne_> #link https://review.openstack.org/#/c/491479/ - could be related patch
20:29:34 <e0ne_> technically, my bug is a duplicate of this one
20:30:22 <ying_zuo> :)
20:30:45 <ying_zuo> it's still unassigned
20:31:18 <e0ne_> IMO, it's OK to close it as duplicate
20:31:43 <e0ne_> my patch fixes issue with 'next' param on the login page
20:31:57 <e0ne_> rdopiera: are you around?
20:32:15 <ying_zuo> we usually mark the one created after as a duplicate
20:33:01 <e0ne_> ying_zuo: +1 on this. but the newer bug has already merged patch
20:33:28 <ying_zuo> oh right
20:33:39 <e0ne_> ying_zuo: it's up to you to decide what bug will be marked as duplicate
20:33:49 <ying_zuo> sure. duplicate this one then
20:34:15 <ying_zuo> #link https://bugs.launchpad.net/horizon/+bug/1646305
20:34:16 <openstack> Launchpad bug 1646305 in OpenStack Dashboard (Horizon) "Federation URL is public, but AUTH_URL is private" [Medium,New]
20:34:25 <e0ne_> ying_zuo: oh... wait please
20:34:48 <e0ne_> ying_zuo: the case " For example, switching projects from the Admin->System->Hypervisors tab will show the page template with no data." is not fixed
20:35:05 <ying_zuo> it's still the same?
20:35:25 <e0ne_> ying_zuo: actually, it's a bit more complex one
20:35:51 <e0ne_> ying_zuo: I'll assign this bug to myself to fix it
20:36:03 <e0ne_> this bug is partially-fixed
20:36:25 <ying_zuo> thank you
20:36:55 <ying_zuo> going back to https://bugs.launchpad.net/horizon/+bug/1646305
20:36:57 <openstack> Launchpad bug 1646305 in OpenStack Dashboard (Horizon) "Federation URL is public, but AUTH_URL is private" [Medium,New]
20:37:54 <ying_zuo> david-lyle: are you here?
20:39:03 <ying_zuo> alright. our federation expert is not here
20:39:14 <ying_zuo> any thoughts on this one?
20:40:49 <ying_zuo> if not, we will move to the last one
20:40:51 <ying_zuo> #link https://bugs.launchpad.net/horizon/+bug/1725493
20:40:52 <openstack> Launchpad bug 1725493 in OpenStack Dashboard (Horizon) "Is "Server" better rather than "Instance"?" [Undecided,New]
20:41:52 <ying_zuo> the other options are virtual machine or vm :p
20:42:18 <Kvisle> are there any good reasons to not follow the same conventions as the openstack cli?
20:42:25 <Kvisle> (server)
20:42:39 <e0ne> it would be good to get operators feedback for this topic
20:43:13 <ying_zuo> +1
20:43:44 <Kvisle> in this context; what does an operator mean? someone who operates openstack in production?
20:43:51 <ying_zuo> Kvisle: that's usually the case but I don't think it's a hard requirement for horizon
20:43:54 <Kvisle> <-- new here.
20:44:24 <e0ne> Kvisle: yes, I mean openstack administrators and deployers
20:44:41 <ying_zuo> but we have been using instance as far as I know
20:45:18 <e0ne> #link https://developer.openstack.org/api-ref/compute/#servers-servers - nova api reference
20:45:57 <e0ne> ying_zuo: IMO, it's the same as we had in the past between 'project' and 'tenant'
20:46:10 <ying_zuo> :)
20:46:11 <Kvisle> (I operate a not very large, but very production openstack cluster for an ISP in Norway) -- I'm in favour of consistency.
20:46:15 <e0ne> from my PoV, there're 2 options:
20:46:21 <e0ne> 1) ask operators
20:46:59 <e0ne> 2) do the same as openstack client did. does it use 'instance' or 'server'?
20:47:06 <Kvisle> server
20:47:14 <ying_zuo> Kvisle: do you meant consistent with the cli or consistent with the older version of horizon?
20:47:24 <Kvisle> ying_zuo: consistent with the cli
20:47:46 <e0ne> I  thinks consistency with OSC is very good point
20:47:56 <e0ne> s/thinks/think
20:47:56 <lajoskatona_> Make sense and extra work
20:48:47 <ying_zuo> yes, this is low priority
20:49:02 <ying_zuo> I will ask in the user feedback session though
20:49:05 <e0ne> #link https://docs.openstack.org/python-openstackclient/latest/cli/command-objects/server.html - OSC CLI reference
20:50:01 <e0ne> 10mins friendly reminder
20:50:10 <ying_zuo> #topic Open Discussion
20:50:50 <ying_zuo> are there any questions or review requests?
20:51:37 <lajoskatona_> ying_zuo: rubasov added to the trunk blueprint whiteboard the problematic/questionable parts for which we need feedback
20:51:53 <ying_zuo> thanks lajoskatona_
20:51:59 <ying_zuo> I will take a look
20:52:20 <lajoskatona_> ying_zuo: (https://blueprints.launchpad.net/horizon/+spec/neutron-trunk-ui), some are quite long but hard to explain
20:52:22 <lajoskatona_> ok thanks
20:52:47 <lajoskatona_> In the meantime we got really useful feedback from Akihiro, we will include those as well
20:53:13 <ying_zuo> great
20:53:32 <lajoskatona_> ying_zuo: By the way, in the PTG there was some discussion about handling admin panels from angular, but can't recall the result
20:53:51 <lajoskatona_> and one of Akihiro's comment related to that.
20:54:23 <ying_zuo> you mean having admin and project dashboard vs. one dashboard?
20:55:09 <lajoskatona_> ying_zuo: Could you (somebody) give some direction how to move forward with the panel if we want to have admin panel as well? Or that is not needed?
20:55:10 <ying_zuo> for that, we decided to keep separate admin and project panels
20:56:06 <ying_zuo> separate panels unless the info is the same
20:56:08 <lajoskatona_> ying_zuo: So duplicate the django code (small in the new angular panels) and angular will do the things for filtering whatever?
20:56:29 <ying_zuo> the admin panel should show more info
20:56:41 <lajoskatona_> ok, we think about that if are in one or the other group :-)
20:57:04 <lajoskatona_> ok, make sense
20:57:07 <lajoskatona_> thanks
20:58:14 <ying_zuo> great! thanks everyone for joining
20:58:34 <lajoskatona_> Bye
20:58:46 <ying_zuo> #endmeeting