<div>Hi , folks </div><div><br></div><div>I'm confusing about the usage of memcached on Swift-proxy serve. There's the description in Swift dev-doc <a href="http://swift.openstack.org/deployment_guide.html?highlight=token#memcached-considerations">http://swift.openstack.org/deployment_guide.html?highlight=token#memcached-considerations</a></div>
<div><br></div><div>Memcached Considerations</div><div>Several of the Services rely on Memcached for caching certain types of lookups, such as auth tokens, and container/account existence. Swift does not do any caching of actual object data. Memcached should be able to run on any servers that have available RAM and CPU. At Rackspace, we run Memcached on the proxy servers. The memcache_servers config option in the proxy-server.conf should contain all memcached servers.</div>
<div><br></div><div>In my knowing , Tempauth uses Memcached to store tokens . So that I always thought swift-proxy will cache "validated tokens" in memcached before expired. </div><div><br></div><div>Also , this consideration keeps in my mind . But it seems not like what I'm thinking while authenticate by Keystone. Swift-proxy does not cache validated tokens in memcached . It always try to validate client's token by query keystone for every requests. </div>
<div>I'm interesting about the reasons of this design. Isn't better letting swift-proxy to check client's token in memcached first ? </div><div><br></div><div>My reasons :</div><div>1. Decreasing keystone's loading </div>
<div>2. Faster response time for a request</div><div>3. Better bandwidth leverage </div><div><br></div><div>So , for keystone as authentication server for swift . Memcached is in charge of caching rings , container/account existence. It does not responsible for cache validated tokens anymore . Am I right ? Or just I miss some configuration for this option?</div>
<div><br></div><div>Any clarify would be great ...................</div><div><br></div><div><br></div><div><br></div><div>Cheers</div><div>-- <br></div><div>Hugo Kuo @ Taiwan</div><div><br></div><div><a href="mailto:tonytkdk@gmail.com" target="_blank">tonytkdk@gmail.com<br>
</a></div><div><a href="mailto:tonytkdk@gmail.com" target="_blank">+</a>886 935004793</div><br>