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',
>
> exchange=Exch
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 du
r – so both consumers need to declare and use the
>>>> same exchange.
>>>>
>>>> ** **
>>>>
>>>> But If I understand the next step right, to get multiple consumers of
>>>> info notification messages they would all need to
> ** **
>>>
>>> But If I understand the next step right, to get multiple consumers of
>>> info notification messages they would all need to create separate “
>>> notifications.info” queues into that exchange. And isn’t that
>>> exactly what Nova currently d
>> But If I understand the next step right, to get multiple consumers of
>>>> info notification messages they would all need to create separate “
>>>> notifications.info” queues into that exchange.And isn’t that
>>>> exactly what Nova currently does t
notifications.info” queues into that exchange. And isn’t that
>>> exactly what Nova currently does to create a shared queue ?
>>>
>>> ** **
>>>
>>> Phil
>>>
>>> ** **
>>>
>>> *From:* Kiall Mac Innes [mailto:ki.
all need to create separate “
>> notifications.info” queues into that exchange.And isn’t that exactly
>> what Nova currently does to create a shared queue ?
>>
>> ** **
>>
>> Phil
>>
>> ** **
>>
>> *From:* Kiall Mac Innes [mailto:ki...@managedit.ie
to: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"?
>
> ** **
&g
gt;=hp@lists.launchpad.net<mailto:hp@lists.launchpad.net>]
On Behalf Of Doug Hellmann
Sent: 08 May 2012 23:34
To: Russell Bryant
Cc: openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>
Subject: Re: [Openstack] [nova] why does notification use a "topic" e
es+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 notif
me exchange ?
Cheers,
Phil
From: openstack-bounces+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] [nov
On Tue, May 8, 2012 at 7:42 PM, Monsyne Dragon wrote:
> 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 messag
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 6:04 PM, Russell Bryant 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:
> >
> >1.
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 5:45 PM, Russell Bryant 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 seems I can't sa
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 c
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
18 matches
Mail list logo
