FedFsInstallNsdbConnParams0.8
From Linux NFS
Chucklever (Talk | contribs) (Created page with "== Project: fedfs-utils == [ Project Home | News | Downloads | Docs | [[FedFsUtilsMailingList...") |
Chucklever (Talk | contribs) (→Create the database and add an NSDB) |
||
| (3 intermediate revisions not shown) | |||
| Line 13: | Line 13: | ||
== Introduction == | == Introduction == | ||
| - | + | Before a fileserver can create and resolve FedFS junctions, or a FedFS administrative client can contact an NSDB, information about how to connect to the NSDB must be stored locally. This information consists of details about the NSDB's hostname and port number, possibly an x.509 certificate that can authenticate the NSDB, and other information. This information is known as an NSDB's [[FedFsGlossary#NSDB_Connection_Parameters|connection parameters]]. | |
| - | + | '''Note:''' ''using an x.509 certificate is not supported in fedfs-utils-0.8, but will be in a future fedfs-utils release.'' | |
| - | Setting up the NSDB connection parameters database is a simple step, but is a requirement for fileservers and administrative tools that connect to a FedFS domain's NSDB. | + | On Linux, these parameters are stored in a database on each fileserver that accesses NSDBs. Setting up the NSDB connection parameters database is a simple step, but is a requirement for fileservers and administrative tools that connect to a FedFS domain's NSDB. This article describes how to populate an NSDB connection parameter database on fileservers and administrative clients. |
| - | == | + | == Create the database and add an NSDB == |
| - | + | NSDBs are identified by their hostname and port number. If the port number isn't specified, the standard LDAP port 389 is assumed. | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | ||
| - | + | For example, suppose your NSDB will reside on the host nsdb.example.net, and it listens on the standard LDAP port. On your fileserver, start with this: | |
# nsdbparams update nsdb.example.net | # nsdbparams update nsdb.example.net | ||
| - | This allows the fileserver to contact this LDAP server to resolve junctions. The fileserver will use | + | This allows the fileserver to contact this LDAP server to resolve junctions. The fileserver will use cleartext LDAP requests. The act of creating a record for the first NSDB automatically initializes the NSDB connection parameter database on your fileserver. |
To see information about this NSDB's connection parameters, use: | To see information about this NSDB's connection parameters, use: | ||
| Line 41: | Line 33: | ||
# nsdbparams show nsdb.example.net | # nsdbparams show nsdb.example.net | ||
| - | Each NSDB that your fileserver contacts must have an entry in the fileserver's NSDB connection parameters database. For example, a fileserver in a FedFS domain that employs a single NSDB typically has just one entry in its NSDB connection parameter database. | + | Each NSDB that your fileserver contacts must have an entry in the fileserver's NSDB connection parameters database. For example, a fileserver in a FedFS domain that employs a single NSDB typically has just one entry in its NSDB connection parameter database. However, if there are junctions on your fileserver that target fileservers in other FedFS domains, those remote NSDBs must be first identified to your fileserver using the nsdbparams command. |
=== Additional parameters === | === Additional parameters === | ||
Latest revision as of 17:25, 27 November 2012
Contents |
Project: fedfs-utils
[ Project Home | News | Downloads | Docs | Mailing Lists | Source Control | Issues ]
Introduction
Before a fileserver can create and resolve FedFS junctions, or a FedFS administrative client can contact an NSDB, information about how to connect to the NSDB must be stored locally. This information consists of details about the NSDB's hostname and port number, possibly an x.509 certificate that can authenticate the NSDB, and other information. This information is known as an NSDB's connection parameters.
Note: using an x.509 certificate is not supported in fedfs-utils-0.8, but will be in a future fedfs-utils release.
On Linux, these parameters are stored in a database on each fileserver that accesses NSDBs. Setting up the NSDB connection parameters database is a simple step, but is a requirement for fileservers and administrative tools that connect to a FedFS domain's NSDB. This article describes how to populate an NSDB connection parameter database on fileservers and administrative clients.
Create the database and add an NSDB
NSDBs are identified by their hostname and port number. If the port number isn't specified, the standard LDAP port 389 is assumed.
For example, suppose your NSDB will reside on the host nsdb.example.net, and it listens on the standard LDAP port. On your fileserver, start with this:
# nsdbparams update nsdb.example.net
This allows the fileserver to contact this LDAP server to resolve junctions. The fileserver will use cleartext LDAP requests. The act of creating a record for the first NSDB automatically initializes the NSDB connection parameter database on your fileserver.
To see information about this NSDB's connection parameters, use:
# nsdbparams show nsdb.example.net
Each NSDB that your fileserver contacts must have an entry in the fileserver's NSDB connection parameters database. For example, a fileserver in a FedFS domain that employs a single NSDB typically has just one entry in its NSDB connection parameter database. However, if there are junctions on your fileserver that target fileservers in other FedFS domains, those remote NSDBs must be first identified to your fileserver using the nsdbparams command.
Additional parameters
There is some additional information that can be stored in a NSDB connection parameter database.
On your administrative hosts, it is convenient to specify the NSDB administrative DN and the NCE to use for administrative operations. If you do this, you don't need to specify these each time you invoke an NSDB administrative tool. Use the -D option to specify the admin DN, and the -e option to specify the default NCE. For example:
# nsdbparams update -D cn=Manager,cn=config -e ou=fedfs,dc=example,dc=net nsdb.example.net
These settings apply only to one NSDB.
