Context Navigation

TemplateCustomization

Timestamp:: Nov 26, 2007, 5:58:59 PM (18 years ago)
Author:: jouvin
Comment:: Document site/subsite BDII configuration

Legend:

: Unmodified
: Added
: Removed
: Modified

Doc/gLite/TemplateCustomization

-              v73
+              v74
 When configuring BDII on a machine, the following variables can be used (in the machine profile or in a site specific template) to tune the configuration :
  * BDII_TYPE : can be `resource`, `site`, `top`. `top` is the default, except if deprecated variable `SITE_BDII` is true.
  * BDII_SUBSITE : name of the BDII sub-site. Ignored on any BDII except `site`. Must be empty for the main site BDII (default) or defined to the sub-site name if this is a subsite BDII.
  * BDII_USE_FCR : set to false to disable use of FCR (Freedom of Choice) on top-level BDII or to true to force its use on other BDII types.
  * BDII_FCR_URL : use a non standard source for FCR.
+ * BDII_URLS (site BDII only) : nlist of URLs corresponding to the Globus MDS or resource BDII URLs to aggregate on the site BDII. Key is a arbitrary name (like `CE`, `DPM1`...) and value is the URL. See [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl site configuration] example.
+ * `BDII_TYPE` : can be `resource`, `site`, `top`. `top` is the default, except if deprecated variable `SITE_BDII` is true.
+ * `BDII_SUBSITE` : name of the BDII sub-site. Ignored on any BDII except `site`. Must be empty for the main site BDII (default) or defined to the sub-site name if this is a subsite BDII.
+ * `BDII_USE_FCR` : set to false to disable use of FCR (Freedom of Choice) on top-level BDII or to true to force its use on other BDII types.
+ * `BDII_FCR_URL` : use a non standard source for FCR.
 Starting with QWG templates [milestone:gLite-3.0.2-13 gLite-3.0.2-13], all machine types publishing information into BDII (almost all except WN, UI and disk servers) are using BDII configured as a ''resource BDII'' for this purpose. In addition all these machine types can be configured as a site/subsite BDII by definining appropriate variable into node profile (`BDII_TYPE='site'` and if applicable `BDII_SUBSITE`). This ''combined BDII'' configuration is the default on a LCG CE : define `BDII_TYPE=resource` in CE profile to change it.
 ''Note : combined BDII is the default on LCG CE for backward compatibility. But it is highly recommended to run the ''site BDII'' on another machine type.''
+=== Configuring BDII URLs on a site BDII ===
+A site BDII aggretates information published by several other BDIIs, typically resource BDIIs or subsite BDIIs. List of resources to aggregate are specicified by variable `BDII_URLS`. This variable is typically defined in site parameters, [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl pro_lcg2_config_site.tpl], and is ignored on all nodes except a site (or combined) BDII.
+Variable `BDII_URLS` is nlist of URLs corresponding to the Globus MDS or resource BDII URLs to aggregate on the site BDII. Key is a arbitrary name (like `CE`, `DPM1`...) and value is the URL. See [source:templates/trunk/sites/example/site/pro_lcg2_config_site.tpl site configuration] example.
+`BDII_URLS` can contain an entry for a ''combined BDII''. When configuring BDII on this server, this entry will be transparently removed. This allows to move site BDII server to another machine already running a resource BDII without editing `BDII_URLS`.
+''Note : mds-vo-name on a combined BDII is the site or subsite name (not `resource`), even for local services.''
+''Restriction : each BDII in BDII hierarchy '''must''' use a different `mds-vo-name`. Thus it is not possible to use site BDII `mds-vo-name` in `BDII_URLS` or this will be considered as a loop and the entry will be ignored.''
+=== Configuring a subsite BDII ===
+It is possible to run a hierarchy of site BDII. This is particularly useful for a site made of several autonomous entities as it allows each subsite to export a unique access point to subsite resources. Each subsite manage the actual configuration of its subsite BDII and all the subsites are then aggregated by the site BDII. GRIF is a site example of such a configuration.
+A subsite BDII is a site BDII where variable `BDII_SUBSITE` has been defined to a non empty value. This value is appended to site name to form the `mds-vo-name` for the subsite.