[openstack-dev] [horizon] [horizon-plugin] Raising Django version cap
adriant at catalyst.net.nz
Mon Jul 17 08:12:03 UTC 2017
Was hoping to play with this much sooner, but here is a quick hack for
horizon working with django 1.11
The main issues are with widgets from Django which are no longer there,
and all I've done is move them to our repo from django 1.10's code. This
is probably not a good long term solution.
Then django-babel doesn't yet have a version that has django 1.11
support, although the change has been merged to master. Just needs a new
release. For now a install from source works to test.
And... because it was easier, I did this off the patch that brings
openstack_auth into horizon. Because of some import order changes in
django (I assume), there was an issue due to an import that caused a
call to get_user_model before openstack_auth was fully loaded.
Beyond that, it all 'appears' to work. I launched some instances,
created some networks, changed my password, managed some projects and
users. There is tons to actually test, but mostly it just seems to work.
On 05/07/17 22:24, Rob Cresswell (rcresswe) wrote:
> If you want to install Django 1.11 and test it, that would be very
> helpful, even if its just to open bugs. I’m in the process of adding a
> non-voting job for 1.11 right now, so we should be able to move quickly.
>> On 5 Jul 2017, at 01:36, Adrian Turjak <adriant at catalyst.net.nz
>> <mailto:adriant at catalyst.net.nz>> wrote:
>> Great work!
>> Is there anything that can be done to help meet that July deadline
>> and get 1.11.x in? I'm more than happy to help with reviews or even
>> fixes for newer Django in Horizon, and we should try and get others
>> involved if it will help as I think this is a little urgent.
>> Running anything less than Django 1.11 leaves us in a weird spot
>> because of the point where support ends for any versions below it.
>> Looking at the release timelines, if we don't get 1.11 in for Pike,
>> we'll have released a version of Horizon that will be for an
>> unsupported version of Django in about 6 months time (8 if deployers
>> stick with django 1.8):
>> It isn't as bad it could be, but it's an awkward situation to be in.
>> 1.9 is no longer supported, 1.10 support stops at 2018, so
>> realistically 1.8 is the only version to have Pike 'safe' until
>> Queens thats not particularly great either. Getting 1.11 support in
>> would be ideal.
>> On 05/07/17 03:01, Rob Cresswell wrote:
>>> Hi everyone,
>>> I've put up a patch to global-requirements to raise the Django cap
>>> to "<1.11", with the upper-constraint at "1.10.7"
>>> (https://review.openstack.org/#/c/480215). Depending on the
>>> remaining time, I'd quite like to move us to "1.11.x" before
>>> Requirements Freeze, which will fall around the 27th of July.
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org
>> <mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev