Difference: CreamWorkPlan (4 vs. 5)

Revision 52008-11-14 - PaoloAndreetto

Line: 1 to 1
 
META TOPICPARENT name="TestWokPlan"
Changed:
<
<

CREAM Test work plan

>
>

CREAM Test work plan (WORK IN PROGRESS)

 

Introduction

Line: 28 to 28
 

Testsuite composition

The set of test can be divided into two main categories, according to the type of status detection mechanism for a job:
  • with polling (synchronous):
Changed:
<
<
    • cream-test-monitored-cancel
    • cream-test-monitored-lease-expired
    • cream-test-monitored-lease-updated
    • cream-test-monitored-proxy-expired
    • cream-test-monitored-submit
    • cream-test-notified-lease-updated
>
>
 
  • with notifications (asynchronous):
Changed:
<
<
    • cream-test-notified-cancel
    • cream-test-notified-lease-expired
    • cream-test-notified-lease-updated
    • cream-test-notified-submit
>
>
 

Proxy management

Each test can be run using either an external user voms-proxy or with an internal management of the voms-proxy.
Line: 49 to 48
 

Delegation management

Each test can be run either using a single delegated proxy on the CE for all the submissions or with one delegated proxy per submitted job, see --delegationType option. The tester must be aware of using the second mode can overload the entire system, both the service and the testsuite, so the tuning of the test parameters must consider that issue.
Added:
>
>

Hints for test tuning

  • Due to unavoidable delays in the command scheduling, the life-time of the job submitted with the cream-test-notified-cancel has to be at least 3 times longer than the rate parameter.
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback