| | 34 | DPM related standard templates require a site template to describe the service site configuration. 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. |
| | 35 | |
| | 36 | There is no default template provided for DPM configuration. To build your own template, you can look at template [source:/templates/trunk/site/example/site/pro_dpm_config.tpl] in examples provided with QWG templates. |
| | 37 | |
| | 38 | If you want to use Oracle version of DPM server define the following variable in your machine profile : |
| | 39 | {{{ |
| | 40 | variable DPM_SERVER_MYSQL = false; |
| | 41 | }}} |
| | 42 | |
| | 43 | As of DPM 1.5.10, the script used to publish dynamic information for DPM into BDII (space used/free per VO) has not been updated to interact properly with VOMS mapping. As a result, all VO specific pools are not counted into values published. QWG templates provide a fixed version of the script that can be installed by adding the following line to DPM head node profile : |
| | 44 | {{{ |
| | 45 | include glite/se_dpm/server/info_dynamic_voms; |
| | 46 | }}} |
| | 47 | |
| | 48 | To work properly this script requires `/opt/lcg/etc/DPMCONFIG` (or whatever file you defined for DPNS database connexion information) to be readable by world. |
| | 49 | |
