FedFsInstallNsdbAdministrator0.9
From Linux NFS
Contents |
Project: fedfs-utils
[ Project Home | News | Downloads | Docs | Mailing Lists | Source Control | Issues ]
Introduction
A Namespace Database, or NSDB, is the repository for fileset location information in a FedFS domain. At its core, an NSDB is simply an LDAP server with an NSDB Container Entry, or NCE, for short. FedFS data is stored as children of this entry.
In this article, we introduce several simple command line tools that can be used to manage and troubleshoot an NSDB.
Install the NSDB admin tools
If you are running Fedora 19, you can install a packaged version of fedfs-utils-0.9. On other distributions, build fedfs-utils from scratch.
Pre-packaged install
On Fedora 19 hosts where it is secure to run administrative commands, install the NSDB tools with this command:
# yum install fedfs-utils-admin
Build from scratch
Unpack the fedfs-utils-0.9 tarball somewhere convenient, and build the package:
$ cd fedfs-utils-0.9 $ ./configure $ make
To install the NSDB admin tools:
# (cd fedfs-utils-0.9/src/nsdbc ; make install)
And install the nsdbparams command:
# (cd fedfs-utils-0.9/src/nsdbparams ; make install)
Initial NSDB configuration
This step is taken care of if you followed the directions for setting up a dedicated LDAP server as an NSDB. However, if you want to set up a pre-existing LDAP server for use as an NSDB, you can follow these steps. Suppose the existing LDAP server is at ldap.example.net, and you'd like to keep FedFS data under the DN "ou=fedfs,dc=example,dc=net" . You know the admin DN for this server (let's say it's cn=Manager, and the admin password.
First, create an entry for the new NSDB in your admin host's NSDB connection parameters database:
# nsdbparams update -D cn=Manager -e ou=fedfs,dc=example,dc=net ldap.example.net
Now you are ready to create the NCE.
$ nsdb-simple-nce -l ldap.example.net
You'll be asked for the LDAP server's admin password.
Simple queries
The NSDB hostname is almost always a parameter of each NSDB admin tool. To save yourself some typing, you can set up an environment variable containing the name of the NSDB you'll be working with.
$ export FEDFS_NSDB_HOST="ldap.example.net"
Now, see if your nsdb-simple-nce command worked:
$ nsdb-nces
This command should tell you which naming contexts host an NCE. You should see the NCE you created above. There should be no FedFS records yet, but you can confirm that with:
$ nsdb-list