15:01:25 #startmeeting horizon 15:01:26 Meeting started Wed Jan 20 15:01:25 2021 UTC and is due to finish in 60 minutes. The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:27 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:30 The meeting name has been set to 'horizon' 15:02:12 hi everybody 15:02:15 o/ 15:02:17 o/ 15:02:18 o/ 15:02:22 hi all 15:02:49 we've got a good team to start with :) 15:03:13 #topic Notices 15:03:39 tomorrow is the wallaby-2 milestone 15:03:58 #link https://releases.openstack.org/wallaby/schedule.html#wallaby-2-milestone 15:04:07 nothing special for horizon 15:04:39 we'll just cut a new release to provide as early as possible it for plugins and users 15:05:05 it's not required but let's allow plugins to test the latest code 15:08:22 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019672.html 15:08:50 ^^ it's lower-contraints discussion 15:09:31 TC will discuss it tomorrow during the meeting 15:09:39 #link https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting 15:10:04 and the last one 15:10:05 some ideas are proposed in this thread 15:10:06 #link https://review.opendev.org/c/openstack/governance/+/770860 15:10:29 ^^ here is the list of proposed runtimes for X release 15:11:09 perhaps it does not affect horizon at least in Xena 15:11:27 horizon dependencies like scss does not support python3.9 and django3 15:11:39 so it would be an issue when we start to support python3.9 15:12:43 let's see. probably it's a good idea to have non-voting job with python3.9 15:13:35 perhaps unit test succeeds with py39 as scss and django-scss aree not related to UT 15:14:34 :( 15:14:49 e0ne: I think you are now one of maintainers of scss? 15:15:22 my memory is not sure on how we handle scss and django-scss when they hit a problem last time 15:15:25 yes, and I can merge pull request with python3.9 support :) 15:15:56 amotoki: I forked that projects and we switched to forks 15:16:21 amotoki: later I became a maintainer of pyscss and fixed it, so we switched back to pyscss 15:16:22 e0ne: but I think we moved back to the original one? 15:16:41 you wrote faster than me :) 15:16:57 :) 15:17:01 we see several warnings when we run manage.py compress with py3 http://paste.openstack.org/show/801774/ 15:17:23 perhaps they need to be addressed for py39 15:18:12 thanks! 15:18:25 at least, I'll file a bug for pyscss :) 15:19:41 does anybody have announcements? 15:20:24 nothing from my side. 15:20:28 I would only like to mention one thing that we are going to work on in W, that we only just learned about recently 15:20:59 We want to improve horizon's support of the role-based policies, with focus on read-only roles in particular 15:21:31 so we will probably be submitting a bunch of patches that change permission checks from checking the role to checking the actual permissions 15:22:01 I hope, it won't break a lot 15:22:19 I do realize we are late with this, and I don't expect help with it -- in the worst case it won't make it to W 15:22:24 rdopiera: great. I think it affects the UI design of horizon right. As automatic swtiching of toke leads to confusions. 15:23:02 amotoki: I don't want to touch that part too much if possible... 15:23:25 so more of incremental improvement than revolution 15:23:47 I certainly don't want to change the ui 15:23:52 one of tricky and difficult points is how to manage a case where some projects support system-scope and some projects do not. 15:24:27 in addition we need to consider a case where a user is NOT associated with a project (i.e. a user is associated only with system-scope all) 15:25:01 I am not sure what is a good compromise and right limitations. 15:25:27 I guess we will make those decisions once we get to those points 15:26:10 anyway I can help reviews. I have no code to support it now but I was thinking problems around system-scope support. 15:26:30 All problems I see are specific to horizon. 15:26:58 rdopiera: it is better to land https://review.opendev.org/c/openstack/horizon/+/769236 soon? 15:29:12 amotoki: I don't see a point for that patch, is it necessary for anything, or is it just cosmetic? 15:29:38 rdopiera: the main goal of this patch is to handle deprecated rules in horizon 15:29:56 and make horizon work with the latest default policues from back-end serivces like keystone. 15:30:09 amotoki: I think you mean this patch https://review.opendev.org/c/openstack/horizon/+/750134 15:30:15 amotoki: did you post a wrong url? 15:30:34 ah,,,,. sorry https://review.opendev.org/c/openstack/horizon/+/750134 is the right one 15:30:48 I was confused, because I also expected your policy patch 15:30:49 I opened several pages :( 15:31:05 yes, I have it open in my browser tab for the last two weeks 15:31:12 sorry it's taking so long 15:31:25 rdopiera: got it. I will update it ASAP 15:32:01 I'm still getting to know the whole policy thing 15:32:11 amotoki: I'm ok with this patch once you update versions and ad release notes 15:34:05 rdopiera: hopefully you can share some planning note on this if any. I will share my thought. 15:34:16 #topic Open Discussion 15:34:27 * e0ne finally changed a topic 15:35:15 regarding jquery thing, I proposed a patch to bump the min ver of xstatic-django per discussion last week https://review.opendev.org/c/openstack/horizon/+/771577 15:36:45 amotoki: +2'ed 15:37:32 so the next step will be to merge xstatic-jquery-migrate from rdopiera and release it 15:40:24 do we plan to do something on jquery 3 in this release? 15:41:12 I would love to switch to it too, we can 15:41:22 that would resolve some cves 15:42:15 let's try it :) 15:42:48 *if we can 15:44:56 :) 15:49:36 nothing more from my side 15:50:17 we saved 10 minutes today :) 15:51:31 :) 15:52:44 thanks everybody for your contirbutions! 15:52:49 see you next week 15:53:23 thanks everyone! 15:56:21 #endmeeting