Merge "Fix doc about nova notifications"

This commit is contained in:
Zuul
2018-12-10 09:45:45 +00:00
committed by Gerrit Code Review

View File

@@ -403,26 +403,22 @@ Watcher can consume notifications generated by the Nova services, in order to
build or update, in real time, its cluster data model related to computing build or update, in real time, its cluster data model related to computing
resources. resources.
Nova publishes, by default, notifications on ``notifications`` AMQP queue Nova emits unversioned(legacy) and versioned notifications on different
(configurable) and ``versioned_notifications`` AMQP queue (not topics. Because legacy notifications will be deprecated, Watcher consumes
configurable). ``notifications`` queue is mainly used by ceilometer, so we can Nova versioned notifications.
not use it. And some events, related to nova-compute service state, are only
sent into the ``versioned_notifications`` queue.
By default, Watcher listens to AMQP queues named ``watcher_notifications`` * In the file ``/etc/nova/nova.conf``, the value of driver in the section
and ``versioned_notifications``. So you have to update the Nova ``[oslo_messaging_notifications]`` can't be noop, and the value of
configuration file on controller and compute nodes, in order notification_format in the section ``[notifications]``
to Watcher receives Nova notifications in ``watcher_notifications`` as well. should be both or versioned ::
* In the file ``/etc/nova/nova.conf``, update the section
``[oslo_messaging_notifications]``, by redefining the list of topics
into which Nova services will publish events ::
[oslo_messaging_notifications] [oslo_messaging_notifications]
driver = messagingv2 driver = messagingv2
topics = notifications,watcher_notifications
* Restart the Nova services. ...
[notifications]
notification_format = both
Configure Cinder Notifications Configure Cinder Notifications