Add memcached_backend option in keystone.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
Wishlist
|
Kui Shi |
Bug Description
If we choose memcached as the token backend driver, we should set proper servers in '[memcache]' section of keystone.conf.
For the memcache backend, there are 3 memcached client supported by dogpile,
-------
# pydoc dogpile.
dogpile.
-------
In keystone, they are listed in keystone/
VALID_DOGPILE_
By default, memcached will be used. The "memcached_backend" option will determine which backend to use.
But there is no simple to pass the "memcached_backend" option.
Changed in keystone: | |
assignee: | nobody → Kui Shi (skuicloud) |
tags: | added: memcache |
tags: |
added: memcached removed: memcache |
Changed in keystone: | |
status: | Triaged → In Progress |
Changed in keystone: | |
status: | In Progress → Incomplete |
description: | updated |
The idea behind the base memcache token driver is that it makes some basic decisions for you. If you would like to utilize a more in-depth dogpile configuration, ideally you would do the raw "kvs" configuration passing extra dogpile config options to the backend (it's not user friendly to do so).
This change would be good making the UX better when configuring the use of memcached as a token persistence store.