20:01:10 <david-lyle> #startmeeting Horizon
20:01:10 <openstack> Meeting started Wed Aug 26 20:01:10 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:01:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:01:13 <openstack> The meeting name has been set to 'horizon'
20:01:29 <david-lyle> Horizon twice a day, isn't it grand ?
20:01:42 <mrunge> yay!
20:01:47 <tsufiev> such a long day
20:01:54 <david-lyle> with some pluck we'll get up to 3 before too long
20:02:00 * david-lyle is really kidding
20:02:16 <tsufiev> taking into account UX meeting there are already 3 of them
20:02:24 <robcresswell> UX isn't Horizon
20:02:24 <hurgleburgler> lol!
20:02:27 <robcresswell> well.
20:02:32 <robcresswell> it's not supposed ot be :p
20:02:32 <mrunge> i18n then?
20:02:38 <TravT_> o/
20:02:45 <Piet> Three UX meetings?
20:02:47 <hurgleburgler> (◕‿◕✿)ノ
20:02:53 <david-lyle> did I kill the wiki page?
20:03:12 <rhagarty_> o/
20:03:31 <tqtran> [=_=]/
20:03:50 <ducttape_> 0/
20:04:30 <david-lyle> ok, agenda is at
20:04:32 <crobertsrh> hello/
20:04:32 <david-lyle> #link https://wiki.openstack.org/wiki/Meetings/Horizon
20:04:50 <david-lyle> apparently I added meeting days, so was quickly correcting
20:05:12 <david-lyle> let's jump in and leave time to review status on priorities
20:05:22 <david-lyle> #topic OpenStack Summit Tokyo: Joint working session for Horizon and Zaqar proposal (vkmc)
20:05:38 <david-lyle> vkmc o/
20:06:10 <david-lyle> ok let's circle back
20:06:24 <david-lyle> #topic OpenStack Summit Tokyo: Joint working session for Horizon and Searchlight discussion (TravT)
20:06:29 <david-lyle> TravT o/
20:06:34 <TravT_> i saw vkmc added that
20:06:37 <TravT_> so i copied her...
20:06:46 <TravT_> but basically, we are building searchlight largely for horizon
20:06:48 <david-lyle> -1 on originality
20:06:54 <david-lyle> +1 for honesty ;)
20:06:59 <TravT_> lol
20:07:14 <TravT_> and in tomorrow's searchlight meeting going to talk about working session requests
20:07:26 <TravT_> with ttx saying that space is tighter than vancouver
20:07:51 <TravT_> was thinking we could put in one combined session for horizon / searchlight if needed.
20:07:58 <Piet> Have you gotten design help from Michael and Jenny on Searchlight?
20:08:00 * ducttape_ looks forward to the openstack google ui so he doesn't mess with api snowflakes
20:08:14 <TravT_> Piet, still waiting on that.
20:08:30 <Piet> Is it a rush?  Do y need ASAP?
20:08:41 <vkmc> o/
20:08:43 <TravT_> sooner is better... but when isn't it?
20:08:50 <Piet> k
20:08:59 <Piet> Will reach-out to Hinnant
20:09:08 <david-lyle> vkmc: we'll come back to your topic in just a minute
20:09:17 <vkmc> david-lyle, np
20:09:20 <vkmc> sorry I'm late
20:09:24 <david-lyle> no worries
20:09:28 <TravT_> so, just thought I'd float it out there as well.
20:09:39 <david-lyle> I'd be fine with a joint working session
20:09:58 <david-lyle> we essentially had a fishbowl on searchlight last summit
20:10:11 <david-lyle> so a working session to make progress would be useful
20:10:11 <TravT_> ok, when we put in the request we can mention that.
20:10:27 <david-lyle> any concerns?
20:11:15 <david-lyle> gone
20:11:22 <TravT_> thx
20:11:37 <david-lyle> was that your stage nick?
20:11:42 <robcresswell> haha
20:11:53 <TravT> yeah, better to have an alter-ego for meetings
20:12:07 <david-lyle> #topic OpenStack Summit Tokyo: Joint working session for Horizon and Zaqar proposal (vkmc)
20:12:16 <david-lyle> vkmc o/ and welcome
20:12:27 <vkmc> david-lyle o/ horizoners o/
20:12:28 <vkmc> thanks
20:12:29 <vkmc> hi all!
20:12:34 <TravT> o/
20:12:55 <vkmc> so, a few summits back there were some discussions about horizon-zaqar integration
20:13:01 <vkmc> I recall there were some use cases
20:13:08 <vkmc> which I listed in this etherpad https://etherpad.openstack.org/p/zaqar-horizon-usecases
20:13:41 <vkmc> we were wondering if those use cases still hold
20:14:02 <mrunge> I wonder if ceilometer would suit those use cases better for horizon
20:14:05 <vkmc> and if there is interest from Horizon team to arrange a working session for the next summit to talk a bit more about those
20:14:24 <mrunge> definitely interested!
20:14:37 <mrunge> we need to fix that async stuff in horizon
20:14:38 <david-lyle> certainly interested in the use cases
20:14:43 <vkmc> :)
20:14:45 <ducttape_> I'm not sure if messaging as a service and then showing rabbit messages from under cloud would be confusing
20:15:03 <mrunge> ducttape_, cinder create is fired async
20:15:15 <mrunge> you don't see, if it fails
20:15:21 <ducttape_> but in general, showing rabbit messages and status / health is not a bad general idea
20:15:24 <mrunge> if you don't pull for service update
20:15:34 <mrunge> sme is true for launching instances
20:15:40 <ducttape_> mrunge, I know.  lots of opportunities
20:15:50 <mrunge> I'll shut up ;-)
20:16:05 <tsufiev> mrunge, could we get rid of constant polling there by the help of zaqar?
20:16:10 <tqtran> we know what you really mean by "opportunities" ducttape_
20:16:16 <ducttape_> I'm just saying the message bus for core services is one thing, but if I have messaging as a service, that is very different
20:16:18 <tsufiev> i mean, at every table...
20:16:27 <mrunge> tsufiev, that might be a possibility
20:16:27 <vkmc> certainly we will need some time to discuss if and how Zaqar would fit the requirements Horizon has
20:16:39 <mrunge> or that's my naive idea
20:16:58 <david-lyle> I think there's a question of which pieces are owned by what, there now seems to be at least 3 possible sources of async notifications
20:17:02 <mrunge> but: you could use ceilo to get notified when an event was triggered
20:17:17 <david-lyle> ceil, zaqar and searchlight
20:17:35 <ducttape_> I could see an admin page that just showed the last X rabbit messages / current stream of them.... and general rabbit health
20:17:46 <david-lyle> but a session to figure out what the right solution and where is certainly high on my list of prioritites
20:17:57 <TravT> yeah, i agree
20:18:01 <ducttape_> so this is good, this is a topic with interest
20:18:07 <tqtran> searchlight is also looking to push notifications?
20:18:15 <tqtran> i thought we were just using it for queries?
20:18:15 <david-lyle> tqtran: it could
20:18:20 <tqtran> oh wow..... ok....
20:18:26 <mrunge> when planning such a session, let's have ceilo and searchlight folks too
20:18:39 <mrunge> just to have all people on the same side
20:18:43 <david-lyle> but if another service is doing that it doesn't need to duplicate
20:18:51 <robcresswell> ducttape_: I'd love a sidebar type thing like OSX and I think the new windows thing does, where alerts and messages just pop up in it.
20:19:08 <david-lyle> vkmc: I think we're all saying we're strongly interested :)
20:19:10 <robcresswell> always thought that would be cool. Like a live feed of cloud updates.
20:19:13 <vkmc> if it helps for something, we now have support for websocket :D
20:19:24 <tqtran> robcresswell: we already have something that can do that, toast service :P
20:19:38 <hurgleburgler> websockets! ٩(͡๏̮͡๏)۶
20:19:38 <mrunge> vkmc++
20:19:39 <TravT> hmmm, not quite tqtran.
20:19:40 <ducttape_> I like toast, except for the carbs
20:20:33 <tqtran> hurgleburgler is volunteering to write our websocket layer?
20:20:36 <david-lyle> vkmc: let's plan on a joint session, if you don't mind us inviting a couple other people to keep us well rounded
20:21:01 <vkmc> david-lyle, not a problem
20:21:03 <david-lyle> might be a useful conversation for all parties
20:21:09 <TravT> sounds good to me
20:21:14 <hurgleburgler> tqtran ok, i'm on it!
20:21:20 <vkmc> helps a lot to hear diff alternatives
20:21:53 <vkmc> hurgleburgler, \o/
20:22:09 <david-lyle> vkmc: absolutely
20:22:18 <hurgleburgler> haha
20:22:31 <david-lyle> #action david-lyle figure out how to propose joint sessions
20:22:38 <vkmc> please, feel free to ping us in #openstack-zaqar, or in our weekly meetings https://wiki.openstack.org/wiki/Meetings/Zaqar
20:23:03 <vkmc> if you have any doubt or concern about Zaqar current status or how we could cover your use cases
20:23:43 <david-lyle> sure, I think we need to do our homework
20:23:53 <swati_> Hi David, I had some queries for getting the blueprints approved?
20:23:55 <ducttape_> I think many people might be interested in joint sessions david-lyle  +1
20:23:58 <david-lyle> and likely there will be quetsoins
20:24:10 <david-lyle> *questions
20:24:15 <vkmc> cool :)
20:24:33 <mrunge> you haven't heard the questions yet
20:24:49 <vkmc> haha mrunge++
20:24:52 <david-lyle> swati_: we're working through an agenda and will have time at the end for open questions
20:25:11 <swati_> Sure, will wait...thanks
20:25:29 <david-lyle> ok 2 joint sessions, which leads into my topic
20:25:47 <david-lyle> #topic summit space planning (david-lyle)
20:26:12 <david-lyle> oh, thanks vkmc :)
20:26:47 <david-lyle> as you all may have deduced, there was a call to provide our space allocation requirements for the Tokyo summit
20:26:49 <vkmc> np, thanks you!
20:27:41 <david-lyle> At the YVR summit we had 3 fishbowl, 8 working sessions, and 2 collab half day sessions
20:28:11 <david-lyle> so the scoop is
20:28:22 <david-lyle> 2x workrooms to fishbowl rooms
20:28:29 <david-lyle> less rooms than YVR
20:28:35 <david-lyle> Rooms are smaller
20:28:49 <david-lyle> and more teams in the big tent fighting for space
20:28:56 <robcresswell> nice
20:28:59 <ducttape_> is there a guess on attendance size relative to YVR ?
20:29:21 <david-lyle> maybe less, but not much, not entirely sure
20:29:34 <david-lyle> HK didn't really shrink either
20:29:46 <david-lyle> just different population
20:30:23 <david-lyle> so the guidance is less room requests
20:30:30 <david-lyle> and workrooms are easier
20:30:57 <david-lyle> the joint sessions will reduce some pressure
20:31:12 <david-lyle> so I'm looking for proposals
20:31:23 <david-lyle> I think we could do with less fishbowl sessions
20:31:27 <mrunge> but joint sessions will require more space
20:31:47 <mrunge> yes! less fishbowl sounds good to me
20:32:03 <david-lyle> they were not largely attended with the growing number of tracks
20:32:07 <mrunge> maybe just one? (Operator feedback)?
20:32:30 <ducttape_> watch out for ops feedback, we got loads of issues
20:32:45 <ducttape_> not too many for horizon tho :D
20:32:46 <david-lyle> I'd like to figure out how to work that in
20:33:11 <mrunge> I have seen increased bugs for horizon in the past
20:33:20 <david-lyle> wondering if there could be a tie in to the ops track, maybe combined feedback?
20:33:29 <david-lyle> if not, we can certainly hold one
20:33:44 <david-lyle> I'll see if there are any organized plans for that
20:33:55 <mrunge> I found ops feedback quite useful in the past
20:34:00 <ducttape_> one thing I'd say is ops people have a tough time with schedules, there is so much we want to attend
20:34:12 <david-lyle> is there another burning topic that would require a fishbowl?
20:34:16 <ducttape_> we are not just horizon or keystone etc
20:34:26 <david-lyle> ducttape_: you should be
20:34:42 <david-lyle> we're working on creating enough problems to be on your radar :P
20:34:59 * ducttape_ still thinking about how many times "joint session" has been mentioned
20:35:08 <david-lyle> ok, 1 fishbowl
20:35:13 <tsufiev> ducttape_, you could record some video in advance and introduce your speech remotely )
20:35:32 <ducttape_> I'll be there, you should be on the lookout
20:36:10 <david-lyle> I found the working session quite useful
20:36:21 <mrunge> yupp!
20:36:34 <david-lyle> I may ask for a similar number and let the schedulers back us down
20:36:46 <david-lyle> the other option is find a table
20:36:59 <mrunge> do we know about tables?
20:37:10 <tqtran> which i dont remember seeing at YVR
20:37:13 <mrunge> last time, that didn't work out
20:37:18 <david-lyle> no pods
20:37:21 <TravT_> they had some in paris...
20:37:21 <david-lyle> just random tables
20:37:33 <david-lyle> paris had pods and atlanta
20:37:48 <david-lyle> not in paris and YVR
20:38:09 <tqtran> you just contradicted yourself there.... i see what you did...
20:38:15 <david-lyle> I see that now
20:38:21 <ducttape_> he is write and wrong
20:38:26 * tsufiev recalls a lot of tables in YVR
20:38:28 <ducttape_> right (derp)
20:38:37 <mrunge> do we want a pod?
20:38:48 <david-lyle> not in YVR
20:38:52 <tqtran> lol write... haha, lets just pick a bench somewhere and call it our pod
20:39:02 <david-lyle> I don't think we need a predetermined space
20:39:15 <TravT_> let's just reserve a spot at a nearby bar.
20:39:24 <mrunge> +1 TravT_
20:39:24 <tqtran> after all, it is not the location but the group that makes us a pod (whales)
20:39:25 <david-lyle> question is should we try using that instead of working session rooms
20:39:47 <kzaitsev_mb> +1 TravT_ =))))
20:39:52 <mrunge> both has pros and cons
20:39:57 <david-lyle> I'm going to request a similar number and be flexible
20:40:07 <mrunge> tables outside can be quite noisy
20:40:08 <ducttape_> +1 - take what is available at location, then karaoke bar works too
20:40:17 <david-lyle> collab full or half day?
20:40:19 <mrunge> oh, btw. don't forget a beamer
20:40:34 <mrunge> I mean, to request a beamer in working rooms
20:40:57 <TravT_> seems to me that last part of the last day kind of falls apart at every summit
20:41:04 <mrunge> can we have 2 half days for collab?
20:41:12 <mrunge> on different days?
20:41:31 <robcresswell> I thought the last day was fairly productive at Vancouver
20:41:32 <david-lyle> no just last day
20:41:44 <mrunge> darn :(
20:41:45 <robcresswell> Hangover aside
20:41:53 <mrunge> yupp
20:42:02 <david-lyle> fishbowls are wed-thur
20:42:13 <david-lyle> working sessions are Tue-Thur
20:42:26 <david-lyle> and contributors meetup is Fri
20:42:55 <david-lyle> ok I'll ask for both and be flexible
20:43:00 <mrunge> well, we're scheduling our sessions, right?
20:43:11 <david-lyle> mrunge: once we have slots
20:43:16 <mrunge> we can call it x and do y
20:43:22 <david-lyle> mrunge: sure
20:43:29 <mrunge> we already did that in YVR
20:43:33 <mrunge> ;-)
20:43:55 <david-lyle> ok, so less fish equal work and contrib
20:43:59 <david-lyle> will make request
20:44:16 <david-lyle> #topic L-3 O_O
20:44:23 <david-lyle> L-3 is Sept 3
20:45:04 <david-lyle> that's it, holy cow
20:45:13 <david-lyle> no
20:45:21 <david-lyle> #link https://etherpad.openstack.org/p/YVR-horizon-liberty-priorities
20:45:53 <david-lyle> ReOrg status?
20:46:03 <david-lyle> seems to be patches there
20:46:25 <david-lyle> seems as though so of the reOrg also created some Selenium issues :/
20:46:33 <hurgleburgler> which reorg status?
20:46:38 <hurgleburgler> angular or css?
20:46:40 <r1chardj0n3s> yeah, they would've been noticed if the selenium tests were running :/
20:46:42 <david-lyle> Line 14
20:46:57 <david-lyle> in the linky thing
20:47:38 <david-lyle> so at this point, we've reduced some of the tech debt, will not finish and created a little along the way
20:47:45 <david-lyle> :)
20:47:47 <tqtran> r1chardj0n3s: hows the investigation cominb along?
20:47:55 <david-lyle> there was a lot to take on
20:47:59 <r1chardj0n3s> tqtran: all selenium tests are fixed, patches are in
20:48:06 <tqtran> oh nice!
20:48:22 <hurgleburgler> r1chardj0n3s that's great!
20:48:37 <david-lyle> #action get selenium actually running in the check/gate
20:48:38 <r1chardj0n3s> it wasn't difficult to fix them, but they only broke because the test suite wasn't being exercised :/
20:48:51 <david-lyle> #undo
20:48:53 <openstack> Removing item from minutes: <ircmeeting.items.Action object at 0xa34ce50>
20:48:59 <r1chardj0n3s> (l0l)
20:49:12 <david-lyle> #action david-lyle get selenium actually running in the check/gate
20:49:23 <r1chardj0n3s> yes, please :)
20:49:24 <david-lyle> unless someone else has a line on that
20:49:50 <hurgleburgler> not it!
20:49:53 <r1chardj0n3s> I'm not entirely sure how they've been disabled, but I could
20:50:03 <r1chardj0n3s> I have a line to #infra to do stuff if needed there
20:50:17 <david-lyle> r1chardj0n3s: me either, just now the happy report no tests run but success
20:50:30 <r1chardj0n3s> david-lyle: yeah, how about I look into that today
20:50:40 <david-lyle> r1chardj0n3s: excellent
20:50:44 <r1chardj0n3s> starting out non-voting, I assume?
20:50:46 <david-lyle> ping me if you need help
20:50:58 <david-lyle> r1chardj0n3s: if they are passing I'd make them voting
20:51:08 <david-lyle> they aren't quite as unstable
20:51:12 <r1chardj0n3s> well, we still need to commit two patches
20:51:18 <david-lyle> (if running)
20:51:26 <david-lyle> r1chardj0n3s: ok, then non-voting
20:51:30 <r1chardj0n3s> https://review.openstack.org/#/c/215408/
20:52:24 <r1chardj0n3s> https://review.openstack.org/#/c/215435/ (though this could be superseded by https://review.openstack.org/#/c/156572/ )
20:52:54 <david-lyle> I'm going to jump the rest of the priorities in concern for time, tl;dr; we made significant progress, but took on too much
20:53:13 <tsufiev> r1chardj0n3s, regarding the latter there is some research about karma vs. selenium to be done
20:53:18 <david-lyle> I think our definition of top priority needs some refining
20:53:35 <ducttape_> dj18 ?
20:53:40 <r1chardj0n3s> tsufiev: nah, let's get that in, it's good enough for now
20:53:43 <tsufiev> david-lyle, top-priority = on what the most time was spent :)
20:53:46 <r1chardj0n3s> (I just +1'ed)
20:53:52 <david-lyle> ducttape_: ah yes
20:54:24 <david-lyle> should be most of the way there, I have a patch to g-r to bump Django support to >=1.7;<1.9
20:54:39 <david-lyle> d-o-a and horizon can support it now
20:54:51 <ducttape_> would be good to get time on that new setup so we can find any issues
20:55:00 <david-lyle> django_openstack_auth 1.4.0 was released this week
20:55:07 <david-lyle> which supports 1.8
20:55:20 <ducttape_> or, so you guys can find issues w dj1.8 and I don't ;)
20:55:33 <david-lyle> I've tested it and not seen any issues
20:55:49 <david-lyle> but that's saying little
20:55:56 <mrunge> there are still warnings (deprecation warnings) witj django-18
20:56:06 <david-lyle> robcresswell: had a patch for that
20:56:14 <david-lyle> not sure the status
20:56:16 <robcresswell> I found more earlier
20:56:27 <mrunge> there are a few....
20:56:32 <david-lyle> ok, they are warnings
20:56:49 <david-lyle> but should be cleaned
20:56:50 <david-lyle> up
20:56:52 * tsufiev snaps eyes at david-lyle and thinks about the integration tests announcement
20:57:01 <david-lyle> tsufiev: trying to get there
20:57:13 <david-lyle> #topic Integration tests
20:57:30 <david-lyle> We have passing integration tests again thanks to tsufiev
20:57:39 <robcresswell> \o/
20:57:41 <TravT> great work, tsulfiev
20:57:44 <david-lyle> did the revert merge?
20:58:06 <tsufiev> david-lyle, not yet as it doesn't have +A )
20:58:08 <david-lyle> +a'd now
20:58:35 <david-lyle> once that's in, the integration tests will be passing
20:58:40 <tsufiev> so the thing with integration tests is that all cores should now pay attention to them before +2
20:58:40 <mrunge> \o/ tsufiev
20:58:47 <david-lyle> reviewers watch those tests
20:58:52 <david-lyle> they are not voting
20:59:00 <tsufiev> otherwise some patch may break  them again (before they become voting)
20:59:09 <david-lyle> if you see a failure on a patch, look into it
20:59:29 <tsufiev> or ping me
20:59:33 <r1chardj0n3s> great work tsufiev
20:59:42 <TravT> what time did that go in?
20:59:43 <r1chardj0n3s> the important point is we should be paying attention to them, yes
20:59:47 <TravT> we'll have to run recheck on some patches
21:00:01 <david-lyle> we will make these voting once we know we've stabilized
21:00:12 <tsufiev> TravT, 3 days if I understood the question
21:00:24 <david-lyle> TravT: well turns out the revert I posted is just making it into the gaet
21:00:33 <david-lyle> so right now you will see tons of failures
21:00:39 <david-lyle> :(
21:00:46 <TravT> ok.
21:00:51 <david-lyle> like 11
21:00:56 <robcresswell> Okay. So integration tests fail, no approval?
21:01:01 <robcresswell> Or just, make a note of it
21:01:06 <robcresswell> See if it can be fixed etc
21:01:19 <tsufiev> robcresswell, it's not always easy :(
21:01:20 <david-lyle> robcresswell: if the failure is related to the change then no approval
21:01:27 <mrunge> what if a client lib update broke integration tests?
21:01:28 <david-lyle> but can be hard to diagnose
21:01:36 <tsufiev> I mean understanding what's wrong with them
21:01:42 <robcresswell> Yep, understood
21:01:48 <david-lyle> mrunge: that should be a bug filed on horizon
21:02:06 <david-lyle> ok we're over time. Please just watch the integration tests
21:02:14 <david-lyle> Thanks everyone
21:02:15 * robcresswell nudges everyone to take a look at Curvature in the final week :) https://review.openstack.org/#/c/141078/
21:02:18 <robcresswell> :p
21:02:31 <david-lyle> there was someone with a question that we didn't get to, please ask in #openstack-horizon
21:02:34 <david-lyle> I'll be there
21:02:41 <david-lyle> #endmeeting