I think we can close this bug for all projects. s3_token is included in
python-keystoneclient for a while now, and the s3 middleware itself is
available on stackforge: https://github.com/stackforge/swift3
-> Closing bug.
** Changed in: swift
Status: New => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1194688
Title:
Devstack uses keystone.middleware.s3_token in swift pipeline
Status in devstack - openstack dev environments:
Confirmed
Status in OpenStack Identity (Keystone):
Invalid
Status in OpenStack Object Storage (Swift):
Fix Released
Bug description:
Coming from https://bugs.launchpad.net/keystone/+bug/1193112 devstack
will use keystone's keystone.middleware.s3token when setting up swift.
If it is being used externally then it shouldn't be in
keystone.middleware and there are two main options for moving it:
1. s3token middleware should be moved into python-keystoneclient.
This makes it available to other components in the same way that the
auth_token middleware was moved.
2. s3token middleware should be moved into swift.
There is already a dependency on swift.common.utils in the s3token middleware
and it appears that is calling keystone via http so it should be fine to be
moved. Note: this is the first time i've paid much attention to this middleware
so please tell me if it needs to be a keystone thing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1194688/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
