The history of the ZeroMQ driver has been quite weird, going through stages where it completely did not work at all, to receiving a few patches to make it work and it's risked being removed from the oslo.messaging package a few times.
For a cluster at a smaller scale, I'd suggest sticking to RabbitMQ in order to avoid dealing with problems which you'll be stuck with. I also don't think the CI at OpenStack does any testing for ZeroMQ. https://wiki.openstack.org/wiki/ZeroMQ On Mon, Aug 15, 2016 at 10:14 AM, William Josefsson <[email protected]> wrote: > thx Clint! okay I will stick to RabbitMQ for now. Do you know any good > up2date guide for replacing RabbitMQ with ZeroMQ, or is the general > documentation > http://docs.openstack.org/developer/oslo.messaging/zmq_driver.html > have you tried this? > > I'm also not sure if the ZeroMQ support is here to stay, or whether it > will be removed going forward. thx will > > On Mon, Aug 15, 2016 at 3:24 AM, Clint Byrum <[email protected]> wrote: >> Excerpts from William Josefsson's message of 2016-08-14 15:39:06 +0800: >>> Hi everyone, >>> >>> I see advice in replacing RabbitMQ with ZeroMQ. I've been running 2 >>> clusters Liberty/CentOS7 with RabbitMQ now for while. The larger >>> cluster consists of 3x Controllers and 4x Compute nodes. RabbitMQ is >>> running is HA mode as per: >>> http://docs.openstack.org/ha-guide/shared-messaging.html#configure-rabbitmq-for-ha-queues. >>> >> >> For 7 real computers, RabbitMQ is actually a better choice. You get >> centralized management and the most battle-tested driver of all. >> >> ZeroMQ is meant to remove the bottleneck and SPOF of a RabbitMQ cluster >> from much larger systems by making the data path for messaging directly >> peer-to-peer, but it still needs a central matchmaker database. So at >> that scale, you're not really winning much by using it. >> >> I can't really speak to the answers for your problems that you've seen, >> but in general I'd expect Liberty and Mitaka on RabbitMQ to handle your >> cluster size without breaking a sweat. Have you reported the errors as >> bugs in oslo.messaging? That might be where to start: >> >> https://bugs.launchpad.net/oslo.messaging/+filebug >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. [email protected] W. http://vexxhost.com _______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
