openstack team mailing list archive

Thread
Date

Re: [OpenStack][Swift] How about move auth_toke and swift_auth middlewares into Swift?

To: Alex Yang <alex890714@xxxxxxxxx>, "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
From: "Nah, Zhongyue" <zhongyue.nah@xxxxxxxxx>
Date: Thu, 30 Aug 2012 03:50:07 +0000
Accept-language: en-US
Cc: PRC Server Performance <PRCServerPerformance@xxxxxxxxx>
In-reply-to: <CADZ3O5yk4qf+ZURY8P9PMc4bGMFK97j6DCkJUqcUmf2QFZGC9A@mail.gmail.com>
Thread-index: AQHNhmJfCxQI4N2SJUq11HslfEPXJZdxuEAA
Thread-topic: [Openstack] [OpenStack][Swift] How about move auth_toke and swift_auth middlewares into Swift?

FYI

From: openstack-bounces+zhongyue.nah=intel.com@xxxxxxxxxxxxxxxxxxx [mailto:openstack-bounces+zhongyue.nah=intel.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of Alex Yang
Sent: Thursday, August 30, 2012 11:46 AM
To: openstack@xxxxxxxxxxxxxxxxxxx
Subject: [Openstack] [OpenStack][Swift] How about move auth_toke and swift_auth middlewares into Swift?

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@xxxxxxxxx<mailto:alex890714@xxxxxxxxx>
GitHub:       https://github.com/AlexYangYu
    Blog:        http://alexyang.sinaapp.com
 Weibo:       http://www.weibo.com/alexyangyu

References

[OpenStack][Swift] How about move auth_toke and swift_auth middlewares into Swift?
From: Alex Yang, 2012-08-30