Permit functional tests against Swift with Keystone

Code Issues Proposed changes

While poking at such problems with authentication other than swauth
it was useful to allow stock functional tests running back-to-back
at two clusters, with tempauth and Keystone.
When running the legacy tests, this version packs account into user
the way it was down previously. This way we do not need to repack
them before every call to get_auth. The downside is additional work
to be done when setting ACLs.
Change-Id: Ieb1d9227cb88977ecd2c39825039bc4be8afae0b

This commit is contained in:

Pete Zaitcev

2013年03月10日 18:52:10 -06:00

parent 5e427e5e3b

commit 35e07e2982

5 changed files with 84 additions and 58 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

6
test/sample.conf

View File

@@ -4,6 +4,12 @@ auth_host = 127.0.0.1

auth_port = 8080

auth_ssl = no

auth_prefix = /auth/

## sample config for Swift with Keystone

#auth_version = 2

#auth_host = localhost

#auth_port = 5000

#auth_ssl = no

#auth_prefix = /v2.0/

# Primary functional test account (needs admin access to the account)

account = test

Permit functional tests against Swift with Keystone

6 test/sample.conf Unescape Escape View File

6
test/sample.conf

View File