12:00:33 #startmeeting Horizon 12:00:34 Meeting started Wed Jan 20 12:00:33 2016 UTC and is due to finish in 60 minutes. The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot. 12:00:35 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:00:39 The meeting name has been set to 'horizon' 12:00:50 o/ 12:00:52 hi 12:00:55 good morning david-lyle, good morning all o/ 12:00:55 Hi 12:01:09 o/ 12:02:37 After a couple weeks off, I'm back 12:02:40 o/ 12:03:02 welcome back david-lyle 12:03:54 There is no formal agenda for today. But I have a couple of items 12:03:59 First 12:04:09 I also have one topic 12:04:23 welcome back david-lyle, 12:04:43 toabctl lets talk mitaka-2 first and then we can hit your item 12:04:52 david-lyle: sure 12:05:12 Mitaka-2 will be tagged either later today or tomorrow AM at the latest 12:05:25 so anything that has not merged will miss it 12:05:49 unless some raises an issue that we should hold the tag for 12:05:57 think critical bug on master 12:06:11 does any one know of any such issues? 12:06:47 Nope 12:06:55 All seems fine to me. 12:06:57 i have one medium bug with one +2 12:07:03 yupp, looks good 12:07:04 for m2 12:07:16 my a bit late o/ 12:07:32 give the state of the gate, I would expect some delays though... 12:08:28 ok, we'll run with what we have 12:08:40 I'll push the release today 12:10:51 the M-2 list in Launchpad is pretty sparse, are there items missing? 12:11:21 #link https://launchpad.net/horizon/+milestone/mitaka-2 12:12:01 it feels like yes 12:12:58 but I don't have anything specific in mind, what's missing there 12:13:07 I just marked Keystone Identity Provider as complete 12:13:16 I will look for more later 12:13:22 I think alot of work falls under blueprints. The bugs seems all there 12:13:26 i think fixed bugs are not targetted to M-2. 12:13:35 I don't know if many bps are actually complete right now though. I'll look too. 12:13:50 2 is just very low for us 12:14:04 based on past performance 12:14:21 will look at bugs too 12:14:40 ok, moving on 12:15:28 I also want to check in quickly on the priorities list for Mitaka 12:16:51 #link https://etherpad.openstack.org/p/mitaka-horizon-priorities 12:17:39 for plugins, remaining documentation patches seem stalled 12:18:20 Yeah, there's tons of comments on there 12:18:51 * david-lyle needs to read them 12:18:52 There's ongoing work with plugin i18n too I believe. The JS part was solved, but we still need a better infra job for automating it. 12:19:32 yes trove-dashboard is the proving ground I believe 12:19:47 re translations, ajaeger and i are working on translation setup on infra https://review.openstack.org/#/c/262545/ 12:20:28 I believe it helps translation setup on horizon plugins. 12:20:39 thanks amotoki 12:20:54 Yes, I wasn't aware of that, scanning now, looks great! thanks! 12:20:59 will read through that as well 12:21:23 i plan to write up a devref about this once it lands. 12:22:20 robcresswell: for the horizon documentation patches are they of the "perfection is the enemy of good" variety, or what about this gaping whole variety? 12:22:27 they === comments 12:24:41 Er, a lot of them seem to be "This doesnt work" 12:25:05 well we can't really skip those 12:25:07 :) 12:25:39 Yeah. I can do a pass on it if you like. I don't like the layout either, it really needs to be python or angular sections 12:25:51 the mix and match is very confusing for those not familiar with horizon 12:26:24 robcresswell: I agree, I keep starting the python side of things and stalling 12:27:01 will see what I have and maybe do that separately 12:27:09 we need some docs in Mitaka 12:28:05 100%, its critical. 12:28:17 For angular content, I see lots of patches going by, not sure if they are getting us to our goal though 12:28:30 some efforts seem stalled, others moving forward 12:28:34 A lot of the easy ones are going in. 12:28:42 But not much of the solid content. 12:29:00 The images stuff seems to be mostly done, but needs reviews. 12:29:22 robcresswell: Which parts are fully anguralized in horizon till now? 12:29:41 So we could do with that to build patterns off. We also need to get magic search fixed because its blocking plugins like Magnum-ui 12:29:53 zabolzadeh: Nothing in master uses a full angular panel. 12:30:30 robcresswell: So, we won't have any angular content in Mitaka, is it? 12:30:50 The plan is to get a couple of panels merged. 12:31:15 zabolzadeh, AFAIK, we have some, but it's disabled by default 12:31:24 zabolzadeh, for example, new Launch Instance wizard 12:31:41 We have a couple of tables and a workflow, but nothing complete. 12:32:04 tsufiev: disabled? what do you mean? 12:32:34 zabolzadeh: The Angular images panel, Users panel and Launch instance workflow are disabled by default. 12:32:43 zabolzadeh, https://github.com/openstack/horizon/blob/master/openstack_dashboard/enabled/_3031_identity_users_panel.py#L27 12:32:54 See openstack_dashboard/enabled and local_settings.py 12:33:41 #link https://github.com/openstack/horizon/blob/master/openstack_dashboard/local/local_settings.py.example#L218 12:33:46 robcresswell, tsufiev: I see. Thanks. But nothing merged into master so far. 12:34:00 Nothing *complete* merged, no. Those panels are in master. 12:34:18 :) 12:34:27 robcresswell: :)) 12:34:32 david-lyle: btw, writing new integration tests have been going quite well, I haven't even been able to review them all so far (too many) :) 12:34:56 robcresswell, Does ng-user panel not completed anguralized work yet? 12:34:58 tsufiev: nice 12:35:17 chestack: Nope, it's just a list of users right now. 12:36:59 ok we have lots of stalled items and a little over a month to straighten them out 12:37:59 I'm going to move on and let toabctl go 12:38:00 zabolzadeh, I guess, you were going to promote Identity Topology blueprint :)? 12:38:12 #topic Open Discussion 12:38:17 I want to ask how to continue with the local_settings.d/ changeset (see https://review.openstack.org/#/c/243974/ ). 12:38:30 There are pros and cons but no more progress. I'm fine with having another discussion, or a -2 so I can abandon the change (and search for another solution) or +2's so it's merged. Moving in one direction would be nice :) 12:38:31 tsufiev: Yes, i started to develop. 12:38:46 tsufiev: The review process, as you know has been finished. 12:39:17 so any suggestion howto proceed ? 12:39:23 toabctl, seems like its missing core votes on it, already has 8 +1 12:39:36 toabctl, should bother the cores, now that they are all in the channel :D 12:39:51 you* 12:40:02 toabctl: I've left comments before on it, I don't like it because it doesn't really solve the main issues with .py vs .ini 12:40:03 itxaka: it's controversial .there was already a +2 and also a -1 from cores. 12:40:23 Which is what the packagers dislike 12:40:38 And I'd prefer a solution that lets us load .ini from external directories. 12:41:30 Adding another python override to me seems like a poor solution. We already have override modules for hacks and enabled files. 12:42:27 robcresswell: are you saying you'd like to see Django settings defined in an ini file as well? 12:42:37 hm... 12:42:42 Do we have a bp for that ini thingie? 12:43:09 doug-fish: It's one of the constant requests from people packaging 12:43:10 this local_settings.d is really about *all* django settings, not only about horizon specifics (plugins or whatever). 12:43:18 I tend to agree it to some extent, but local.settings.d helps distribution or horizon plugin I think. 12:43:48 toabctl: I'm warming to the patch 12:43:52 I currently don't have another solution to change a setting during a package install 12:43:52 IMO a long term solution is to migrate ini style. 12:43:55 itxaka, https://review.openstack.org/#/c/100521/ 12:44:06 I'm reluctant to make a wholesale switch to .ini 12:44:18 thanks tsufiev 12:44:18 amotoki: so do you want to map all possible settings from local_settings.py to a ini file? 12:44:47 toabctl: I hope so though there are some difficult points. 12:44:48 mostly because django has a rather rich set of settings to try and support 12:44:48 ini file and toabctl s patch should be not connected here 12:45:30 mrunge: Why? Local settings is all about deployments and dsitributions 12:45:31 I think the .d patch helps distros and some plugins 12:45:36 not Horizon specific settings 12:45:52 exactly. the .d patch is greatly welcome from distr side 12:46:14 it will not really be used in tree 12:46:26 yes. that's also my understanding 12:46:42 robcresswell, the thing is, one can not change local_settings while adding plugins to horizon 12:46:49 Yes, I understand 12:46:54 the change would then be manual 12:47:01 but that is not desirable 12:47:12 My contention is that next summit, we will have packagers request .ini, as they do at every single summit :/ 12:47:19 my original thought was to use enabled files, but for theming that doesn't really make sense 12:47:29 well, probably becuase its the proper way robcresswell 12:47:39 and the python change will not help us 12:47:42 david-lyle, there are other settings desired for changes 12:47:45 config whould not be mixed with code logic, one of the things that django does wrongly :P 12:47:52 mrunge: I understand 12:47:52 whould == should! 12:47:53 robcresswell: I promise to not request .ini files :-) 12:48:12 mrunge: using theming as an example 12:48:23 just noting it doesn't really fit as a plugin 12:48:45 theming misuses plugins 12:48:53 due to better options 12:48:58 missing 12:49:06 here is what I'm doing with the patch for a theme: https://github.com/SUSE-Cloud/horizon-suse-theme 12:49:33 but one could add another auth plugin, which could require additional config 12:49:40 that's currently impossible 12:50:07 or think of adding a plugin for supporting more options in a storage driver 12:50:10 or what else 12:50:16 david-lyle: I am working on glance image sharing mechanism in horizon & I think I can implement it completely for mitaka release(https://review.openstack.org/#/c/242691/). 12:50:25 david-lyle: Does the feature set open right now? 12:50:53 zabolzadeh: it's not locked 12:51:06 one question: why do we use underscore (_NNN_xxx filename) in enabled (and proposed local.settngs.d) instead of NNN_xxxx filename)? 12:51:47 python files can't start with numbers 12:52:10 ah..... I totally forgot it 12:52:12 thanks 12:52:13 Ah, that's a good reason! :) 12:53:20 toabctl: will do a proper review of your patch 12:53:24 so howto proceed now? I'm fine with having a -2 and also having 2x +2 (prefered) 12:53:39 It seems the general consensus is to merge 12:53:48 david-lyle: Ok, sound like good. The core has been implemented, Timur, wants me a slight change. 12:54:16 zabolzadeh: just keep pushing on it 12:54:21 the bp is approved 12:54:36 so just needs reviews 12:55:12 david-lyle: ok, I'll send the patch 4 days later. 12:55:26 reviews is an important point 12:55:36 we're currently lacking reviews in general 12:55:45 robcresswell: ok. then I'll wait for more comments and hopefully for some +2's. thanks for the discussion everybody! 12:55:53 mrunge: yeah I need to catch up 12:55:57 zabolzadeh, if you want your code reviewed, be prepared to review other code as well 12:56:04 david-lyle, I was not pointing at you 12:56:23 mrunge: yeah, good point. 12:56:33 I just observed the review queue increasing by about 100 patches over the last 4 weeks 12:56:37 400 to 500 now 12:57:04 * david-lyle wonders about signal to noise ratios 12:58:23 agreed, there are some patches aging since january 12:58:26 If you want a fun one, check out https://review.openstack.org/#/c/118334/ 12:58:35 364 days since last patch set. 12:58:44 It's been rebased constantly :) 12:59:09 We shouldn't be able to say happy birthday to a patch :p 12:59:31 robcresswell, we already had that at least twice 12:59:36 I've always thought of that patch as a solution looking for a problem 12:59:48 lol 12:59:55 Can someone -2 it then? 13:00:06 there was an iteration before that even I believe 13:00:11 robcresswell, no, we'r too polite :) 13:00:16 tsufiev: ha :) 13:00:31 robcresswell: I think I did on the previous incarnation 13:00:58 Ah, I hadn't realised 13:01:00 I'm also allowing for someone to explain why it's useful 13:01:35 I have no interest in it personally, it's just a very old patch. 13:01:44 robcresswell: understood 13:01:55 #link http://russellbryant.net/openstack-stats/horizon-openreviews.html 13:01:56 times up 13:01:57 that patch seems to fix a bug? https://bugs.launchpad.net/horizon/+bug/1363188 13:01:58 Launchpad bug 1363188 in OpenStack Dashboard (Horizon) "Change user settings as non-admin user changes for all the users across all the projects" [Low,In progress] - Assigned to Rob Cresswell (robcresswell) 13:02:31 lets continue in #horizon 13:02:38 yum, thank you all 13:03:18 thx 13:03:31 mrunge: can you please end the meeting? :) 13:03:38 reminder of the midcycle sprint on Portland Feb 23-25, https://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint 13:03:47 please register 13:03:51 #endmeeting