Keystone should use memcached for tokens

Bug #1556164 reported by David Moreau Simard
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OPNFV
New
Undecided
Unassigned
Packstack
New
Undecided
Unassigned
puppet-openstack-integration
Fix Released
Undecided
David Moreau Simard

Bug Description

Right now some projects install memcached (such as Swift) but Keystone is not set up to use memcached.

When Keystone does not have a token cache method (such as memcached) configured, keystonemiddleware will throw the following error:
2016-03-11 02:48:21.508 17343 WARNING keystonemiddleware.auth_token [-] Using the in-process token cache is deprecated as of the 4.2.0 release and may be removed in the 5.0.0 release or the 'O' development cycle. The in-process cache causes inconsistent results and high memory usage. When the feature is removed the auth_token middleware will not cache tokens by default which may result in performance issues. It is recommended to use memcache for the auth_token token cache by setting the memcached_servers option.

Revision history for this message
David Moreau Simard (dmsimard) wrote :

puppet-openstack-integration: https://review.openstack.org/#/c/342391/

Changed in puppet-openstack-integration:
status: New → In Progress
assignee: nobody → David Moreau Simard (dmsimard)
Changed in puppet-openstack-integration:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.