I got confused, I cannot remember was it always that VOLs were not available to clients outside of a volume's subnet or this is new or...
something is not working here for me... I wonder.
eg.
...
Bricks:
Brick1: 10.1.0.100:/devs/00.GLUSTERs/VMs
Brick2: 10.1.0.101:/devs/00.GLUSTERs/VMs
Brick3: 10.1.0.99:/devs/00.GLUSTERs/VMs-arbiter (arbiter)
and on a client with an IP of 10.3.9.144 I can see that this request comes to the brick, but mount like this fails:
-> $ mount -t glusterfs 10.3.1.100:/VMs /mnt -o log-file=/root/gluster-mount.log
That is one...
but second - which is even more confusing to me - is, with 'auth.allow' like this:
-> $ gluster volume set VMs auth.allow 10.1.0.100,10.1.0.101,10.1.0.99
I can still mount with:
-> $ mount -t glusterfs 10.3.1.100:/VMs /mnt -o log-file=/root/test.log
this mount is on one of the peers/bricks(10.3.1.99 / 10.1.0.99)
GS is 10.3
What is happening here - I'd appreciate all comments shared.
many thanks, L.
________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://meet.google.com/cpu-eiue-hvk Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
