12:01:08 <david-lyle> #startmeeting horizon
12:01:09 <openstack> Meeting started Wed Dec  9 12:01:08 2015 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:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:01:12 <openstack> The meeting name has been set to 'horizon'
12:01:22 <david-lyle> anyone around?
12:01:24 <r1chardj0n3s> o/
12:01:27 <robcresswell> o/
12:01:31 <lhcheng> o/
12:02:45 <neillc> o/
12:02:56 <itxaka> o/
12:03:13 <tsufiev> o/
12:03:15 <amotoki> o/
12:03:18 <kzaitsev_mb> o/
12:03:23 <david-lyle> General things first.
12:03:39 <david-lyle> Welcome r1chardj0n3s and tsufiev to horizon-core
12:03:51 <mrunge> o/
12:03:52 <r1chardj0n3s> thanks :-)
12:04:07 <tsufiev> thanks as well :)
12:04:09 <robcresswell> \o/
12:04:16 <amotoki> welcome :)
12:04:28 <neillc> grats to you both
12:04:29 <pkarikh> o/
12:04:45 <itxaka> congrats!
12:05:09 <david-lyle> Next item, we released M-1 for Horizon last week
12:05:50 <david-lyle> I will be looking to release d-o-a soon as well. both domain scoped token related patches merged
12:06:54 <david-lyle> Wanted to quickly run through Mitaka priorities
12:07:04 <tsufiev> david-lyle, is it still some time left to push https://review.openstack.org/#/c/224756/1 before DOA release?
12:07:32 <david-lyle> tsufiev: we can release as often as needed
12:07:36 <tsufiev> this renaming will require at least 2 releases of DOA :/
12:07:44 <tsufiev> awesome
12:08:14 <david-lyle> have to read that review
12:08:40 <tsufiev> still WIP, will finalize it in a matter of few day
12:08:57 <david-lyle> that was the mailing list item for transitioning the AVAILABLE_ReGIONS setting?
12:09:08 <tsufiev> yes
12:09:48 <david-lyle> essentially it's just adding a second setting for the same thing
12:09:52 <lhcheng> david-lyle: can we include this too for d-o-a release: https://review.openstack.org/#/c/235609/
12:10:35 <lhcheng> would be better to release this earlier to catch any regression it may have
12:10:41 <tsufiev> david-lyle, to some extent, my second intention was to clean up code so there would be no 'available_regions' mentions left
12:10:53 <david-lyle> lhcheng: yes, +a'd now
12:11:06 <lhcheng> david-lyle: thanks!
12:11:06 <david-lyle> tsufiev: we have to depricate it
12:11:19 <david-lyle> *deprecate
12:11:27 <tsufiev> and since DOA and horizon are very intertwined regarding this setting, it requires a lot of changes
12:11:28 <david-lyle> 2 cycles
12:11:47 <tsufiev> sure
12:11:54 <david-lyle> which reminds me of general item for later
12:12:49 <david-lyle> ok one last general bit before mitaka status
12:13:16 <david-lyle> I don't know how many people follow the project tags
12:13:33 <david-lyle> but I need to consider adding  a few
12:14:08 * r1chardj0n3s twitches at the mention of tags
12:14:16 <david-lyle> one is http://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html
12:14:26 <amotoki> http://governance.openstack.org/reference/tags/index.html
12:14:35 <david-lyle> second is http://governance.openstack.org/reference/tags/assert_supports-upgrade.html
12:14:51 <david-lyle> I think both of those are definitely applicable
12:15:04 <david-lyle> the third is http://governance.openstack.org/reference/tags/assert_supports-rolling-upgrade.html
12:15:18 <r1chardj0n3s> david-lyle: forgive my ignorance, but are those git tags, or are they somewhere else?
12:15:39 <david-lyle> the third is technically true too, I believe
12:15:44 <tsufiev> r1chardj0n3s, I guess it's the governance/big tent tags
12:16:14 <david-lyle> r1chardj0n3s: those tags are for projects to indicated behavior to operators
12:16:41 <robcresswell> r1chardj0n3s: https://github.com/openstack/governance/blob/master/reference/projects.yaml#L736
12:16:46 <robcresswell> I think its those.
12:16:50 <amotoki> rickflare: you can find various defined tags in http://governance.openstack.org/reference/tags/index.html
12:16:52 <r1chardj0n3s> ah, thanks robcresswell
12:16:56 <amotoki> rickflare: sorry
12:17:02 <amotoki> r1chardj0n3s: ^^
12:17:45 <david-lyle> I will be proposing patches to add all three, unless someone has a reason not to
12:18:00 <amotoki> I think both of three sounds reasonable.
12:18:34 <r1chardj0n3s> we would need to update our dev documentation where appropriate (like "standard" deprecation, whatever that is ;-)
12:18:40 <robcresswell> They sound fine
12:19:00 <amotoki> r1chardj0n3s: good point
12:19:01 <david-lyle> r1chardj0n3s: just when deprecating something
12:19:03 * r1chardj0n3s is reading a bunch of pages at the moment
12:19:04 <robcresswell> I'd assume standard in that case means at least one cycle of "THIS IS DEPRECATED"
12:19:19 <david-lyle> two cycles
12:19:38 <r1chardj0n3s> http://governance.openstack.org/reference/tags/assert_follows-standard-deprecation.html is quite detailed, which is good
12:19:40 <david-lyle> is the standard before removing something
12:20:03 <robcresswell> Oh, I didn't know that. Interesting.
12:20:58 <david-lyle> That's it for general.
12:21:25 <amotoki> one request as neutron liaison
12:21:47 <david-lyle> amotoki: yes
12:21:48 <amotoki> could you add a comment on dashbaord for neutron subprojects thread ? http://lists.openstack.org/pipermail/openstack-dev/2015-December/081050.html
12:22:12 <robcresswell> amotoki: I wrote a response, just wanted ot think a bit more before sending. Will do that today.
12:22:14 <david-lyle> amotoki: my apologies, keeps getting overlooked. Yes
12:22:15 <robcresswell> to*
12:22:22 <amotoki> most neutron folks prefers to having dashboard directory in their own repo. I would like to see input from neutorn side.
12:22:36 <amotoki> ...woops from horizon side.
12:22:55 <amotoki> david-lyle: no problem.
12:23:12 <amotoki> i was asked about the status of the thread from some folks.
12:23:28 <amotoki> robcresswell: thanks, great.
12:23:41 <robcresswell> david-lyle: I've gone through the mitaka-priorities etherpad and crossed through some of the merged entries.
12:23:44 <amotoki> I don't want to discuss it here. please reply the thread.
12:24:03 <robcresswell> oops, sorry there amotoki :)
12:24:06 <david-lyle> amotoki: thanks
12:24:35 <amotoki> robcresswell: go ahead :)
12:24:38 <david-lyle> Since there was no agenda items posted, ad hoc agenda 1) Mitaka progress 2) midcycle
12:24:47 <david-lyle> #topic Mitaka priorities
12:25:14 <david-lyle> #link https://etherpad.openstack.org/p/mitaka-horizon-priorities
12:25:24 <david-lyle> ok robcresswell you were saying?
12:25:37 <robcresswell> Just been marking things as done on that list
12:25:56 <robcresswell> We're making fairly good progress on most points.
12:26:23 <robcresswell> The last of the theming docs merged
12:26:38 <robcresswell> and I know the plugin docs are out now too
12:27:08 <robcresswell> doug-fis_ is looking into plugin i18n, we had a good discussion on it a couple days back
12:27:25 <robcresswell> r1chardj0n3s has a new approach to pbr, which he seems to have just added to the etherpad
12:27:46 <r1chardj0n3s> yes, I'd appreciate eyes on the new proposal if you have spare moments https://review.openstack.org/#/c/253296/
12:27:58 <r1chardj0n3s> it's more likely to get up since it doesn't involve changing pbr
12:28:10 <robcresswell> Nice
12:28:14 <r1chardj0n3s> well
12:28:25 <r1chardj0n3s> it does involve changing #infra build nodes tho ;-)
12:28:37 <robcresswell> Other than that, a lot of the angular patches seem to have settled into long chains for review.
12:28:49 <robcresswell> And tsufiev has a war plan for integration tests iirc
12:28:58 <r1chardj0n3s> boy does he!
12:29:10 <r1chardj0n3s> https://etherpad.openstack.org/p/horizon-integration-tests
12:29:27 <robcresswell> We will need to add release notes for m-1 bugs and bps btw. There are several missing.
12:29:54 <tsufiev> robcresswell, a war plan and no soldiers :/
12:29:54 <robcresswell> I'll start nagging people on IRC about that :)
12:30:46 <robcresswell> I think thats most of the update on priorities
12:31:47 <david-lyle> Federation configuration is not on that list but I consider it a high priority as well
12:31:55 * david-lyle must find patch
12:32:00 <robcresswell> Was that lhcheng patch?
12:32:12 <lhcheng> https://review.openstack.org/#/c/244991/
12:32:30 <lhcheng> for Idp mgmt
12:32:40 <mrunge> ah yes
12:33:00 <lhcheng> there are three sets of panels needed to make that usable
12:33:18 <lhcheng> all panels are simple though
12:33:20 <david-lyle> just added
12:33:32 <robcresswell> Nice.
12:33:35 <david-lyle> to the priorities at least, not finished with the review
12:33:41 <lhcheng> planning to implement basic functionality, then add the code from University of Kent for attribute mapping
12:34:06 <lhcheng> we should add the Message of the day too, a lot of operators are asking for it
12:34:19 <tsufiev> lhcheng, does it include the UI they've been proposing (attribute mapping)?
12:34:25 <robcresswell> heh, my university :)
12:34:31 <lhcheng> tsufiev: yep
12:35:07 <lhcheng> I implemented an edit box for the json data for the first pass, then add the attribute mapping UI later.
12:35:31 <r1chardj0n3s> seems reasonable
12:35:54 <robcresswell> FYI I updated the bug report. I'm unsure if its worth updating though. I think it has some value as a reference point, but I don't want to waste time on something that is unused.
12:36:01 <robcresswell> #link https://wiki.openstack.org/wiki/Horizon/WeeklyBugReport
12:36:03 <tsufiev> lhcheng, thanks, got it. I'm interested in reviewing the new UI for it
12:36:21 <lhcheng> I expect the attribute mapping UI will require a couple of iteration, for both code and UX
12:37:37 <david-lyle> robcresswell: thanks. I think it's useful
12:37:48 <r1chardj0n3s> robcresswell: I refer to it, definitely
12:37:53 <david-lyle> wish gerrit was more configurable to honor such things
12:38:07 * david-lyle is not entirely sure how that would work
12:38:31 <amotoki> robcresswell: how does the weekly bug report works?
12:39:01 <robcresswell> amotoki: There's a description on the link :)
12:39:13 <r1chardj0n3s> david-lyle secretly wants to work on gerrit
12:39:29 <david-lyle> r1chardj0n3s: stop right there
12:39:46 <amotoki> robcresswell: i see.
12:39:49 <robcresswell> Its a wiki so anyone is free to add to it. Its just a short list for people to focus on. So if they are new, or short on time, its a quick list to refer to of "things Horizon community want to see merged"
12:40:24 <robcresswell> 1000+ bug list on launchpad doesnt really offer us that. So I just spend a bit of time updating it before each Horizon meeting usually.
12:40:27 <amotoki> on the other hand, we have 234 new bugs with undecided priority. I wonder how we can deal with incoming bugs.
12:40:36 <robcresswell> Oh! So, bug day 2.
12:40:39 <r1chardj0n3s> amotoki: bug day
12:40:42 <r1chardj0n3s> :-)
12:40:49 <robcresswell> I've drafted an email for 12th Jan
12:40:53 <amotoki> yeah, but day works.
12:40:59 <robcresswell> Will send out at a later date
12:41:02 <tsufiev> robcresswell, have you arranged amotoki's question :)?
12:41:20 <robcresswell> tsufiev: ?
12:41:31 <david-lyle> was his question a setup?
12:41:36 <doug-fis_> tsufiev: I thought the same thing
12:41:51 <robcresswell> I'm lost
12:41:52 <tsufiev> yep, it was the perfect timing to promote the bug day :)
12:41:52 <r1chardj0n3s> sadly I will most likely be on vacation on the 12th, but I'll triage some bugs in spirit
12:42:13 <mrunge> I like that spirit
12:42:14 <robcresswell> I tried to make it far enough from Christmas that people could mostly attend, sorry :/
12:42:31 <r1chardj0n3s> well, you Northern Hemisphere folks will be all shut inside anyway so :-)
12:42:40 <robcresswell> the 5th seemed like it may interfere with post-holiday "omg the data center is on fire" issues.
12:42:45 <amotoki> in neutron, we recenlty intorduced weekly bug deputy mechanism. one person per week. he/she watches and triages incoming bug and raise needs-attention bugs.
12:43:07 <r1chardj0n3s> robcresswell: I'll have my own Bug Day to make up for it!
12:43:18 <mrunge> r1chardj0n3s, I'll trust you to triage twice as much bugs for the next bug day after
12:43:24 <robcresswell> amotoki: I think the main issue is the backlog, not the incoming bugs.
12:43:37 <robcresswell> At least in Horizon
12:43:53 <r1chardj0n3s> mrunge: imagine me with that water-drinking bird from the Simpsons over a button that says "invalid" :-)
12:43:56 <amotoki> robcresswell: there are two points. incoming bugs and reducing unhandled bugs.
12:44:04 <robcresswell> And tbh last time we got through something like 20 - 25% of the undecided in a single day
12:44:18 <david-lyle> although last 5 bugs are untriaged and unprioritized
12:44:47 <mrunge> it would be great, if we had a way on force-closing bugs
12:45:38 <amotoki> mrunge: bugs marked  as incomplete and without assignee will be expired by launchpad after some period (60 days?)
12:45:50 <amotoki> https://help.launchpad.net/BugExpiry
12:46:35 <mrunge> amotoki, yes. but imho it would make it cleaner for us if we could expire bugs earlier than waiting 60 days
12:47:29 <robcresswell> Could just mark as Invalid, no?
12:47:33 <robcresswell> Or wont fix
12:47:38 <amotoki> mrunge: hmm... if a bug does not exist already, mark invalid.
12:47:38 <tsufiev> mrunge, we could just filter them out in a bug list
12:47:52 <amotoki> if the bug was fixed already, fix released (?)
12:48:26 <mrunge> the idea was just to get the number of bugs down to a more reasonable number
12:48:33 <david-lyle> ooh https://launchpad.net/horizon/+expirable-bugs
12:48:44 <david-lyle> TIL
12:49:14 <mrunge> aha!
12:50:01 <amotoki> and we are not sure a given bug exists, mark it Incomplete (and it means we request bug authors to reopen it again if necessary)
12:50:48 <david-lyle> #topic Midcycle
12:50:56 <david-lyle> Piet ran a poll
12:51:26 <david-lyle> and Portland or San Antonio/Austin were the top vote getters in that order
12:51:41 <david-lyle> The difficult part is settling on dates
12:52:04 <r1chardj0n3s> just occurred to me: is Portland a weather risk for flying in Febraury?
12:52:26 <david-lyle> we look to drop a couple of cores (that responded) regardless of what date we choose
12:52:47 <ducttape_> portland is more moderate, due to being close to coast r1chardj0n3s
12:53:06 <r1chardj0n3s> ducttape_: ok, cool. want to minimise risk of cancelled flights :-)
12:53:27 <mrunge> I haven't seen a poll at all....
12:53:51 <david-lyle> 10-18 C typically in Feb
12:54:16 <lhcheng> mrunge: I think Piet just dropped the link in the irc room..
12:54:26 <tsufiev> mrunge, http://goo.gl/forms/TVtWP96KjY
12:54:27 <david-lyle> yeah not the best approach
12:54:28 <mrunge> ouch
12:54:42 <neillc> I didn't see it either, but thought that must just be me
12:55:02 <david-lyle> I think you can still add input
12:55:08 <tsufiev> no, there was a mail. It seems that added recipients manually
12:55:17 <tsufiev> should have some kind of alias...
12:55:38 <lhcheng> tsufiev: hmm I didn't get an email, perhaps directly to UX core only?
12:56:24 <tsufiev> lhcheng, perhaps, but I'm not sure
12:56:42 <david-lyle> so the main issue is there is no sweet spot on dates
12:56:58 <mrunge> do we have a result yet?
12:57:01 <tsufiev> maybe if more people vote, London would be more popular :)?
12:57:03 <lhcheng> btw, who's hosting in Portland? :)
12:57:22 <david-lyle> lhcheng: I would be
12:57:57 <david-lyle> the actual campus is 20 minutes outside portland, but it's essentially portland
12:58:38 <lhcheng> cool
12:58:44 <david-lyle> mrunge: I've seen the results
12:58:56 <david-lyle> I can probably cut and paste
12:58:57 <mrunge> david-lyle, ack
12:59:11 <david-lyle> google form that was shared with me
12:59:40 <david-lyle> so I'm trying to work on a firm plan.
12:59:59 <david-lyle> seems like sometime in Feb probably in Portland
13:00:09 <mrunge> david-lyle, I guess, travel logistics have to be figured out, once we have something more official
13:00:11 <david-lyle> unless 12 people vote today
13:00:34 * r1chardj0n3s crossed fingers for not first two weeks of Feb which are a solid no-go for me :-)
13:00:44 <mrunge> yeah
13:00:50 <r1chardj0n3s> I look forward to finding out the eventualy date :-)
13:00:56 <r1chardj0n3s> eventual
13:00:58 <r1chardj0n3s> it's late
13:01:03 <mrunge> there is FOSDEM in Brussels and devconf in Brno
13:01:11 <mrunge> in early Feb
13:01:30 <david-lyle> I have a meeting in Portland unrelated on Feb 16-17 which makes that week difficult for me
13:01:49 <mrunge> so, week after then ;-)
13:02:00 <david-lyle> oh well time. I will continue to try to optimize
13:02:05 <david-lyle> times up
13:02:09 <david-lyle> thanks everyone
13:02:12 <r1chardj0n3s> o/
13:02:13 <david-lyle> #endmeeting