Re: [openstack-dev] [Openstack-operators] [openstack-operators] [Keystone] flush expired tokens and moves deleted instance

2015-01-27 Thread Clint Byrum
Excerpts from Tim Bell's message of 2015-01-25 22:10:10 -0800: This is often mentioned as one of those items which catches every OpenStack cloud operator at some time. It's not clear to me that there could not be a scheduled job built into the system with a default frequency (configurable,

Re: [openstack-dev] [Openstack-operators] [openstack-operators] [Keystone] flush expired tokens and moves deleted instance

2015-01-27 Thread John Dewey
This is one reason to use the memcached backend. Why replicate these tokens in the first place. On Tuesday, January 27, 2015 at 10:21 AM, Clint Byrum wrote: Excerpts from Tim Bell's message of 2015-01-25 22:10:10 -0800: This is often mentioned as one of those items which catches every

Re: [openstack-dev] [Openstack-operators] [openstack-operators] [Keystone] flush expired tokens and moves deleted instance

2015-01-27 Thread Clint Byrum
The problem with running in memcached is now you have to keep _EVERY_ token in RAM. This is not any cheaper than cleaning out a giant on-disk table. Also worth noting is that memcached can produce frustrating results unless you run it with -M. That is because without -M, your tokens may be