15:02:20 #startmeeting horizon 15:02:21 Meeting started Wed Oct 30 15:02:20 2019 UTC and is due to finish in 60 minutes. The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:22 hi 15:02:23 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:25 The meeting name has been set to 'horizon' 15:02:30 hi 15:03:31 let's wait others for a couple of mins 15:03:45 hi all. 15:05:05 okay, let's start 15:05:34 The agenda of the meeting is found at "Weekly meeting" section in https://etherpad.openstack.org/p/horizon-release-priorities 15:05:46 #topic Notices 15:06:23 Ussuri PTG will be held next week 15:06:37 I am looking forward to meeting you all soon 15:07:05 you can find the etherpad list at http://ptg.openstack.org/etherpads.html 15:07:32 we will meet Wed morning 15:07:50 and the team photo time is Thu 11:40-11:50 15:08:10 amotoki: great. 15:08:45 any other announcement? 15:09:11 nothing from me 15:09:50 let's move on 15:09:55 #topic Community Goals 15:10:11 Discussion on Ussuri goals are under discussion 15:10:28 you can find the latest update at http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010421.html 15:11:04 "Add goal for project specific PTL and contributor guides" and "Propose a new goal to migrate all legacy zuul jobs" are near approval I think. 15:11:24 "3) Consistent and secure default policies" is under discussion. 15:12:20 Regarding the policies, regardlesss of that it is selected as the goal or not, we need a work to support new keystone policies (and coming nova new ones) 15:12:31 +1 15:13:12 we can remember our status and discuss the plan in the PTG 15:14:06 if you have time, it would be nice to check how keystone policies (from oslo-policy-generator) do not work with horizon 15:15:05 another one is "drop python2.7" 15:15:37 In the TC office hour last week, we agree server projects will drop python2.7 support till Ussuri-1 milestone 15:16:08 horizon will follow this and drop py27 support (at least in testing) till Ussuri-1 15:16:24 note that dropping "six" is optional. 15:16:47 it could be a community goal for Ussuri 15:16:51 #link https://review.opendev.org/#/c/691178/6 15:17:19 yes, we discussed it during the meeting 15:18:18 I will look thru it tomorrow. 15:19:18 one question: do we cover horizon plugins on py27 drop? 15:19:58 IMO, we need to communicate with plugin teams that we dropped py27 testing 15:20:17 hopefully initial efforts can happen by project teams and we can help it 15:20:24 e0ne: totally agree 15:20:52 +1. 15:21:11 I plan to send a reminder of py27 drop in horizon to the mailing list perhaps after the PTG 15:21:18 as it affects horizon plugin py27 jobs. 15:22:19 if it fails, it is a good chance to drop py27 job in their plugins :) 15:22:35 :) 15:23:56 if a bug fix is not compatible with py27, we can fix it in a backport. it was discussed in the TC office hours. keep in my mind in stable reviews 15:24:11 +1 15:24:23 I don't want to block patches with py3 syntax 15:24:50 :) 15:25:25 that's all I have on this topic. 15:26:09 #topic Django 2.2 in horizon plugins 15:26:20 vishalmanchanda: your turn :) 15:26:56 amotoki: thanks for heat plugin fix. you was faster then me today 15:27:07 amotoki 15:27:26 amotoki: e0ne : thank you guys helping me in this migration. 15:27:37 e0ne: no problem. 15:28:05 I have purposed the patch for masakari-dashboard. 15:28:39 there are 4 plugins where this patches are not merged yet. 15:28:44 link: https://review.opendev.org/#/q/topic:django22+status:open 15:29:48 our plugin registry does not cover masakari-dashboard and qinling-dashboard 15:29:59 we need to check qinling-dashboard too. 15:30:06 Now I will add comments about the plugins which doesn't have Unit tests to check django -compatibility. 15:30:52 will you add comments to https://etherpad.openstack.org/p/Enable_Django22_support_in_Horizon_Plugin ? 15:30:58 amotoki: ok will purposed patch for qinling-dashboard after the meeting. 15:31:10 amotoki: yeah. 15:31:36 I have not added comments yet as i have to check for all. 15:32:30 thanks for leading the effort vishalmanchanda 15:32:32 amotoki: Also i will purpose a patch to update this plugin table doc. 15:32:57 as it miss masakari and qinling dashboard plugin. 15:32:58 vishalmanchanda: regarding the plugin table, I am thinking to generate it from openstack/releases deliverable files 15:33:06 amotoki: welcome. 15:33:24 amotoki: ok go ahead. 15:33:52 it looks like most plugins work with django 2.2 at least from results of UT 15:34:08 yeah. 15:34:31 the next step would be to bump upper-constriants.txt and make django 2.2 default 15:34:54 amotoki: +1. 15:34:59 awesome! 15:35:06 it will potentially detect more issues in real envs 15:35:13 +1 15:35:37 I'm working on some simple integration tests in the backgroud 15:35:47 it uses devstack deployment 15:37:03 it would be really helpful! 15:37:06 amotoki: I'll share a python script to get all plugins from openstack/releases and project/config later today 15:37:39 e0ne: I also have a script to check all plugins from the releases repo 15:37:50 I need to find it... but I'm sure I did something like it once I started work on integration tests 15:37:55 ok 15:38:02 please share it with me. 15:38:04 but we might be thinking different things 15:38:12 so it may be useful to share them 15:38:12 I something new for me. 15:39:35 mine is http://paste.openstack.org/show/785660/ 15:39:50 very straight forward :p 15:39:58 amotoki: thanks. 15:40:32 amotoki: thanks 15:40:39 anyway we have a good progress and almost finish the first step 15:41:38 anything to be discussed on django 22? 15:41:51 amotoki: none from my side. 15:42:31 let's move on 15:42:38 #topic bugs 15:43:22 https://bugs.launchpad.net/horizon/+bug/1847959 related to the latest novaclient 16.0.0 has landed 15:43:22 Launchpad bug 1847959 in OpenStack Dashboard (Horizon) "nova list-extensions is abandoned" [High,Fix released] - Assigned to Matt Riedemann (mriedem) 15:43:55 it highlighted that we need to sync backend services more... 15:45:32 https://bugs.launchpad.net/zun-ui/+bug/1847889 also needs attention 15:45:32 Launchpad bug 1847889 in OpenStack Dashboard (Horizon) "Cloud-shell and console break in websockify 0.9.0" [Undecided,In progress] - Assigned to hongbin (hongbin034) 15:46:03 I have no real env with serial console. If anyone has such env, it would be nice. 15:47:56 the above are all bugs I would like to talk. 15:48:35 we will have this topic every meeting. let's raise bugs which you think needs attentions. 15:48:37 amotoki: I have your comments on this patch https://review.opendev.org/#/c/680603/ 15:49:05 amotoki: This bug is not clears to me. 15:49:46 vishalmanchanda: in such case, we need to re-evaluate a bug report itself first. 15:49:50 I rember when the last time I have tried i was not able to reproduce it and left some comments in lanchpad. 15:50:55 vishalmanchanda: it is related to image metadata (min_disk, min_ram and so on) 15:51:07 vishalmanchanda: I wonder you specified the metadata 15:51:46 vishalmanchanda: if it is unclear, you can request the bug author detail command lines or some 15:52:26 does it work for you? 15:52:52 I can check it but I am afraid I don't have enough time this week 15:52:58 amotoki: ok will take a another when get some time. 15:53:24 amotoki: no problem i will check. 15:53:31 thanks 15:53:43 #topic On-demand Agenda 15:53:59 I have one topic I added to the etherpad 15:54:19 it is about deprecating OPENSTACK_NOVA_EXTENSIONS_BLACKLIST option. 15:54:42 During the support to novaclient 16.0.0 which drops list-extension python bindings https://review.opendev.org/#/c/690134/, we wonder why and how this option is useful or not. 15:55:00 The description of the option mentions performance, but according to the result of checking horizon code http://paste.openstack.org/show/785541/ there seems less related to performance. 15:55:11 All of them are mainlined in the nova API for long, so there is no potentential performance issue at least in the nova API. 15:56:02 this option was added by rdopiera long ago, but he no longer has a good memory on the detail context. 15:56:22 I think we can drop this. 15:58:24 it is not easy to understand the full context of this. I plan to propose a patch to deprecate it, so we can discuss it there. 15:58:48 +1 15:59:58 we are almost out of time. 16:00:07 thanks for joining, all 16:00:24 see you in Shanghai 16:00:28 #endmeeting