Changes between Version 3 and Version 4 of Development/Scrum/QWG-EMI1

Timestamp:

Jun 27, 2012, 6:44:59 PM (13 years ago)

Author:

/O=GRID-FR/C=FR/O=CNRS/OU=LLR/CN=Andrea Sartirana

Comment:

--

Development/Scrum/QWG-EMI1

@@ -27 +27 @@
 (1 machine for both CREAM and Torque/Maui) and in the "two servers
 mode" (1 machine Torque/Maui + 1 machine CREAM). The only working
-configuration - among those which I have tested - is
+configuration, among those which I have tested, is
 
 EMI-1 CREAM/WN + Torque server/client 2.5.7m + Maui server 2.3.6p21 
@@ -33 +33 @@
 The concerned templates are the following:
 
-+ cfg/grid/emi-1/glite/cream_ce/* for setup of cream
-
-+ cfg/grid/emi-1/common/torque2/* for setup of torque
-
-+ cfg/grid/emi-1/common/maui/* for setup of maui
-
-+ cfg/grid/emi-1/common/blparser/* for setup of blparser
-
-+ cfg/grid/emi-1/glite/wn/* for setup of WN
-
-+ cfg/grid/emi-1/common/gip/* for setup of gip (not working, see below)
-
-+ cfg/grid/emi-1/common/gridftp/* for setup of gridftp
+{{{
+cfg/grid/emi-1/glite/cream_ce/* 
+cfg/grid/emi-1/common/torque2/* 
+cfg/grid/emi-1/common/maui/* 
+cfg/grid/emi-1/common/blparser/* 
++ cfg/grid/emi-1/glite/wn/* 
++ cfg/grid/emi-1/common/gip/* 
++ cfg/grid/emi-1/common/gridftp/* 
+}}}
 
 There are still several open problems or non-optimal soultions that
 should be improved (normally marked as TO_BE_FIXED in the templates)
 
-+ GIP2 and lcgndii components has not been fixed and many old configurations simply do not work. So, for the moment the resource BDII is broken.
+* GIP2 and lcgndii components has not been fixed and many old configurations simply do not work. So, for the moment the resource BDII is broken.
 
-+ bad hack to set the good torque server parameters to allow submission from the CREAM CE
+* bad hack to set the good torque server parameters to allow submission from the CREAM CE
 
   in cfg/grid/emi-1/common/torque2/server/config.tpl
@@ -60 +56 @@
   pbsserver conmponent is required.
 
-+ as it is given by the rpm the init script of the blparser requires
+* as it is given by the rpm the init script of the blparser requires
   the grid env to be already set. Thus, at reboot, the daemon does not
   find the correct env and does not start. Fixed by overwriting 
@@ -71 +67 @@
   cfg/grid/emi-1/common/blparser/config.tpl
 
-+ the part denoted as "Configure minimal Globus environment as it is required by 'lcg-tags --ce'" in
+* the part denoted as "Configure minimal Globus environment as it is required by 'lcg-tags --ce'" in
 
   cfg/grid/emi-1/common/gridftp/service.tpl
@@ -78 +74 @@
 
 
-+ some weird rpm inclusion are required in the cream_ce rpm profile
+* some weird rpm inclusion are required in the cream_ce rpm profile
 
   cfg/grid/emi-1/glite/cream_ce/rpms/x86_64/config.tpl
@@ -86 +82 @@
   "/software/packages"=pkg_repl("java-1.6.0-openjdk","1.6.0.0-1.11.b16.el5","x86_64");
 
-+ some reconfigurations (see below [1]) have all been grouped at the beginning of 
+* some reconfigurations (see below [1]) have all been grouped at the beginning of 
 
   cfg/grid/emi-1/glite/cream_ce/config.tpl
@@ -92 +88 @@
   which is probably not the best place where to put them
 
-+ commented the line
+* commented the line
 
   include { if ( CREAM_HOMEDIR_CLEANUP ) 'lcg/ce/cleanup-accounts' };
@@ -102 +98 @@
   as it was not compiling. Should check further.
 
-+ some of the rpm included in 
+* some of the rpm included in 
 
   cfg/grid/emi-1/glite/wn/rpms/x86_64/config.tpl
@@ -109 +105 @@
   is the good place to include them.
 
-+ workaround by Fred for globuscfg component failure in EMI (some features are now useless).
+* workaround by Fred for globuscfg component failure in EMI (some features are now useless).
   At the beginning of:
          cfg/grid/emi-1/glite/wn/service.tpl
 
-+ EMI_LOCATION* variables defined at the beginning of 
+* EMI_LOCATION* variables defined at the beginning of 
 
   cfg/grid/emi-1/machine-types/ce.tpl
@@ -119 +115 @@
   probably not the good place
 
-+ had to remove some 32bit packages explicitly in the machine profile/
+* had to remove some 32bit packages explicitly in the machine profile/
   See list below [3]