deb-murano/releasenotes/notes/configure-notifications-0c84a5085c25f6e7.yaml
kbespalov c188b5cd12 [messaging] Using get_notification_transport()
We should separate transports for the RPC and Notifiers
in order to have a possibility of using different messaging
configurations, like rabbit for RPC and kafka for notifications.

e.g.

[DEFAULT]
rpc_backend = rabbit

[oslo_messaging_rabbit]
rabbit_hosts = ...
rabbit_password = ...
rabbit_userid = ...

[oslo_messaging_notifications]
driver = ...
transport_url = kafka://...
topics = ...

Change-Id: I965fdb4bb1883d05c43766cf12d620d7ab038e36
Closes-Bug: #1620545
2016-09-06 09:59:53 +00:00

6 lines
344 B
YAML

features:
- It is now possible to configure the notifications to use a different
transport URL than the RPCs. These could potentially be completely
different message broker hosts (though they doesn't need to be). If the
notification-specific configuration is not provided, the notifier will use
the same transport as the RPCs.