
The section in the Watcher docs that describes how to enable cinder notifications incorrectly tells the user to change the cinder config to send notification to the watcher.watcher_notifications exchange and topic. Instead, it should instruct the user to change the Watcher configuration of the notification_topics [1] to listen to the 'openstack.notifications', which is the one used by cinder by default[2]. This patch also adds 'openstack.notifications' to the default value for the 'notification_topics' parameter. [1] https://docs.openstack.org/watcher/latest/configuration/watcher.html#watcher_decision_engine.notification_topics [2] https://docs.openstack.org/cinder/latest/configuration/block-storage/samples/cinder.conf.html Partial-Bug: 2121384 Change-Id: I4dc1a72af79a23c9ca07d2da5ff41bd7741e37d8 Signed-off-by: jgilaber <jgilaber@redhat.com>
8 lines
319 B
YAML
8 lines
319 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Watcher now listens by default to the exchange and channel used by default
|
|
in Cinder, which is 'openstack.notifications'. The previous instructions
|
|
in the documentation to enable cinder notifications have been modified to
|
|
make clear that there is no need of changing the cinder conf.
|