Changes between Version 82 and Version 83 of Doc/gLite/TemplateCustomization


Ignore:
Timestamp:
Feb 12, 2008, 11:36:22 PM (18 years ago)
Author:
jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/gLite/TemplateCustomization

    v82 v83  
    66Site customization to QWGtemplates is done through a small set of templates used to define variables used as input by QWG templates. This doesn't cover OS basic configurationt that is decribed in the page about [wiki:Doc/TemplateCustom template framework].
    77
    8 All site parameters related to QWG middleware are supposed to be declared in template `pro_lcg2_config_site.tpl`. To start a new site, import the site paramater template [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl example]. The list of all available variables with their description and their default value can be consulted in template source:templates/trunk/grid/glite-3.0.0/defaults/glite.tpl. '''This template is a critical part of standard templates and should not be modified or duplicated'''.
    9 
    10 ''Note : Information in this page may document features or configuration options not present in the current release. These information are related to changes and improvement that will be available in next release and are already present in the [source:templates/branches/gLite-3.0.0 current development branch]. If you are urgently requiring these features, [wiki:Download/QWGTemplates use content] of this branch.''
    11 
     8All site parameters related to QWG middleware are supposed to be declared in template `pro_lcg2_config_site.tpl`. To start a new site, import the site paramater template [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl example]. The list of all available variables with their description and their default value can be consulted in template source:templates/trunk/grid/glite-3.1/defaults/glite.tpl. '''This template is a critical part of standard templates and should not be modified or duplicated'''.
     9
     10''Note : Information in this page may document features or configuration options not present in the current release. These information are related to changes and improvement that will be available in next release and are already present in the [source:templates/branches/gLite-3.1 current development branch]. If you are urgently requiring these features, [wiki:Download/QWGTemplates use content] of this branch.''
     11
     12Documentation in this page is based on [source:templates/trunk/grid/glite-3.1 QWG templates for gLite 3.1]. Everything mentionned here also applies to [source:templates/trunk/grid/glite-3.0.0 QWG templates for gLite 3.0], except when explicitly stated.
    1213
    1314== Machine types ==
    … …  
    2425# Define specific configuration for a GRIF CE to be added to
    2526# standard configuration
    26 variable CE_TORQUE_CONFIG_SITE = "pro_ce_torque_grif";
     27variable CE_CONFIG_SITE = "pro_ce_torque_grif";
    2728
    2829# Configure as a CE (Torque) + Site's BDII
    29 include pro_ce_torque;
     30include machine-types/ce;
    3031
    3132#
    … …  
    3536}}}
    3637
    37 In this example, {{{CE_TORQUE_CONFIG_SITE}}} specify the name of a template defining the Torque configuration.
    38 
    39 All the machine types share a common basic configuration, described in template `machine-types/base.tpl`. This template allows to add site specific configuration to this common basic configuration (e.g. configuration of a monitoring agent). This is done by defining variable {{{GLITE_BASE_CONFIG_SITE}}} to a template containing the site specific configuration to be added to the common configuration (at the end of the common configuration). This variable can be defined, for example, in template {{{pro_site_cluster_info.tpl}}}.
     38In this example, {{{CE_CONFIG_SITE}}} specify the name of a template defining the Torque configuration.
     39
     40All the machine types share a common basic configuration, described in template `machine-types/base.tpl`. This template allows to add site specific configuration to this common base configuration (e.g. configuration of a monitoring agent). This is done by defining variable {{{GLITE_BASE_CONFIG_SITE}}} to a template containing the site specific configuration to be added to the common configuration (at the end of the common configuration). This variable can be defined, for example, in template {{{pro_site_cluster_info.tpl}}}.
     41
     42The following sections describe specific variables that can be used with each machine type. The machine type template to include is specified at the beginning of the section as ''Base template''. In addition, to get more details, you can look at [source:templates/clusters/example-3.1/profiles examples].
    4043
    4144== VO Configuration ==
    … …  
    228231''Note : when possible, this is recommended to replace default value for NFS_WN_HOSTS by one or several regexpsmatching WN names.''
    229232
     233=== NFS Server ===
     234
     235__Base template__ : `machine-types/nfs`.
     236
     237With QWG templates, it is possible to configure a machine as a dedicated NFS server whose configuration is shared with grid machines for file system configuration and accounts.
     238
    230239== LCG CE Configuration ==
    231240
     241__Base template__ : `machine-types/ce`.
     242
    232243QWG templates handle configuration of the LCG CE and the selected batch system (LRMS). To select the LRMS you want to use, you have to define variable `CE_BATCH_NAME`. '''There is no default'''. If you want to use Torque/MAUI, recommended version is `torque2`.
    233244
    … …  
    235246
    236247''Note : as of gLite 3.0.2, LRMS supported are Torque v1 (`torque1`) and Torque v2 (`torque2`), with MAUI scheduler.'' 
    237 
    238248Previous versions of QWG templates used to require definition of `CE_BATCH_SYS`. This is deprecated : this variable is now computed from `CE_BATCH_NAME`.
    239249
    … …  
    338348== SE Configuration ==
    339349
     350__Base template__ :
     351 * DPM : `machine-types/se_dpm`.
     352 * dCache : `machine-types/se_dCache`.
     353
    340354''Note : This section covers the generic SE configuration, not a specific implementation.''
    341355
    … …  
    443457=== LFC site parameters ===
    444458
     459__Base template__ : `machine-types/lfc`.
     460
    445461Normally the only thing really required in this site specific template is the password for LFC user (by default `lfc`) and the DB accounts. Look at standard LFC [source:templates/trunk/glite-3.0.0/glite/lfc/config] configuration template for the syntax.
    446462
    … …  
    468484== LCG RB Configuration ==
    469485
     486__Base template__ : `machine-types/rb`.
     487
    470488After the initial installation of the RB, it is necessary to manually initialize the MySQL database used by the RB using MyQL script provided by YAIM and then rerun NCM components for Quattor to complete the configuration, using the command :
    471489{{{
    … …  
    475493
    476494== BDII ==
     495
     496__Base template__ : `machine-types/bdii`.
    477497
    478498QWG Templates support configuration of all types of BDII :
    … …  
    534554
    535555On machine types supporting it (e.g. UI, VOBOX, WN), you can configure a FTS client. To get the client fully configured, you need to define variable `FTS_SERVER_URL` to your preferred FTS server (normally your ''closer'' T1). Look at [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl site configuration] example for more details.
     556
     557
     558== MyProxy Server ==
     559
     560__Base template__ : `machine-types/px`.
     561
     562
     563== VOBOX ==
     564
     565__Base template__ : `machine-types/vobox`.
     566
     567
     568== UI ==
     569
     570__Base template__ : `machine-types/ui`.
     571
    536572
    537573== RPMs Repositories ==