<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Thank you Dolph.<br>
    <br>
    Best regards,<br>
      Alex Levine<br>
    <br>
    <div class="moz-cite-prefix">On 8/13/15 4:02 PM, Dolph Mathews
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAC=h7gW5ZsCEbA0RUsPymEWWba2yBfdUgOTpA0Ls5vP85B1xTA@mail.gmail.com"
      type="cite">
      <div dir="ltr"><a moz-do-not-send="true"
          href="https://review.openstack.org/#/c/212515/">https://review.openstack.org/#/c/212515/</a><br>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Thu, Aug 13, 2015 at 6:57 AM,
          Alexandre Levine <span dir="ltr"><<a
              moz-do-not-send="true"
              href="mailto:alexandrelevine@gmail.com" target="_blank">alexandrelevine@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
            everybody,<br>
            <br>
            There is a problem using keystone v3 in Kilo by external EC2
            API service. The problem doesn't exist for keystone v2 and
            it is fixed in master for keystone v3 by the following
            patch:<br>
            <a moz-do-not-send="true"
href="https://github.com/openstack/python-keystoneclient/commit/f6ab133f25f00e041cd84aa8bbfb422594d1942f"
              rel="noreferrer" target="_blank">https://github.com/openstack/python-keystoneclient/commit/f6ab133f25f00e041cd84aa8bbfb422594d1942f</a><br>
            <br>
            We do need to have EC2 API working with the keystone v3 in
            Kilo so the question is: would it be possible to backport
            the patch into Kilo?<br>
            We can create a review and a bug if necessary, we just need
            to know that it's going to be accepted some time soon.<br>
            <br>
            The problem is in keystoneclient so we do have a workaround
            which can be introduced into our EC2 API code - it'll bypass
            keystone client and send raw REST request. But I understand
            it's not the most sound approach.<br>
            <br>
            Best regards,<br>
              Alex Levine<br>
            <br>
            <br>
__________________________________________________________________________<br>
            OpenStack Development Mailing List (not for usage questions)<br>
            Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
              rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
            <a moz-do-not-send="true"
              href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
              rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
          </blockquote>
        </div>
        <br>
      </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>