Consume notification from the default queue
Closes-Bug: #1209198 Change-Id: Id31953207d03a172353dc311a1a7df7b88780318 Signed-off-by: Julien Danjou <julien@danjou.info>
This commit is contained in:
parent
fee311c138
commit
4c4434de20
@ -175,7 +175,7 @@ class CollectorService(rpc_service.Service):
|
||||
try:
|
||||
self.conn.join_consumer_pool(
|
||||
callback=self.process_notification,
|
||||
pool_name='ceilometer.notifications',
|
||||
pool_name=topic,
|
||||
topic=topic,
|
||||
exchange_name=exchange_topic.exchange,
|
||||
ack_on_error=ack_on_error)
|
||||
|
@ -374,6 +374,19 @@ Configuring keystone to work with API
|
||||
default port value for ceilometer API is 8777. If the port value
|
||||
has been customized, adjust accordingly.
|
||||
|
||||
Notifications queues
|
||||
========================
|
||||
|
||||
.. index::
|
||||
double: installing; notifications queues
|
||||
|
||||
By default, Ceilometer consumes notifications on the RPC bus sent to
|
||||
**notification_topics** by using a queue/pool name that is identical to the
|
||||
topic name. You shouldn't have different applications consuming messages
|
||||
from this queue.
|
||||
If you want to also consume the topic notifications with a system other than
|
||||
Ceilometer, you should configure a separate queue that listens for the same
|
||||
messages.
|
||||
|
||||
Use multiple dispatchers
|
||||
========================
|
||||
|
Loading…
x
Reference in New Issue
Block a user