Changes between Version 18 and Version 19 of Doc/gLite/TemplateCustomization/Services

Timestamp:

Jan 22, 2013, 6:29:29 PM (11 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Doc/gLite/TemplateCustomization/Services

@@ -323 +323 @@
 == SE Configuration ==
 
-__Base template__ :
- * DPM : `machine-types/se_dpm`.
- * dCache : `machine-types/se_dCache`.
-
 ''Note : This section covers the generic SE configuration, not a specific implementation.''
 
@@ -364 +360 @@
 == DPM Configuration ==
 
+__Base template__ : DPM : `machine-types/se_dpm`.
+
 DPM-related standard templates require a site template to describe site/SE configuration for DPM. The variable `DPM_CONFIG_SITE` must contain the name of this template. This template defines the whole DPM configuration, including all disk servers used and is used to configure all the machines part of the DPM configuration.
 
@@ -376 +374 @@
 === DPM site parameters ===
 
-DPM configuration '''requires''' a site specific description to define configuration parameters where no sensible default value can be provided (eg. list of disk servers). To build your own template, you can look at template [source:templates/trunk/sites/example/site/glite/dpm_config.tpl site/glite/dpm_config.tpl] in examples provided with QWG templates. 
+DPM configuration '''requires''' a site specific description to define configuration parameters where no sensible default value can be provided (eg. list of disk servers). The configuration description must be the same for all nodes participating to the DPM instance. The variable `DPM_CONFIG_SITE` must point to this template. To build your own template, you can look at template [source:templates/trunk/sites/example/site/glite/dpm_config.tpl site/glite/dpm_config.tpl] in examples provided with QWG templates. 
 
 All the configuration must be done through variables in this template. The main variables available are:
@@ -397 +395 @@
 }}}
 
+An alternative to this variable is to define parameter `requestMaxAge` for `dpm` service in variable `DPM_SERVICE_PARAMS`.
+
 Avoid too low value (less than 1 month) as it may affect pinning (check the exact value of pinning default/max time in your configuration).
 
@@ -402 +402 @@
 
 
-
 == LFC Configuration ==
 
 __Base template__ : `machine-types/lfc`.
 
-LFC related standard templates require a site template to describe the service site configuration. The variable `LFC_CONFIG_SITE` must contain the name of this template.
-
-If you want to use Oracle version of LFC server define the following variable in your machine profile :
-{{{
-variable LFC_SERVER_MYSQL = false;
-}}}
+LFC configuration '''requires''' a site specific description to define configuration parameters where no sensible default value can be provided (eg. password for accessing the DB). This configuration can be ither directly in the LFC server profile or in a dedicated template pointed by variable `LFC_CONFIG_SITE`. As an example, you can look at template [source:templates/trunk/clusters/example-emi-2/profiles/lfc.example.org.tpl lfc.example.org.tpl] in examples provided with QWG templates. 
+
+All the configuration must be done through variables in this template. The main variable available is:
+ * `LFC_DB_PARAMS`: define paramaters related to the LFC DB. This is a nlist where the name of parameters must match DB related options in the [source:templates/trunk/grid/emi-2/components/dpmlfc/schema.pan schema]. Main options are :
+   * `password`: the MySQL password to be used by DPM daemons to access the DB
+   * `user`: the MySQL user to be used by DPM daemons to access the DB. Normally default should be  
+   * `adminpwd`: the MySQL aministrator password used for configuring the DB
+   * `adminuser`: the MySQL administrator user to be used for configuring the DB. Normally default should be appropriate. D: `root`.
 
 LFC 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 :
@@ -421 +422 @@
 }}}
 
-VOs listed in both lists must be present in `VOS` variable. These 2 variables have no impact on GSI (security) configuration and don't control access to the server. If you want to have `VOS` variable (controlling access to the server) matching the list of VOs supported by the LFC server (either as central or local catalogues), you can add the following definition to your LFC server profile :
+VOs listed in both lists must be present in `VOS` variable. These 2 variables have no impact on security configuration and don't control access to the server. If you want to have `VOS` variable (controlling access to the server) matching the list of VOs supported by the LFC server (either as central or local catalogues), you can add the following definition to your LFC server profile :
 {{{
 variable VOS = merge(LFC_CENTRAL_VOS, LFC_LOCAL_VOS);