+philip.day=hp@lists.launchpad.net
[mailto:openstack-bounces+philip.day=hp@lists.launchpad.net] On Behalf Of
Doug Hellmann
Sent: 08 May 2012 23:34
To: Russell Bryant
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] [nova] why does notification use a topic exchange
instead
@lists.launchpad.net
*Subject:* Re: [Openstack] [nova] why does notification use a topic
exchange instead of fanout?
** **
** **
On Tue, May 8, 2012 at 6:04 PM, Russell Bryant rbry...@redhat.com wrote:
On 05/08/2012 05:59 PM, Doug Hellmann wrote:
Here is a relevant section pulled out
Cc: openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] [nova] why does notification use a topic exchange
instead of fanout?
On Tue, May 8, 2012 at 6:04 PM, Russell Bryant
rbry...@redhat.commailto:rbry...@redhat.com wrote:
On 05/08/2012 05:59 PM, Doug
@lists.launchpad.net; Russell Bryant; Doug Hellmann
*Subject:* Re: [Openstack] [nova] why does notification use a topic
exchange instead of fanout?
** **
Your own queue listener should attempt to declare the exchange, using the
same settings as Nova does.
If the exchange exists, its a noop
** **
*From:* Kiall Mac Innes [mailto:ki...@managedit.ie]
*Sent:* 09 May 2012 10:51
*To:* Day, Phil
*Cc:* openstack@lists.launchpad.net; Russell Bryant; Doug Hellmann
*Subject:* Re: [Openstack] [nova] why does notification use a topic
exchange instead of fanout?
** **
Your own queue listener
] *On Behalf Of *Doug
Hellmann
*Sent:* 08 May 2012 23:34
*To:* Russell Bryant
*Cc:* openstack@lists.launchpad.net
*Subject:* Re: [Openstack] [nova] why does notification use a topic
exchange instead of fanout?
On Tue, May 8, 2012 at 6:04 PM, Russell Bryant rbry...@redhat.com
Innes [mailto:ki...@managedit.ie]
*Sent:* 09 May 2012 10:51
*To:* Day, Phil
*Cc:* openstack@lists.launchpad.net; Russell Bryant; Doug Hellmann
*Subject:* Re: [Openstack] [nova] why does notification use a topic
exchange instead of fanout?
** **
Your own queue listener should attempt
]
*Sent:* 09 May 2012 10:51
*To:* Day, Phil
*Cc:* openstack@lists.launchpad.net; Russell Bryant; Doug Hellmann
*Subject:* Re: [Openstack] [nova] why does notification use a topic
exchange instead of fanout?
** **
Your own queue listener should attempt to declare the exchange, using
@lists.launchpad.net] *On Behalf Of
*Doug Hellmann
*Sent:* 08 May 2012 23:34
*To:* Russell Bryant
*Cc:* openstack@lists.launchpad.net
*Subject:* Re: [Openstack] [nova] why does notification use a topic
exchange instead of fanout?
On Tue, May 8, 2012 at 6:04 PM, Russell Bryant rbry
On 05/09/2012 01:57 PM, Doug Hellmann wrote:
Is that the preferred way to do it, rather than attaching another queue
to the existing exchange with the same routing key?
I would just do what you're doing now, which is to use the existing
exchange. That lets the message broker do the work of
On 05/09/2012 03:17 PM, Tihomir Trifonov wrote:
Hi Doug,
not sure if you've hit the same problem, but I've spent some time on
that when I started using RabbitMQ. As I see from the example, you've
provided:
queue = Queue(name='notifications.info',
I'm working on some code to monitor notification messages coming from nova
by listening directly on the AMQP queue. Unfortunately, nova is using a
topic exchange so it seems I can't safely consume the messages or they
might not go to some other client that is expecting to see them (especially
some
On 05/08/2012 04:19 PM, Doug Hellmann wrote:
I'm working on some code to monitor notification messages coming from
nova by listening directly on the AMQP queue. Unfortunately, nova is
using a topic exchange so it seems I can't safely consume the messages
or they might not go to some other
On Tue, May 8, 2012 at 5:45 PM, Russell Bryant rbry...@redhat.com wrote:
On 05/08/2012 04:19 PM, Doug Hellmann wrote:
I'm working on some code to monitor notification messages coming from
nova by listening directly on the AMQP queue. Unfortunately, nova is
using a topic exchange so it
On 05/08/2012 05:59 PM, Doug Hellmann wrote:
Here is a relevant section pulled out of the amqp 0-9-1 spec:
3.1.3.3 The Topic Exchange Type
The topic exchange type works as follows:
1. A message queue binds to the exchange using a routing
On Tue, May 8, 2012 at 6:04 PM, Russell Bryant rbry...@redhat.com wrote:
On 05/08/2012 05:59 PM, Doug Hellmann wrote:
Here is a relevant section pulled out of the amqp 0-9-1 spec:
3.1.3.3 The Topic Exchange Type
The topic exchange type works as follows:
The reason nova uses a topic exchange and queues like it does is so the
processing of notifications can be round-robined to multiple workers. You
should be able to open a new queue on the same exchange and receive copies of
each message.
On May 8, 2012, at 3:19 PM, Doug Hellmann wrote:
I'm
On Tue, May 8, 2012 at 7:42 PM, Monsyne Dragon mdra...@rackspace.comwrote:
The reason nova uses a topic exchange and queues like it does is so the
processing of notifications can be round-robined to multiple workers. You
should be able to open a new queue on the same exchange and receive
18 matches
Mail list logo
