12:01:01 #startmeeting Horizon 12:01:02 Meeting started Wed Feb 3 12:01:01 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:01:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 12:01:06 The meeting name has been set to 'horizon' 12:01:12 o/ 12:01:15 o/ 12:02:11 packed house 12:02:58 so, I guess you're wondering why I called you all here 12:03:13 :) 12:03:22 general items 12:03:37 reminder March 3 is the date for Mitaka 3 12:04:46 Second is midcycle https://wiki.openstack.org/wiki/Sprints/HorizonMitakaSprint 12:05:07 the wiki page contains a link to the topics etherpad 12:05:46 yeah, I need to get onto that 12:06:22 * tsufiev started thinking if we should consume latest versions of external dependencies 12:07:47 tsufiev: we should for more restrictive pinning of dependencies, especially in toolchain like selenium, etc 12:08:12 s/should for/should have far 12:08:22 it's late 12:08:41 r1chardj0n3s, it's never too late to retreat :) 12:09:08 there is a reason upper dependency limits on master are open and set on stable 12:10:14 david-lyle, well, it's just a moment of weakness 12:11:42 o/ 12:12:29 though the meeting time on the wiki is set at 2000 UTC today 12:12:57 hi everyone 12:13:14 hi :-) 12:13:42 someone has been doing a poor job of copy/pasting in the meeting wiki ;-) 12:14:04 i am an intern at openstack 12:14:26 ohai njirap, I think we've exchanged email 12:14:33 njirap, r1chardj0n3s fixed the wiki 12:14:43 oh hi richard its you 12:14:50 yep 12:15:29 we have a couple items on the agenda today 12:15:33 camouflage nick :) 12:15:43 #link https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_2016-02-03_1200_UTC 12:15:57 so just to intro myself i have hitherto been working on the openstack-manuals(no particular project) but i am now specializing in horizon 12:16:36 welcome njirap 12:16:46 thanks david 12:16:54 #topic Are we ready to move to keystone v3 for horizon in default devstack config? 12:16:57 njirap, welcome! 12:17:04 o/ 12:17:06 thanks tsufiev 12:17:16 david-lyle, I felt it would good to remind everybody about this thing 12:17:18 I think the simple answer is yes 12:17:27 I test all the time with v3 12:17:55 I also talked to lhcheng and he was also of that opinion 12:18:19 I run against v3 with OSA 12:18:22 david-lyle, is it no longer tied to enablement of non-cookies SESSION_ENGINE in devstack? 12:18:34 there is https://bugs.launchpad.net/python-novaclient/+bug/1522402 12:18:35 Launchpad bug 1522402 in python-novaclient "Novaclient does not support v3 Keystone API" [High,Confirmed] 12:18:36 but I don't use all of keystone 12:18:43 the concern was that v3 means bigger token 12:18:49 tsufiev: ah yes 12:18:51 good point 12:19:04 I have a different SESSION_ENGINE enabled all the time 12:19:20 yeah, same here 12:19:28 AFAIR, SESSION_ENGINE in devstack was a blocker for this enhancement for a long time 12:19:34 I may just move horizon in devstack to use locmemcache 12:19:40 what I really wanted to understand if it's still a blocker 12:19:45 tsufiev: yeah my patch withered a bit 12:19:52 I can try pushing that again 12:19:54 david-lyle: that's a sensible move 12:20:03 r1chardj0n3s: which? 12:20:06 david-lyle, \o/ 12:20:11 can't we just use like memcached, and use memcache even for session engine? 12:20:31 I mean, memcached is easy to setup 12:20:46 mrunge: https://review.openstack.org/#/c/193611/ 12:20:48 david-lyle: swicthing devstack to locmemcache 12:20:49 and we should have it anyways, no? 12:21:01 since people shouldn't be deploying devstack anyway 12:21:04 (lol) 12:21:18 good point r1chardj0n3s 12:21:24 make it useless 12:21:57 so we either do locmemcache or I rebase my devstack patch 12:22:05 other devstack patch 12:22:14 (can't wait for the "my login doesn't work" bugs filed against horizon by locmemcache-devstack-deployers) 12:22:39 so memcache is already part of devstack? 12:22:47 r1chardj0n3s: not really 12:22:56 we could even use redis 12:22:59 they don't want it in by default 12:23:03 right 12:23:11 that is required by ceilo 12:23:36 mrunge: aren't they using mongodb anymore? 12:23:47 yeah, I thought they used mongo 12:23:55 I'll rebase my memcache adding patch and if that doesn't move in the next week or so, put up a competing LocMemcache patch and see who wins 12:24:15 wait, I thought redis was pulled in anyways 12:24:54 db mgmt increases the complexity of the devstack change 12:27:22 ceilometer seems to use mongo for data store 12:27:31 and redis for backend coordination 12:27:55 why can't we have two different dbs ? 12:28:16 * david-lyle is really kidding 12:28:18 sure.... 12:28:32 seriously, we should start using postgres 12:28:40 I was about to say that mrunge 12:29:03 or rather, that we have a db around because of the other services (which IIRC is actually mysql) 12:29:36 * r1chardj0n3s is painfully ignorant of how database access is structured in openstack 12:29:52 r1chardj0n3s, that's somehow constantly changing 12:30:02 I prefer to stick with a cache that will clean up after itself 12:30:10 of course, it's OpenStack(tm) 12:30:15 * mrunge still looking for redis reference in ceilometer 12:30:33 anyways, any of them should be fine 12:30:45 what people use in the privacy of their own deployment is up to them 12:30:46 if we already have redis somewhere, we could use it 12:30:50 yupp 12:31:10 I think david-lyle's proposal for rebasing memcache and seeing if it gets traction is worthwhile. if that gets in, then we're done. 12:31:30 yep 12:31:41 +1 12:31:55 properly testing devstack patches is time consuming to I have let that one rot a bit 12:32:02 will find the time today 12:32:27 ok moving on 12:32:30 #topic What is actually going on with JS linting anyway? Anyone know? 12:32:30 for reference: https://github.com/openstack/ceilometer/blob/master/devstack/plugin.sh#L87 12:32:59 ok, to step back topics for a sec 12:33:23 the other thing we could do is make horizon a devstack plugin rather than integrated content 12:33:44 then changing things like the SESSION_ENGINE become a lot more trivial 12:33:54 david-lyle: I'm not sure what that means but it sounds intriguing 12:34:05 but I'm not sure the extra effort for tempest 12:34:18 although horizon should only plugin into tempest too 12:34:20 david-lyle, as I understand it from here: we would be fine with any cache 12:34:35 I'll look into the plugin path 12:35:04 r1chardj0n3s: projects can own how they are set up in devstack by putting a devstack dir in their repo 12:35:12 ahh 12:35:16 and setting it up as a devstack plugin 12:35:28 same for tempest 12:36:23 ok, shall we talk linting? 12:36:25 so to use horizon with devstack, you'd have to add an plugin line to your local.conf 12:36:32 yes 12:36:36 lint away 12:36:39 (thanks for the explanation) 12:36:42 So I'm working on this Swift UI rework, and it's a bunch of JS and I've just run the "npm run lint" and hoo boy there's a lot of garbage spewing out of that 12:37:03 * david-lyle is shocked 12:37:08 so I'm wondring is there anyone who knows how this stuff works, or is it just krotscheck? 12:37:25 matt-borland maybe 12:37:33 a lot of the spew is warnings, apparently a misconfiguration, which also results in actual errors 12:37:33 heh, I had the feeling, krotscheck just proposes rules 12:38:03 but if I'm reading this config right (and I might not be) we're overriding some of the "openstack" lint rules with our own 12:38:30 r1chardj0n3s: I believe there were many we weren't ready for 12:38:38 and some that were angular specific 12:38:56 but I may be making that up 12:39:03 there's a lot of these "lint" rules that are all about code *style* which I'm not sure I agree with :/ 12:39:28 ok, maybe I should email this stuff to openstack-dev and see if I can get some info there 12:39:30 r1chardj0n3s, then I think we should more actively participate in openstack-eslint-rules reviews 12:39:39 that is probably the issue with lint rules defined outside of horizon 12:39:46 tsufiev: I kinda keep an eye on it, but the volume, along with other things... 12:40:21 mrunge: as I understand it, krotscheck is trying to create an "openstack js lint standard" ... which is funny given the number of non-horizon JS projects... 12:40:36 Horizon community needs at least 3 people per review to counterbalance krotchek's enthusiasm :) 12:40:45 we there is at least one non horizon 12:40:50 *well 12:40:56 js project 12:41:08 regardless, at the moment the lint configuration is *broken* and I need someone to 'fess up to knowing what it's supposed to be :/ 12:41:28 yes, I agree with having just one definition around all openstack projects 12:41:46 just to have sane defaults for all 12:41:58 depends on %sane% here 12:42:15 I'd say this initiative is just premature 12:43:14 so at the moment we've got lint errors because we're not assigning the "this" variable to another variable called "vm" in our angular controllers 12:43:36 except Horizon's configuration explictly says that variable should be called "ctrl" which is what we use everywhere 12:43:45 but the linter complains anyway 12:43:52 r1chardj0n3s, heretics, you deny the holy John Papa's Guide! :) 12:44:01 tsufiev: don't make me come over there 12:44:16 lol 12:44:35 that would be handy for meetings, though ;-) 12:44:48 ok, I shall write a TODO for tomorrow to email openstack-dev to try to resolve this 12:44:52 david-lyle: please move on 12:45:39 #topic Install Guide and Quickstart revamp? 12:45:48 njirap: o/ 12:45:56 yes thats me 12:46:15 so i installed horizon outside devstack 12:46:33 i followed the two guides available, the quickstart and the install guide 12:46:55 it is my opinion that the two have the potential to be better 12:47:09 njirap: dev docs or docs docs 12:47:33 david the quickstart http://docs.openstack.org/developer/horizon/quickstart.html 12:47:42 * mrunge would think, install docs should be moved to docs.openstack... 12:47:54 and the other install guide docs.openstack.org/developer/horizon/topics/install.html 12:47:56 there is an install guide on docs.open 12:48:22 quickstart is meant for folks using git checkouts 12:48:34 the quickstart could use some attention though, it's a little ... oddly structured :-) 12:48:50 yeah 12:48:54 issue1 -> the install guide does not document some dependencies 12:49:10 njirap: http://docs.openstack.org/kilo/install-guide/install/apt/content/install_dashboard.html 12:49:21 is that latest version I know of 12:49:50 njirap, are you installing for a deployment? 12:49:58 or for a dev setup? 12:49:58 sorry http://docs.openstack.org/kilo/install-guide/install/apt/content/ch_horizon.html is the top level 12:50:14 hi mrunge 12:50:28 i am personally installing for development 12:51:10 what dependency is missing? 12:51:11 david am lookin at that now 12:51:27 njirap: ok then the docs you referenced are more applicable 12:51:44 I thought you were trying to deploy horizon 12:51:51 njirap, I would make a distinction between developer setup or deployment for a larger base 12:52:03 horizon docs just cover developer setup 12:52:23 the real stuff should go to docs.openstack.org, what david mentioned 12:52:50 but if it's not clear from our docs, that's room for improvement 12:53:01 hi mrunge.. that information is not clear in the two guides,,, a production setup'pper is not explicitly directed to the right doc neither the development setup'per 12:53:22 njirap: short answer is if you feel you find errors in either set of docs, feel free to propose changes 12:53:33 aah ok thanks david 12:53:51 issue2-> both guides ends at the login page 12:54:05 I'm not sure a wholesale revamp is necessary, but there is always room for improvement 12:54:35 njirap, is there something to set up after login?? 12:54:36 i think i can setup launchpad blueprint for individual changes 12:54:54 njirap: http://docs.openstack.org/user-guide/dashboard.html 12:55:05 mrunge.. it is not documented where one can get or set the login credentials 12:55:09 is past the login page 12:55:31 njirap: mostly because that is owned by another service 12:55:42 feel free to add that info. (keystone) 12:56:12 but yes, feel free to fill in any of the blanks you find 12:56:41 hi david. it is my opinion that that should be documented as well,,the keystone bit,,,other than leaving(assuming a beginner) at the login page... 12:57:15 njirap, we should not duplicate that bit, hinting to keystone is fine 12:57:26 and there are so many install guides 12:57:48 feel free to drop the ubuntu one... 12:57:50 :P 12:57:54 haha 12:58:23 seriously, that is generated from one source 12:58:37 there is actually no duplication 12:58:52 we have two minutes left 12:58:56 would it make sense to move that topic over to #openstack-horizon? 12:59:19 sure 12:59:23 I would like to ask for the way forward with https://review.openstack.org/#/c/255854/ 12:59:26 yes it would mrunge but i can also attempt bug reports on launchpad 12:59:29 if there is any way forward 12:59:43 i am good he meeting can move on 12:59:49 *the 13:00:03 that patch adds info about a the user launching an instance 13:00:08 mrunge: let's move to #openstack-horizon 13:00:09 rather than just showing the id 13:00:16 ack 13:00:16 Thanks everyone. 13:00:21 #endmeeting