5fdef82a30
configuring pools for notificaiton listeners is an alternative approach to using per-component notification topics, however not all oslo.messaging drivers support it (from currently available, zmq and amqp1 do not, rabbit and kafka do support listener pools). This patch adds a config option 'listener-pool-name' to [service:sink] config section (defaults to None) that can be used to configure a common pool for designate-sink notification listeners if the messaging driver does support them. Change-Id: I4fc1c7264671c3102c067beb7298879e62214d60
16 lines
728 B
YAML
16 lines
728 B
YAML
---
|
|
features:
|
|
- |
|
|
Designate-Sink service now supports notification listener pooling
|
|
for those oslo.messaging drivers that support this feature
|
|
(currently those are ``rabbit``/``kombu`` and ``kafka``).
|
|
`Listener pools <https://docs.openstack.org/oslo.messaging/latest/reference/notification_listener.html>`_
|
|
is an alternative to specifying several topics for notification consumers
|
|
in configuration of service that emits notifications.
|
|
|
|
To enable listener pooling, set the option
|
|
``[service:sink]listener_pool_name`` to some string value, that must be the
|
|
same for all designate-sink service instances.
|
|
Default value of this option (``None``) disables notification listener
|
|
pooling.
|