20:00:37 <r1chardj0n3s> #startmeeting horizon
20:00:37 <openstack> Meeting started Wed Jan 11 20:00:37 2017 UTC and is due to finish in 60 minutes.  The chair is r1chardj0n3s. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:38 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:41 <openstack> The meeting name has been set to 'horizon'
20:00:44 <r1chardj0n3s> good morning :-)
20:00:53 <viks> good morning
20:01:10 <david-lyle> o/
20:01:16 <rdopiera> o/
20:01:22 <rhagarty> o/
20:01:48 <ankur-gupta-f> \o/
20:02:01 <r1chardj0n3s> thanks folks for coming along, I'll get through some procedural stuff first
20:02:09 <r1chardj0n3s> #topic Ocata Feature Freeze next week
20:02:22 <r1chardj0n3s> #link https://releases.openstack.org/ocata/schedule.html
20:02:28 <TravT> o/
20:02:29 <betherly> o/
20:02:29 <r1chardj0n3s> As per the Ocala schedule, we will be going into feature freeze next week. We freeze a week before other projects to give plugin authors a chance to respond to changes in our release.
20:02:45 <r1chardj0n3s> Once Ocata-3 has been tagged, we will only be accepting release-critical bug fix patches unless you receive a feature freeze exception (FFE). We will also try to reduce the amount of string changes to give the translation team time to complete translation.
20:03:03 <TravT> yeah, we just made some adjustments to the searchlight-ui plugin
20:03:40 <betherly> r1chardj0n3s: I'm currently working on the qos panel. Will that be under the feature freeze or under the same leeway as the plugins?
20:03:56 <r1chardj0n3s> betherly: plugins still freeze a week later
20:04:39 <betherly> r1chardj0n3s: yep. Just checking when the hard deadline is for it to try and get in. Not sure it will make this release either way though tbh...
20:05:11 <r1chardj0n3s> and the qos panel isn't under the Horizon project, so I have no control over FFE there :-)
20:05:30 <tsufiev> o/
20:05:45 <deshipu> r1chardj0n3s: I thought it's in the horizon repo?
20:07:24 * deshipu <-- rdopiera, sorry, my work server just went down
20:08:11 <r1chardj0n3s> oh, it's a new panel in Horizon? right, sorry for my confusion
20:08:27 <r1chardj0n3s> so yeah, that freezes with the rest of Horizon
20:08:41 <ankur-gupta-f> r1chardj0n3s: would the lbaas-dash fall under the restriction?
20:08:58 <david-lyle> because it effects plugins?
20:09:12 <david-lyle> :-D
20:10:07 <r1chardj0n3s> ankur-gupta-f: plugins still go into feature freeze at the time of the rest of OpenStack, a week after Horizon does
20:10:15 <ankur-gupta-f> okay thanks
20:11:02 <betherly> r1chardj0n3s: thanks :)
20:11:06 <r1chardj0n3s> Review rate is still very low, but if you are reviewing then I'll remind you that the priorities for this release are:
20:11:07 <r1chardj0n3s> #link https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open
20:11:27 <r1chardj0n3s> please consider focusing your efforts there, thanks :-)
20:12:15 <david-lyle> let's add K2K support?
20:12:57 <r1chardj0n3s> david-lyle: the DOA patch https://review.openstack.org/#/c/415521/ ?
20:13:13 <r1chardj0n3s> oh, and the rest
20:13:30 <david-lyle> https://review.openstack.org/408450
20:13:44 <david-lyle> is the horizon piece
20:14:09 <r1chardj0n3s> yup, so I see four patches related to that bp
20:14:10 <david-lyle> I'm about ready to push the refactor, then tackle reviewing the d-o-a side
20:14:22 <david-lyle> we'll need to release d-o-a
20:14:22 <r1chardj0n3s> er, three
20:14:24 <r1chardj0n3s> I can't count
20:14:30 <david-lyle> and do the requirements dance
20:14:41 <r1chardj0n3s> that's gonna end up in FFE land :-)
20:14:53 <r1chardj0n3s> but I think it's justifiable with minimal plugin impact
20:15:23 <r1chardj0n3s> I've added the three patches to the priority list
20:15:46 <r1chardj0n3s> which shall be known as the list that grows, and never shrinks :-P
20:15:46 <david-lyle> if that breaks a plugin, someone is doing something wrong :)
20:16:14 <r1chardj0n3s> It's a good thing that people never do anything wrong :P
20:16:35 <r1chardj0n3s> ok, moving on
20:16:36 <r1chardj0n3s> #topic Pike PTG planning
20:16:43 <r1chardj0n3s> #link https://etherpad.openstack.org/p/horizon-ptg-pike
20:17:31 <r1chardj0n3s> I've put together a start at an etherpad. If you're going to the PTG, which is just over a month away now, then please add topics of discussion to that etherpad. It'd be handy to know who's actually going too.
20:17:45 <r1chardj0n3s> I don't have confirmation of attendance at this time.
20:18:16 <david-lyle> r1chardj0n3s: I just added that to https://wiki.openstack.org/wiki/PTG/Pike/Etherpads
20:18:29 <r1chardj0n3s> thanks david-lyle
20:19:17 <david-lyle> where do you want attendance info?
20:19:24 <david-lyle> here or etherpad?
20:19:42 <r1chardj0n3s> the etherpad would be more convenient I reckon
20:20:17 <david-lyle> I added the folks I know of
20:20:24 <r1chardj0n3s> cheers
20:20:46 <r1chardj0n3s> #topic BP: Snapshot listing per volume
20:20:49 <r1chardj0n3s> #link https://blueprints.launchpad.net/horizon/+spec/snapshot-listing-per-volume
20:20:53 <viks> hi
20:20:57 <r1chardj0n3s> hai
20:21:09 <viks> I have put up the BP
20:21:18 <r1chardj0n3s> I've added a comment to the BP whiteboard, you might not have seen it yet
20:21:32 <viks> ok
20:22:03 <viks> I will update the blue print
20:22:22 <viks> but in case of systems which have large number of volume snapshts
20:22:30 <david-lyle> you could even provide a link from volumes to the filtered view
20:22:43 <r1chardj0n3s> that was my thought
20:22:50 <viks> it becomes very difficult
20:23:17 <viks> ok
20:23:31 <viks> but having a page makes it upfront usable
20:23:55 <david-lyle> is this a view off the volume itself?
20:23:59 <viks> aslo we have scheduled snapshots
20:24:02 <david-lyle> like in the volume details?
20:24:25 <viks> so it becomes very difficult to locate snapshots becase names are real long string
20:24:39 <viks> so volume based page helps
20:24:50 <viks> yes
20:24:55 <viks> yes david
20:25:07 <david-lyle> so a tab on the volume details page
20:25:09 <viks> it is another tab next to volume details/overview
20:25:21 <david-lyle> I could see that
20:25:28 <r1chardj0n3s> yeah, that makes sense
20:26:09 <viks> so IMO I can implment it the older way first
20:26:19 <viks> then I can try for complete angular way
20:26:53 <viks> I thin I can do it for Ocata...
20:27:19 <r1chardj0n3s> we only have 1 week to get Ocata patches in, there's no way it'll get reviewed in time I'm afraid
20:27:38 <ediardo> :(
20:28:01 <viks> Let me try non angular way of tabtable in this release
20:28:07 <r1chardj0n3s> ok
20:28:09 <viks> I will put up angular in next release
20:28:12 <r1chardj0n3s> yup
20:28:15 <viks> I think I can get it in :)
20:28:25 <r1chardj0n3s> the non-angular approach should be less work
20:28:46 <viks> yes richard
20:29:57 <viks> should I start the omplentation
20:29:59 <r1chardj0n3s> with some small changes to the BP for clarity I think it's worth having, so I'll approve it
20:30:10 <viks> i guess I will need approval for check-in and reviews
20:30:21 <viks> gr8
20:30:26 <viks> :)
20:30:37 <viks> I will update the BP
20:30:44 <viks> and start putting up the code asap
20:31:14 <r1chardj0n3s> #topic Open Discussion
20:31:23 <r1chardj0n3s> does anyone have anything else they'd like to bring up?
20:31:30 <deshipu> I do
20:31:38 <r1chardj0n3s> go for it :-)
20:31:51 <jlopezgu> r1chardj0n3s: I'll update the keystone patches this week, sorry I've been busy with another project
20:31:56 <deshipu> I have a patch up that fixes the VersionManager to make it possible to distinguish between version 4.2 and version 4.20
20:32:09 <r1chardj0n3s> jlopezgu: +1
20:32:43 <deshipu> I just realized that without this patch the simple-tenant-pagination patch will be impossible to use, because the pagination only works with nova api versions above 4.20
20:32:53 <r1chardj0n3s> I see rdopiera's patch https://review.openstack.org/#/c/410688/ ?
20:32:57 <TravT> r1chardj0n3s question on the tox usage with plugins.
20:33:01 <deshipu> and we currently can't configure Horizon to use that version
20:33:18 <r1chardj0n3s> deshipu: is that the patch you're referring to?
20:33:32 <deshipu> r1chardj0n3s: thank you, sorry, I'm on my private laptop
20:33:34 <deshipu> r1chardj0n3s: yes
20:34:13 <deshipu> the issue is that we are using floats for the versions
20:34:15 <david-lyle> r1chardj0n3s: deshipu = rdoperia
20:34:16 <r1chardj0n3s> right, I had reviewed that and need to follow up on rdopiera's revision, yep
20:34:22 <deshipu> and 4.2 and 4.20 are the same floats
20:34:23 <r1chardj0n3s> whaaaaa???
20:34:27 <r1chardj0n3s> that's crazy!!
20:34:57 <r1chardj0n3s> right, now that rdopiera==deshipu things make more sense :-D
20:35:03 <david-lyle> haha
20:35:12 <deshipu> the way I did it in this patch, I'm making a magical Version object that behaves like floats, but hase semantic_version inside
20:35:16 <r1chardj0n3s> the patch itself made sense, I just had that issue with reimplementing semantic_version
20:35:24 <deshipu> this way I don't have modify all the code in Horizon
20:35:26 <r1chardj0n3s> now that's fixed, it should be fine
20:35:34 <r1chardj0n3s> I'll review it today
20:35:45 <deshipu> however, I wonder if it would be cleaner in the long term to actually modify all the code in Horizon to use semantic_version directly
20:35:57 <deshipu> but that is a considerably higher risk change
20:36:32 <deshipu> we probably don't want it just before a freeze?
20:36:32 <r1chardj0n3s> yeah
20:36:36 <david-lyle> microversions just keep on giving
20:36:56 <deshipu> this is not caused by microversions directly
20:37:03 <r1chardj0n3s> deshipu: if it turns out to be broken or just plain bad we have enough time to fix/remove it
20:37:04 <deshipu> we would hit that as soon as we reach 4.10
20:37:36 <deshipu> which is feasible without microversions
20:37:40 * david-lyle has to look closer
20:39:48 <r1chardj0n3s> OK, one last thing: I'm at a conference next week. I'll still be around but won't be able to run the weekly meeting. Rob has said he'll be able to run it though, so yay Rob!!
20:40:08 <deshipu> enjoy the trip
20:40:19 * david-lyle is jealous
20:40:26 <viks> one more thing from my side...https://review.openstack.org/#/c/372150/
20:40:29 <jlopezgu> hahaaha
20:40:40 <viks> i dont know if this is the correct forum
20:40:43 <jlopezgu> why jelous david-lyle if you're coming to SA next week?
20:40:45 <viks> but we can close this
20:40:49 <TravT> r1chardj0n3s: where is the conference?
20:41:06 <david-lyle> Tazmania vs San Antonio, I'm not sure jlopezgu
20:41:06 <jlopezgu> jealous*
20:41:15 <david-lyle> ;)
20:41:17 <jlopezgu> hahahahaha
20:41:24 <r1chardj0n3s> TravT: is in Hobart, which will be 10ºC cooler than Melbourne (we're due for ~40ºC over a couple of days)
20:41:48 <deshipu> viks: it looks like it's already abandoned?
20:41:49 <jlopezgu> It should be cool to visit Tazmania
20:41:55 <TravT> sounds like fun!
20:41:59 <clu_> O_O
20:42:02 <jlopezgu> you should also come soon r1chardj0n3s
20:42:11 <viks> i mean let us close the big...it still shows in progress
20:42:37 <viks> bug*
20:42:43 <r1chardj0n3s> viks: I just looked, that patch is superseded by https://review.openstack.org/#/c/335020/ which is merged, yes?
20:42:53 <r1chardj0n3s> ahhhh
20:42:58 <r1chardj0n3s> I understand, sorry viks
20:43:09 <r1chardj0n3s> the replacement patch didn't reference the bug :/
20:43:32 <r1chardj0n3s> since the bug was a wishlist item, we can just close it
20:44:00 <viks> ok
20:44:03 <viks> thanks
20:44:07 <r1chardj0n3s> thx david-lyle
20:44:11 <david-lyle> np
20:45:08 <r1chardj0n3s> also
20:45:11 <r1chardj0n3s> "Tazmania"
20:45:15 <r1chardj0n3s> really, david-lyle? :-P
20:45:31 <david-lyle> what can't I spell
20:45:52 <david-lyle> In 'merica we like 'z's
20:45:59 <r1chardj0n3s> you do like your zeees
20:46:09 <david-lyle> just sprinkle liberally
20:46:24 <clu_> zavid-zyle
20:46:30 <david-lyle> exacltly
20:46:31 <jlopezgu> LOL
20:46:34 <r1chardj0n3s> omg a wild clu_ appears!
20:46:42 <r1chardj0n3s> #endmeeting