Open Stack

Thats like saying you should implement a sql engine inside of Berkeley DB since so many folks like sql... Not a good fit. If you want AMQP, get an AMQP server. Zaqar's intentionally lighter weight then that. Hardly any OpenStack services use but a fraction of AMQP though, so getting oslo.messaging to support that simple subset of AMQP on top of Zaqar is much more reasonable then getting Zaqar to support all of AMQP.

Thanks,
Kevin
________________________________________
From: Gordon Sim [gsim at redhat.com]
Sent: Thursday, May 28, 2015 8:48 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Zaqar][all] Zaqar will stay... Lots of work ahead

On 05/27/2015 05:08 PM, Hayes, Graham wrote:
> It was agreed that Zaqar would look at a oslo_messaging driver for the
> services that did not agree with the 3 options presented.

Another option there would be to add amqp 1.0 support to zaqar, and then
you could use the amqp 1.0 driver with zaqar as the back-end.

(Support for an existing protocol would be beneficial for the general
messaging as a service use case also.)

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev