Changes between Version 160 and Version 161 of Doc/gLite/TemplateCustomization


Ignore:
Timestamp:
Feb 25, 2010, 10:36:02 PM (16 years ago)
Author:
/O=GRID-FR/C=FR/O=CNRS/OU=LAL/CN=Michel Jouvin
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/gLite/TemplateCustomization

    v160 v161  
    493493 * `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.
    494494
    495 === Sharing WNs between several CEs ===
     495=== Sharing WNs between several CEs === #CESharingWNs
    496496
    497497QWG templates allow to configure several CEs sharing the same WNs. They must share the same gLite parameters and the variable `CE_HOSTS` must contain all the CE host names. They can be LCG CE and/or CREAM CE. If you want to mix LCG and CREAM CE, it is recommended to maintain a separate list of for each CE type and build `CE_HOSTS` by merging them as in the following example:
    … …  
    506506=== CREAM CE Specific Configuration === #CREAMConfig
    507507
    508 CREAM CE has some unique features and requirements, not available in LCG CE, that can be easily customized with QWG templates.
     508CREAM CE has some unique features and requirements, not available in LCG CE, that can be easily customized with QWG templates. To identify CREAM CEs among all defined CEs, they must belong to the list `CE_HOSTS_CREAM`, as suggested [#CESharingWNs above].
    509509
    510510CREAM CE uses internally a MySQL database. The database connexion can be configured with the following variables:
    … …  
    524524''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`.''
    525525
    526 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`:
    527 {{{
    528 variable CREAM_SANDBOX_MPOINTS ?= nlist(
    529   'ce1.example.org', '/cream_sandbox/ce1.example.org',
    530   'ce2.example.org', '/cream_sandbox/ce2.example.org',
    531 );
    532 }}}
    533 
    534 Or a possible definition that will implement such a naming scheme for every CREAM CE defined:
    535 {{{
    536 variable CE_HOSTS_CREAM ?= list('cream1.example.org','cream2.example.org');
    537 variable CE_HOSTS_LCG ?= list('lcg1.example.org','lcg2.example.org');
    538 variable CE_HOSTS ?= merge(CE_HOSTS_LCG,CE_HOSTS_CREAM);
     526When 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.  Below is an example showing how to define `CREAM_SANDBOX_MPOINTS` based on `CE_HOSTS_CREAM`:
     527{{{
    539528variable CREAM_SANDBOX_MPOINTS ?= {
    540529  foreach (i;ce;CE_HOSTS_CREAM) {