gLite > gLite 3.1 > glite-CREAM > Update to glite-CREAM 3.1.9-0  
 
 

 

 

gLite 3.1

glite-CREAM - Update to version 3.1.9-0


Date 25.02.2009
Priority Normal

Description



Release 08_98 of the WMS for gLite3.1/SL4. Changes with respect to the current production version (patch #1726):

  • Enabled submission to CREAM CE. A newly introduced component in the WMS internal architecture, called ICE, implements the job submission service to CREAM. Its functionality can be compared to what the three components JC. LM and CondorG do for the submission to LCG CE


Please also have a look at the list of known issues.

This update fixes various bugs. For the full list of bugs, please see list below.

Fixed bugs

Number Description
 #39684 [ yaim-cream-ce ] YAIM version in yaim cream CE
 #39991 At start-up time CREAM must consider as ABORTED all job commands with PROCESSING status
 #40757 [ yaim-cream-ce ] clean glite-creamce.pre variables
 #40760 [ yaim-creamce ] glexec user should only be created if CONFIG_USERS=yes
 #40762 [ yaim-creamce ] config_gip_service_release should be included
 #40821 Some information must be better managed in the CREAM log files
 #41437 CEMon laks a c++ command line interface
 #41715 Task #7739 requires to introduce some modifications to CREAM database APIs.
 #42342 Several parts of code lacks debug log messages
 #42343 new feature required in CEMon: possibility to clear sensor events at startup
 #42626 The shutdown of the CeMonitor is slow.
 #42777 CREAM yaim based configuration procedure doesn't call config_gip_software_plugin
 #42914 Implement in CREAM the LCG-CE based solution as short term solution for proxy renewal
 #42918 Implement in BLAH the LCG-CE based solution as short term solution for proxy renewal
 #43036 Support needed in yaim cream for the short term solution for proxy renewal
 #43113 [YAIM] ACCESS_BY_DOMAIN should be in defaults/glite-creamce.pre and not in services/glite-creamce
 #43399 yaim-cream-ce: file in /etc/grid-security/vomsdir/file are renamed in file.pem, including directories
 #43541 All processes created via glexec can be killed only via glexec
 #43542 pbs_status.sh problem when called with -w
 #43746 CREAM YAIM based conf shouldn't configure blah.config when the batch system is not pbs/torque or lsf
 #43777 [ yaim-creamce ] Needed to add /bin/kill to glexec-enabled-commands
 #43928 The retrieveJobIdByGridJobId method doesn't work correctly.
 #44036 AdminCheckerPDP doesn't work
 #44066 yaim-cream-ce doesn't have to create anymore blah.sh
 #44534 [ yaim-cream-ce] CREAM CE gip defaults should change
 #44642 BLParser could crash with incomplete lines in log
 #44712 Problem with lcmaps conf file used for glexec in the CREAM CE
 #44887 Configuration of CREAM and CEMon conf files
 #44892 yaim--cream-ce: config_cream_apel should be removed
 #44963 [ yaim-cream-ce ] Duplicated definition of grid environment variables

Updated rpms

Name Version Full RPM name Description
glite-CREAM 3.1.9-0 glite-CREAM-3.1.9-0.i386.rpm gLite metapackage (glite-CREAM)
glite-ce-blahp 1.10.9-1.slc4 glite-ce-blahp-1.10.9-1.slc4.i386.rpm org.glite.ce.blahp (1.10.9)
glite-ce-ce-plugin 1.10.1-0 glite-ce-ce-plugin-1.10.1-0.noarch.rpm org.glite.ce.ce-plugin (1.10.1)
glite-ce-cream 1.10.3-0 glite-ce-cream-1.10.3-0.noarch.rpm org.glite.ce.cream (1.10.3)
glite-ce-job-plugin 1.10.1-4 glite-ce-job-plugin-1.10.1-4.noarch.rpm org.glite.ce.job-plugin (1.10.1)
glite-ce-monitor 1.10.1-0 glite-ce-monitor-1.10.1-0.noarch.rpm org.glite.ce.monitor (1.10.1)
glite-wms-utils-exception 3.1.3-2.slc4 glite-wms-utils-exception-3.1.3-2.slc4.i386.rpm org.glite.wms-utils.exception v. 3.1.3
glite-wms-utils-jobid 3.1.5-1.slc4 glite-wms-utils-jobid-3.1.5-1.slc4.i386.rpm org.glite.wms-utils.jobid v. 3.1.5
glite-yaim-cream-ce 4.0.7-2 glite-yaim-cream-ce-4.0.7-2.noarch.rpm cream CE configuration

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

Service restart after update

Service must be restarted.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)