[
https://issues.jboss.org/browse/JGRP-1840?page=com.atlassian.jira.plugin....
]
Arne Osthues commented on JGRP-1840:
------------------------------------
My experience with docker and jgroups so far.
Running multiple containers on one host works well since all containers can connect to
each other through their default interface. For discovery using a gossip router is one
solution that works.
If the containers run on different hosts it gets more complicated. By default each
container can only be reached by its host and other containers.
The general ideas to get it working are:
* Add an extra software network layer to put the containers into the same network. There
are several tools that try to support this approach. i.E.
[
weave|https://github.com/zettio/weave] , [
pipework|https://github.com/jpetazzo/pipework]
and [
libswarm|https://github.com/docker/libswarm].
* Trying to put the load on jgroups. The different hosts can be treated like different
networks separated by a firewall. Using a TUNNEL can be a solution.
I haven't found the perfect way yet. I am still trying to avoid the need for the extra
software network since this it makes it more complicated to automate starting containers
with tools like vagrant or fig.
Provide docker image for JGroups
--------------------------------
Key: JGRP-1840
URL:
https://issues.jboss.org/browse/JGRP-1840
Project: JGroups
Issue Type: Task
Reporter: Bela Ban
Assignee: Bela Ban
Priority: Optional
Fix For: 3.6
Provide a docker image for one or more JGroups demos. People could run multiple instances
and see a cluster. Candidates for demos:
* Draw (can we set DISPLAY to be the user's desktop?)
* Topology
* Some replicated map (ReplCache)
* Chat
[1]
https://gist.github.com/goldmann/d38589ad919343ba30dd
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)