Changes between Version 28 and Version 29 of Doc/gLite/TemplateCustomization
- Timestamp:
- Mar 4, 2007, 5:51:07 PM (19 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/gLite/TemplateCustomization
v28 v29 67 67 === Defining Site Specific Defaults for VOs === 68 68 69 It 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. This nlist can contain one entry per VO plus an entry `DEFAULT`. Entry `DEFAULT` is used to define paramaters that will apply to all VOs . The entry key is the VO name, as used in `VOS` variable.69 It 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. This nlist can contain one entry per VO plus an entry `DEFAULT`. Entry `DEFAULT` is used to define paramaters that will apply to all VOs, other entries apply only to one specific VO. The entry key is the VO name (except for `DEFAULT`), as used in `VOS` variable. 70 70 71 71 Each entry value must be the name of a structure template or a nlist defining any of these properties : … … 80 80 * `sw_mgr_role` : description of VO software manager role. Avoid to change default. 81 81 82 === Defining Site Specific Parameters for a VO ===83 84 In addition to defining site specific defaults for VO parameters, it is possible to define site specific parameters for a specific VO. These parameters '''override''' standard parameters for the VO.85 86 This is done in much the same way as defining site specific defaults. Variable `VOS_SITE_PARAMS` must be defined as a nlist with an entry corresponding the VO name (as used in `VOS` variable). The value must be the name of a structure template. This template can define or redefine any properties supported to define value parameters.87 88 82 For example, to define a site specific RB for VO Alice, create a template `vo/site/alice.tpl` in your site directory like : 89 83 {{{ … … 95 89 96 90 and add the following entry in `VOS_SITE_PARAMS` in your `pro_lcg2_config_site.tpl` : 97 91 {{{ 98 92 variable VOS_SITE_PARAMS = nlist ('alice', 'vo/site/alice', 99 93 ); 94 }}} 95 96 Alternativly, you can define these parameters directly into `VOS_SITE_PARAMS` : 97 {{{ 98 variable VOS_SITE_PARAMS = nlist ('alice', nlist('lbhost' = 'myrb.example.org:9000', 99 'nshost' = 'myrb.example.org:7772', 100 ), 101 ); 102 }}} 100 103 101 104