FedFsInstallNsdbAdministrator0.9

From Linux NFS

(Difference between revisions)
Jump to: navigation, search
(Created page with "== Project: fedfs-utils == [ Project Home | News | Downloads | Docs | [[FedFsUtilsMailingList...")
 
Line 13: Line 13:
== Introduction ==
== Introduction ==
-
A ''[[FedFsGlossary#Namespace_Database|Namespace Database]]'', or NSDB, is the repository for fileset location information in a ''[[FedFsGlossary#FedFs_Domain|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.
+
A [[FedFsGlossary#Namespace_Database|Namespace Database]], or NSDB, is the repository for fileset location information in a [[FedFsGlossary#FedFs_Domain|FedFS domain]].  At its core, an NSDB is simply an LDAP server with an [[FedFsGlossary#NSDB_Container_entry|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.
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 ==
+
== Simple queries ==
-
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.  
+
First, create an entry for your NSDB in your admin host's NSDB connection parameters database.  Support your NSDB can be contacted at ldap.example.net:389, and the distinguished name of the NSDB Container Entry is "ou=fedfs,dc=example,dc=net". Then:
-
=== Pre-packaged install ===
+
# nsdbparams update -D cn=Manager -e ou=fedfs,dc=example,dc=net ldap.example.net
-
On Fedora 19 hosts where it is secure to run administrative commands, install the NSDB tools with this command:
+
The NSDB hostname and port are almost always a parameter of each NSDB admin tool.  To save yourself some typing, you can set up environment variables containing the hostname and port of the NSDB you'll be working with.
-
  # yum install fedfs-utils-admin
+
  $ export FEDFS_NSDB_HOST="ldap.example.net"
-
=== Build from scratch ===
+
By default, the standard LDAP port is assumed, so nothing else needs to be done.  But if your NSDB uses port 636, for example, you could use something like this:
-
Unpack the fedfs-utils-0.9 tarball somewhere convenient, and build the package:
+
$ export FEDFS_NSDB_PORT=636
-
$ cd fedfs-utils-0.9
+
Now, assuming you've already configured it, see if your NSDB is listening:
-
$ ./configure
+
-
$ make
+
-
To install the NSDB admin tools:
+
$ nsdb-nces
-
  # (cd fedfs-utils-0.9/src/nsdbc ; make install)
+
This command should tell you which naming contexts on your NSDB host an NSDB Container Entry. You should see the NCE you may have created earlier with the nsdb-simple-nces command. There are probably no FedFS records yet, but you can confirm that with:
-
And install the nsdbparams command:
+
$ nsdb-list
-
# (cd fedfs-utils-0.9/src/nsdbparams ; make install)
+
== Resolving FSNs ==
-
== Initial NSDB configuration ==
+
The "nsdb-list" command displays a list of Fileset Names (FSNs).  These represent filesets.  Each replica of a fileset is represented by the children FSLs also listed.
-
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.
+
You can examine one FSN more closely by copying its UUID from this list and using it as an argument of the "nsdb-resolve-fsn" command.  For example:
-
First, create an entry for the new NSDB in your admin host's NSDB connection parameters database:
+
$ nsdb-resolve-fsn b0f5d578-1e13-11e2-a64a-000c296d4dd3
-
# nsdbparams update -D cn=Manager -e ou=fedfs,dc=example,dc=net ldap.example.net
+
You can adjust the information in the children FSLs using the "nsdb-update-fsl" command.  See its man page for details.
-
 
+
-
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
+

Latest revision as of 21:22, 9 January 2013

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.

Simple queries

First, create an entry for your NSDB in your admin host's NSDB connection parameters database. Support your NSDB can be contacted at ldap.example.net:389, and the distinguished name of the NSDB Container Entry is "ou=fedfs,dc=example,dc=net". Then: 

# nsdbparams update -D cn=Manager -e ou=fedfs,dc=example,dc=net ldap.example.net

The NSDB hostname and port are almost always a parameter of each NSDB admin tool. To save yourself some typing, you can set up environment variables containing the hostname and port of the NSDB you'll be working with. 

$ export FEDFS_NSDB_HOST="ldap.example.net"

By default, the standard LDAP port is assumed, so nothing else needs to be done. But if your NSDB uses port 636, for example, you could use something like this: 

$ export FEDFS_NSDB_PORT=636

Now, assuming you've already configured it, see if your NSDB is listening: 

$ nsdb-nces

This command should tell you which naming contexts on your NSDB host an NSDB Container Entry. You should see the NCE you may have created earlier with the nsdb-simple-nces command. There are probably no FedFS records yet, but you can confirm that with: 

$ nsdb-list

Resolving FSNs

The "nsdb-list" command displays a list of Fileset Names (FSNs). These represent filesets. Each replica of a fileset is represented by the children FSLs also listed.

You can examine one FSN more closely by copying its UUID from this list and using it as an argument of the "nsdb-resolve-fsn" command. For example: 

$ nsdb-resolve-fsn b0f5d578-1e13-11e2-a64a-000c296d4dd3

You can adjust the information in the children FSLs using the "nsdb-update-fsl" command. See its man page for details.

Retrieved from "http://linux-nfs.org/wiki/index.php/FedFsInstallNsdbAdministrator0.9"
Personal tools