Changes between Version 86 and Version 87 of Doc/gLite/TemplateCustomization


Ignore:
Timestamp:
Apr 15, 2008, 10:28:35 AM (18 years ago)
Author:
jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/gLite/TemplateCustomization

    v86 v87  
    486486== LCG RB Configuration ==
    487487
     488''__Note__ : LCG RB is a deprecated service, replaced by gLite WMS. It is available only in gLite 3.0.''
     489
    488490__Base template__ : `machine-types/rb`.
    489491
     
    493495}}}
    494496
     497
     498== gLite WMS and LB ==
     499
     500__Base templates__ :
     501 * `machine-types/wms` : a WMS only node.
     502 * `machine-types/lb` : a LB only node.
     503 * `machine-types/wmslb` : a combined WMS/LB node (not recommended).
     504 
     505WMS 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.
     506
     507WMS 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 .
     508
     509List of VOs supported by WMS, if not your default list as defined in your [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl site-specific parameters], must be defined in another template that will be included very early in the configuration. Variable `NODE_VO_CONFIG` must be defined to the name of this template. This template generally contains only variable `VOS` definition.
     510
     511Main variables available to customize WMS and LB configuration are :
     512 * `LB_MYSQL_ADMINPWD` : password of MySQL administrator account. There is no default, be sure to define to a non empty string.
     513 * `LB_TRUSTED_WMS` : a list of DN matching host DN of all WMS allowed to use this LB. May remain empty (default) on a combined WMS/LB.
     514 * `WMS_LB_SERVER_HOST` : define LB used by this WMS. Keep default value on a combined WMS/LB.
     515
     516In 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 shuld be appropriate, avoid to modify these variables without a clear reason to do that.
     517
     518=== Load Monitor ===
     519
     520WMS has an integrated feature to monitor load on the machine it runs on and refuse to accept new jobs if the load is higher than defined thresholds. Available variables to define threshold are :
     521 * `WMS_LOAD_MONITOR_CPU_LOAD1` :  maximum CPU load averaged on 1 minute (as defined by `top` or `xload`). Default : 10.
     522 * `WMS_LOAD_MONITOR_CPU_LOAD5` : maximum CPU load averaged on 1 minute (as defined by `top` or `xload`). Default : 10.
     523 * `WMS_LOAD_MONITOR_CPU_LOAD15` :  maximum CPU load averaged on 1 minute (as defined by `top` or `xload`). Default : 10.
     524 * `WMS_LOAD_MONITOR_DISK_USAGE` : maximum usage (in percent) of any file system present on the machine. Default : 95 (%).
     525 * `WMS_LOAD_MONITOR_FD_MIN` :  minimum number of free file descriptors. Default : 500.
     526 * `WMS_LOAD_MONITOR_MEMORY_USAGE` :  maximum usage (in percent) of virtual memory. Default : 95 (%).
    495527
    496528== BDII ==