Bug 1041942

Summary: [RFE][keystone]: periodically flush expired token
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/keystone/+spec/periodically-flush-expired-token
Whiteboard: upstream_milestone_none upstream_status_not-started upstream_definition_superseded
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:05:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-12 20:12:06 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/periodically-flush-expired-token.

Description:

Now we need the deployer to add a cron-like job to call 'keystone-manage token_flush' to remove the expired token records in the token backend (kvs, mysql, memcache, etc) so that the token persistence mechanism will not be filled up with expired tokens.

This BP adds a periodic thread in keystone-all process, which will run at a configurable interval to flush the expired token from DB. The interval should be configured more than CONF.token.expiration (86400). If the configured value is no more than 0, the periodic thread will not run.

It also flushes the oauth token.

Specification URL (additional information):

None