From 7c6618e69a2cfcd63450e5c264d4371d600e2675 Mon Sep 17 00:00:00 2001 From: Edward Hope-Morley Date: Wed, 14 Jun 2023 16:58:28 +0100 Subject: [PATCH] Add release note for new keystone role cache config Change-Id: I7c1f1e16ee1ac41318f16bac7ba8a134a200c003 Closes-Bug: #1771114 --- doc/source/release-notes/2023.2-bobcat.rst | 21 +++++++++++++++++++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/doc/source/release-notes/2023.2-bobcat.rst b/doc/source/release-notes/2023.2-bobcat.rst index 08b72733..b8185f8c 100644 --- a/doc/source/release-notes/2023.2-bobcat.rst +++ b/doc/source/release-notes/2023.2-bobcat.rst @@ -42,8 +42,25 @@ test bundle, and/or a section in the current guide (Charm Guide) that details its usage. Test bundles are located in the ``src/tests/bundles`` directory of the relevant charm repository (see all `charm repositories`_). - -~~~~~~~ +Keystone role cache config +~~~~~~~~~~~~~~~~~~~~~~~~~~ + +The keystone charm now supports configuring the keystone [role] cache_time using +a new role-cache-expiration config. If not set, this defaults to the global +expiration_time (configurable by the dogpile-cache-expiration config option). Setting +the role cache_time to something closer to 10s is recommended for +clouds that receive frequent role assignment changes and are sensitive to the +(default) 600s delay that assignements can take to propagate to all keystone +peer caches. + +For example, to set the role cache expiration time to 10 seconds do: + +.. code-block:: none + + juju config keystone role-cache-expiration=10 + +The result of this being that keystone will only used cached role assignments for up to +10 seconds before refreshing them from the database. Documentation updates ---------------------