Changes between Version 151 and Version 152 of Doc/gLite/TemplateCustomization

Timestamp:

Feb 7, 2010, 9:44:35 PM (16 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin

Comment:

--

Doc/gLite/TemplateCustomization

@@ -459 +459 @@
 = Service-specific Configuration =
 
-== LCG and CREAM CE Configuration ==
-
-__Base template__ (LCG CE) : `machine-types/ce`.
-
-__Base template__ (CREAM CE) : `machine-types/cream_ce`.
-
-QWG templates handle configuration of the LCG or CREAM CE and the selected batch system (LRMS). Most of the configuration is common to both type of CE. To select the LRMS you want to use, you have to define variable `CE_BATCH_NAME`. '''There is no default'''. If you want to use Torque/MAUI, `CE_BATCH_NAME` value must be `torque2` (Torque v1 is no longer supported).
-
-The value of `CE_BATCH_NAME` must match a directory in `common` directory of gLite templates. Currently supported LRMS in QWG templates (Octobre 2008) are Torque/MAUI and Condor.
+== CE Configuration ==
+
+__Base template__ : `machine-types/ce`.
+
+QWG templates can handle configuration of the LCG (gLite 3.1 only) or the CREAM CE and its associated batch system (LRMS). Most of the configuration description is common to both type of CE. In gLite 3.1, CE type defaults to LCG for backward compatibility whereas in gLite 3.2 it defaults to CREAM, the only CE availabe. CE type selection is done with variable `CE_TYPE` which must be `lcg` or `cream`. This variable is ignore in gLite 3.2.
+
+LRMS selection is done with variable `CE_BATCH_NAME`. '''There is no default'''. The supported LRMS and associated values are:
+ * Torque/MAUI: `torque2`
+ * Condor: `condor`
+
+''Note: the value of `CE_BATCH_NAME` must match a directory in `common` directory of gLite templates.''
 
 ''Note: previous versions of QWG templates used to require definition of `CE_BATCH_SYS`. This is deprecated : this variable is now computed from `CE_BATCH_NAME`.''
 
-Most of the variables related to the CE configuration are in fact used to configure the underlying LRMS. The following variables are independent of the LRMS used:
- * `CE_HOST`: CE host name
- * `CE_PRIV_HOST`: alternate name of CE host. Used in configuration where WNs are in a private network and CE has 2 network names/adresses.
+Site-specific gLite parameters must declare the host name of the CEs that share the same worker nodes. All the CEs declared in one set of gLite parameters (one gLite parameter template) will share the same WNs. To configure several CEs with distinct worker nodes, you must create separate clusters. Host name of the CEs can be declared with one of the following two variables:
+ * `CE_HOSTS`: a list of host names corresponding to the different CEs sharing the same WNs.
+ * `CE_HOST`: for backward compatibility, when there is only one CE, this variable can be defined to its name, instead of using `CE_HOSTS`.
+
+In addition, 2 other variables independent of the LRMS are available:
+ * `CE_PRIV_HOST`: alternate name of CE host. Used in configuration where WNs are in a private network and CE has 2 network names/adresses. This variable is not (yet) supported with multiple CEs.
  * `CE_WN_ARCH`: OS architecture on CE worker nodes. Due to limitation in the way this information is published now, this is a CE-wide value. If you have both 64-bit and 32-bit WNs, you must publish 32-bit (`i386`). Default value is based on CE architecture.
+
+=== CREAM CE Specific Configuration ===
+
+The CREAM CE has some unique features, not available in LCG CE, that can be configured with the following variables:
+ * To be written...
 
 === Home Directories of VO Accounts ===