FedFsInstallNsdbAdministrator0.8
From Linux NFS
Chucklever (Talk | contribs) (Created page with "== Project: fedfs-utils == [ Project Home | News | Downloads | Docs | [[FedFsUtilsMailingList...") |
Chucklever (Talk | contribs) (→Introduction) |
||
(One intermediate revision not shown) | |||
Line 13: | Line 13: | ||
== Introduction == | == Introduction == | ||
- | A | + | 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. | ||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
- | |||
== Simple queries == | == Simple queries == | ||
Line 48: | Line 34: | ||
$ nsdb-list | $ nsdb-list | ||
+ | |||
+ | == Resolving FSNs == | ||
+ | |||
+ | The "nsdb-list" command displays a list of Fileset Names (FSNs). These represent one or more replicas of the same fileset. Each replica 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 the man page for details. |
Latest revision as of 17:30, 27 November 2012
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:
# nsdbparams update -D cn=Manager -e ou=fedfs,dc=example,dc=net ldap.example.net
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 what NCEs exist on your NSDB:
$ 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
Resolving FSNs
The "nsdb-list" command displays a list of Fileset Names (FSNs). These represent one or more replicas of the same fileset. Each replica 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 the man page for details.