PATCH 4415

Automatic tests

• report #1:
  • CREAM UI version: 1.12.1; CREAM testsuite version: 1.0.7
  • Used direct polling for monitoring and BUpdater/BNotifier for status change detection
  • Batch system: TORQUE
  • All tests have been performed successfully (see the report from the testsuite)

Tested that the BDII is operational

ldapsearch -x -h cream-42.pd.infn.it -p 2170 -b o=infosys

Output is here Checked the Glue 1.3 root entry:

ldapsearch -x -h cream-42.pd.infn.it -p 2170 -b mds-vo-name=resource,o=grid

Output is here

Checked the Glue 2.0 root entry:

ldapsearch -x -h cream-42.pd.infn.it -p 2170 -b o=glue

Output is here

Information content check:

$ gstat-validate-ce -H cream-42.pd.infn.it -p 2170 -b o=grid
OK - errors 0, warnings 0, info 0

Checked bugs

• Bug #54755: Could YAIM warn if a site tries to enable whole-VO FQANs? FIXED
  • Define a VO with the character "/" as a prefix in the variables [queue]_GROUP_ENABLE of the site-info.def
  • Run the YAIM configurator and verify that in the output the following warning appears: "Queue [vo name] was enabled for one or more FQANs which specify an entire VO"

• Bug #61396: CREAM and CEMon log4j.properties should take into account the value of GLITE_LOCATION_LOG TODO
  • no comment

• Bug #62078: Missing glite-pbsparser.log file on standalone Torque-Server TODO
  • no comment

• Bug #63007: CREAM sandbox dir should be relocatable FIXED
  • Define the variable CREAM_SANDBOX_PATH in the file services/glite-creamce
  • Reconfigure with YAIM, submit a job and verify that the sandbox of that job is placed into the new sandbox path

• Bug #63956: config_cream_gip may use wrong VO TODO
  • no comment

• Bug #67238: BUpdaterLSF problem with bhist failure TODO
  • no comment

• Bug #68225: In some cases the sudoers file created by yaim-cream-ce can be syntactically wrong TODO
  • no comment

• Bug #69785: Use #include to modify /etc/sudoer for CREAM with sudo >= 1.7.1 FIXED
  • With sudo version >= 1.7.1 installed, reconfigure with YAIM
  • Verify that all CREAM directives are written into the file /etc/sudoers.forcream

• Bug #70285: it should be possible to tell bhist and tracejob how many logs to read TODO
  • no comment

• Bug #70287: Problem with AssignFinalState if state is IDLE TODO
  • no comment

• Bug #70808: PBS submission script creates wrong stagein/stageout directives with qsub's -W option TODO
  • no comment

• Bug #71038: CE certificate publication error TODO
  • no comment

• Bug #71055: LL_ and IL_ PIDFILE added more times in /opt/glite/etc/lb.conf FIXED
  • Run more times the YAIM configurator and verify that the file /opt/glite/etc/lb.conf does not change.

• Bug #71967: There should be in blah the option to set the temporary job work dir TODO
  • no comment

• Bug #72097: cream-config.xml and cemonitor-config.xml should use GLITE_LOCATION_LOG and GLITE_LOCATION_VAR FIXED
  • Define the variables GLITE_LOCATION_VAR=[new var directory] and CREAM_SANDBOX_PATH=[new sandbox dir] in the file services/glite-creamce
  • Run the YAIM configurator and verify that the new var directory is specified into the following attributes:
    • cream-config.xml: cream_scratch_dir, cream_sandbox_dir, delegation_storage, CREAM_SANDBOX_DIR, JOBS_SCRATCH_DIR
    • cemonitor-config.xml: backendLocation

• Bug #72508: variable CREAM_DB_PASSWORD missed in services/glite-creamce FIXED
  • Verify that the file ${GLITE_LOCATION}/yaim/examples/siteinfo/services/glite-creamce contains the variable CREAM_DB_PASSWORD

• Bug #72756: glite-ce-blahparser missed in gLiteservices FIXED
  • Stop all the gLite service on the CE
  • Remove the script glite-ce-blahparser from the gLiteservices list
  • Reconfigure with YAIM and verify that the glite-ce-blahparser has been re-inserted into the list

Clean installation

• Installation steps:

  wget http://etics-repository.cern.ch/repository/pm/registered/repomd/name/................................./etics-registered-build-by-name.repo -O /etc/yum.repos.d/glite-CREAM.repo
  yum install xml-commons-apis
  yum install glite-CREAM
  wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-TORQUE_utils.repo -O /etc/yum.repos.d/glite-TORQUE_utils.repo
  wget http://grid-deployment.web.cern.ch/grid-deployment/glite/repos/3.2/glite-TORQUE_server.repo -O /etc/yum.repos.d/glite-TORQUE_server.repo
  yum install glite-TORQUE_utils glite-TORQUE_server
  /opt/glite/yaim/bin/yaim -c -s site-info.def -n creamCE -n TORQUE_server -n TORQUE_utils
  

• View the log of yum for a clean installation
• View the log of yaim for a clean installation (TORQUE is used)

Upgrade from production

• Upgrade steps:

  wget http://etics-repository.cern.ch/repository/pm/registered/repomd/name/................................./etics-registered-build-by-name.repo -O /etc/yum.repos.d/glite-CREAM.repo
  yum update
  /opt/glite/yaim/bin/yaim -c -s site-info.def -n creamCE -n TORQUE_server -n TORQUE_utils
  

• View the log of yum for an upgrade
• View the log of yaim for an upgrade (TORQUE is used)