Difference: WmsTestPlan (21 vs. 22)

Revision 222011-06-27 - MarcoCecchi

Line: 1 to 1
 

WMS Test Plan

Deleted:
<
<

Service Description

The Workload Management System (gLite WMS) is a software service of the gLite suite which is responsible for distributing and managing tasks across computing and storage resources available on a Grid. WMS assigns user jobs to CEs and SEs belonging to a Grid environment in a convenient fashion, so that:

  • jobs are always executed on resources that match the job requirements
  • grid-wide load balance is maintained, i.e. jobs are evenly and efficiently distributed across the entire Grid.

The WMS basically receives requests of job execution from a client, finds the required appropriate resources, then dispatches and follows them until completion. This is done handling failure in between and whenever possible. Other than single batch-like jobs, compound job types handled by the WMS are Directed Acyclic Graphs (a set of jobs where the input/output/execution of one of more jobs may depend on one or more other jobs), Parametric Jobs (multiple jobs with one parametrized description), and Collections (multiple jobs with a common description). Jobs are described via a flexible, high-level Job Definition Language (JDL).

Functional Description

Service Reference Card

 

Unit tests

N/A

Deleted:
<
<

Deployment tests

 

Repository

The EMI-1 RC4 repository can be found under:

Line: 44 to 29
 
yum install ca-policy-egi-core

Install the WMS metapackage:

Changed:
<
<
yum install emi-wms 
>
>
yum install emi-wms
  (see log file)
Line: 55 to 39
  (see log file)
Added:
>
>

Deployment tests

 

Update test

N/A

Line: 71 to 57
 Submit a job to the WMS service and when finished retrieve the output. Test job submission with the following type of jobs:
Added:
>
>
Bunch #1: submission of normal jobs.

Test 1.1: Test this JDL:

[ Executable = "/bin/echo"; Arguments = "Hello"; StdOutput = "out.log"; StdError = "err.log"; InputSandbox = {"Test.sh"}; OutputSandbox = {"out.log", "err.log"}; requirements = RegExp("cream.*", other.GlueCEUniqueID);; AllowZippedISB = false; rank=0; myproxyserver="myproxy.cnaf.infn.it"; RetryCount = 0; ShallowRetryCount = 1; ]

Test 1.10 submit a job with an empty file in ISB

 
Normal Job
  • Test submission of normal jobs with different options and situation Implemented
Line: 86 to 95
  Directed Acyclic Graphs (a set of jobs where the input/output/execution of one of more jobs may depend on one or more other jobs).
Changed:
<
<
  • Submit a jdl like this one:
>
>
  • Try with JDL:
 
[
  type = "dag";
Line: 186 to 196
 
  • When job finishes retrieve the output files
  • Check the final status of the job
Added:
>
>

Delegation

Explicit delegation, automatic delegation

Brokerinfo

 

WMS Job shallow and deep re-submission

There two type of resubmission; the first is defined deep occurs when the user's job has stardted running on the WN and then the job itself or the WMS JobWrapper has failed. The second one is called shallow and occurs when the WMS JobWrapper has failed before starting the actual user's job. Implemented

Added:
>
>

Replanning

MaxReplansCount in glite_wms.conf
 

WMS Job List-match Testing

Without data
 
This site is powered by the TWiki collaboration platformCopyright © 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