3355891490
some oslo.messaging transport backends support listener pooling, when the listener declares a pool it belongs, and each message of the topic is delivered once to each pool (plus to 'default' pool for those that have not declared a pool). In particular, rabbitmq and kafka support it. This mechanism should be preferrable over setting a separate topic for barbican to listen notifications on. This patch adds a new config option `[keystone_notifications]pool_name` (None by default for backward compatibility) that can be used to set up barbican-keystone-listener to create a separate pool for its listeners. For more details see oslo.messaging docs https://docs.openstack.org/oslo.messaging/latest/reference/notification_listener.html Change-Id: Ie011266f5ebe03bc6053bfe68e2bee27e07ea11c
15 lines
706 B
YAML
15 lines
706 B
YAML
---
|
|
features:
|
|
- |
|
|
It is now possible for barbican-keystone-listener to listen on the same
|
|
standard notification topic without interfering with other services by
|
|
using the notification listener pools feature of oslo.messaging.
|
|
To use it, set the new ``[keystone_notifications]pool_name`` option
|
|
to some unique value (but the same for all instances of
|
|
barbican-keystone-listener service).
|
|
This feature is available only for those messaging transports of
|
|
oslo.messaging that support it.
|
|
At the moment those are rabbitmq and kafka.
|
|
For more details see
|
|
`oslo.messagind docs <https://docs.openstack.org/oslo.messaging/latest/reference/notification_listener.html>`_
|