15:02:38 <e0ne> #startmeeting horizon
15:02:38 <openstack> Meeting started Wed Jun 20 15:02:38 2018 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:39 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:02:42 <openstack> The meeting name has been set to 'horizon'
15:03:13 <e0ne> hi Team
15:03:17 <betherly> o/
15:03:34 <vladiskuz> hi
15:03:46 <e0ne> let's wait few minutes more until more people join us
15:04:58 <e0ne> #link https://wiki.openstack.org/wiki/Meetings/Horizon
15:05:51 <e0ne> our agenda contains release priorities, so feel free to add anything to open discussion section
15:06:30 <e0ne> there are no updates from me, so let's skip Notices topic
15:06:43 <e0ne> #topic mox => mock migration
15:07:15 <e0ne> #link https://etherpad.openstack.org/p/horizon-unittest-mock-migration - here is our current progress
15:07:40 <e0ne> I'll propose a patch for openstack_auth later this week
15:08:07 <e0ne> we can still meet this community goal in Rocky :)
15:08:57 <e0ne> #topic horizon release model
15:08:59 <dklyle> o/
15:09:15 <e0ne> dklyle: welcome, David:)
15:09:22 <e0ne> #link http://lists.openstack.org/pipermail/openstack-dev/2018-June/131458.html
15:09:52 <e0ne> it would be good to have more feedback on this ^^ mailing thread to discuss it later or at PTG
15:10:24 <e0ne> it's very important topic for plugins and horizon itsef
15:10:55 <e0ne> there are two proposals at the moment:
15:11:03 <e0ne> 1) introduce horizon lib
15:11:10 <e0ne> 2) release Horizon using the cycle-with-intermediar
15:11:58 <e0ne> I'll create an etherpad with pros and cons for both options and will send it to the mailing list
15:12:21 <e0ne> that's all from me
15:12:32 <e0ne> dklyle: do you have any inputs on this?
15:13:10 <dklyle> changing release cycle is much lighter weight
15:13:31 <dklyle> also are we expecting plugins to used without horizon?
15:13:55 <dklyle> creating a particial dependency rather than full may not make sense if not
15:14:49 <e0ne> dklyle: AFAIK, plugins are not used without horizon
15:15:42 <e0ne> that's a good point
15:16:19 <e0ne> I'm afraid that without good amount of active contributors, we'll have less releases and new features with new cycle
15:17:17 <dklyle> then sadly, the problem becomes less pressing
15:18:51 <e0ne> anyway, I don't expect any decision sooner than PTG
15:19:37 <e0ne> I'll support any decision which will help us with current issues and community will be OK with it
15:20:37 <e0ne> new release model will help us deliver new feature after openstack components will be released
15:21:14 <e0ne> but I don't know how vendors support projects with  cycle-with-intermediar release model in their distos
15:21:32 <dklyle> that's a good point too
15:21:58 <dklyle> I think that prevented us from changing in the past
15:22:44 <e0ne> rdopiera, betherly: it would be good have inputs from RedHat
15:23:45 <betherly> e0ne: apologies my input has been sporadic lately! got some time at the moment to fix up some patches and get things going again
15:24:45 <e0ne> betherly: np. I just ping you because you've tot own distro and new release model could affect you
15:25:48 <betherly> e0ne: ye i need to look into how it works practically
15:26:18 <e0ne> betherly: it would be awesome
15:27:08 <e0ne> it seems that we've done with this topic
15:27:31 <e0ne> #topic Improve Horizon Testing
15:27:43 <e0ne> nothing new from the last week
15:28:34 <e0ne> I'm testing this patch
15:28:35 <e0ne> #link https://review.openstack.org/#/c/575538/
15:28:46 <e0ne> it'a fix of some our integration tests
15:29:12 <betherly> ooo awesome
15:29:17 * e0ne forgot to publish patch with experimental integration job to gerrit :(
15:29:24 <betherly> ill take a look too
15:29:31 <e0ne> betherly: thanks!
15:29:47 <betherly> whats the best way to test that patch?
15:30:05 <e0ne> I discussed this topic at the Summit and found several volunteers to fix tests
15:30:20 <e0ne> betherly: I just use 'tox -e py27integration' to run them
15:30:43 <e0ne> some of them failed on my env now
15:30:59 <e0ne> I'm trying to figure out why it happens
15:31:11 <betherly> e0ne: perfect thanks! will do that
15:31:19 <e0ne> cool
15:32:08 <e0ne> #topic Django 2 support
15:32:18 <e0ne> nothing new since last week
15:32:31 <e0ne> #link current status: https://etherpad.openstack.org/p/django20-support
15:32:39 <e0ne> it looks pretty good
15:32:56 <e0ne> only few plugins don't support django2 now
15:33:03 <e0ne> some of them are not maintained :(
15:33:28 <betherly> e0ne: is that something we should discuss more at PTG too re what to do with those?
15:33:47 <e0ne> betherly: are you talking about django2?
15:33:51 <betherly> we dont have enough developers to improve horizon features quickly let alone plugins
15:34:01 <betherly> e0ne: im talking about un-maintained plugins
15:34:35 <e0ne> betherly: we just help plugin teams with fixing
15:34:45 <e0ne> to not beak them with new horizon
15:35:19 <betherly> e0ne: ye absolutely. my question is are we going to maintain un-maintained plugins ourselves?
15:35:30 <e0ne> betherly: I don't think so
15:35:40 <betherly> if so what is our plan for doing so and working through them
15:35:44 <e0ne> we've got a very limited capacity
15:35:44 <betherly> if not do we remove them?
15:36:15 <betherly> we dont want to lose functionality but equally if they are not fixed or maintained and then break, that looks worse than not having the functionality at all
15:36:25 <e0ne> my idea is to have some CI job to verify that plugin works with current horizon
15:36:38 <e0ne> betherly: +1
15:36:47 <betherly> e0ne: good idea
15:37:09 <e0ne> that's why I removed nose almost from all plugins
15:37:52 <e0ne> amotoki also helps with plugins to migrate from mox and support django2
15:39:39 <e0ne> betherly: I'll note somewhere to not forget to add this topic to the PTG agenda
15:40:05 <e0ne> #topic Open Discussion
15:40:41 <e0ne> technically, we started open discussion few minutes ago and there is nothing more in the agenda
15:42:46 <e0ne> does anybody want to discuss anything?
15:44:36 <e0ne> looks like we've done for today
15:44:51 <e0ne> thanks everybody for the participation
15:44:58 <e0ne> see you next week!
15:45:06 <e0ne> #endmeeting