20:00:20 <robcresswell> #startmeeting horizon
20:00:21 <openstack> Meeting started Wed Sep 14 20:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:23 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:25 <openstack> The meeting name has been set to 'horizon'
20:00:39 <r1chardj0n3s> o/
20:00:39 <david-lyle> o/
20:00:42 <bpokorny> o/
20:01:28 <robcresswell> Hey all
20:01:54 <r1chardj0n3s> hi rob!
20:01:55 <robcresswell> SO
20:02:13 <robcresswell> agenda's looking pretty empty, I guess everyone is digging into bps for next cycle and summit stuff ;)
20:02:25 <robcresswell> Reminder about the summit planning
20:02:34 <robcresswell> #link https://etherpad.openstack.org/p/horizon-ocata-summit
20:02:48 <robcresswell> Add session thoughts there
20:03:26 <robcresswell> I don't know how much actual discussion will be needed; but it'll be good to plan out features and who can do what
20:03:50 <david-lyle> with working sessions, we can talk or work on making it happen
20:03:57 <robcresswell> Yup
20:04:27 <robcresswell> I'll be tagging RC1 tomorrow, hoping to squeeze in Glance v2, which still needs reviews please!
20:04:35 <bpokorny> +1 :)
20:05:00 <robcresswell> I've gone over it once and found a couple minor things, but it mostly worked for me. Still, it needs more eyes
20:05:56 <robcresswell> Thats all from me I think, and the agenda is empty today
20:06:01 <robcresswell> #topic Open Discussion
20:06:28 <david-lyle> hmm filtering should get in especially the setting one
20:06:36 <david-lyle> so we don't have to change a setting again
20:06:41 <robcresswell> it has a +2
20:06:52 * david-lyle goes to review
20:06:55 <robcresswell> :)
20:06:57 <david-lyle> well after the meeting
20:07:12 <r1chardj0n3s> https://review.openstack.org/#/c/369648/ is the one you mean?
20:07:19 <david-lyle> r1chardj0n3s: yeah
20:07:20 <robcresswell> thats the one
20:07:36 <david-lyle> still don't like the ADMIN at the beginning of the setting name
20:07:42 <r1chardj0n3s> oh, it was created yesterday, that's why I didn't notice it ;-)
20:07:46 <david-lyle> lcastell: I thought we were removing that?
20:08:07 <david-lyle> updated and better plan thanks to ducttape_
20:08:24 <robcresswell> if we're nitpicking, can we indent the dict in the rst properly too :p
20:09:03 <david-lyle> I just think it could be more generally useful, but will not complain about the setting name again
20:09:33 <robcresswell> david-lyle: I'm not bothered either way, but its a reasonable comment
20:09:36 * david-lyle stop complaining, funny
20:09:51 <robcresswell> We have time to alter it anyway, if others agree
20:09:58 <lcastell_> Sorry  i'm late
20:10:28 <robcresswell> https://review.openstack.org/#/c/324112 would also be a good patch to get merged
20:10:52 <robcresswell> Just because it implements the filter for projects/users, which are potentially problematic anyway
20:11:07 <david-lyle> they would all be nice to get in
20:11:10 <david-lyle> :D
20:11:16 <david-lyle> but I agree
20:11:20 <lcastell_> So remove the admin prefix  then?, I thought leaving it so users know it's only for admin views
20:11:24 <robcresswell> Yes
20:11:29 <david-lyle> lcastell: going to merge as is
20:11:37 <david-lyle> hmmm
20:12:01 * robcresswell can hear the cogs turning
20:12:06 <david-lyle> lcastell: theoretically you could implement it in all the table views
20:12:13 <david-lyle> and turn them on 1 by 1
20:12:17 <lcastell> yeah :P
20:12:26 <lcastell> hehe
20:12:29 <david-lyle> since we have the trigger mech in the patch now
20:12:39 * david-lyle is torn
20:13:00 <david-lyle> let's just move forward with what we have
20:13:15 <lcastell> Ok, I can update it later
20:13:23 <robcresswell> Well
20:13:28 <robcresswell> no, you cant really :p
20:13:32 <david-lyle> lcastell: my main concern is not releasing it and then changing it
20:13:43 <david-lyle> s/not//
20:14:12 <robcresswell> Yeah, we'd end up with a PROJECT_FILTER_FIRST setting
20:14:14 <david-lyle> anyone else have an opinion?
20:14:14 <lcastell> Oh! :(
20:14:30 <robcresswell> you could do filter_first, and then admin_networks, admin_users etc.
20:14:42 <robcresswell> project_users, project_networks etc..
20:14:43 <lcastell> well I can update it fast if necessary
20:15:05 <lcastell> your call guys
20:15:06 <david-lyle> technically it should probably be based on the table class
20:15:14 <robcresswell> I don't think david-lyle will be able to sleep unless we change it
20:15:21 <r1chardj0n3s> heh
20:15:24 <david-lyle> rather than arbitrary
20:15:26 <lcastell> hahaha
20:16:08 <r1chardj0n3s> sorry I had to duck out for a moment; david-lyle your concern is just over s/ADMIN_FILTER_DATA_FIRST/FILTER_DATA_FIRST in that patch?
20:16:16 <david-lyle> yes
20:16:29 <r1chardj0n3s> and then the confusion over turning it on in admin vs. project panels
20:16:33 <robcresswell> and then prefixing the admin versions with admin_ I think
20:16:41 <lcastell> yeah
20:16:46 <david-lyle> especially since some are in the identity dash
20:16:57 <david-lyle> I've convinced myself
20:16:59 <robcresswell> david-lyle: I would just use <dashboard>_<table_name>
20:17:02 <david-lyle> I would like it updated
20:17:08 <david-lyle> not table name?
20:17:13 <david-lyle> err, view name
20:17:15 <robcresswell> as in the class name?
20:17:19 <robcresswell> or the meta name
20:17:28 <robcresswell> view wont work, technically there can be multiple tables.
20:17:30 <david-lyle> don't ask me questions :P
20:17:34 <robcresswell> haha
20:17:37 <lcastell> :P
20:17:40 <r1chardj0n3s> I think it should be <dashboard>.<view name>
20:17:45 <lcastell> ok let's draft another blueprint :P
20:17:55 <robcresswell> view name is nearly always the same as the table name anyway
20:18:00 <david-lyle> ok
20:18:04 <david-lyle> I can live with that
20:18:21 <david-lyle> just thinking python could block some of the potential conflicts for us
20:18:22 <robcresswell> I'm not even sure what we just resolved.
20:18:30 <david-lyle> but we'll rely on people
20:18:33 <robcresswell> oh
20:18:37 <r1chardj0n3s> lcastell: I vote that the blueprint should be blue
20:18:38 <robcresswell> conflicts like what?
20:18:51 <robcresswell> r1chardj0n3s: It should be drafted with invisible ink.
20:18:52 <david-lyle> using the same name agian
20:19:01 <lcastell> lol
20:19:05 <robcresswell> example?
20:19:24 <david-lyle> my plugin goes into the admin dash and implements an images view
20:19:33 <david-lyle> not replaces but complimentary
20:19:42 <david-lyle> I happen to use admin.images
20:19:54 <david-lyle> corner case
20:20:00 <david-lyle> it'll be fine
20:20:26 * robcresswell sits and waits for dave to finish discussing with himself
20:20:27 <david-lyle> too late for that change
20:20:52 <lcastell> so i.e "project.instances" is it OK or not?
20:20:54 <david-lyle> name of setting is good and <dashboard>.<view> string is good enough
20:21:03 <david-lyle> lcastell: yea
20:21:06 <lcastell> ok
20:21:16 <lcastell> and no "ADMIN" prefix
20:21:20 <r1chardj0n3s> yeah
20:21:27 <david-lyle> I don't see the need for ADMIN_
20:21:37 <david-lyle> reduces flexibility
20:21:43 <lcastell> fair enough
20:21:47 <david-lyle> sold
20:21:50 <david-lyle> make it so
20:21:55 <r1chardj0n3s> I'll take two
20:21:57 <lcastell> I'll have something in a couple
20:22:01 <david-lyle> make mine pink
20:22:12 <lcastell> be ready to review ;) haha
20:22:23 <david-lyle> thanks lcastell
20:22:48 <lcastell> np
20:23:10 <robcresswell> Cool, we got there
20:23:40 <robcresswell> So, setting change, glance v2, identity filters please :)
20:23:55 <robcresswell> I've gone over all of them and will be looking again tomorrow morning
20:23:57 <r1chardj0n3s> roger!
20:24:00 <david-lyle> and a quart of milk and a stick of butter
20:24:10 <robcresswell> 0.o
20:24:17 <r1chardj0n3s> "stick" is such a bizarre measurement
20:24:23 <r1chardj0n3s> (not that "quart" isn't also)
20:24:24 <lcastell> lol
20:24:38 <robcresswell> If anyone feels like banging their head against a desk, glance at https://review.openstack.org/#/c/357829/
20:24:43 <david-lyle> don't mind me
20:24:57 <robcresswell> there is a d_o_a patch for dj110 which has had a few reviews from richard
20:25:09 <david-lyle> we really ought to get that in if at all possible and the doa
20:25:20 <david-lyle> but doa is not going to release anyway
20:25:22 <robcresswell> I've been staring at this today and can't figure out why the request data isn't getting populated.
20:25:53 <robcresswell> It may well be a line im missing from the release notes, or a misconfiguration in my change... idk.
20:26:30 <robcresswell> But commenting out a couple of lines makes the dashboard 99% usable, all the actions work, navigation all works, majority of tests pass (all but 3 iirc)
20:26:41 <r1chardj0n3s> 99%? heck, ship it!
20:26:46 <robcresswell> haha
20:26:51 <r1chardj0n3s> this is the web!
20:26:52 <david-lyle> comment out more
20:26:55 <robcresswell> screw tests
20:26:57 <david-lyle> maybe it will all work
20:27:10 <david-lyle> you're just trying to do too much
20:27:41 <robcresswell> *anyway*
20:27:57 <r1chardj0n3s> (yes, I will try to look at that also today)
20:28:02 <robcresswell> \o/
20:28:11 <david-lyle> robcresswell: is tomorrow the deadline?
20:28:33 <robcresswell> david-lyle: For RC1? This week. So yes, tomorrow.
20:28:45 <david-lyle> what day is it?
20:28:51 <robcresswell> If we patch it, we can always tag an RC2.
20:28:56 <robcresswell> Thursday
20:29:01 <r1chardj0n3s> well, it's Thursday here
20:29:03 <david-lyle> features don't go into RC2
20:29:30 <robcresswell> I'm sure we patched dj19 in RC2 last time?
20:29:36 <robcresswell> maybe im imagining that.
20:29:49 * david-lyle will not confirm even if true
20:30:01 * david-lyle does not remember
20:30:24 <robcresswell> Well, lets not plan to do that anyway. If anyone has an observations, feel free to upload a new patch or comment.
20:30:45 <david-lyle> robcresswell: is that the only dj10 blocker?
20:30:53 <r1chardj0n3s> it's the sort of change that could have bizarre side-effects that we really need to notice during rc1 I think
20:31:24 <robcresswell> It could do, but the actual release isn't for another 3 weeks iirc
20:31:37 * robcresswell checks
20:31:38 <r1chardj0n3s> we're rc1'ing early, yes?
20:31:42 <david-lyle> thing is d-o-a release would not make requirements or u-c changes happen, it's just an enabler for distros
20:32:02 <robcresswell> the auto u-c update might catch it
20:32:13 <robcresswell> r1chardj0n3s: No, we're RC-ing on time
20:32:25 <robcresswell> Actual Newton Release is Oct 6
20:32:33 <robcresswell> Final RC date is Sep 29
20:32:41 <r1chardj0n3s> I thought we were doing the week-earlier thing for plugins
20:33:01 <robcresswell> we had FF early
20:33:06 <robcresswell> but not RC
20:33:08 <david-lyle> we need an RC-1 to make sure translations make it
20:33:15 <david-lyle> for RC-2
20:33:17 <r1chardj0n3s> right, yup
20:33:22 <robcresswell> RC1 is hard string freeze.
20:33:46 <r1chardj0n3s> just pulled up the schedule (geez they make it hard to find through google)
20:33:57 <robcresswell> releases.openstack.org :)
20:34:05 <r1chardj0n3s> yes
20:34:48 <david-lyle> look out across the horizon, some day this could all be yours
20:35:02 <david-lyle> don't mind the ugly bits
20:35:04 <robcresswell> david-lyle: To answer your earlier question, yes, I think it should be the last patch
20:35:07 <robcresswell> for dj110
20:35:13 <david-lyle> robcresswell: ok
20:35:56 <david-lyle> I wonder about a weasely release note then
20:36:11 <david-lyle> should d-o-a ever support dj10, horizon will too
20:36:34 <david-lyle> something to really stoke confidence
20:36:38 <robcresswell> Isn't doa on independent release anyway?
20:37:04 * david-lyle looks at requirements
20:37:05 <robcresswell> Huh, no it isnt.
20:37:13 <robcresswell> - release:cycle-with-intermediary
20:37:30 <david-lyle> robcresswell: we can release it whenever
20:37:42 <david-lyle> it's updating the requirements I wonder about
20:38:21 <david-lyle> robcresswell:  as long as we don't break backwards compatibility
20:38:38 <robcresswell> https://review.openstack.org/#/c/353350/
20:38:42 <robcresswell> thats the patch in question
20:38:46 <david-lyle> but adding dj10 seems like more than a minor bug fix
20:38:52 <robcresswell> its 1.10 specific, all conditional.
20:39:46 <david-lyle> I suppose it's the last bit of it
20:39:56 <david-lyle> a strong maybe for bug fix
20:40:48 <robcresswell> The other alternative is just to point packagers at specific patches
20:41:55 <david-lyle> yup
20:42:07 <david-lyle> well let's make sure it's working and then we can figure out the release path
20:42:13 <robcresswell> agreed
20:43:46 <robcresswell> Anything else?
20:44:15 <r1chardj0n3s> (sorry, ADSL dropped out for a bit there)
20:44:38 <robcresswell> ADSL
20:44:43 <robcresswell> -.-
20:44:48 <r1chardj0n3s> I think the DOA patch should be able to go in today
20:44:56 <r1chardj0n3s> I just need to test it properly
20:45:09 <r1chardj0n3s> and the convince another sucker^H^H^H^H^Hcore to review it ;-)
20:45:13 <robcresswell> I thought Australia had a great broadband network? They always talk about it
20:45:20 <david-lyle> haha
20:45:37 <r1chardj0n3s> it does get talked about a lot, yes
20:45:49 <robcresswell> :p
20:46:09 <robcresswell> r1chardj0n3s: Testing would be good
20:46:22 <robcresswell> Even better if the testing was before the +2 :D
20:46:25 <r1chardj0n3s> robcresswell: it's a thing the kids do these days
20:46:33 <r1chardj0n3s> :-P
20:46:33 <robcresswell> beggars cant be choosers though
20:47:47 <robcresswell> I think we're about done here :)
20:47:59 <r1chardj0n3s> +a
20:48:03 <robcresswell> Thanks everyone!
20:48:07 <robcresswell> #endmeeting