Changes between Version 71 and Version 72 of Doc/gLite/TemplateCustomization

Timestamp:

Nov 26, 2007, 12:32:21 AM (18 years ago)

Author:

jouvin

Comment:

Clarify BDII configuration

Doc/gLite/TemplateCustomization

@@ -467 +467 @@
  * Top-level BDII (default type) : use a central location to get their data (all BDIIs use the same source). This central location contains information about all sites registered in the GOC DB. Use of FCR (Freedom of Choice) enabled by default.
  * Site BDII : BDII in charge of collecting information about site resources. Support the concept of sub-site BDII (hierarchy of BDII to collect site information).
- * Resource BDII : used in replacement of Globus MDS on some resources (e.g. DPM).
-
-Site (or subsite) BDII and a resource BDII can be combined on the same machine.
+ * Resource BDII : used in replacement of Globus MDS to publish resource information into BDII.
 
 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` or `combined`. A `combined` BDII is a BDII configured both as a resource and a site BDII (this is the default on a LCG CE). `top` is the default, except if deprecated variable `SITE_BDII` is true.
+ * 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.
+
+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.''