-
-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to setup docker-vernemq on Docker Swarm #43
Comments
Hey @mitchellvanrijkom totally sorry, missed your issue here somehow. My apologies. |
Hey @ioolkos No problem! Thanks for the reply. What we would like is when we have deployed VerneMQ broker as a Service. We want to make use of the scaling functionality in docker swarm to scale the numbers of running containers to autojoin a VerneMQ cluster by a simple command instead of defining own containers with the docker run command. See Docker documentation about scaling a service: https://docs.docker.com/engine/swarm/swarm-tutorial/scale-service/. When you want to use Autojoining you are required to set a IP-address of the first VerneMQ container. In a Docker swarm we can make use of Service discovery. Swarm manager nodes assign each service in the swarm a unique DNS name and load balances running containers. You can query every container running in the swarm through a DNS server embedded in the swarm. Thereby no need to set an IP-address. Let me know if i am unclear in my explanation. Thanks in advance! |
@mitchellvanrijkom I guess this issue might be solved as part of our work in https://github.com/vernemq/vmq-discovery cc: @ioolkos, @codeadict |
Yes, that will be possible with vmq-discovery indeed.
…On Tue, Jun 26, 2018, 02:56 Andre Graf ***@***.***> wrote:
@mitchellvanrijkom <https://github.com/mitchellvanrijkom> I guess this
issue might be solved as part of our work in
https://github.com/vernemq/vmq-discovery cc: @ioolkos
<https://github.com/ioolkos>, @codeadict <https://github.com/codeadict>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKR-ABDpzK3L02h5oUL80ZpslqqhfQTks5uAdsvgaJpZM4TJ1Gb>
.
|
Any update for this? I've looked at vmq-discovery but the repo is so bare. |
Not yet, vmq-discovery is being worked slowly, work starting new year,
contributions always welcome :)
…On Wed, Dec 26, 2018, 07:11 Andida Syahendar ***@***.***> wrote:
Any update for this? I've looked at vmq-discovery but the repo is so bare.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#43 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKR-P9P58jQoSOhYchGV-fAT7JBHV5Zks5u82dhgaJpZM4TJ1Gb>
.
|
@codeadict sadly I don't know Erlang yet. Thanks anyway, keep up the good work! |
Environment
VerneMQ Version: None
OS: Docker Swarm (Docker images based on Alpine or Ubuntu)
Erlang/OTP version (if building from source):
Expected behavior
3 node VerneMQ cluster running in Docker Swarm with Docker services/stacks
Actual behaviour
Unknown. I can't find this use case in the documentation and it would be very, very nice to have it!
There is some documentation about starting a Docker container. But Docker swarm works with services/stacks that are available between the nodes.
Is it even possible to run as a service/stack or do you have start it manually on different servers?
We are comparing different MQTT brokers and those who appeal to us the most are VerneMQ and EMQ. We would like to run it in our production system but want to have native Docker Swarm support.
Thanks in advance!
The text was updated successfully, but these errors were encountered: