15:01:55 <amotoki> #startmeeting horizon
15:01:55 <openstack> Meeting started Wed Apr  8 15:01:55 2020 UTC and is due to finish in 60 minutes.  The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:56 <amotoki> hi
15:01:57 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:00 <openstack> The meeting name has been set to 'horizon'
15:02:11 <vishalmanchanda> hi
15:02:34 <e0ne> hi
15:03:18 <rosmaita> e0ne: congratulations!
15:03:53 <amotoki> okay, let's start
15:03:55 <e0ne> rosmaita: thanks :)
15:04:02 <amotoki> #topic notices/announcements
15:04:23 <amotoki> this week is milestone-3 i.e. feature freeze
15:04:58 <amotoki> I will prepare a release patch tomorrow or early Friday in local time
15:05:20 <e0ne> amotoki: do we have anything we should merge before FF?
15:05:41 <amotoki> I haven't checked the list yet. I would like to look thru pending reviews later in this meeting.
15:06:19 <e0ne> ok
15:06:53 <amotoki> another thing is TC voting period started.
15:07:26 <amotoki> you can ask questions to TC candidates in the mailing list as you already see.
15:08:06 <amotoki> one more
15:08:20 <amotoki> virtual PTG planning is ongoing https://etherpad.openstack.org/p/Virtual_PTG_Planning
15:08:37 <amotoki> you can find discussions in past meetings
15:09:14 <amotoki> it is not specific to individual projects but we can give input to planning if you have any
15:10:10 <amotoki> that's all from me as announcements
15:10:37 <amotoki> anything other?
15:11:11 <e0ne> nothing from me
15:11:20 <vishalmanchanda> none
15:11:26 <amotoki> moving on
15:11:40 <amotoki> #topic reviews for FF
15:11:57 <amotoki> I would like to discuss this topic first
15:12:56 <amotoki> I failed to find enough time to review vishalmanchanda's error msg stuff https://review.opendev.org/#/c/708069/
15:13:22 <amotoki> how do you think the status?
15:13:30 <vishalmanchanda> hmm np.
15:13:51 <vishalmanchanda> I will continue it in next cycle.
15:15:49 <amotoki> I will look and test it tomorrow. we can measure its readiness and risk.
15:16:09 <vishalmanchanda> I am not able to explore more from past two week due to poor internet connectivity in my area.
15:16:10 <amotoki> another one is https://review.opendev.org/709025
15:16:42 <amotoki> already +2 from e0ne
15:16:51 <amotoki> I looked thru it today
15:17:15 <vishalmanchanda> i have seen this patch but i didn't have env. to test it.
15:17:16 <amotoki> it is generally good, but it passes if-condition for display_name from the server side to client side
15:17:29 <vishalmanchanda> will take a look after the meeting.
15:17:53 <amotoki> that's the only point I am not a fan of, but it looks like a refactoring issue
15:18:24 <amotoki> so if it works well I would like to have it in ussuri
15:18:44 <amotoki> another one is https://review.opendev.org/#/c/630663/
15:19:13 <amotoki> e0ne is a co-author of this
15:19:25 <e0ne> amotoki: oh.. I miised your last comment :(
15:21:15 <amotoki> e0ne: my question does not block it. it is just a question.
15:22:02 <amotoki> I totally forgot a comment on patch set 3 when I posted it, but hopefully it still works
15:23:30 <amotoki> other two are maintenance stuffs https://review.opendev.org/714933 and https://review.opendev.org/#/c/715925/
15:23:51 <amotoki> requirements change might be better to be a part of ussuri-3
15:24:04 <amotoki> a release note is optional but nice to have it
15:24:50 <e0ne> amotoki: answered to your comments in gerrit
15:24:58 <amotoki> e0ne: thanks
15:25:04 <amotoki> ah.... do you think we need a release note on pyScss 1.3.6 or later?
15:25:48 <e0ne> according #714933 we can add a release note libpcre3-dev package but it's not mandatory anymore
15:26:17 <amotoki> yeah, I think we need another release note on a known issue on the material theme
15:26:18 <e0ne> amotoki: personally, I'm ok to wait 2 seconds more during deployment time
15:26:43 <amotoki> e0ne: +1
15:26:50 <e0ne> amotoki: I'd got a bug assigned to me. I didn't have a time to take a look on it
15:26:57 <e0ne> https://bugs.launchpad.net/horizon/+bug/1771559
15:26:58 <openstack> Launchpad bug 1771559 in OpenStack Dashboard (Horizon) "error while loading icon with pyscss 1.3.5 or later" [High,Confirmed] - Assigned to Ivan Kolodyazhny (e0ne)
15:27:15 <e0ne> IMO, we can add a release not or a fix before RC1
15:27:28 <amotoki> exactly
15:28:04 <e0ne> #715925 - I've already +2ed on it
15:28:06 <amotoki> I found similar scss code in the material them, so perhaps we can apply similar workaround
15:29:25 <amotoki> a final one in my list is https://review.opendev.org/#/c/711195/ (transition to pytest)
15:29:41 <amotoki> it requires dependency change, so I raise it here
15:30:02 <e0ne> I'm a co-author of this patch too, so I'm not feeling good to +2 on it
15:30:24 <amotoki> looking at the code, it looks good
15:30:32 <amotoki> I would like to run it locally before +2
15:30:51 <vishalmanchanda> will review it asap.
15:30:53 <amotoki> IMHO it is almost ready to go
15:31:22 <e0ne> thanks
15:31:24 <amotoki> I already reviewed it in detail :)
15:31:43 <vishalmanchanda> cool..
15:32:15 <amotoki> any other reviews good for ussuri feature freeze?
15:33:07 <vishalmanchanda> https://review.opendev.org/#/c/640981/
15:33:17 <vishalmanchanda> any thoughts on this patch?
15:33:54 <vishalmanchanda> or we can see it in next cycle.
15:33:56 <amotoki> IMHO we need to defer it to Victoria
15:34:14 <vishalmanchanda> sure.
15:34:19 <amotoki> it is because it needs changes in language code in zanata and the infra scripts
15:34:38 <e0ne> +1
15:34:54 <amotoki> even if we merge it, the infra script will override it and the patch will be reverted immediately
15:35:05 <vishalmanchanda> ohk.
15:36:57 <amotoki> okay, let's review them and hopefully we can have them in ussuri.
15:37:07 <vishalmanchanda> +1.
15:37:25 <amotoki> moving on
15:37:27 <amotoki> #topic General Priorities
15:37:40 <amotoki> I would like to share the status on "Catch up the new policy mechanism"
15:38:47 <amotoki> passing system_scope to the policy engine itself is simple, but it turns out it affects the horizon UI design
15:39:27 <amotoki> as of now, in the identity panel, the policy engine automatically switches the token from a project-scoped to a domain-scoped
15:39:45 <amotoki> so we can see the panels under the identity dashboard
15:40:14 <amotoki> to support system-scope, we need a system-scoped token
15:40:30 <amotoki> but we have a no way to switch to system-scoped token
15:40:58 <amotoki> we always depends on a project token (and domain_id in a user info)
15:41:17 <amotoki> we may need another scope "switch" mechanism
15:41:25 <e0ne> seems to be a good discussion on the PTG
15:42:11 <amotoki> I considered an option to automatically try a system-scoped token, but it looks too aggresive
15:42:35 <amotoki> e0ne: yeah
15:42:52 <amotoki> I will summarize what I investigated so far.
15:43:28 <amotoki> that's the update on the policy stuff.
15:44:20 <amotoki> next topic is about xstatic updates
15:44:52 <amotoki> I recently proposed xstatic maintenance updates under horizon governance.
15:45:21 <amotoki> two patches are pending https://review.opendev.org/#/q/project:%255E.*/xstatic-.*+status:open+owner:%22Akihiro+Motoki+%253Camotoki%2540gmail.com%253E%22
15:46:30 <amotoki> vishalmanchanda raised a question on whether we prepare a new version for the above two patches
15:47:18 <vishalmanchanda> yeah.
15:47:27 <rdopiera> I don't think a README change warrants a version bump
15:47:36 <e0ne> rdopiera: +1
15:47:39 <amotoki> I personally am okay to release new versions to sync PyPI and openstack/releases instead of reverting existing updates in the repo
15:47:47 <rdopiera> (also, I already made them start merging)
15:48:05 <vishalmanchanda> cool:)
15:48:46 <amotoki> thanks rdopiera
15:48:55 <amotoki> they are now in the gate queue
15:49:29 <amotoki> I will prepare a release patch after Ussuri-3
15:49:51 <amotoki> so that we can test them during RC period
15:50:07 <e0ne> +1
15:50:39 <amotoki> rdopiera: what about xstatic-angular-fileupload?
15:51:06 <rdopiera> I got distracted, I will release it next week
15:51:53 <amotoki> np
15:52:11 <e0ne> amotoki: there is one more patch  from me: https://review.opendev.org/#/c/718379/
15:52:28 <e0ne> amotoki: I'm not sure how to treat it: a bug or a feature...
15:52:40 <amotoki> e0ne: I think it is a bug
15:52:46 <e0ne> ok
15:53:00 <amotoki> we support custom templating for openrc but we don't provide enough info :(
15:53:04 <e0ne> so I'm ok to get it landed after FF
15:53:15 <amotoki> e0ne: bug report would be nice
15:53:31 <e0ne> amotoki: will do it
15:53:36 <amotoki> e0ne: thanks
15:53:52 <amotoki> rdopiera and all: do we want to have xstatic-angular-fileupload under the horizon governance?
15:54:10 <rdopiera> I think so
15:54:12 <amotoki> we already have the repository under openstack/ namespace, so the process would be much simpler
15:54:39 <rdopiera> what is involved?
15:54:45 <amotoki> in addition, the PyPI repo already allows openstackci to publish deliverables
15:54:47 <amotoki> https://pypi.org/project/XStatic-Angular-FileUpload/
15:55:52 <amotoki> I think what we need are (1) to add the repo under horizon in the governance repo and (2) configure publish-to-pypi in project-config
15:56:08 <amotoki> then it is ready to release a new version
15:56:19 <amotoki> this is another way to publish a new version
15:56:45 <amotoki> rdopiera: one question: how urgent do we need a new version of xstaic-angular-fileupload?
15:56:52 <rdopiera> amotoki: not at all
15:57:31 <rdopiera> I don't know any CVEs or bugfixes we need in it, I just upgraded it because it was alphebetically at the beginning of the list
15:57:44 <amotoki> :)
15:57:52 <rdopiera> however, it would be nice to have it cleaned up eventually
15:57:58 <rdopiera> but it doesn't have to be ussuri
15:58:06 <amotoki> so it looks better to add xstaic-angular-fileupload to OpenStack governance so that everyone can cut a release
15:58:50 <amotoki> does it make sense?
15:58:57 <e0ne> +1
15:59:02 <rdopiera> yes
15:59:44 <amotoki> thanks, I will move the transition forward along with other xstatic releases.
16:00:06 <amotoki> oh, we are out of time
16:00:16 <amotoki> if anything other, let's continue in #-horizon
16:00:20 <amotoki> thanks for joining
16:00:22 <amotoki> #endmeeting