openstack/charm-keystone
Code Issues Proposed changes

Enable global cache by default

Browse Source 
The commit d2e42f1 introduced the config option enable-cache set to
False by default to cache inconsistency when keystone was deployed in
HA, since then a new change by made to disable token caching (563b453),
it has tested that this option alleviates the performance regression
seen when disabling the cache, whitout leaving the system exposed to
expired token reuse.

Change-Id: I584b7d2ea03d824c229cf5b21723d3645ffc2056
Related-Bug: #2113772
Related-Bug: #2089616
Signed-off-by: Felipe Reyes <felipe.reyes@canonical.com>
This commit is contained in:
Felipe Reyes
2025-09-17 15:58:29 -03:00
parent 6cf03639e0
commit c99079b83a
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
config.yaml
View File

@@ -136,7 +136,7 @@ options:
cache expiration time.
enable-cache:
type: boolean
default: False
default: True
description: |
Enable caching across Keystone using unit localised memcache; enabling
this feature may cause caching inconsistency in multi-unit deployments