20:00:20 #startmeeting horizon 20:00:21 Meeting started Wed Sep 20 20:00:20 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:22 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:25 The meeting name has been set to 'horizon' 20:00:32 Hi everyone :) 20:00:37 o/ 20:00:46 o/ 20:00:46 hi 20:00:50 o/ 20:01:32 o/ 20:01:40 #topic Notices 20:01:41 o/ 20:01:48 #info PTG 20:02:05 Thanks everyone for attending the PTG. I am glad most of the active developers were able to make it. It’s such a great opportunity to meet the team and be able to discuss various topics face to face. 20:02:13 #link PTG discussion: https://etherpad.openstack.org/p/horizon-ptg-queens 20:02:19 #link Our team photos: https://plus.google.com/101186576626172577894/posts/LQnT6pXnRix 20:02:27 #link Photos for all the OpenStack team at the PTG: https://www.flickr.com/photos/152419717@N06/albums/72157689092104285/with/37136316176/ 20:03:24 #topic Bugs Review 20:03:40 We talked about ways to reduce the backlog during PTG. One of them is to review some bug reports during the weekly meeting. Thanks gary-smith for helping out with the bug triage. 20:04:00 You're welcome! 20:04:07 :) 20:04:15 ying_zuo: I started to verify old in-progress bugs. some of them moved to new or fix commited 20:04:43 great! thanks e0ne 20:05:04 e0ne: Thanks for the help. I noticed the bug count dropping between my triaging. I knew someone else was working on that too 20:05:05 there are dozens of in-progress bugs started 2+ years ago 20:05:26 gary-smith, ying_zuo: you're welcome 20:05:58 e0ne: why am I not surprised ;) 20:06:12 ying_zuo: :) 20:06:22 Today we will discuss a few unassigned and high priority tickets. Mainly to get some attention to those tickets and some pointers to start would be helpful. 20:06:24 there are only 2 ways to cut bugs list... 20:06:25 If you find bugs have been solved elsewhere, just mark them Invalid. There'll already be a bug report elsewhere 20:06:46 robcresswell: ok, will do 20:06:56 thanks 20:07:11 #link https://bugs.launchpad.net/horizon/+bug/1434241 20:07:12 Launchpad bug 1434241 in OpenStack Dashboard (Horizon) " Internal Server Error while updating project quota when using Keystone LDAP backend" [High,New] 20:07:27 a note that they have been otherwise fixed is helpful on the bug as well 20:08:11 usually, I add something like 'can't reproduce it on master' 20:08:25 This one requires keystone LDAP backend. It was opened in 2015. Would be good if someone can help confirming if it’s still valid. 20:08:32 note: only if I tried to reproduce it 20:08:57 heh, yeah, leave a comment saying "why" its marked invalid 20:09:44 +1 20:09:48 +1 20:10:44 #link https://bugs.launchpad.net/horizon/+bug/1436239 20:10:44 Launchpad bug 1436239 in OpenStack Dashboard (Horizon) "modifying users in non-default domain project fails" [High,Confirmed] 20:10:44 #link https://bugs.launchpad.net/horizon/+bug/1563005 20:10:46 Launchpad bug 1563005 in OpenStack Dashboard (Horizon) "pseudo translation tool creates uncompilable PO files" [High,Confirmed] 20:10:50 same for these two 20:10:52 there is an ldap plugin for devstack, hopefully it's still functional 20:11:42 hopefully 20:12:28 IMO, #1563005 is invalid now. we don't have 'pseudo' now 20:12:42 I'll take 1436239 20:13:16 * david-lyle assigns himself 20:13:39 thanks david-lyle 20:14:03 does anyone know about the pseudo translation tool ? 20:14:40 ying_zuo: it's removed from master but still available in older branches 20:14:48 No, its still available 20:15:02 It's just in a management command, instead of a script 20:15:24 https://docs.openstack.org/horizon/latest/contributor/topics/translation.html#pseudo-translation-tool 20:15:26 I can take that anyway. I ported it to the management files, which is what broke it I assume :p 20:15:42 creating work for yourself :) 20:15:49 :) 20:15:52 #1655487 has a patch, https://review.openstack.org/461490, that needs some core review love 20:16:08 :) thanks robcresswell 20:16:12 david-lyle: I'm keeping myself employed forever 20:17:43 gary-smith: I will take a look at that one 20:18:01 ying_zuo: Thanks 20:18:20 #link https://bugs.launchpad.net/horizon/+bug/1715066 20:18:21 Launchpad bug 1715066 in OpenStack Dashboard (Horizon) "Cannot launch instance with Django Launch Instance form with multiple networks for a tenant" [High,Confirmed] 20:20:21 I was able to reproduce. There’s no obvious error so someone will need to look into it. 20:20:43 e0ne: glad to see you taking those MS browser bugs; I have no windowz box anywhere to even reproduce them on 20:20:59 gary-smith: Very few people do; they tend to sit around for ages 20:21:11 gary-smith: at lease, you can verify than nothing is broken in other browsers 20:21:26 good point 20:21:27 s/ at lease/at least 20:21:42 reg 1715066, It seems generated HTML has been changed and horizon.list.generate_html JS cannot handle it. 20:21:47 ying_zuo: I can take this one #1715066 20:21:54 one question for queens and django 20:22:15 do we bump the minimum version of django for Queens or keep the minimum >=1.9 ? 20:22:31 cool. thanks e0ne 20:22:36 we're jumping straight to django 4 :) 20:22:58 wait, wrong framework 20:23:06 david-lyle: you missed django 3.6 for python 3.6 ;) 20:23:07 bump to 1.11 20:23:22 I vote to bump to the LTS as well 20:23:33 everything else is EOL during this cycle anyway iirc 20:23:49 david-lyle: +1 20:23:56 Djangos lifecycle is about as aggressive as openstacks XD 20:24:08 one thing to note is bug 1715066 exists in Pike, so even when we bump the min to 1.11 we need to explore a solution which works for Pike too 20:24:09 bug 1715066 in OpenStack Dashboard (Horizon) "Cannot launch instance with Django Launch Instance form with multiple networks for a tenant" [High,Confirmed] https://launchpad.net/bugs/1715066 20:24:44 #link https://www.djangoproject.com/download/ (Supported Versions section) 20:25:37 Should bug 1547290 (gen'ing JS docs) be downgraded? It doesn't seem to "prevent a key feature from working properly" 20:25:38 bug 1547290 in OpenStack Dashboard (Horizon) "We currently do not generate Javascript API docs" [High,In progress] https://launchpad.net/bugs/1547290 - Assigned to Richard Jones (r1chardj0n3s) 20:26:25 gary-smith: only if we can develop w/o these docs :) 20:26:52 I think more of a medium 20:27:27 medium is good 20:27:48 ying_zuo: looks like you are editing that one. Can you change to medium? 20:27:57 I just did :) 20:27:59 Thx 20:28:48 one could argue since we don't have API docs, that it's a bp rather than a bug, but details 20:29:17 That's right. It's a feature 20:30:21 I guess a bug report will do for now. 20:31:24 Anything else we should discuss regarding bug 1715066? 20:31:25 bug 1715066 in OpenStack Dashboard (Horizon) "Cannot launch instance with Django Launch Instance form with multiple networks for a tenant" [High,Confirmed] https://launchpad.net/bugs/1715066 - Assigned to Ivan Kolodyazhny (e0ne) 20:32:07 here is a patch: https://review.openstack.org/#/c/289932/ 20:32:26 oops, sorry, a wrong window:( 20:34:30 cool. unit test is added :) 20:34:52 #link https://bugs.launchpad.net/horizon/+bug/1717542 20:34:53 Launchpad bug 1717542 in openstack-secaudit " Possible client side template injection in horizon login screen" [Undecided,New] 20:35:25 This one is the last one I want to bring up today. It’s a security issue. Just wondering if someone is aware of this issue or has any thoughts on it. 20:35:56 that wasn't marked correctly, hmm 20:36:01 ying_zuo: it wasn't me 20:36:04 it's a public bug now 20:36:48 sorry about that 20:37:09 but I think the discussion went something along the lines of since we changed the escape characters, this is a false positive 20:37:41 gary-smith, the bug filer has to mark it correctly 20:39:14 which is why automated tool results have to be double checked 20:39:35 david-lyle: can you add a comment on the ticket? 20:40:12 I believe it's on the actual security bug, but will double check if that's open yet 20:40:47 which is this https://bugs.launchpad.net/horizon/+bug/1567673 20:40:48 Launchpad bug 1567673 in OpenStack Dashboard (Horizon) "[OSSA-2016-010] Possible client side template injection in horizon (CVE-2016-4428)" [Critical,Fix released] - Assigned to Tristan Cacqueray (tristan-cacqueray) 20:40:59 which is now public because fixed 20:41:10 and OSSA published 20:41:37 but will add comment 20:42:31 thanks david-lyle 20:43:36 That's the list of bug reports I have for today 20:43:54 ying_zuo: thanks for bringing this to the meeting 20:44:19 I marked the issue as incomplete 20:44:35 asking for verification 20:44:51 cool 20:45:05 As always, if you have any thoughts of any tickets, please leave a comment there. 20:45:31 i have one question 20:45:37 Also, confirming the bugs will be very helpful too 20:45:51 ying_zuo: +1 20:45:55 #topic Open Discussion 20:45:58 I see some heat related bugs were marked as Won't Fix 20:46:28 I think until heat is excised marking them as won't fix is premature 20:46:31 don't we keep them open (with heat tag) and move them to heat-dashboard (once it is split out 20:46:32 ? 20:46:49 I should think so 20:47:03 +1 20:47:37 when I checked bugs targeted to 'next' milestone, I noticed it but I have no good way to recover them... 20:48:15 ? Just mark them as new again or something 20:48:28 And target them to Heat instead of Horizon 20:49:20 I wouldn't retarget them until there is a separate plugin 20:49:33 but moving to new is correct, IMO 20:49:44 maybe just add a tag as heat 20:50:13 sounds good 20:50:26 I added 'heat' tag to heat related bugs several days ago. 20:50:35 Either is fine 20:50:50 When heat decide how they want to manage bugs, we can move them over 20:51:45 cool. what's next 20:53:21 any other questions or concerns? 20:53:30 i have one more thing to raise. https://bugs.launchpad.net/horizon/+bug/1321865 20:53:31 Launchpad bug 1321865 in OpenStack Dashboard (Horizon) "Networks panel can't be actually disabled" [Medium,Confirmed] 20:53:45 it is related to the template design and raises a question on where we should have common templates. 20:54:43 i just would like to know opinions to the team: do we really support disabling some specific project panel? 20:54:54 we should 20:55:03 5mins reminder 20:55:16 All you can really do atm is hide it :/ 20:55:50 the problem is if we hide a project network panel, the admin network panel does not work.... 20:56:14 it depends on templates from the project network panel.... 20:56:24 ideally, this is a policy configuration 20:56:49 and only admin type users have roles to see any networking panels 20:57:14 policy configuration on templates? 20:57:26 on panels 20:57:37 What I meant was, you can hide the pabel, but still register it 20:57:45 Right ^^ 20:57:57 ah.... 20:57:58 amotoki, you've kind of hit two use cases which are different 20:58:07 So then it doesn't affect admin 20:58:08 one is remove all network panel support 20:58:24 the other is hide project/network but not admin/network 20:58:38 yes, my point is the latter. 20:59:07 ok, in that case I would suggest policy rather than enabled/disabled 20:59:44 ah I see. I think i got your point 20:59:55 unless you're just wanting to change horizon and not cli/API behavior 21:00:07 We are about at time :) 21:00:29 david-lyle: Nothing to stop you altering Horizons copy of policy only 21:00:29 at that point I think common template location should be above dashboard like usages 21:00:43 that's right. we can continue the discussion in #openstack-horizon. 21:01:04 Thanks everyone! \o 21:01:06 see you next week 21:01:19 thanks everyone for joining the meeting! 21:01:25 #endmeeting