Context Navigation

TemplateCustomization

Timestamp:: Jan 29, 2007, 11:07:44 PM (19 years ago)
Author:: /C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

Doc/gLite/TemplateCustomization

-              v22
+              v23
  * `pool_digits` : define default number of digits to use when creating pool accounts
  * `pool_offset` : define offset from VO base uid for the first pool account
+ * `pool_start` : index of the first pool accounts to create for a VO
  * `pool_size` : number of pool accounts to create by default for a VO
  * `sw_mgr_role` : description of VO software manager role. Avoid to change default.
 …
 There are a couple of variables available to customize VO specific areas (software area, VO accounts home directories...) :
  * `VO_SW_AREAS` : a nlist with one entry per VO (key is the VO name as used in `VOS` variable). The value is a directory to use for the VO software area. Be sure to list this directory or its parent in `WN_NFS_AREA` if you want to use a shared filesystem for this area (this is highly recommended).
+ * `VO_SW_AREAS` : a nlist with one entry per VO (key is the VO name as used in `VOS` variable). The value is a directory to use for the VO software area. Be sure to list this directory or its parent in `WN_SHARED_AREAS` if you want to use a shared filesystem for this area (this is highly recommended). Directories listed in this variable will be created with the appropriate permissions (`0755` for VO group).
  * `VO_HOMES` : a nlist with one entry per VO (key is the VO name as used in `VOS` variable). The value is a directory prefix to use when creating home directories for accounts. A suffix will be added to this name corresponding to the VO role suffix for role accounts or the the account number for pool accounts. By default, VO accounts are created in `/home`.
  * `VO_SWMGR_HOMES` : a nlist with one entry per VO (key is the VO name as used in `VOS` variable). The value is a directory to use as the home directory for the VO software manager. If there is not entry for a VO, VO_HOMES is used. Main purpose of this variable is to define home directory for the software manager as the VO software area. This can be achieved easily by assigning `VO_SW_AREAS` to this variable.
  * `CREATE_HOME` : this variable controls creation of VO accounts home directories. It accepts 3 values : `true`, `false` and `undef`. `undef` is a ''conditional true'' : home directories is not created if it resides on a NFS shared file system (it is listed in `WN_NFS_AREAS`) and the NFS server is not the current machine.
+ * `CREATE_HOME` : this variable controls creation of VO accounts home directories. It accepts 3 values : `true`, `false` and `undef`. `undef` is a ''conditional true'' : home directories are not created if they reside on a NFS shared file system (it is listed in `WN_SHARED_AREAS`) and the NFS server is not the current machine.
 === Tuning VO configuration on a specific node ===
 …
 Each machine type templates define VO configuration (pool accounts, gridmap file/dir...) appropriate to the machine type. If you want to change this configuration, on a specific node, you can use the following variables :
  * `NODE_VO_POOLACCOUNTS` (boolean) : pool account must be created for each VO initialized. Default : true.
  * `NODE_VO_GRIDMAPDIR_CONFIG` (boolean) : gridmapdir entries must be initialized for pool accounts. Default : `NODE_VO_POOLACCOUNTS` variable.
+ * `NODE_VO_ACCOUNTS` (boolean) : VO accounts must be created for each VO initialized. Default : true.
+ * `NODE_VO_GRIDMAPDIR_CONFIG` (boolean) : gridmapdir entries must be initialized for pool accounts. Default : `false`.
  * `NODE_VO_WLCONFIG` (boolean) : initialize workload management environment for each VO. Normally enabled only on resource brokers. Default : false.
  * `NODE_VO_CREATEHOME` (boolean) : create home directories for pool accounts. Default : true.
 …
 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 shared file systems. Configuration is done by the following variables :
  * `WN_NFS_AREAS` : a nlist with one entry per file system that must be NFS mounted on worker nodes (key is the escaped file system mount point). 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.
+ * `WN_SHARED_AREAS` : a nlist with one entry per file system that must be NFS mounted on worker nodes (key is the escaped file system mount point). 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.
  * `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.
+File systems listed in this variable are mounted on CE and WNs. The NFS server for the file systems can be a CE, a SE or any other machines that includes `machine-types/nfs`.
+''__Note__ : variable WN_NFS_AREAS has been deprecated and replaced by WN_SHARED_AREAS. It the latter is not defined, WN_NFS_AREAS is used if defined.''
+File systems listed in this variable are mounted on CE and WNs. The NFS server for the file systems can be any machine types and is not required to be managed by Quattor (but in this case, you probably need to force `CREATE_HOME` to `true` on one machine). If it is managed by Quattor, all actions required are done automatically.
 == LCG CE Configuration ==