Looking at the "rabbitmq" notifier, it actually just wraps rpc (so it is really
an "rpc notifier")… it won't work with the ZeroMQ driver because it breaks the
presumption that topics are "$topic.$host". Granted, that might have been
presumptuous, but nothing besides the notifier did this. I'd mu
The notification system is simply 'borrowing' some code from rpc to push
notifications. The notifications have a specified JSON message format,
documented on the wiki: http://wiki.openstack.org/NotificationSystem
As far as the notification drivers, they are very very simple.
On Apr 25, 2012,
Sure, but then the contract becomes between the notifier and the client,
presumably? I'm not as familiar with the notification system as I should be.
I haven't written a ZeroMQ notifier yet, figuring that task would be better
delayed until the move to openstack-common.
--
Eric Windisch
On
On 04/25/2012 03:22 PM, Eric Windisch wrote:
> I've heard a few people mention pulling messages off the queue, or
> communicating via RPC outside of the project, or outside of Python. In
> theory, this sounds nice, but the RPC implementations are strictly
> making sure that A can execute calls on t
4 matches
Mail list logo
