Changes between Version 155 and Version 156 of Doc/gLite/TemplateCustomization

Timestamp:

Feb 8, 2010, 9:17:09 PM (16 years ago)

Author:

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

Comment:

--

Doc/gLite/TemplateCustomization

@@ -483 +483 @@
 === CREAM CE Specific Configuration ===
 
-The CREAM CE has some unique features, not available in LCG CE, that can be easily customized with QWG templates. 
+CREAM CE has some unique features and requirements, not available in LCG CE, that can be easily customized with QWG templates. 
+
+CREAM CE uses internally a MySQL database. The database connexion can be configured with the following variables:
+ * `CREAM_MYSQL_ADMINUSER` (optional): MySQL user with administrative privileges. Default: `root`.
+ * `CREAM_MYSQL_ADMINPWD` (required): password of MySQL administrative account. No default.
+ * `CREAM_DB_USER` (optional): MySQL user used by CREAM CE components. Default: `creamdba`.
+ * `CREAM_DB_PASSWORD` (required): password of MySQL user used by CREAM CE components. No default.
+ * `CREAM_MYSQL_SERVER` (optional): host name running the MySQL server used by the CE. Default: CE host name.
 
 In particular, CREAM CE has a WMS-like management of user input and output sandbox : they are all stored in a dedicated area, outside user home directory. In a configuration where home directories are shared through NFS (or another distributed file system), this requires an additional to share this sandbox area too. It is also possible to share the sandbox area between the CE and the WNs, even though the home directories are not. Variables related to sandbox management are:
- * `CREAMCE_SANDBOX_MPOINTS`: a nlist defining the CE whose sandbox area must be shared. Only the CE with an entry in this nlist will have their sandbox area shared with WN. The key is the CE host name and the value is the mount point to use on the WN. There is no need for the mount point on the WN to be the same as on the CE. There is no default for this variable.
- * `CREAMCE_SANDBOX_DIRS`: a nlist defining where the sandbox area is located on each CE. There may be one entry per CE and one default entry (key=`DEFAULT`). If no entry apply to a CE, the standard default, `/var/cream_sandbox`, is used.
- * `CREAMCE_SANDBOX_SHARED_FS`: a nlist defining the protocol to use for sharing sandbox area. There may be one entry per CE and one default entry (key=`DEFAULT`). If undefined, `nfs` is assumed. If defined but no entry apply to the current CE (and there is no default entry), assume something other than NFS.
+ * `CREAM_SANDBOX_MPOINTS`: a nlist defining the CE whose sandbox area must be shared. Only the CE with an entry in this nlist will have their sandbox area shared with WN. The key is the CE host name and the value is the mount point to use on the WN. There is no need for the mount point on the WN to be the same as on the CE. There is no default for this variable.
+ * `CREAM_SANDBOX_DIRS`: a nlist defining where the sandbox area is located on each CE. There may be one entry per CE and one default entry (key=`DEFAULT`). If no entry apply to a CE, the standard default, `/var/cream_sandbox`, is used.
+ * `CREAM_SANDBOX_SHARED_FS`: a nlist defining the protocol to use for sharing sandbox area. There may be one entry per CE and one default entry (key=`DEFAULT`). If undefined, `nfs` is assumed. If defined but no entry apply to the current CE (and there is no default entry), assume something other than NFS.
  
 When NFS is used to share sandbox area, the [Shared File Systems usual NFS variables] apply to define NFS version to use, mount options...
 
-''Note: sandbox area sharing is configured independently of other file systems specified in `WN_SHARED_AREAS`. Sandbox areas are normally not specified in `WN_SHARED_AREAS` but if they are, this takes predence over the specific configuration done with `CREAMCE_SANDBOX_MPOINTS`.''
-
-When using sandbox sharing with several CEs (specified in the same `CE_HOSTS` variable), it is important to define a distinct mount point for each CE.  An example using `CREAMCE_SANDBOX_MPOINTS`:
-{{{
-variable CREAMCE_SANDBOX_MPOINTS ?= nlist(
+''Note: sandbox area sharing is configured independently of other file systems specified in `WN_SHARED_AREAS`. Sandbox areas are normally not specified in `WN_SHARED_AREAS` but if they are, this takes predence over the specific configuration done with `CREAM_SANDBOX_MPOINTS`.''
+
+When using sandbox sharing with several CEs (specified in the same `CE_HOSTS` variable), it is important to define a distinct mount point for each CE.  An example using `CREAM_SANDBOX_MPOINTS`:
+{{{
+variable CREAM_SANDBOX_MPOINTS ?= nlist(
   'ce1.example.org', '/cream_sandbox/ce1.example.org',
   'ce2.example.org', '/cream_sandbox/ce2.example.org',
@@ -507 +514 @@
 variable CE_HOSTS_LCG ?= list('lcg1.example.org','lcg2.example.org');
 variable CE_HOSTS ?= merge(CE_HOSTS_LCG,CE_HOSTS_CREAM);
-variable CREAMCE_SANDBOX_MPOINTS ?= {
+variable CREAM_SANDBOX_MPOINTS ?= {
   foreach (i;ce;CE_HOSTS_CREAM) {
     SELF[ce] = '/cream_sandbox/'+ce;
@@ -516 +523 @@
 
 A few other variables specific to CREAM CE are available, in particular to define log locations:
- * `CREAMCE_LOG_DIR`: location of CREAM CE log. Default: `/var/log/glite`.
+ * `CREAM_LOG_DIR`: location of CREAM CE log. Default: `/var/log/glite`.
  * `BLPARSER_LOG_DIR`: location of BLParser log file. Default: `/var/log/glite`.
  * `GLEXEC_LOG_DIR`; location of glexec log files. '''This must be different from the 2 other log locations''' because the permissions are not compatible (none belong to `root`). Default: `/var/log/glexec`.