Keystone auth_token middleware should support Swift global memcache
Bug #1052674 reported by
Guang Yee
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Invalid
|
High
|
Guang Yee | ||
| Folsom |
Invalid
|
Undecided
|
Unassigned | ||
| python-keystoneclient |
Fix Released
|
High
|
Guang Yee | ||
Bug Description
Keystone Essex-3 auth_token middleware supports both Swift global cache via the "cache" configuration option and Keystone local cache option via the "memcache_hosts" configuration option. That was prior to the introduction of KSL.
Since Essex RC1, Swift global cache option was no longer supported. And the Keystone local cache option has changed to "memcache_servers". But definition, backward compatibility was no longer preserved even though Essex-3 and Essex final was the same release.
With shared caching, we don't have to configure memcache in multiple filters, which arguably makes deployment and troubleshooting a lot easier.
| tags: | added: folsom-rc-potential |
| Changed in keystone: | |
| status: | New → Triaged |
Revision history for this message
| Joseph Heck (heckj) wrote | #1 |
| Changed in keystone: | |
| importance: | Undecided → High |
| tags: | removed: folsom-rc-potential |
| Changed in keystone: | |
| assignee: | nobody → Guang Yee (guang-yee) |
Revision history for this message
| Joseph Heck (heckj) wrote | #2 |
Revision history for this message
| Adam Young (ayoung) wrote | #3 |
| Changed in keystone: | |
| status: | Triaged → Fix Committed |
| Changed in keystone: | |
| milestone: | none → grizzly-rc1 |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Alan Pevec (apevec) wrote | #4 |
| Changed in keystone: | |
| status: | Fix Released → Invalid |
| Changed in python-keystoneclient: | |
| status: | New → Fix Committed |
| assignee: | nobody → Guang Yee (guang-yee) |
| Changed in keystone: | |
| milestone: | grizzly-rc1 → none |
| Changed in python-keystoneclient: | |
| importance: | Undecided → High |
| milestone: | none → 0.2.3 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
When we converted to loading configurations, we lost checking for a config('cache') and using it if present. If not present, it was defaulting to keystone.cache