FedFsInstallationGuide0.9
From Linux NFS
Chucklever (Talk | contribs) (→Road map for setting up a complete FedFS domain) |
Chucklever (Talk | contribs) (→What you need for a minimal FedFS file-access server) |
||
| Line 33: | Line 33: | ||
* Linux NFS server that supports NFSv4 or later (any recent Linux distribution) | * Linux NFS server that supports NFSv4 or later (any recent Linux distribution) | ||
| + | * rpc.mountd updated with junction support (nfs-utils 1.2.6 or later, built with the nfs-plugin.h header present) | ||
* nfsref program installed (fedfs-utils package install, or built from source) | * nfsref program installed (fedfs-utils package install, or built from source) | ||
* libnfsjunct.so installed (fedfs-utils package install, or built from source) | * libnfsjunct.so installed (fedfs-utils package install, or built from source) | ||
| - | |||
==== What you need to define a FedFS domain ==== | ==== What you need to define a FedFS domain ==== | ||
Revision as of 21:00, 8 October 2012
Contents |
Project: fedfs-utils
[ Project Home | News | Downloads | Docs | Mailing Lists | Source Control | Issues ]
Introduction
The purpose of fedfs-utils is to manage a network file namespace (a FedFS domain) that consists of multiple exports on one or more file servers. There are three roles a host can play in a FedFS domain. A host can play one or more of these roles.
- File-access client
- This is a network file system client that communicates with fileservers using a standard file-access protocol (such as NFS).
- File-access server
- This is a server that stores data or refers file-access clients to other file-access servers
- Namespace Database (NSDB)
- An NSDB node stores location information about data on file-access servers. LDAP is used to access and manage this information.
A DNS SRV record refers file-access clients to the top-most directory in a FedFS domain, which is stored in a special export on a file server.
The NSDB is optional. If an NSDB is employed, an administrative entity that has write access to the NSDB is required to create, modify and delete the entries describing FedFS filesets.
Road map for setting up a simple FedFS domain
A "simple" FedFS domain does not use a separate LDAP server to keep track of fileset locations. Only NFS basic junctions (where fileset locations are stored directly on file servers) are used.
What you need for a minimal FedFS file-access server
- Linux NFS server that supports NFSv4 or later (any recent Linux distribution)
- rpc.mountd updated with junction support (nfs-utils 1.2.6 or later, built with the nfs-plugin.h header present)
- nfsref program installed (fedfs-utils package install, or built from source)
- libnfsjunct.so installed (fedfs-utils package install, or built from source)
What you need to define a FedFS domain
- Define a domain root directory on a FedFS-enabled NFS server, then export it
- Define a DNS SRV record that points to that export
- Create NFS referrals in the root directory to other NFS servers that participate in this domain
What you need for a minimal FedFS file-access client
- Linux NFS client that supports NFSv4 or later
- Kernel DNS resolver upcall working
- Automounter installed and enabled
- fedfs-nfs4-map program installed
Road map for setting up a complete FedFS domain
A "complete" FedFS domain stores fileset location information in an LDAP server known as the domain's Namespace Database (or NSDB). Both NFS basic junctions and FedFS junctions can be used in this type of domain. All the items in the "simple" FedFS domain set up above, and:
What you need for a minimal FedFS NSDB
- An installed and configured LDAP server
- Backing database set up for the DIT that hosts FedFS entries
- The FedFS schema installed on the server
- Administrative access to the DIT that hosts FedFS entries
What you need to allow file servers to access the NSDB
- Install nsdbparams program on file servers that participate in your FedFS domain
What you need to administer junctions and NSDB connection parameters remotely
- Install rpc.fedfsd program (this is optional)
