Changes between Version 11 and Version 12 of Doc/gLite/TemplateCustomization


Ignore:
Timestamp:
Dec 21, 2006, 10:35:13 AM (19 years ago)
Author:
/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/gLite/TemplateCustomization

    v11 v12  
    6464For each VO listed in `VOS`, there must be a template defining the VO parameters in `vo/params`. The template name must be the same as the VO name used in `VOS`. If the VO to be added has no template to define its parameters, refer to next section about adding a new VO.
    6565
     66
     67=== Defining Site Specific Defaults for VOs ===
     68
     69It is possible to define site specific defaults for VOs that override standard default. This must be done by defining variable `VOS_SITE_PARAMS` as a nlist with an entry `DEFAULT`. The value must be the name of a structure template defining any of these properties :
     70
     71 * `create_home` : Create home directories for VO accounts. Default defined by variable `CREATE_HOME` variable.
     72 * `create_keys` : Create SSH keys for VO accounts. Default defined by variable `CREATE_KEYS` variable.
     73 * `pool_digits` : define default number of digits to use when creating pool accounts
     74 * `pool_offset` : define offset from VO base uid for the first pool account
     75 * `pool_size` : number of pool accounts to create by default for a VO
     76 * `sw_mgr_role` : description of VO software manager role. Avoid to change default.
     77
    6678=== Adding a new VO ===
    6779
     
    7183
    7284To create a template to describe a new VO, the easiest is to copy the template for an already configured VO. The main variables supported in this template are :
     85
     86 * `name` : VO official name. No default.
     87 * `account_prefix` : prefix to use when creating accounts for the VO. Generally the 3 first letters of the VO name. No default.
     88
     89 * `voms_servers` : a nlist describing VOMS server used by the VO, if any. If the VO has several (redundant) VOMS servers, this property can be a list of nlist. For each VOMS server, supported properties are :
     90   * `name` : name of the VOMS server. This is a name used internally by template. By default, template defining VOMS server certificate has the same name. No default.
     91   * `host` : VOMS server host name. No default.
     92   * `port` : VOMS server port associated with this VO. No default.
     93   * `cert` : template name, in `vo/certs` , defining VOMS server certificate. If not specified, defaults to the VOMS server name.
     94 * `voms_roles` : list of VOMS roles supported by the VO. This property is optional. For each role, the entry is a nlist with the following possible properties :
     95   * `description` : description of the VO role. This property is informational, except for VO software manager where it must be "SW manager"
     96   * `name` : VO role name, as defined on the VOMS server
     97   * `suffix` : suffix to append to `account_prefix` to build account name associated with this role.
     98 * `proxy` : name of the proxy server used by the VO. No default, optional.
     99 * `nshosts` : name:port of the RB used by the VO (Network Server). No default.
     100 * `lbhosts` : name:port of the RB used by the VO (Logging and Bookeeping). No default.
     101 * `pool_size` : number of pool accounts to create for the VO. Defaults : 200.
     102 * `pool_digits` : number of digits to use for pool accounts. Must be large enough to handle `pool_size`. Default is 3.
     103 * `base_uid` : first uid to use for the VO.
     104 * `catalog` : define catalog type used by the VO. Optional. Must be defined only for VO still using `RLS` (value must be `rls` or `RLS`).
     105 * `create_home` : Create home directories for VO accounts. Default defined by variable `CREATE_HOME` variable.
     106 * `create_keys` : Create SSH keys for VO accounts. Default defined by variable `CREATE_KEYS` variable.
    73107
    74108In addition to this template, you need to have another template defining the public key of the VOMS server used by the VO. This template has the name of the VOMS server by default. It can be explicitly defined with `cert`property of a VOMS server entry. If the new VO is using an already used VOMS server, there is no need to add the certificate.
     
    206240
    207241
    208