There is a new revision of this tutorial available for Fedora 13.
Creating An NFS-Like Standalone Storage Server With GlusterFS On Fedora 12
This tutorial shows how to set up a standalone storage server on Fedora 12. Instead of NFS, I will use GlusterFS here. The client system will be able to access the storage as if it was a local filesystem. GlusterFS is a clustered file-system capable of scaling to several peta-bytes. It aggregates various storage bricks over Infiniband RDMA or TCP/IP interconnect into one large parallel network file system. Storage bricks can be made of any commodity hardware such as x86_64 servers with SATA-II RAID and Infiniband HBA.
I do not issue any guarantee that this will work for you!
1 Preliminary Note
In this tutorial I use two systems, a server and a client:
- server1.example.com: IP address 192.168.0.100 (server)
- client1.example.com: IP address 192.168.0.101 (client)
Both systems should be able to resolve the other system's hostname. If this cannot be done through DNS, you should edit the /etc/hosts file so that it contains the following two lines on both systems:
[...] 192.168.0.100 server1.example.com server1 192.168.0.101 client1.example.com client1 [...]
(It is also possible to use IP addresses instead of hostnames in the following setup. If you prefer to use IP addresses, you don't have to care about whether the hostnames can be resolved or not.)
2 Setting Up The GlusterFS Server
The GlusterFS server is available as a package for Fedora 12, therefore we can install it as follows:
yum install glusterfs-server
should now show the GlusterFS version that you've just installed (2.0.9 in this case):
[[email protected] ~]# glusterfs --version
glusterfs 2.0.9 built on Jan 3 2010 00:12:49
Repository revision: v2.0.9
Copyright (c) 2006-2009 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.
[[email protected] ~]#
Next we create a few directories:
Now we create the GlusterFS server configuration file /etc/glusterfs/glusterfsd.vol (we make a backup of the original /etc/glusterfs/glusterfsd.vol file first) which defines which directory will be exported (/data/export) and what client is allowed to connect (192.168.0.101 = client1.example.com):
cp /etc/glusterfs/glusterfsd.vol /etc/glusterfs/glusterfsd.vol_orig
cat /dev/null > /etc/glusterfs/glusterfsd.vol
volume posix type storage/posix option directory /data/export end-volume volume locks type features/locks option mandatory-locks on subvolumes posix end-volume volume brick type performance/io-threads option thread-count 8 subvolumes locks end-volume volume server type protocol/server option transport-type tcp option auth.addr.brick.allow 192.168.0.101 # Edit and add list of allowed clients comma separated IP addrs(names) here subvolumes brick end-volume
Please note that it is possible to use wildcards for the IP addresses (like 192.168.*) and that you can specify multiple IP addresses separated by comma (e.g. 192.168.0.101,192.168.0.102).
Afterwards we create the system startup links for the GlusterFS server and start it:
chkconfig --levels 35 glusterfsd on