An unifed caching system for middlewares
Registered by
Chmouel Boudjnah
With the included middle-ware we currently have auth_token doing its own caching via memcache while ec2 and s3 middlewares doesn't cache validated token received from keystone.
We could use common functions but those middle-ware are supposed to be dropped as in and it would not be nice to have another dependence.
We could have a cache middleware like used in swift ;
https:/
which we could reuse in keystone for cache management.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Low
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Dolph Mathews
Related branches
Related bugs
Sprints
Whiteboard
should this be moved to keystoneclient?
probably more in oslo now -- chmouel
(?)