20:00:10 <ying_zuo> #startmeeting horizon
20:00:13 <openstack> Meeting started Wed Jan 31 20:00:10 2018 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:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:17 <openstack> The meeting name has been set to 'horizon'
20:00:21 <ying_zuo> Hi everyone!
20:00:37 <lajos> Hi
20:01:22 <ying_zuo> #topic RC-1 milestone
20:01:33 <ying_zuo> Queens-3 was released last week
20:01:40 <ying_zuo> #link https://launchpad.net/horizon/+milestone/queens-3
20:01:50 <amotoki> hi
20:01:51 <ying_zuo> Thanks everyone's great work on it!
20:02:03 <ying_zuo> we are in RC-1 right now
20:02:08 <ying_zuo> #link https://launchpad.net/horizon/+milestone/queens-rc1
20:02:25 <ying_zuo> so only patches for translation and bug fixes will be merged
20:02:57 <ying_zuo> #topic Rocky PTG
20:03:19 <e0ne> hi
20:03:24 <ying_zuo> #link https://docs.google.com/spreadsheets/d/e/2PACX-1vRmqAAQZA1rIzlNJpVp-X60-z6jMn_95BKWtf0csGT9LkDharY-mppI25KjiuRasmK413MxXcoSU7ki/pubhtml
20:03:40 <ying_zuo> #link https://etherpad.openstack.org/p/horizon-ptg-rocky
20:04:01 <ying_zuo> please add the topics that you want to discuss on the etherpad
20:04:11 <ying_zuo> there are already some good ones there
20:04:12 <e0ne> ying_zuo: could you please add etherpad link to https://wiki.openstack.org/wiki/PTG/Rocky/Etherpads?
20:04:26 <ying_zuo> will do
20:04:41 <e0ne> thanks
20:04:52 <ying_zuo> you can also find this link in #openstack-horizon IRC channel
20:05:06 <amotoki> added
20:05:21 <ying_zuo> #topic Open Discussion
20:05:39 <amotoki> hey.... the meeting agenda is not checked? https://wiki.openstack.org/wiki/Meetings/Horizon
20:05:49 <amotoki> i added several items....
20:06:12 <amotoki> or is it no longer used?
20:06:16 <ying_zuo> #topic FFE discussion
20:06:29 <lajoskatona> Thanks :-)
20:06:34 <ying_zuo> it's used, I didn't a notification so didn't know there are updates
20:06:56 <ying_zuo> #info Trunk admin panel
20:07:04 <ying_zuo> #link http://lists.openstack.org/pipermail/openstack-dev/2018-January/126694.html
20:07:14 <ying_zuo> #link https://review.openstack.org/#/c/516657/
20:07:17 <e0ne> I +2'ed on the patch
20:07:29 <lajoskatona> Thanks for everybody.
20:07:32 <e0ne> ying_zuo: we need your +2/-2 on this
20:08:48 <ying_zuo> afaik, we can't merge feature related patches after Q3
20:09:08 <ying_zuo> I don't know when we can make an exception for this
20:09:23 <e0ne> ying_zuo: it's up to you as PTL to allow feature freeze exception for this patch
20:09:36 <dklyle> ying_zuo, you can allow feature exceptions in the RC period
20:09:41 <amotoki> ying_zuo: so you don't have any FFE process?
20:10:04 <amotoki> anyway, it's up to the PTL
20:10:40 <e0ne> amotoki: +1
20:10:53 <ying_zuo> is this the last patch for the blueprint?
20:11:09 <lajoskatona> yeah it seems.
20:11:15 <amotoki> yes, the ML post describes it
20:11:24 <amotoki> #link https://review.openstack.org/#/q/topic:bp/neutron-trunk-ui+(status:open+OR+status:merged)
20:12:17 <lajoskatona> There was another request from Akihiro, but we opened a bug for that (to have links for ports: #1746082
20:12:27 <amotoki> as my neutron core hat, I can say the feature is completed by this patch.
20:13:06 <ying_zuo> okay. I am fine with it
20:13:16 <lajoskatona> \o/
20:13:19 <lajoskatona> Thanks
20:13:44 <ying_zuo> sure. thanks for completing the blueprint :)
20:14:13 <ying_zuo> #topic Request to review targeted to RC1
20:14:24 <ying_zuo> #link https://review.openstack.org/539534
20:14:32 <amotoki> I just listed pending reviews as FYI.
20:14:45 <ying_zuo> #link https://review.openstack.org/538472
20:15:00 <ying_zuo> #link https://review.openstack.org/#/c/539528/
20:15:10 <ying_zuo> #link https://review.openstack.org/#/c/539530
20:15:20 <ying_zuo> #link https://review.openstack.org/#/c/527670/
20:15:29 <ying_zuo> thanks amotoki
20:16:06 <amotoki> if there are any other reviews to be raised, feel free to raise it. all above are from me.
20:16:56 <ying_zuo> #topic Open Discussion
20:17:18 <amotoki> how do we move forward the ngdetail refresh?
20:17:47 <amotoki> do we land minimum in queens, or defer all to Rocky?
20:18:21 <e0ne> just a reminder that Pike will be in Phase II in February, so we need to backport bugs to it befoere that deadline
20:18:28 <e0ne> #link https://releases.openstack.org/
20:18:52 <ying_zuo> if we have to take it as it is, then we can create a lower priority ticket
20:19:05 <ying_zuo> e0ne: thanks for the reminder
20:19:11 <e0ne> ying_zuo: np
20:19:16 <amotoki> #link https://review.openstack.org/#/q/status:open+project:openstack/horizon+branch:stable/pike
20:19:23 <amotoki> #link https://review.openstack.org/#/q/status:open+project:openstack/horizon+branch:stable/ocata
20:19:30 <lajoskatona> As I see there will be some discussion in Dublin as well for that topic
20:19:40 <lajoskatona> I mean the ngDetails
20:19:44 <e0ne> amotoki: do you have a link for ngDetail branch by the hand?
20:19:48 <ying_zuo> #link https://review.openstack.org/#/q/status:open+project:openstack/horizon+branch:stable/pike
20:19:58 <ying_zuo> some of them need another +2
20:20:23 <ying_zuo> oh amotoki is faster than me :)
20:21:00 <amotoki> re: stable branches, I heard robcresswell that backports from stable cores needs a single +2 when I was added to the stable team.
20:21:03 <lajoskatona> The tipic for ngDetails: https://review.openstack.org/#/q/topic:bug/1681627+(status:open+OR+status:merged)
20:21:09 <amotoki> I am not sure this policy is applied now.
20:22:42 <ying_zuo> yes, that's right
20:23:49 <ying_zuo> just merged two from amotoki :)
20:23:51 <amotoki> e0ne: are you familiar with the stable policy?
20:24:11 <e0ne> amotoki: what actually do you mean?
20:24:20 <amotoki> e0ne: i think you are a candidate for the stable team.
20:24:25 <e0ne> I read the docs and maintain stable branches in cinder too
20:24:32 <e0ne> amotoki: :)
20:24:36 <amotoki> we have only three cores in the stable team now.
20:24:47 <amotoki> *three active cores*
20:24:56 <e0ne> I'm trying to follow upstream stable policy in our downstream too
20:25:15 <amotoki> e0ne: nice
20:25:50 <ying_zuo> #link https://docs.openstack.org/project-team-guide/stable-branches.html
20:27:43 <amotoki> there is no decision needed here. anyway it would be nice if we have healthy review team for stable branches :)
20:28:22 <amotoki> lajoskatona: thanks for ngdetail link
20:28:41 <e0ne> amotoki: +1
20:29:24 <ying_zuo> +1
20:30:03 <amotoki> can we back to ngdetail refresh?
20:31:15 <amotoki> what do you think about the first one https://review.openstack.org/#/c/520340/ ?
20:31:40 <ying_zuo> yes like I mentioned, will need to create a bug report for the issues if we have to merge it as it is
20:32:06 <amotoki> +1 to ying_zuo's suggestion
20:32:50 <e0ne> why can't we use an existing bug https://bugs.launchpad.net/zun-ui/+bug/1681627?
20:32:51 <openstack> Launchpad bug 1681627 in Zun UI "Page not found error on refreshing bowser " [Critical,In progress] - Assigned to Shu Muto (shu-mutou)
20:34:01 <ying_zuo> that's fine too
20:34:01 <amotoki> e0ne: I think it is because fixing a bug across releases is sometimes not easy to track.
20:35:17 <e0ne> I want to test these patches before I put my vote in gerrit
20:35:23 <amotoki> so in my understanding ying_zuo's suggestion is to close bug 1681627 with the first one and to open another bug for further fix (like navigation issue)
20:35:26 <openstack> bug 1681627 in Zun UI "Page not found error on refreshing bowser " [Critical,In progress] https://launchpad.net/bugs/1681627 - Assigned to Shu Muto (shu-mutou)
20:35:26 <e0ne> will try to do it this week
20:35:28 <amotoki> e0ne: of course
20:36:11 <ying_zuo> amotoki: yes, that may be better
20:36:33 <e0ne> such bugs are very annoying for users (and me) :(
20:37:17 <amotoki> after merging https://review.openstack.org/#/c/524948/, the thing becomes worse
20:37:34 <e0ne> :(
20:37:36 <amotoki> when we back to a ngdetail page by browser back button, we will get not found.
20:38:07 <e0ne> :(
20:38:38 <e0ne> I tested that patch but didn't face the issue with ngdetail
20:39:12 <e0ne> will test again tomorrow or on Friday
20:39:22 <amotoki> for example, go to a image detai, go to the instance table and then click a back button
20:40:06 <ying_zuo> those are separate issues
20:42:03 <amotoki> separate issues but I think an error is triggered by a direct url to ngdetail page
20:42:22 <e0ne> it sounds reasonable
20:42:55 <ying_zuo> yes
20:43:40 <amotoki> so I think the root cause is same
20:44:27 <ying_zuo> agree
20:45:56 <ying_zuo> are there any other topics from anyone?
20:47:02 <ying_zuo> alright. thanks everyone for joining!
20:47:17 <ying_zuo> #endmeeting