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


Ignore:
Timestamp:
Jan 22, 2013, 4:27:58 PM (11 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/gLite/TemplateCustomization/Services

    v17 v18  
    385385   * `adminuser`: the MySQL administrator user to be used for configuring the DB. Normally default should be appropriate. D: `root`.
    386386 * `DPM_ACCESS_PROTOCOLS`:  a list specifying the access protocols that must be configured on the disk servers. Possible values are: `gsiftp`, `https`, `rfio`, `xroot`.
    387  * `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.
    388  * `DPM_SERVICE_PARAMS`:
     387 * `DPM_HOSTS`; nlist describing the list of hosts for each service. Possible services (the nlist key) 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. nlist value is  the list of host (as a list, even if there is only one host).
     388 * `DPM_SERVICE_PARAMS`: configuration parameters for each service, to be applied to all hosts running the service. This variable is a nlist where the key is one of the value valid for `DPM_HOSTS`. The value must be a nlist specifying the value for each configuration parameter specified. The exact list of parameters possible depends on the service. For the exact list, look at NCM::Component::dpmlfc man page or at [source:templates/trunk/grid/emi-2/components/dpmlfc/schema.pan schema]: valid values are those under the `dpmlfc_xxx_node_config` appropriate the service.
    389389
    390390If 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).