Open jjzieve opened 6 years ago
This plugin is on life support but @Gsantomaggio definitely mentioned Docker Swarm many months ago. So if someone contributes support for it, we'll be happy to include it and then port to 3.7.x's peer discovery interface.
@jjzieve yes we planned to implement it.
In the meantime, you can use ETC2.
I wrote a post about it: https://www.erlang-solutions.com/blog/scaling-rabbitmq-on-a-coreos-cluster-through-docker.html
but you should use the image pivotalrabbitmq/rabbitmq-autocluster:3.6.14 instead of using gsantomaggio/rabbitmq-autocluster image
@michaelklishin and @Gsantomaggio thanks for the feedback, and good to know. I'd be interested in contributing, do you all have another channel for communication (i.e. irc, slack, etc.)?
Take a look at the Community section. We are not on Slack all the time but mailing list response time is usually fairly good. And, of course, there is a decent number of examples to inspect.
You mention that this plugin is on life support. Is that because it has been subsumed by rabbitmq 3.7.0? Doesn't that mean that @jjzieve is better off making contributions to the rabbitmq core repo and not the autodiscover plugin?
I'm also interested in Docker support but am willing to wait a while for it to use Docker Swarm's native service discovery capabilities if it is under development.
Please see this post.
This plugin, just like RabbitMQ 3.6.x, won't go out of use in a few months. If there's interest in adding Docker Swarm support specifically to this plugin, we would consider it. The post above should make it obvious where the future is.
I am not aware of any ongoing work on Docker Swarm.
Excuse my ignorance on how autocluster works under the hood, but are there any plans to support using the newer docker swarm mode's native service discovery?