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)
Information system checks
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 #68159: Error parsing output from id executable FIXED
- Configure a CREAM CE with a pool account whose member's names contain the characther "-"
- Submit a job using a credential mapped into the pool account described above.
- Verify that the job is correctly processed by the service.
- Bug #69545: Cream digests asynchronous commands very very slow HOPEFULLY FIXED
- This bug was triggered by an issue of the security layer.
- Verified with the testsuite.
- Bug #70058: Implement support for new LB locallogger in the CREAM CE FIXED
- Verify the correct startup of the locallogger using the init-script
- Verify that the process IDs of the localloger daemons are correctly written in the files /opt/glite/var/cream_lb/glite-lb-logd.pid and /opt/glite/var/cream_lb/glite-lb-interlogd.pid
Clean installation
Upgrade from production