Gluster users - Oct 2017 - create volume in two different Data Centers

thanks for answering. But I have to setup and test it myself and record the
result. Can you guide me a little more. The problem is, one valid ip for
each data centers exist, and each data centers have 3 servers. How should I
config the network in which the server bricks see each other to create a
glusterfs volume?

On Tue, Oct 24, 2017 at 1:47 PM, <lemonnierk at ulrar.net> wrote:
> Hi,
>
> You can, but unless the two datacenters are very close, it'll be slow
as
> hell. I tried it myself and even a 10ms ping between the bricks is
> horrible.
>
> On Tue, Oct 24, 2017 at 01:42:49PM +0330, atris adam wrote:
> > Hi
> >
> > I have two data centers, each of them have 3 servers. This two data
> centers
> > can see each other over the internet.
> > I want to create a distributed glusterfs volume with these 6 servers,
> but I
> > have only one valid ip in each data center. Is it possible to create a
> > glusterfs volume?Can anyone guide me?
> >
> > thx alot
>
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://lists.gluster.org/mailman/listinfo/gluster-users
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20171024/9c2f5f44/attachment.html>

Il 24/10/2017 12:45, atris adam ha scritto:
> thanks for answering. But I have to setup and test it myself and
> record the result. Can you guide me a little more. The problem is, one
> valid ip for each data centers exist, and each data centers have 3
> servers. How should I config the network in which the server bricks
> see each other to create a glusterfs volume?
>
I would set up a VPN (tinc could work well).
Though probably if you have 1 public IP then you would have to forward
it to one of the internal servers.
A workaround could be to have a "floating" IP which is handled by VRRP
or similar, that depends on the gateway you have.

Have no idea on performance :-)


Alessandro
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20171024/908e8200/attachment.html>

On 24/10/17 13:01, Alessandro Briosi wrote:
> I would set up a VPN (tinc could work well).
I, too, would recommend to try tinc for this, it can automatically route
traffic of nodes that don't have direct access to other nodes via those
nodes that do.

I have a publicly available setup of Gluster over tinc on NixOS here:
https://github.com/nh2/nixops-gluster-example/
and it works pretty well, certainly tinc is not a bottleneck in it
(though note my nodes do have full mesh connectivity and I use this only
with 0.5 ms latency).