20:00:12 <r1chardj0n3s> #startmeeting horizon
20:00:16 <openstack> Meeting started Wed Nov 30 20:00:12 2016 UTC and is due to finish in 60 minutes.  The chair is r1chardj0n3s. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:17 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:20 <betherly> o/ hallo
20:00:21 <openstack> The meeting name has been set to 'horizon'
20:00:25 <r1chardj0n3s> o/
20:00:36 <robcresswell> o/
20:00:50 <r1chardj0n3s> UK represent!
20:00:55 <tqtran> [=_=]/
20:00:57 <betherly> wooooot
20:01:29 <r1chardj0n3s> okie dokie, on with the thing
20:01:30 <rhagarty_> o/
20:01:32 <r1chardj0n3s> #topic Priority patches for review
20:01:46 <clu_> o/
20:01:53 <r1chardj0n3s> #link https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open is the list of patches we'd like to see reviewed as highest priority
20:02:22 <r1chardj0n3s> #link https://etherpad.openstack.org/p/horizon-ocata-priorities has a bunch of patches under Ocata-2 that we'll start moving on to
20:02:35 <r1chardj0n3s> I’ve tried to capture all of the in-play angularjs panel work, but if I missed any please note them.
20:03:05 <r1chardj0n3s> I think since there’s so many, I’d like to know whether anyone has any priorities in that lot. Yes, high priority priority patches
20:04:17 <david-lyle> o/
20:06:02 <r1chardj0n3s> OK, I'll just mark the ones that have active developers working on them then ;-)
20:06:09 <r1chardj0n3s> #topic Badges
20:06:10 <r1chardj0n3s> #link https://review.openstack.org/#/c/402556/ if anyone cares enough, please fix this thing
20:06:23 <r1chardj0n3s> (we do love a bit of make-work here in OpenStack)
20:07:10 <david-lyle> r1chardj0n3s: I thought there was a patch fixing that already
20:07:21 <robcresswell> -.-
20:07:30 <robcresswell> Fixing openstack one pointless patch at a time
20:07:39 <david-lyle> https://review.openstack.org/#/c/404382/ maybe
20:08:25 <r1chardj0n3s> david-lyle: right. my care level is super low, given other priorities
20:09:09 <r1chardj0n3s> ok, moving on
20:09:15 <r1chardj0n3s> #topic Zaqar push-based communication via websocket (POC)
20:10:03 <tqtran> so i brought this up last week, but wanted to wait until this week for more people to get input
20:10:03 <r1chardj0n3s> tqtran?
20:10:10 <r1chardj0n3s> (ah, sorry)
20:10:31 <tqtran> the zaqar ptl uploaded a POC patch showing how we can use websocket instead of polling
20:10:53 <tqtran> https://review.openstack.org/#/c/246009/
20:11:08 <tqtran> but the problem is that its written using legacy js
20:11:22 <tqtran> we have plans on implementing instances panel, but i doubt that will land anytime soon
20:11:47 <tqtran> so the question is: do we want the POC using legacy now, or wait until the new instances panel kick in
20:12:09 <robcresswell> it'd be best to do it on Images right?
20:12:17 <robcresswell> That already misses the polling anyway
20:12:21 <david-lyle> why would we poll images?
20:12:38 <robcresswell> status
20:12:48 <david-lyle> are you expecting them to change?
20:12:57 <tqtran> i believe we are polling images in the ngimages panel
20:12:57 <robcresswell> When creating new ones? Yeah I assume so
20:13:08 <robcresswell> I dont think angular tables poll do they?
20:13:26 <r1chardj0n3s> that patch needs a lot of work, also, there's a lot of hard-coding of things that should be configurable or discoverable in there
20:13:26 <tqtran> they are polling sadly, theres no push-based mechanism on the backend
20:13:38 <robcresswell> I thought they did nothing right now
20:13:46 <robcresswell> the regular one does, bug I thought ng didnt
20:14:09 <tqtran> pretty sure its polling, i remember reviewing a patch on it
20:14:54 <tqtran> anyway, maybe we can get the POC websocket thing to work on images first?
20:14:59 <david-lyle> was are polling :(
20:15:05 <david-lyle> at least the django was
20:15:14 <david-lyle> s/was/we/
20:15:29 <robcresswell> anyway, yes, a websocket angular POC would make more sense
20:15:30 * david-lyle hangs head
20:15:53 <r1chardj0n3s> +1 to getting it working for images
20:16:02 <tqtran> ok, i'll tell them that then
20:16:11 <r1chardj0n3s> websocket polling came up at the summit and searchlight was mentioned, yeah?
20:16:35 <david-lyle> I feel like we should have two dashboards
20:16:42 <r1chardj0n3s> or am I misremembering things
20:16:54 <david-lyle> one with only core services and plugin support
20:17:23 <david-lyle> and one with support for several dependent projects that would make life better
20:17:29 <david-lyle> but I digress
20:17:41 <r1chardj0n3s> crazy
20:17:51 <r1chardj0n3s> moving on
20:18:00 <r1chardj0n3s> #topic Using execfile also for local_settings.py, not just loca_settings.d
20:18:20 <r1chardj0n3s> (no name against this, assuming it was radomir?)
20:18:20 <david-lyle> I mean currently we're polling on the server side regardless
20:18:28 <robcresswell> yeah thats rdopiera
20:19:43 <r1chardj0n3s> I assume he's agitating for not using import to get the contents of local_settings.py; I'm not sure exactly why, but I'm generally in favour of using execfile over import unless there's a good reason to use the latter.
20:20:34 <r1chardj0n3s> .. but I thought he wanted to get rid of Python-based settings completely
20:21:44 <david-lyle> these are for plugins and themes, that would be even further down the road
20:22:52 <r1chardj0n3s> OK, in the absence of Radomir, I guess we'll have to table that discussion until next meeting.
20:23:02 <r1chardj0n3s> #topic Open Discussion
20:23:28 <r1chardj0n3s> anyone got anything they'd like to bring up? say, the size of the ocata-2 priority list? :-)
20:24:31 <robcresswell> Nothing in particular :)
20:25:19 <ediardo> me
20:25:48 <ediardo> https://review.openstack.org/#/c/388200/
20:25:56 <r1chardj0n3s> I would like to point out that the run_tests.sh removal effort by robcresswell is moving along really well, and if you've not stopped using it already you should do so :-)
20:25:56 <r1chardj0n3s> the "final" tox fixup patch will merge imminently
20:25:57 <r1chardj0n3s> #link https://review.openstack.org/#/c/391506/
20:25:57 <r1chardj0n3s> give it a run if you haven't, please
20:25:57 <ediardo> I nevermind
20:26:08 <ediardo> I read something there
20:26:25 <r1chardj0n3s> we've also been trying to enforce upper-constraints in all the stable branches, so we'll probably release xstatic-angular-bootstrap 2.2.0.0 very soon, which breaks a bunch of stuff
20:27:19 <r1chardj0n3s> ediardo: yeah, the coverage fairy decided to pay a visit :-(
20:27:46 <ediardo> yes, I'll work on it
20:28:02 <r1chardj0n3s> did you find the coverage reports?
20:28:11 <ediardo> I just read Thai's comment
20:28:15 <r1chardj0n3s> yup
20:28:34 <ediardo> Yes, I found 'em
20:29:03 <ediardo> Thanks
20:29:38 <r1chardj0n3s> ok folks, I reckon we're done then, thanks for coming!
20:29:43 <r1chardj0n3s> #endmeeting