On 01/28/2015 01:13 AM, Fischer, Matt wrote:
> Our keystone database is clustered across regions, so we have this job
> running on node1 in each site on alternating hours. I don’t think you’d
> want a bunch of cron jobs firing off all at once to cleanup tokens on
> multiple clustered nodes. That’
+100
Dani
On Mon, Jan 26, 2015 at 1:10 AM, Tim Bell wrote:
> 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,
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,
ideally).
If we are all configuring this as a cron job, is there a
It is still mentioned in the Juno installation docs:
By default, the Identity service stores expired tokens in the database
indefinitely. The
accumulation of expired tokens considerably increases the database size and
might degrade
service performance, particularly in environments with limited r
