Changes between Version 112 and Version 113 of Doc/gLite/TemplateCustomization


Ignore:
Timestamp:
Dec 3, 2008, 10:56:50 PM (17 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/gLite/TemplateCustomization

    v112 v113  
    275275''__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.''
    276276
    277 ''__Note__ : non shared filesystem for home directories is supported only with Globus job manager `lcgpbs`. '''This job manager is no longer available in gLite 3.1'''.''
    278 
    279 NFS file systems listed in this variable with a defined value 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.
     277''__Note__ : non shared filesystem for home directories is supported only with Globus job manager `lcgpbs`.''
     278
     279NFS server is configured on any machine (whatever its machine type) managed by Quattor and listed as the NFS server for one of the entries in `WN_SHARED_AREAS`. All actions required are done automatically. If the NFS server listed is not managed by Quattor, it is necessary to force `CREATE_HOME` to `true` on one machine.
     280
     281NFS client can be potentially configured on any machine type but by default this is done only on CE and WNs. To configure the client on other machine types, define variable `NFS_SERVER_ENABLED` to one the following values:
     282 * `undef`: configure NFS client if needed according to the configuration (`WN_SHARED_AREAS` contents).
     283 * `true`: force configuration of NFS client even though there is no NFS file system to mount on the machine.
     284
    280285
    281286=== Specifying NFS options ===
     
    306311
    307312''Note: currently `NFS_CLIENT_HOSTS` is used to build the list of hosts in `exports` file but has no impact on the mounting of file systems on clients.''
     313
     314=== Relocation of Home Directories of VO Accounts ===
     315
     316When using a NFS-served file system for home directories, the traditional approach to mount it under '/home' has several drawbacks. In particular, all service accounts also have NFS-based home directories and this may impact all services when NFS becomes unavailable or irresponsive. On the other hand, this is desirable to keep a unified configuration shared by machines sharing the NFS file systems and the other machines (e.g. WMS, VOBOX... all machines with VO accounts).
     317
     318With QWG templates this is easily done by defining variable `VO_HOMES_NFS_ROOT` to the directory parent to use for home directories on a machine with NFS client configured, when parent described in variable `VO_HOMES` is `/home`. The directory pointed by `VO_HOMES_NFS_ROOT` must correspond to an entry (or children of an entry) in `WN_SHARED_AREAS`. Look at site parameter [source:templates/trunk/site/example/site/glite/config.tpl example] for more details.
    308319
    309320=== NFS Server ===