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 resources.
We recommend that you use cron to configure a periodic task that purges expired 
tokens
hourly:
# (crontab -l -u keystone 2>&1 | grep -q token_flush) || \
echo '@hourly /usr/bin/keystone-manage token_flush >/var/log/keystone/
keystone-tokenflush.log 2>&1' \
>> /var/spool/cron/keystone



Mike Smith
Principal Engineer, Website Systems
Overstock.com<http://Overstock.com>



On Jan 24, 2015, at 10:03 AM, Daniel Comnea 
<comnea.d...@gmail.com<mailto:comnea.d...@gmail.com>> wrote:

Hi all,


I just bumped into Sebastien's blog where he suggested a cron job should run in 
production to tidy up expired tokens - see blog[1]

Could you please remind me if this is still required in IceHouse/ Juno? (i kind 
of remember i've seen some work being done in this direction but i can't find 
the emails)


Thanks,
Dani

[1] 
http://www.sebastien-han.fr/blog/2014/08/18/a-must-have-cron-job-on-your-openstack-cloud/
_______________________________________________
OpenStack-operators mailing list
openstack-operat...@lists.openstack.org<mailto:openstack-operat...@lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


________________________________

CONFIDENTIALITY NOTICE: This message is intended only for the use and review of 
the individual or entity to which it is addressed and may contain information 
that is privileged and confidential. If the reader of this message is not the 
intended recipient, or the employee or agent responsible for delivering the 
message solely to the intended recipient, you are hereby notified that any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in error, please notify 
sender immediately by telephone or return email. Thank you.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to