Hi, The keystone middleware has been moved to swift already, it just wasn't removed from keystone, I haven't send a removal request from keystone since there is a massive works of documentation that needed to be done and it's a bit too late for this release timeline since distributors/operators may be not ready for it yet. Chmouel. On Thu, Aug 30, 2012 at 5:45 AM, Alex Yang <alex890714 at gmail.com> wrote: > Hi Swifters， > I use keystone for the authentication and authorization of swift. During the > benchmark test, I also encountered this kind of problems > https://bugs.launchpad.net/keystone/+bug/1020127. > I do some changes that moved the auth_toke and swift_auth middlewares into > swift and replace the python-memecache client with > swift.common.memcaced.MemcacheRing. > It's works well for my business environment and easy to setup. > > I am willing to contribute this changes to swift or keystone. > What's your advices? > ______________________________________________________________________________________________________________________________ > 杨雨 > Email: alex890714 at gmail.com > GitHub: https://github.com/AlexYangYu > Blog: http://alexyang.sinaapp.com > Weibo: http://www.weibo.com/alexyangyu > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp >