<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Was hoping to play with this much sooner, but here is a quick
      hack for horizon working with django 1.11</p>
    <p><a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/484277/">https://review.openstack.org/#/c/484277/</a></p>
    <p>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.</p>
    <p>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.<br>
    </p>
    <p>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.<br>
    </p>
    <p>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.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 05/07/17 22:24, Rob Cresswell
      (rcresswe) wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:FE7B34B6-CEBB-44BE-94BC-87B884C72361@cisco.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      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.
      <div class=""><br class="">
      </div>
      <div class="">Rob</div>
      <div class=""><br class="">
        <div>
          <blockquote type="cite" class="">
            <div class="">On 5 Jul 2017, at 01:36, Adrian Turjak <<a
                href="mailto:adriant@catalyst.net.nz" class=""
                moz-do-not-send="true">adriant@catalyst.net.nz</a>>
              wrote:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <div text="#000000" bgcolor="#FFFFFF" class="">Great work!<br
                  class="">
                <br class="">
                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.<br
                  class="">
                <br class="">
                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.<br class="">
                <br class="">
                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):<br class="">
                <a class="moz-txt-link-freetext"
                  href="https://releases.openstack.org/pike/schedule.html"
                  moz-do-not-send="true">https://releases.openstack.org/pike/schedule.html</a><br
                  class="">
                <a class="moz-txt-link-freetext"
                  href="https://www.djangoproject.com/download/"
                  moz-do-not-send="true">https://www.djangoproject.com/download/</a><br
                  class="">
                <br class="">
                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.<br class="">
                <br class="">
                <br class="">
                <div class="moz-cite-prefix">On 05/07/17 03:01, Rob
                  Cresswell wrote:<br class="">
                </div>
                <blockquote type="cite"
cite="mid:HE1P195MB0009F2A00A5B0FEF3819A42E88D70@HE1P195MB0009.EURP195.PROD.OUTLOOK.COM"
                  class="">
                  <div dir="ltr" class="">Hi everyone,
                    <div class=""><br class="">
                    </div>
                    <div class="">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"
                      (<a href="https://review.openstack.org/#/c/480215"
                        moz-do-not-send="true" class="">https://review.openstack.org/#/c/480215</a>).
                      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.</div>
                    <div class=""><br class="">
                    </div>
                    <div class="">Rob</div>
                  </div>
                  <br class="">
                  <fieldset class="mimeAttachmentHeader"></fieldset>
                  <br class="">
                  <pre class="" wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" moz-do-not-send="true">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
                </blockquote>
                <br class="">
              </div>
__________________________________________________________________________<br
                class="">
              OpenStack Development Mailing List (not for usage
              questions)<br class="">
              Unsubscribe: <a
                href="mailto:OpenStack-dev-request@lists.openstack.org"
                class="" moz-do-not-send="true">
                OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br
                class="">
              <a
                href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                class="" moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br
                class="">
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>