Changes between Version 14 and Version 15 of Doc/gLite/TemplateCustomization

Timestamp:

Dec 21, 2006, 3:08:58 PM (19 years ago)

Author:

/C=FR/O=CNRS/OU=UMR8607/CN=Michel Jouvin/emailAddress=jouvin@…

Comment:

--

Doc/gLite/TemplateCustomization

@@ -76 +76 @@
  * `sw_mgr_role` : description of VO software manager role. Avoid to change default.
 
-=== Adding a new VO ===
+=== Defining Site Specific Parameters for a VO ===
+
+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.
+
+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.
+
+For example, to define a site specific RB for VO Alice, create a template `vo/site/alice.tpl` in your site directory like :
+{{{
+structure template vo/site/alice;
+
+'lbhost' = 'myrb.example.org:9000';
+'nshost' = 'myrb.example.org:7772';
+}}}
+
+and add the following entry in `VOS_SITE_PARAMS` in your `pro_lcg2_config_site.tpl` :
+
+variable VOS_SITE_PARAMS = nlist ('alice', 'vo/site/alice',
+                                 );
+
+
+=== Adding a New VO ===
 
 Adding a new VO involved the creation of a template defining VO parameters. This template name must be the name you use to refer to the VO in rest of the configuration but is not required to be the real VO name (can be an alias used in the configuration). This template must be located in directory `vo/params`, in one of your cluster or site specific hierarchy of templates or in gLite templates.