Tags:
create new tag
,
view all tags
---++ BLAH Testplan %TOC% ---+++ 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 [[http://wiki.italiangrid.it/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1][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 [[%ATTACHURL%/blex.tar.gz][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: <verbatim> glite-ce-job-submit -a -r <CEId> test1.jdl test1.jd: [ executable="/bin/sleep"; arguments="100"; ] </verbatim> 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: <verbatim> glite-ce-job-submit -a -r <CEId> test1.jdl test1.jd: [ executable="/bin/sleep"; arguments="100"; ] </verbatim> 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: <verbatim> glite-ce-job-submit -a -r <CEId> test1.jdl test1.jd: [ executable="/bin/sleep"; arguments="200"; ] </verbatim> 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: <verbatim> glite-ce-job-submit -a -r <CEId> test1.jdl test1.jd: [ executable="/bin/sleep"; arguments="100"; ] </verbatim> 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: <verbatim> glite-ce-job-submit -a -r <CEId> test1.jdl test1.jd: [ executable="/bin/sleep"; arguments="100"; ] </verbatim> 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: <verbatim> glite-ce-job-submit -a -r <CEId> test1.jdl test1.jd: [ executable="/bin/sleep"; arguments="200"; ] </verbatim> 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 -- Main.MassimoSgaravatto - 2011-12-20
Attachments
Attachments
Topic attachments
I
Attachment
Action
Size
Date
Who
Comment
gz
blex.tar.gz
manage
16.8 K
2011-12-20 - 16:18
MassimoSgaravatto
E
dit
|
A
ttach
|
PDF
|
H
istory
: r1
|
B
acklinks
|
V
iew topic
|
M
ore topic actions
Topic revision: r1 - 2011-12-20
-
MassimoSgaravatto
Home
Site map
CEMon web
CREAM web
Cloud web
Cyclops web
DGAS web
EgeeJra1It web
Gows web
GridOversight web
IGIPortal web
IGIRelease web
MPI web
Main web
MarcheCloud web
MarcheCloudPilotaCNAF web
Middleware web
Operations web
Sandbox web
Security web
SiteAdminCorner web
TWiki web
Training web
UserSupport web
VOMS web
WMS web
WMSMonitor web
WeNMR web
General Doc
Functional Description
Batch System Support
CREAM and Information Service
Release Notes
Known Issues
Security in CREAM
Nagios Probes to monitor CREAM and WN
Papers
Presentations
User Doc
CREAM User Guide for EMI-1
CREAM User Guide for EMI-2
CREAM User Guide for EMI-3
CREAM JDL Guide
BLAH User Guide
Troubleshooting Guide
System Administrator Doc
System Administrator Guide for CREAM (EMI-3 release)
System Administrator Guide for CREAM (EMI-2 release)
System Administrator Guide for CREAM (EMI-1 release)
The CREAM configuration file
The CEMonitor configuration file
The CREAM CE Service Reference Card (EMI-2 release)
The CREAM CE Service Reference Card (EMI-1 release)
Batch System related documentation
Troubleshooting Guide
The guide for integrating EMIR in CREAM
]
Developers Doc
CREAM Client API C++ Documentation
CREAM Client API for Python
Other Doc
Contacts
Moving to CREAM from LCG-CE
Testing
Internal Collaboration Information
Credits
CREAM Web utilities
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
P
P
View
Raw View
Print version
Find backlinks
History
More topic actions
Edit
Raw edit
Attach file or image
Edit topic preference settings
Set new parent
More topic actions
Account
Log In
E
dit
A
ttach
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback