Changes between Version 119 and Version 120 of Doc/gLite/TemplateCustomization

Timestamp:

Mar 14, 2009, 5:57:30 PM (17 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Doc/gLite/TemplateCustomization

@@ -302 +302 @@
 == Shared File Systems ==
 
-It is recommended to use a shared file system mounted (at least) on CE and WNs for VO software areas. It is also sometimes convenient to use a shared file system for VO pool accounts (this is more or less a requirement to run MPI jobs). Currently, QWG templates support the use of NFS or non NFS shared file systems. Configuration is done by the following variables : 
-
- * `WN_SHARED_AREAS` : a nlist with one entry per file system which is shared between worker nodes and CE (key is the escaped file system mount point). If the filesystem is served by NFS and managed by Quattor on client and/or server, the value for each entry is the name of the NFS server and optionaly the path on the NFS server if different from the path on the worker node. Else (NFS filesystem not managed by Quattor, non NFS filesystem like AFS, LUSTRE, GPFS...) the value must be `undef`.
+It is recommended to use a shared file system mounted (at least) on CE and WNs for VO software areas. It is also sometimes convenient to use a shared file system for VO pool accounts (this is more or less a requirement to run MPI jobs). Currently, QWG templates support the use of NFS or non-NFS shared file systems but only the NFS service is configured by the templates. For other distributed file system (AFS, LUSTRE, GPFS...), you must add the necessary configuration to the site specific configuration.
+
+Configuration is done by the following variables : 
+ * `WN_SHARED_AREAS` : a nlist with one entry per file system which is shared between worker nodes and CE (key is the escaped file system mount point). See below the format of the entries for NFS-served file systems. For other distributed file systems providing a global namespace (like AFS, LUSTRE, GPFS), the value must be `undef`.
  * `NFS_AUTOFS` : when true, use `autofs` to mount NFS file systems on NFS clients. This is the recommended setting, as this is the only one to avoid complex inter-dependency in startup order. But for backward compatibility, default value is false.
 
@@ -316 +317 @@
  * `undef`: configure NFS client if needed according to the configuration (`WN_SHARED_AREAS` contents).
  * `true`: force configuration of NFS client even though there is no NFS file system to mount on the machine.
+
+=== Specifying server of a NFS file system ===
+
+In variable `WN_SHARED_AREAS`, the value of each entry specified the NFS server for the file system and optionally the file system mount point on the server if it is different than the one used on the clients. The general format for the value is a URL like:
+{{{
+nfs|nfs3|nfs4://server[/mount/point]
+}}}
+
+When the protocol specified is `nfs` (without an explicit version), `server` will be configured with both versions and client, unless an explicit version is request (see next section), will be configured with v3.
+
+The legacy format:
+{{{
+server[:/mount/point]
+}}}
+is still supported and is equivalent to:
+{{{
+nfs3://server[/mount/point]
+}}}
+
+=== Selecting NFS version to use on the client ===
+
+For NFS, both v3 and v4 are supported. When the version is specified in the protocol token of the server URL (see previous section), this version is used both on the server and on the clients. Otherwise both versions are configured on the server and the version configured on the client depends on the following variables:
+ * `NFS_CLIENT_VERSION`: a nlist with one entry per node whose key is the escaped client host name and the value is a string ('3' or '4'). If the client configured has an entry in this variable, the specified NFS version is used.
+ * `NFS_CLIENT_DEFAULT_VERSION`: a nlist where entry keys are either an escaped regexp matched against the node being configured or 'DEFAULT'. If host name of the client being configured is matched by one of the regexp, the specified value is used. Else if `DEFAULT` entry is present it is used.
+ * If no match was found with the previous variables, v3 is used.
+
+Suppose you want to configure v4 on all your grid nodes and only on these nodes and that their host names always start with prefix `grid` and belonging to domain `example.org`, you can use the following definition:
+{{{
+variable NFS_CLIENT_DEFAULT_VERSION = nlist(
+  'DEFAULT',                                   '3',
+  '^grid.*\.example\.org$',           '4',
+);
+}}}