<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; "><br><div><div>On Mar 1, 2013, at 4:40 PM, Dolph Mathews <<a href="mailto:dolph.mathews@gmail.com">dolph.mathews@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Fri, Mar 1, 2013 at 4:59 PM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 03/01/2013 01:18 PM, Vishvananda Ishaya wrote:<br>
> Hi Everyone,<br>
><br>
> So I've been doing some profiling of api calls against devstack and I've discovered that a significant portion of time spent is in the auth_token middleware validating the PKI token. There is code to turn on caching of the token if memcache is enabled, but this seems like overkill in most cases. We should be caching the token in memory by default. Fortunately, nova has some nifty code that will use an in-memory cache if memcached isn't available.<br>
<br>
</div>We gave up on PKI in Folsom after weeks of trouble with it:<br>
<br>
* Unstable -- Endpoints would stay up >24 hours but after around 24<br>
hours (sometimes sooner), the endpoint would stop working properly with<br>
the server user suddenly returned a 401 when trying to authenticate a<br>
token. Restarting the endpoint with a service nova-api restart gets rid<br>
of the 401 Unauthorized for a few hours and then it happens again.<br></blockquote><div><br></div><div style="">Obviously that's not acceptable behavior; is there a bug tracking this issue? I poked around but didn't see anything related to unexpected 401's.</div></div></div></div></blockquote><br></div><div>This bug was fixed quite a while ago:</div><div><br></div><div><a href="https://bugs.launchpad.net/keystone/+bug/1074172">https://bugs.launchpad.net/keystone/+bug/1074172</a></div><div><br></div><div><a href="https://review.openstack.org/#/c/15242/">https://review.openstack.org/#/c/15242/</a></div><div><br></div><div>But it looks like it was never backported to stable/folsom. I've proposed it here:</div><div><br></div><div><a href="https://review.openstack.org/#/c/23334/">https://review.openstack.org/#/c/23334/</a></div><div><br></div><div>If someone can target the bug to folsom that would be awesome.</div><div><br></div><div>Vish</div><div><br></div><div><br></div><br></body></html>