Functionality to be tested

Note that the following list is not sorted according to priority

  1. Verify the proper functionality of the glite-ce-job-submit command with different JDLs (see below)
  2. Verify job submissions with automatic delegations (-a) and with explicit delegations (-D)
  3. Verify that a user who is not administrator can not manage jobs submitted by other users. Verify that a user who is administrator can manage jobs submitted by other users. See http://wiki.italiangrid.org/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#2_9_4_How_to_define_a_CREAM_admi
  4. Verify the proper functionality of the glite-ce-job-status command. In particular verify that in the output of with different levels of verbosity all the needed information is reported. Verify also the functionality of the "filters" (options --from, --to, --status)
  5. Verify the proper functionality of the glite-ce-job-output command
  6. Verify the proper functionality of the glite-ce-job-list command
  7. Verify the proper functionality of the glite-ce-job-purge command. In particular verify that the job has been removed from the CREAM DB and that the job sandbox dir has been scratched
  8. Verify the proper functionality of the automatic job purger (see http://wiki.italiangrid.org/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#2_15_1_Automatic_job_purging). In particular verify that the relevant jobs have been removed from the CREAM DB and that the job sandbox dir has been scratched
  9. Verify the proper functionality of the glite-ce-job-suspend and glite-ce-job-resume commands. In particular check in the glite-ce-job-status output ("job status changes") that the job went through the HELD status
  10. Verify the proper functionality of the glite-ce-job-cancel command. In particular verify that job status eventually is CANCELLED (by user)
  11. Try to manually (bkill/qdel) a job. Eventually job status should be DONE-FAILED or CANCELLED (by admin)
  12. Verify that the limiter (see http://wiki.italiangrid.org/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#2_12_Self_limiting_CREAM_behavio) works and job submissions are indeed disabled when it detects that at least a threshold has been overtaken
  13. Verify the proper functionality of glite-ce-disable-submission and glite-ce-enable-submission commands. Verify that they can be issued only by an admin. Verify that job submissions are then really disabled/re-enabled.
  14. Verify the proper functionality of the glite-ce-allowed-submission command
  15. Verify the proper functionality of the glite-ce-service-info command. In particular verify that in the output all the relevant information is reported
  16. Verify the functionality of the glite-ce-proxy-renew command. In particular verify that the proxy is indeed renewed on the WN (note that the proxy on the WN is supposed to be renewed when needed, i.e. before proxy expiration, not when the glite-ce-proxy-renew is issued)
  17. Try the functionality of the BLparser (in particular it can be verified with the cancel operations) with both the old and the new blparser (see http://wiki.italiangrid.org/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#1_2_3_Choose_the_BLAH_BLparser_d)
  18. Try functionality of CREAM with both Argus based authorizations and gJAF based authorizations (see http://wiki.italiangrid.org/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#1_2_2_Choose_the_authorization_m)
  19. Check if the resource bdii publishes all the relevant objectclasses for both glue1 and glue2. Check with glue validator (see https://tomtools.cern.ch/confluence/display/IS/GLUEValidator) the correctness of the published information
  20. Check if the banning of a user works (see http://wiki.italiangrid.org/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#2_9_2_How_to_block_ban_a_user)
  21. Try file transfers between CE and WN with both available options (see http://wiki.italiangrid.org/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#2_10_Input_and_Output_Sandbox_fi)
  22. Try if the automatic purging of expired proxies (see http://wiki.italiangrid.org/twiki/bin/view/CREAM/SystemAdministratorGuideForEMI1#2_16_Proxy_purging) works

JDLs to be tested

Try both input and output sandbox staging, considering all the possibilities:

  • Staging of ISB files from client to the CE node
  • Staging of ISB files from remote gridftp servers
  • Staging of OSB files to remote gridftp servers
  • Staging of OSB files to the CE node (gsiftp://localhost)
For ISB try also with InputSandboxBaseURI.

For OSB try both OutputSandboxDestURI and OutputSandboxBaseDestURI


Try jobs with Epilogue and Prologue


Try setting Environment variables in the JDL (JDL attribute Environment) and check that these variables are indeed set in the job


Try jobs where the attributes CPUNumber and/or SMPGranularity and/or WholeNodes and/or HostNumber have been set Check that the job submission script (see http://wiki.italiangrid.org/twiki/bin/view/CREAM/TroubleshootingGuide#4_1_Saving_the_batch_job_submiss ) is compliant with what reported in: TBD


Try OutputData JDL attributes considering all the possible combinations. Check the result of output data staging operation in the DSUpload_.out file

References

-- MassimoSgaravatto - 2011-04-28


This topic: CREAM > WebHome > OtherDocumentation > CreamTesting > InputToGRNETForTesting
Topic revision: r4 - 2011-04-28 - MassimoSgaravatto
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback