Changes between Version 171 and Version 172 of Doc/gLite/TemplateCustomization


Ignore:
Timestamp:
May 11, 2010, 9:27:44 AM (15 years ago)
Author:
/C=UK/O=eScience/OU=CLRC/L=RAL/CN=richard hellier
Comment:

Minor typo and clarity changes

Legend:

Unmodified
Added
Removed
Modified

  • Doc/gLite/TemplateCustomization

    v171 v172  
    1414''Note: this documentation often makes reference to a template called `site/glite/config.tpl`. This template used to be called `pro_lcg2_config_site.tpl` in the past. Both names are valid and taken into account by current templates, even though the namespaced name is the recommended one.''
    1515
    16 = Service-Independant Configuration =
     16= Service-Independent Configuration =
    1717
    1818This section contains information about how to tweak machine describe site configuration and how to build services shared by several node types, like VO configuration, LCAS/LCMAPS, Globus...
    … …  
    137137=== Site-Specific Defaults for VO Parameters === #VODefaultParams
    138138
    139 It is possible to define site specific defaults for VOs that override standard default. This must be done by defining entry `DEFAULT` in  nlist variable `VOS_SITE_PARAMS`. This entry is used to define paramaters that will apply to all VOs if they are not defined explicitly in VO parameters.
     139It is possible to define site-specific defaults for VOs that override standard default. This must be done by defining entry `DEFAULT` in  nlist variable `VOS_SITE_PARAMS`. This entry is used to define paramaters that will apply to all VOs if they are not defined explicitly in VO parameters.
    140140
    141141Each entry value must be the name of a structure template or a nlist defining any of these properties :
    … …  
    558558 * `@VOALIAS@` : will be expanded to the VO alias name locally defined. When possible, it is better to use the VO full name which is unique and will not change.
    559559
    560 For example, the following variable create one directory per VO under `/home` and accounts for each VOs will be created in the VO-specific directory:
     560For example, the following variable create one directory per VO under `/home` and accounts for each VO will be created in the VO-specific directory:
    561561{{{
    562562variable VO_HOMES ?= nlist(
    … …  
    729729The main variable to enable profile cloning (currently supported only for gLite WN) is `USE_DUMMY`. It is `false` by default and must be set to `true` to enable profile cloning. This variable must be defined to `true` on all WNs, including the reference one (''exact node'').
    730730
    731 To use profile cloning, in additon to enable its use, you need to define a set of variables, generally in a common profile called by all WNs. This is generally done by creating a site-specific machine type for the WN (typically in `sites/xxx/machine-types/xxx/wn`, be sure no to overload standard `machine-types/wn`) that will do all the necessary initializations and include the standard `machine-types/wn`.
     731To use profile cloning, in additon to enable its use, you need to define a set of variables, generally in a common profile called by all WNs. This is generally done by creating a site-specific machine type for the WN (typically in `sites/xxx/machine-types/xxx/wn`, be sure not to overload standard `machine-types/wn`) that will do all the necessary initializations and include the standard `machine-types/wn`.
    732732
    733733The variables you need to define for profile cloning to work are:
    … …  
    816816
    817817
    818 === Using non standard port numbers ===
    819 
    820 It is possible to use non standard port numbers for DPM daemons `dpm`, `dpns` and all SRM daemons. To do this, you  need to define the `XXX_PORT` variable corresponding to the service in your gLite site parameters. Look at gLite [source:templates/trunk/grid/glite-3.0.0/defaults/glite.tpl default parameters] to find the exact name of the variable.
     818=== Using non-standard port numbers ===
     819
     820It is possible to use non-standard port numbers for DPM daemons `dpm`, `dpns` and all SRM daemons. To do this, you  need to define the `XXX_PORT` variable corresponding to the service in your gLite site parameters. Look at gLite [source:templates/trunk/grid/glite-3.0.0/defaults/glite.tpl default parameters] to find the exact name of the variable.
    821821
    822822''Note: this is not recommended to change the port number used by DPM services in normal circumstances.''
    823823
    824 === Using a non standard account name for dpmmgr ===
     824=== Using a non-standard account name for dpmmgr ===
    825825
    826826If you want to use an account name different from `dpmmgr` to run DPM daemons, you need to define variable `DPM_DAEMON_USER` in your site configuration template and provide a template to create this account, based on [source:templates/trunk/grid/gLite-3.0.0/users/dpmmgr.tpl users/dpmmgr.tpl].
    … …  
    838838}}}
    839839
    840 LFC templates allow a LFC server to act as a central LFC server (registered in BDII) for somes VOS and as a local LFC server for the others. This are 2 variables controlling what is registered in the BDII :
     840LFC templates allow a LFC server to act as a central LFC server (registered in BDII) for some VOs and as a local LFC server for the others. This are 2 variables controlling what is registered in the BDII :
    841841 * `LFC_CENTRAL_VOS` : list of VOs for which the LFC server must be registered in BDII as a central server. Default is an empty list.
    842842 * `LFC_LOCAL_VOS` : list all VOs for which the server must be registered in BDII as a local server. Default to all supported VOs (`VOS`variable). If a VO is in both lists, it is removed from `LFC_LOCAL_VOS`. If you don't want this server to be registered as a local server for any VO, even if configured on this node (present in `VOS` list), you must define this variable as an empty list :
    … …  
    866866 * `alias` : DNS alias to use to register this LFC server into the BDII
    867867 
    868 === Using non standard port numbers ===
    869 
    870 It is possible to use non standard port numbers for LFC daemons. To do this, you only need to define the `XXX_PORT` variable corresponding to the service. Look at gLite [source:templates/trunk/grid/glite-3.0.0/defaults/glite.tpl default parameters] to find the exact name of the variable.
     868=== Using non-standard port numbers ===
     869
     870It is possible to use non-standard port numbers for LFC daemons. To do this, you only need to define the `XXX_PORT` variable corresponding to the service. Look at gLite [source:templates/trunk/grid/glite-3.0.0/defaults/glite.tpl default parameters] to find the exact name of the variable.
    871871
    872872''Note: this is not recommended to change the port number used by LFC services in normal circumstances.''
    873873
    874 === Using a non standard account name for lfcmgr ===
     874=== Using a non-standard account name for lfcmgr ===
    875875
    876876If you want to use an account name different from `lfcmgr` to run LFC daemons, you need to define variable `DPM_USER` in your site configuration template and provide a template to create this account, based on [source:templates/trunk/grid/gLite-3.0.0/users/lfcmgr.tpl users/lfcmgr.tpl].
    … …  
    884884 * `machine-types/wmslb` : a combined WMS/LB node (not recommended).
    885885 
    886 WMS and LB are 2 inter-related services : a complete WMS is made of at least one WMS and 1 LB. For scalability reasons, it is recommended to run WMS and LB on several machines : 1 LB should scale to 1M+ jobs per day where 1 WMS scales only to 20 Kjobs per day. Several WMS can share the same LB. Don't expect a combined WMS/LB to scale upper than 10 Kjobs/day. And be aware that a WMS needs a lot of memory: 4 GB is the required minimum.
     886WMS and LB are 2 inter-related services : a complete WMS is made of at least one WMS and 1 LB. For scalability reasons, it is recommended to run WMS and LB on several machines : 1 LB should scale to 1M+ jobs per day where 1 WMS scales only to 20 Kjobs per day. Several WMS can share the same LB. Don't expect a combined WMS/LB to scale to more than 10 Kjobs/day. And be aware that a WMS needs a lot of memory: 4 GB is the required minimum.
    887887
    888888WMS and LB site-specific configuration is normally kept in one template, even if they run on several machines, to maintain consistency. Variable `WMS_CONFIG_SITE` must be defined to the name of this template, even for a LB. If you want to use a separate template to configure LB (not recommended), you can also use LB-specific variable, `LB_CONFIG_SITE`.
    … …  
    895895 * `WMS_LB_SERVER_HOST` : define LB used by this WMS. Keep default value on a combined WMS/LB.
    896896
    897 In addition to these variables, there are several variables to tune performances of WMS, in particular its load monitor subsystem. Look at [source:templates/trunk/grid/glite-3.0.0/glite/wms/config.tpl glite/wms/config.tpl] and templates provided with `ncm-wmslb` component for a list of all available variables. Defaults should be appropriate, avoid to modify these variables without a clear reason to do that. In particular avoid to set too high thresholds as it may lead to WMS machine to be very much overloaded and service response time to be very bad. Most of the variables are related to WM component of WMS. The main ones are:
     897In addition to these variables, there are several variables to tune performances of WMS, in particular its load monitor subsystem. Look at [source:templates/trunk/grid/glite-3.0.0/glite/wms/config.tpl glite/wms/config.tpl] and templates provided with `ncm-wmslb` component for a list of all available variables. The defaults should be appropriate; avoid modifying these variables without a clear reason to do so. In particular avoid setting too high thresholds as it may lead to WMS machine to be very much overloaded and service response time to be very bad. Most of the variables are related to the WM component of WMS. The main ones are:
    898898 * `WMS_WM_EXPIRY_PERIOD` : maximum time in seconds to retry match making in case of failure to find a resource compatible with requirements. Default: 2 hours.
    899899 * `WMS_WM_MATCH_RETRY_PERIOD` : Interval in seconds between 2 match making attempts. Must be less than `WMS_WM_EXPIRY_PERIOD`. Default : 30 mn.
    … …  
    931931 * `BDII_SUBSITE_ONLY` (gLite 3.1 only) : if false, allow to run both subsite and site BDII on the same machine. Default : true.
    932932 * `BDII_USE_FCR` : set to false to disable use of FCR (Freedom of Choice) on top-level BDII or to true to force its use on other BDII types. This value is ignored if BDII type is not `top`. Default is `true`.
    933  * `BDII_FCR_URL` : use a non standard source for FCR.
     933 * `BDII_FCR_URL` : use a non-standard source for FCR.
    934934
    935935Starting with QWG templates [milestone:gLite-3.0.2-13 gLite-3.0.2-13], all machine types publishing information into BDII (almost all except WN, UI and disk servers) are using a BDII configured as a ''resource BDII'' for this purpose. In addition all these machine types can also be configured as a [#siteBDII site]/[#subsiteBDII subsite] BDII by defining appropriate variable into node profile (`BDII_TYPE='site'` and if applicable `BDII_SUBSITE`).