| 46 | | |
| 47 | | == Template Customization == |
| 48 | | |
| 49 | | Despite the change in template layout, LCG2 [wiki:Doc/LCG2/TemplateLayout template customization] is still valid for gLite3. Refer to this description, except for components with an explicit description provided here. |
| 50 | | |
| 51 | | === Allocation of Service Accounts === |
| 52 | | |
| 53 | | Some services allow to define a specific account to be used to run the service. In this case, there is one template for each of these accounts in `common/users`. The name of the template generally matches the user account created or, when the template is empty, the name of the service. |
| 54 | | |
| 55 | | A site can redefine account names or characteristics (uid, home directory...). To do this, you should not edit directly the standard templates as the changes will be lost in the next version of the template (or you will have to redo them by hand). You should create a `users` directory somewhere in your site or cluster hierarchy (e.g. under the `site` directory, not directly at the same level else it will not work without adjusting `cluster.build.properties`) and put your customized version of the template here. |
| 56 | | |
| 57 | | '''Note : don't change the name of the template, even if you change the name of the account used''' (else you'll need to modify standard templates needing this user). |
| 58 | | |
| 59 | | === Accepted CAs === |
| 60 | | |
| 61 | | There is one template defining all the accepted CAs. We generally produced a new one each time there is a new release of the list of CAs officially accepted by EGEE. If you need to adjust it, create a site or cluster specific copy of `common/security/cas.tpl` in a directory `common/security`. |
| 62 | | |
| 63 | | === DPM Configuration === |
| 64 | | |
| 65 | | === LFC Configuration === |
| 66 | | |
| 67 | | 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. |
| 68 | | |
| 69 | | Normally the only thing really required in this site specific template is the password for LFC user (by default `lfc`) and the MySQL administrator (by default `root`). There a no default value provided for these password. Look at standard LFC [source:templates/trunk/glite-3.0.0/glite/lfc/config] configuration template for the syntax. |
| 70 | | |
| 71 | | If you want to use Oracle version of LFC server define the following variable in your machine profile : |
| 72 | | {{{ |
| 73 | | variable LFC_SERVER_MYSQL = false; |
| 74 | | }}} |
| 75 | | |
| 76 | | LFC templates allow a LFC server to act as a central LFC server (registered in BDII) for somes VOS and as a local LFC server for the others. This are 2 variables controlling what is registered in the BDII : |
| 77 | | * `LFC_CENTRAL_VOS` : list of VOs for which the LFC server must be registered in BDII as a central server. Default is an empty list. |
| 78 | | * `LFC_LOCAL_VOS` : list all VOs for which the server must be registered in BDII as a local server. Default to all supported VOs (`VOS`variable). If a VO is in both lists, it is removed from `LFC_LOCAL_VOS`. If you don't want this server to be registered as a local server for any VO, even if configured on this node (present in `VOS` list), you must define this variable as an empty list : |
| 79 | | {{{ |
| 80 | | variable LFC_LOCAL_VOS = list(); |
| 81 | | }}} |
| 82 | | |
| 83 | | 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. |
| 84 | | |
| 85 | | |
| 86 | | |
| 87 | | |
| 88 | | |
