From b25798b8f000facad56a83b0158809072b527813 Mon Sep 17 00:00:00 2001 From: Juan Antonio Osorio Robles Date: Wed, 1 Nov 2017 10:47:49 +0000 Subject: Make keystone notification topics configurable By default keystone sends notifications to the 'notifications' topic. This is consumed by default by ceilometer. However, when ceilometer is not enabled, rabbitmq accumulates these notifications since nothing is consuming them. This results in the queue consuming rabbitmq's memory. With this capability, we can now dynamically configure notification topics depending on the 'keystone_notification_topics' hiera key. Related-Bug: #1729293 Change-Id: I4dcce73446633c08ea37ba567610eec398094036 (cherry picked from commit bbe7d9effe51324ef5fa75e40f9d0ca74544d484) --- .../notes/keystone-notification-topics-5b155e7b5e60b7fd.yaml | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 releasenotes/notes/keystone-notification-topics-5b155e7b5e60b7fd.yaml (limited to 'releasenotes') diff --git a/releasenotes/notes/keystone-notification-topics-5b155e7b5e60b7fd.yaml b/releasenotes/notes/keystone-notification-topics-5b155e7b5e60b7fd.yaml new file mode 100644 index 0000000..3986c6f --- /dev/null +++ b/releasenotes/notes/keystone-notification-topics-5b155e7b5e60b7fd.yaml @@ -0,0 +1,7 @@ +--- +features: + - | + keystone notification topics are now configured via the + keystone_notification_topics hiera key. Which aggregates + all the keys that match this. It's useful for dynamically + configuring the topics and not always sending them. -- cgit 1.2.3-korg