This patch moves (as discussed at the Newton design summit) the
s3_token middleware from keystonemiddleware to swift3. The git
history is not included based upon the agreement between the
Keystone team and the Swift3 team.
This is based on s3_token.py from openstack/keystonemiddleware@234913e
Note that the egg entrypoint has changed from "s3_token" to "s3token"
for consistency between entrypoint and recommended pipeline names.
Additionally, keystone functional tests now use the in-tree s3token
middleware.
Upgrade Impact
==============
Deployers currently using keystone for authentication should change
their s3token filter definition to use the middleware provided by swift3
rather than the one provided by keystonemiddleware. Note that
keystonemiddleware will still need to be installed, and its auth_token
middleware configured.
UpgradeImpact
Co-Authored-By: Tim Burke <tim.burke@gmail.com>
Co-Authored-By: Kota Tsuyuzaki <tsuyuzaki.kota@lab.ntt.co.jp>
Change-Id: I1c0e68a5276dd3dee97d7569e477c784db8ccb8a
Fix the version of the Swift described in requirements.txt from 1.8.0
to 2.1.0.
In between updates from 1.8.0 to 2.0.0, the process for pipeline of
Swift was changed.
And object sysmeta metadata was supported from 2.1.0.
Therefore, 2.1.0 or later is not installed, starting of
proxy-server with Swift3 fails and it is impossible to use s3_acl.
For more information about the changes of Swift, check the following
commit IDs.
- 4ce9b252fd44dae74b47d5b5c48e9403b5d36a4a
- 4286f36a60446e322f23a329416be3ed67db1149
Change-Id: I793b0f325ea34f208784d60f2b038e75f6d239b9
The lxml XML toolkit is a binding for the C libraries libxml2 and libxslt. It
is compatible with ElementTree API, which is more pythonic than the DOM
interface. In addition, lxml has attractive features like XML validation and
namespace mapping.
Replacing the current DOM interface with the lxml API will simplify Swift3 code
a lot and improve maintainability, I believe.
Change-Id: Ie2291f180421559ed3320a173d2f7eea81f459d9
This patch fix a bug when installing a swift3 on
devstack.
Because devstack uses pbr/requirements.txt to
sync global requirements, we need to add setup.cfg and
pbr support to swift3 so it can be installed on devstack.
This also allow to take advantage of the pbr facilities
(version number support, etc)
Change-Id: Id0179fad179efac5ba85bef7838365a4d304d196
Kota Tsuyuzaki