Changes between Version 16 and Version 17 of Doc/gLite/TemplateCustomization/Services

Timestamp:

Jan 22, 2013, 2:02:17 PM (11 years ago)

Author:

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

Comment:

--

Doc/gLite/TemplateCustomization/Services

@@ -376 +376 @@
 === DPM site parameters ===
 
-There is no default template provided for DPM configuration. 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. 
-
-There is no default password value provided for account used by DPM daemons and for the DB accounts used to access the DPM database. You '''must''' provide one in your site configuration. If you forget to do it, you'll get a not very explicit panc error :
-{{{
-[pan-compile] *** wrong argument: operator + operand 1: not a property: element
-}}} 
+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. 
+
+All the configuration must be done through variables in this template. The main variables available are:
+ * `DPM_DB_PARAMS`: define paramaters related to the DPM 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`.
+ * `DPM_ACCESS_PROTOCOLS`:  a list specifying the access protocols that must be configured on the disk servers. Possible values are: `gsiftp`, `https`, `rfio`, `xroot`.
+ * `DPM_HOSTS`; list of hosts for each service. Possible services are: `dpm`, `dpns`, `copyd`, `srmv1`, `srmv2`, `srmv22` and `disk`. `disk` is a special value to list disk servers: on these machines, all the access protocols specified by `DPM_ACCESS_PROTOCOLS` will be configured.
+ * `DPM_SERVICE_PARAMS`:
 
 If you want to use a specific VO list on your DPM server and you have several nodes in your DPM configuration (DPM head node + disk servers), you need to write a template defining `VOS` variable (with a non default value) and define variable `NODE_VO_CONFIG` to this template in the profile of DPM nodes (both head node and disk servers).
@@ -396 +401 @@
 If you want to disable automatic purging, set the variable to `null`.
 
-
-=== Using non-standard port numbers ===
-
-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.2.0/defaults/glite/config.tpl default parameters] to find the exact name of the variable.
-
-''Note: this is not recommended to change the port number used by DPM services in normal circumstances.''
-
-=== Using a non-standard account name for dpmmgr ===
-
-If 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.2.0/users/dpmmgr.tpl users/dpmmgr.tpl].