Commit Graph

11 Commits

Author SHA1 Message Date
Thiago da Silva 211def7d59 swift3 is now s3api middleware
Change-Id: Ic0431c491f2450ba2b45b974ced1e7cdf3f19ac1
Signed-off-by: Thiago da Silva <thiago@redhat.com>
2018-05-28 13:45:51 -04:00
Tim Burke c63f89cdcb Clean up how we keystone
The docs were recommending a bad config (see related change).

Related-Change: I21e38884a2aefbb94b76c76deccd815f01db7362
Change-Id: Idca96a39f552083b55dc5a86d14ee4357777d6fe
2017-09-15 04:25:45 +00:00
Charles Farquhar 9efa650e21 Update pipeline ordering in README.md
The recommended pipeline ordering changed beginning with 6ffcc294e3 .
After moving to use keystone v3 API, the new order becomes mandatory.

Change-Id: Ic9af387b9192f285f0f486e7171eefb23968007e
2017-07-28 17:54:46 +00:00
Kota Tsuyuzaki f197217f0b Small updates for readme
Change-Id: Icf6b0abe457b47edbb9b5ff72cf56fe3f0ee263b
2016-10-16 19:48:20 -07:00
Morgan Fainberg b626a3ca86 Add s3token middleware to the swift3 project
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
2016-05-20 10:07:51 -07:00
Tim Burke fd58f579ae Update version of keystone used for functests
Previously, the gate tests used a version of keystone that didn't have a
cap on oslo.config. This led to gate checks failing because they pulled
in a version of oslo.config that broke backward compatibility. Even if
we updated within icehouse, the last oslo.messaging does not include a
cap on oslo.utils, which *also* broke backwards compatibility.

Now, we'll install the most recently released version of keystone,
updating some testing and example config along the way.

Change-Id: Id357975413094bab751c5b8549d9201e9232af7f
2015-08-12 21:03:07 +00:00
Charles Hsu a6a0710bce Update README.
Change-Id: I50dcffbe29f26aa606242c75c47e73a3706beaee
2015-02-03 13:11:20 +08:00
Bill Owen 8622b1cdab Update documentation to use keystoneauth name
Update documentation to use keystoneauth in the proxy server pipeline.  Change 5e372016 added
pipeline checking and explicitly looks for keystoneauth name, so README should match.

Also update package name for s3_token middleware to be keystoneclient, not keystone.

Closes-Bug: #1381758
Change-Id: I0d769e47ffc32725c1df2def4d9d46c25474132e
2014-10-17 14:50:25 -07:00
FUJITA Tomonori 5e1a67cb0d Update README about keystone usage
Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
2013-02-08 08:34:35 +09:00
FUJITA Tomonori 0e8be459da update README
Add 'Install' section.

Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
2012-06-16 21:14:49 +09:00
Chmouel Boudjnah eb624f3332 Addding a few base files to the project.
- Inspired mostly from gholt's swift-staticweb repository.
2012-05-21 13:05:34 +02:00