<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">And yeah, we're planning on removing the code specifically from keystone, although we'll do some fancy import-y thing to keep backwards compatibility with the namespace keystone.middeware.auth_token. We will encourage and submit changes for all the devstack and related paste.ini files to reference the new location (keystoneclient.middleware.auth_token), and get the docs all updated as well to reflect the new location for this code.<div><br></div><div>The primary driver was the very reasonable complaint that to use the middleware, you had to install all of keystone, which the packagers typically had with services and everything else, and it was a PITA to install keystone and deal with all the rest when all you really wanted was that middleware for your service</div><div><br></div><div>-joe</div><div><br></div><div>ps: and yeah, I can't spell keystone - it was a tragic day for me yesterday.</div><div><br><div><div>On Nov 16, 2012, at 5:35 PM, Dolph Mathews <<a href="mailto:dolph.mathews@gmail.com">dolph.mathews@gmail.com</a>> wrote:</div><blockquote type="cite">henrynash is currently working on importing keystoneclient middleware into the exist keystone namespace to maintain backwards compatibility with the current middleware.<span></span><div><br></div><div>-Dolph<br><br>On Friday, November 16, 2012, Chmouel Boudjnah wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Joe,<div><br></div><div>Nice new features, a few question about the auth_token move apologies if this has been discussed earlier but grepping thru the auth_token ml threads yield a LOT...<br>
<div><br><div class="gmail_quote">
On Sat, Nov 17, 2012 at 9:39 AM, heckj <span dir="ltr"><<a href="javascript:_e({}, 'cvml', 'heckj@mac.com');" target="_blank">heckj@mac.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm pleased to announce that keystoneclient has just received a fairly large update, and we've released this update publicly at python-keystoneclient 0.2.0. The new version is now available on PyPi (<a href="http://pypi.python.org/pypi/python-keystoneclient/0.2.0" target="_blank">http://pypi.python.org/pypi/python-keystoneclient/0.2.0</a>).<br>
<br>
Highlights for this release:<br>
<br>
* the auth_token middleware from keystone has been moved into keystoneclient<br></blockquote><div><br></div><div>This seems to be still in the keystone directory, what is the plan for the migration as this may lead a lot of config updates for upgrades. We could make it easy by installing auth_token from keystoneclient in the keystone.middleware namespace.</div>
<div><br></div><div>Chmouel.</div><div><br></div><div>PS: Talking about migration I should probably remove swift_auth from keystone as this has been sometime since we moved it from swift.</div></div></div></div>
</blockquote></div><br><br>-- <br><div><br></div>-Dolph<br>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></body></html>