BLAH Testplan
Unit tests
Not available
Deployment tests
Since BLAH is deployed as part of the CREAM-CE, the installation and configuration of a CREAM CE should be considered.
This is documented in the
CREAM system administrator guide.
System tests
Basic functionality tests
Test submission
On each supported batch system (now LSF, PBS and GE) the following tests should be performed:
- Test plain submission
- Test submission with file transfers
The first two tests are implemented with the
attached scripts.
To run it:
- Log on on the CREAM CE as user tomcat
- Create the directory
/tmp/blex
and cd on this directory
- Copy a proxy of yours and install it in this directory. Call it
/tmp/blex/proxy
. It should have tomcat.tomcat as ownership
- wget and untar the blex.tar.gz
- Edit and customize the file
blex_local_conf.sh
:
-
blex_x509userproxy
should be "/tmp/blex/proxy"
- blex_blah_path= should be "/usr/bin/blahpd"
-
blex_iwd
should be "/tmp/blex"
-
blex_file_storage
should be "/tmp"
-
blex_desired_batchsystem
should be set to "lsf" or "pbs" or "sge" according to the batch system where to perform the test
-
blex_desired_queue
should be set to the queue where to submit the jobs
-
blex_setup_glexec
should be set to 0
-
blex_setup_sudo
should be set to 1
-
blex_setup_sudo_user
should be set to a valid existing local account
-
blex_proxy_in_submit_cmd
should be set to 1
-
blex_n_DEFAULT_jobs
should be set to 0
-
blex_n_HOLDRELEASE_jobs
should be set to 0
-
blex_n_RENEWAL_jobs
should be set to 0
-
blex_n_TRANSFERFILES_jobs
should be set to the number of jobs to be submitted. 1000 can be a valid value
- Run the script
blah_exerciser.sh
- Check its output in the stdout. It should report that all jobs succeeded and 0 failed.
BLParser test
The following test of the blparser (configured in old and new way) should be performed:
- Test that notifications are sent for a job which finishes normally
- Test that notifications are sent for a job which is cancelled
- Test that notifications are sent for a job which is suspended and then resumed
Test that notifications are sent for a job which finishes normally with old blparser
First of all configure a CREAM-CE using the old blparser configured in the old way as described at:
http://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#1_2_4_Choose_the_BLAH_BLparser_d
Submit this JDL to a CREAM-CE using the
glite-ce-job-submit
command:
glite-ce-job-submit -a -r <CEId> test1.jdl
test1.jd:
[
executable="/bin/sleep";
arguments="100";
]
After the job completed its execution (it must be needed to then wait for a couple of minutes), check the log file
/var/log/cream/glite-xxxparser.log
. For the relevant job there should be:
- A notification with JobStatus=1 (this can be missing)
- A notification with JobStatus=2 (this can be missing)
- A notification with JobStatus=4 (this must be there)
Test that notifications are sent for a job which is cancelled with old blparser
First of all configure a CREAM-CE using the old blparser configured in the old way as described at:
http://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#1_2_4_Choose_the_BLAH_BLparser_d
Submit this JDL to a CREAM-CE using the
glite-ce-job-submit
command:
glite-ce-job-submit -a -r <CEId> test1.jdl
test1.jd:
[
executable="/bin/sleep";
arguments="100";
]
Then cancels the job with
glite-ce-job-cancel
.
After the job is actually cancelled (it must be needed to then wait for a couple of minutes), check the log file
/var/log/cream/glite-xxxparser.log
. For the relevant job there should be:
- A notification with JobStatus=1 (this can be missing)
- A notification with JobStatus=2 (this can be missing)
- A notification with JobStatus=3 (this must be there)
Test that notifications are sent for a job which is suspended and then resumed with old blparser
First of all configure a CREAM-CE using the old blparser configured in the old way as described at:
http://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#1_2_4_Choose_the_BLAH_BLparser_d
Submit this JDL to a CREAM-CE using the
glite-ce-job-submit
command:
glite-ce-job-submit -a -r <CEId> test1.jdl
test1.jd:
[
executable="/bin/sleep";
arguments="200";
]
Then suspends the job with
glite-ce-job-suspend
.
Check the batch system and verify than the job is actually suspended. Then wait for 5 minutes and then resume the job using the
glite-ce-job-resume
command.
After the job finishes (it must be needed to then wait for a couple of minutes), check the log file
/var/log/cream/glite-xxxparser.log
. For the relevant job there should be:
- A notification with JobStatus=1 (this can be missing)
- A notification with JobStatus=2 (this can be missing)
- A notification with JobStatus=5 (this must be there)
- A notification with JobStatus=2 (this can be missing)
- A notification with JobStatus=4 (this must be there)
Note that with PBS and SGE it is possible to suspend only IDLE (i.e. not yet running) jobs.
Test that notifications are sent for a job which finishes normally with new blparser
First of all configure a CREAM-CE using the new blparser configured in the old way as described at:
http://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#1_2_4_Choose_the_BLAH_BLparser_d
Submit this JDL to a CREAM-CE using the
glite-ce-job-submit
command:
glite-ce-job-submit -a -r <CEId> test1.jdl
test1.jd:
[
executable="/bin/sleep";
arguments="100";
]
After the job completed its execution (it must be needed to then wait for a couple of minutes), check the log file
/var/log/cream/glite-ce-bnotifier.log
. For the relevant job there should be:
- A notification with JobStatus=1 (this can be missing)
- A notification with JobStatus=2 (this can be missing)
- A notification with JobStatus=4 (this must be there)
Test that notifications are sent for a job which is cancelled with new blparser
First of all configure a CREAM-CE using the old blparser configured in the new way as described at:
http://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#1_2_4_Choose_the_BLAH_BLparser_d
Submit this JDL to a CREAM-CE using the
glite-ce-job-submit
command:
glite-ce-job-submit -a -r <CEId> test1.jdl
test1.jd:
[
executable="/bin/sleep";
arguments="100";
]
Then cancels the job with
glite-ce-job-cancel
.
After the job is actually cancelled (it must be needed to then wait for a couple of minutes), check the log file
/var/log/cream/glite-ce-bnotifier.log
. For the relevant job there should be:
- A notification with JobStatus=1 (this can be missing)
- A notification with JobStatus=2 (this can be missing)
- A notification with JobStatus=3 (this must be there)
Test that notifications are sent for a job which is suspended and then resumed with new blparser
First of all configure a CREAM-CE using the old blparser configured in the new way as described at:
http://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#1_2_4_Choose_the_BLAH_BLparser_d
Submit this JDL to a CREAM-CE using the
glite-ce-job-submit
command:
glite-ce-job-submit -a -r <CEId> test1.jdl
test1.jd:
[
executable="/bin/sleep";
arguments="200";
]
Then suspends the job with
glite-ce-job-suspend
.
Check the batch system and verify than the job is actually suspended. Then wait for 5 minutes and then resume the job using the
glite-ce-job-resume
command.
After the job finishes (it must be needed to then wait for a couple of minutes), check the log file
/var/log/cream/glite-ce-bnotifier.log
. For the relevant job there should be:
- A notification with JobStatus=1 (this can be missing)
- A notification with JobStatus=2 (this can be missing)
- A notification with JobStatus=5 (this must be there)
- A notification with JobStatus=2 (this can be missing)
- A notification with JobStatus=4 (this must be there)
Note that with PBS and SGE it is possible to suspend only IDLE (i.e. not yet running) jobs.
Regression tests
See:
http://wiki.italiangrid.it/twiki/bin/view/CREAM/RegressionTestWorkPlan
Standard compliance and conformance tests
Not available
Inter-component tests
Not available
--
MassimoSgaravatto - 2011-12-20