1) On hardware node:
bash# modprobe fuse
2) On hardware node:
#1 – make sure no iptablse/firewalls blocking connection to the GlusterFS server 192.168.15.104, and make sure the VPS has a private IP added that isn’t conflicting with other ip in the private range
Make sure the private IP is working in the vps , sometimes a special route rule needs to be created to send private traffic to the private interface IP due to the bridge nature of the venet interfaces – see the /etc/rc.local on the vps108 for example… i.e. make sure you can ping 192.168.15.104
#2 – install glusterfs client libraries – requires fuse module usually
--vps usually requires some special permissions – see the /etc/vz/conf/CTID.conf file
CAPABILITY="SYS_ADMIN:on "
DEVICES="c:10:229:rw "
And then from the hardware node:
# vzctl exec CTID mknod /dev/fuse c 10 229
Lthere used to be some other advanced stuff needed, but might not be needed on the newver version of Glusterfs client (http://forum.proxmox.com/threads/1252-Proxmox-GlusterFS-2-and-FUSE)
#3 – mount the parition
Create mount point, i.e. /home2
Then mount with the command:
mount -t glusterfs 192.168.15.104:/newvol /home2
usually we just put this in the /etc/rc.local file
http://gluster.org/community/documentation/index.php/Gluster_3.1:_Automatically_Mounting_Volumes
For the route add : bash# ip route add 192.168.15.0/24 via 192.168.15.XXX