FedFsInstallationGuide0.9

From Linux NFS

Revision as of 23:26, 4 October 2012 by Chucklever (Talk | contribs)
Jump to: navigation, search

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.

An administrative entity that has write access to the LDAP server acting as the NSDB that can create, modify and delete the entries.

Road map for setting up a simple FedFS domain

What you need for a minimal FedFS file-access server

  • Linux NFS server that supports NFSv4 or later
  • nfsref program installed
  • libnfsjunct.so installed
  • rpc.mountd updated with junction support

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
  • Automounter installed
  • fedfs-nfs4-map program installed
  • Kernel DNS resolver upcall working

Road map for setting up a complete FedFS domain

All the items in the "minimal 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)
Personal tools