20:00:09 <ying_zuo> #startmeeting horizon
20:00:10 <openstack> Meeting started Wed Dec  6 20:00:09 2017 UTC and is due to finish in 60 minutes.  The chair is ying_zuo. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:13 <openstack> The meeting name has been set to 'horizon'
20:00:17 <ying_zuo> Hi everyone o/
20:00:20 <e0ne> hi
20:01:25 <ying_zuo> #topic Queens-2 Milestone Release
20:01:31 <ying_zuo> #link https://review.openstack.org/#/c/525880/
20:01:45 <ying_zuo> It will be available in GitHub when this patch is merged
20:02:06 <ying_zuo> #link https://launchpad.net/horizon/+milestone/queens-2
20:02:29 <ying_zuo> Thanks everyone’s contribution to this milestone!
20:02:47 <e0ne> we've got about 1.5 months before feature freeze
20:03:29 <ying_zuo> #link https://releases.openstack.org/queens/schedule.html
20:03:45 <e0ne> about one month if we exclude holodays
20:03:53 <e0ne> s/holodays/holidays
20:03:55 <ying_zuo> until the week of Jan 22
20:04:08 <ying_zuo> yes
20:04:28 <cshen_> how long is each milestone?
20:04:50 <ying_zuo> let's focus on the reviews for the blueprints during Queens-3
20:05:25 <e0ne> cshen_: about 1.5 month in this cycle
20:05:49 <cshen_> I see, thx
20:06:12 <ying_zuo> #topic PTG
20:06:18 <ying_zuo> #link https://www.openstack.org/ptg/
20:06:23 <ying_zuo> The next PTG will take place on 2/26 - 3/2 in Dublin, Ireland
20:06:34 <ying_zuo> I requested two days for the Horizon team meeting
20:06:39 <ying_zuo> same as last time
20:07:04 <e0ne> sounds good
20:07:17 <e0ne> I hope, I'll attend this PTG too
20:08:31 <ying_zuo> cool. that will be great
20:08:49 <ying_zuo> #topic Publishing server projects to PyPI (amotoki)
20:08:59 <ying_zuo> #link http://lists.openstack.org/pipermail/openstack-dev/2017-November/thread.html#124676
20:09:23 <ying_zuo> Some notes from amotoki: horizon (and neutron) causes a tricky situation around unit testing. Someone needs to be aware of the direction. tox_install.sh is a really workaround. In the past, we explored horizon-lib but somehow it failed (thought I don't know the exact reason).
20:10:06 <ying_zuo> #topic Open Discussion
20:10:36 <ying_zuo> someone left a question on the meeting note for bumping Django minimum version to >=1.11 in Queens
20:10:56 <ying_zuo> the version is set by the global requirements project
20:11:10 <e0ne> I think, it was amotoki
20:11:19 <ying_zuo> #link https://github.com/openstack/requirements/blob/master/global-requirements.txt
20:11:52 <e0ne> to bump django to 1.11 we need to drop support of 1.8 and maybe 1.9
20:11:53 <ying_zuo> it's still 1.8 at the moment
20:12:05 <e0ne> 1.8 is not supported for a while
20:12:22 <e0ne> 1.11 is LTS, so it will have security updates
20:12:44 <e0ne> #link https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
20:13:20 <e0ne> we're going to switch to 1.11 in our distro with pike
20:13:29 <cshen_> 1.8 is also a LTS version.
20:13:37 <cshen_> support till at least April 2018
20:13:51 <e0ne> cshen_: it's not supported anymore
20:14:07 <cshen_> #link https://www.djangoproject.com/download/
20:14:11 <e0ne> cshen_: hm.. do you have any link with this date
20:14:13 <e0ne> ?
20:14:18 <cshen_> I just found the date there.
20:14:32 <e0ne> thanks
20:14:39 <e0ne> so, we've got time until april
20:14:48 <cshen_> 1.9 and 1.10 are dead for sure.
20:15:11 <e0ne> my vote is to drop everything older than 1.11
20:15:41 <e0ne> we must do it in Queens or Rocky for sure
20:15:47 <cshen_> +1
20:16:53 <ying_zuo> I will check with the global requirements project
20:16:59 <e0ne> once we drop <1.11 we would be able to start adoption for 2.0+
20:17:22 <e0ne> ying_zuo: https://github.com/openstack/requirements/blob/master/global-requirements.txt#L36
20:17:42 <e0ne> ying_zuo: it looks safe to support 1.11+ only
20:17:54 <e0ne> ying_zuo: we tested it for a while
20:18:29 <ying_zuo> I think that will be a better place to bump up the version
20:18:36 <e0ne> if we don't switch to 1.11+, we'll have new release (Queens) with outdated django :(
20:18:51 <e0ne> TBH, it will be up to vendors to update django or noe
20:19:31 <ying_zuo> sure
20:20:07 <e0ne> it could affect plugins too
20:21:09 <e0ne> I don't know if any other projects except horizon and plugins use django too
20:21:31 <ying_zuo> I would think most of them do
20:22:20 <e0ne> http://codesearch.openstack.org/ doesn't help a lot: plugins and some old projects have django in requirements
20:22:20 <ying_zuo> I think that would fine
20:22:32 <ying_zuo> are there any other questions?
20:22:55 <cshen_> how to put my patch on hold? #link https://review.openstack.org/#/c/518104/
20:23:03 <cshen_> just leave it there, not doing anything?
20:24:04 <ying_zuo> just leaving there for now
20:24:04 <e0ne> cshen_: add WIP status
20:24:21 <ying_zuo> we have two approaches
20:24:29 <ying_zuo> just want to see what people think
20:24:47 <cshen_> e0ne: where to add WIP status?
20:24:50 <ying_zuo> if one of them get merged, the other one can be abandoned
20:25:08 <ying_zuo> it's not really WIP per se
20:25:25 <ying_zuo> you can add WIP to first line of the commit message
20:25:28 <e0ne> cshen_: reply -> workflow -> -1
20:25:50 <ying_zuo> I don't think that's the case here
20:27:01 <cshen_> ying_zuo: I felt the other patch is better. so I'm fine with it.
20:28:35 <ying_zuo> the other one seems more favorable at the moment
20:28:50 <cshen_> true
20:30:09 <cshen_> the other question is regarding the concurrently fetching data proposed by e0ne
20:30:21 <cshen_> I had a look at blueprint.
20:30:26 <e0ne> oh.. it's a hard question
20:30:54 <e0ne> we agreed with robcresswell earlier today that I'll do some more testing no multinode env with more instances
20:31:07 <cshen_> I mean how can I contribute to it? If I have interest.
20:31:49 <e0ne> cshen_: any kind of contributions (reviews, testing, proposing your ideas) are welcome
20:32:11 <cshen_> sure, how big will be your multinode setup?
20:33:28 <e0ne> I've got only 1 controller+ 2 computes now
20:33:46 <e0ne> not a really big scale, but it's better than was my devstack vm
20:34:06 <cshen_> I see, looking forward to your new test result.
20:34:25 <cshen_> because I'm also interested in concurrency in Python.
20:34:42 <e0ne> do you have any suggestion to my proposal?
20:35:18 <cshen_> To be host, not really, I'm also quite new to horizon project and also Futurist lib
20:35:29 <cshen_> it sounds promising.
20:36:59 <ying_zuo> the whiteboard section on the blueprint is for discussion
20:37:35 <ying_zuo> but yes, please work with e0ne if you are interested
20:37:41 <e0ne> we can do it in the mailing list too to get more attention
20:37:41 <cshen_> Sure.
20:38:06 <e0ne> I'll send a mail once I'll have new information about it
20:38:33 <ying_zuo> thanks
20:39:38 <ying_zuo> I think that's it for today's meeting
20:39:55 <ying_zuo> thanks for joining :)
20:40:03 <cshen_> thx, have a nice day!
20:40:06 <ying_zuo> #endmeeting