Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 2735 to 2735 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 2525 to 2525 | ||||||||
Glue 1 compliance | ||||||||
Changed: | ||||||||
< < | Glue 1 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. | |||||||
> > | Glue 1 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using GlueValidator. | |||||||
Status: Implemented in the Robot based testsuite
Glue 2 compliance | ||||||||
Changed: | ||||||||
< < | Glue 2 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. | |||||||
> > | Glue 2 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using GlueValidator. | |||||||
Status: Implemented in the Robot based testsuite |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 1748 to 1748 | ||||||||
Verify also that the output file gsiftp://cream-35.pd.infn.it/tmp/file.out has been created. | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
Submission of multiple activities | ||||||||
Line: 1841 to 1842 | ||||||||
[sgaravat@cream-50 ADLExamples]$ | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
Validation for unsupported capability | ||||||||
Line: 1970 to 1972 | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
Pre and Post Executables | ||||||||
Line: 2089 to 2092 | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | Status: Not Implemented | |||||||
Activity with Environment | ||||||||
Line: 2180 to 2183 | ||||||||
forma=rombo | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
List | ||||||||
Line: 2249 to 2253 | ||||||||
CR_ES975108994 | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
ActivityInfoSubmit an activity and then check it with the activityinfo operation, e.g.: | ||||||||
Line: 2314 to 2322 | ||||||||
[sgaravat@cream-50 ADLExamples]$ | ||||||||
Changed: | ||||||||
< < | TBC | |||||||
> > | Status: Not Implemented | |||||||
Line: 2374 to 2384 | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
CancelSubmit a long activity: | ||||||||
Line: 2411 to 2424 | ||||||||
Description = cancelled by the user | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
WipeSubmit an activity and wait that the status is TERMINAL: | ||||||||
Line: 2445 to 2463 | ||||||||
Verify that the job sandbox directory has been removed | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
Regression testsSee: http://wiki.italiangrid.it/twiki/bin/view/CREAM/RegressionTestWorkPlan |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 1370 to 1370 | ||||||||
Status: Not Implemented | ||||||||
Deleted: | ||||||||
< < | Activity with Input and Output with multiple Sources (both wrong)TBD Status: Not Implemented | |||||||
Activity with Input and Output with multiple Sources (one wrong, one correct) |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 548 to 548 | ||||||||
Verify the final job status which should eventually be DONE-OK | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
Automatic proxy purger test | ||||||||
Line: 559 to 559 | ||||||||
Try again the submission using the same delegationid after 24 hours. This should not work (the error message should say that the delegation was not found) | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
Line: 670 to 670 | ||||||||
Verify the output of glite-ce-service-info command for both verbosity levels. | ||||||||
Changed: | ||||||||
< < | TBD | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
Line: 740 to 740 | ||||||||
Subject = CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=IT | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
Proxy renewal | ||||||||
Line: 793 to 794 | ||||||||
Subject = CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=IT | ||||||||
Added: | ||||||||
> > | Status: Not Implemented | |||||||
Activity without data stagingSubmit an activity where in the Application part there is just the Executable withoutfailifExitCodeNotEqualTo . |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 1844 to 1844 | ||||||||
Changed: | ||||||||
< < | Validations | |||||||
> > | Validation for unsupported capabilityConsider a ADL specifying a not supported atribute (e.g. RemoteLogging):[sgaravat@cream-50 ADLExamples]$ cat remotelogging.adl <ActivityDescription> <ActivityIdentification> <Name>sleep60</Name> <Description>sleep 60</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/sleep</Path> <Argument>60</Argument> </Executable> <RemoteLogging> <ServiceType>LB</ServiceType> <URL>https://locallogger.com</URL> </RemoteLogging> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> </DataStaging> </ActivityDescription>Submit it: a "capability not supported" message should be returned: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it remotelogging.adl ***************************************** ActivityID = FAULT: Message=[remote logging capability not supported!] Timestamp=[1332346982] ActivityMgrURI = Status = N/A ETNSC = STAGEIN Dir = {} SESSION Dir = {} STAGEOUT Dir = {}Repeat the test specifying optional=false. The same error message should be returned: [sgaravat@cream-50 ADLExamples]$ cat remotelogging.adl <ActivityDescription> <ActivityIdentification> <Name>sleep60</Name> <Description>sleep 60</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/sleep</Path> <Argument>60</Argument> </Executable> <RemoteLogging optional="false"> <ServiceType>LB</ServiceType> <URL>https://locallogger.com</URL> </RemoteLogging> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> </DataStaging> </ActivityDescription> [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it remotelogging.adl ***************************************** ActivityID = FAULT: Message=[remote logging capability not supported!] Timestamp=[1332347088] ActivityMgrURI = Status = N/A ETNSC = STAGEIN Dir = {} SESSION Dir = {} STAGEOUT Dir = {}Repeat the test specifying optional=true. In this case the activity should be submitted: [sgaravat@cream-50 ADLExamples]$ cat remotelogging.adl <ActivityDescription> <ActivityIdentification> <Name>sleep60</Name> <Description>sleep 60</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/sleep</Path> <Argument>60</Argument> </Executable> <RemoteLogging optional="true"> <ServiceType>LB</ServiceType> <URL>https://locallogger.com</URL> </RemoteLogging> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> </DataStaging> </ActivityDescription> [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it remotelogging.adl ***************************************** ActivityID = CR_ES663995663 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Wed Mar 21 17:25:09 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/66/CR_ES663995663/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/66/CR_ES663995663/OSB} | |||||||
Deleted: | ||||||||
< < | TBD | |||||||
Pre and Post Executables |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 2058 to 2058 | ||||||||
Added: | ||||||||
> > | ListUse the list operation and check if all your jobs are returned:[sgaravat@cream-50 ADLExamples]$ glite-es-activity-list -e cream-47.pd.infn.it CR_ES121359049 CR_ES271831319 CR_ES355205210 CR_ES393049605 CR_ES699482608 CR_ES745555371 CR_ES799188399 CR_ES810395877 CR_ES898737831 CR_ES931295038 CR_ES953523652 CR_ES975108994Test the limit option. Only at most the specified number of entries should be returned: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-list -e cream-47.pd.infn.it -l 1 CR_ES121359049Submit a job, and while it is running issue a list with the filter on the PROCESSING-RUNNING status:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it activity_sleep60.adl ***************************************** ActivityID = CR_ES747877778 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Tue Mar 20 14:45:24 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/74/CR_ES747877778/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/74/CR_ES747877778/OSB} [sgaravat@cream-50 ADLExamples]$ glite-es-activity-list -e cream-47.pd.infn.it -S PROCESSING_RUNNING CR_ES747877778Test the filter on the submission time, e.g.: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-list -e cream-47.pd.infn.it -F '2012-03-20 10:00:00' CR_ES699482608 CR_ES747877778 CR_ES799188399 [sgaravat@cream-50 ADLExamples]$ glite-es-activity-list -e cream-47.pd.infn.it -F '2012-03-01 10:00:00' -T '2012-03-19 10:00:00' CR_ES121359049 CR_ES271831319 CR_ES393049605 CR_ES745555371 CR_ES810395877 CR_ES898737831 CR_ES931295038 CR_ES953523652 CR_ES975108994 ActivityInfoSubmit an activity and then check it with the activityinfo operation, e.g.:[sgaravat@cream-50 ADLExamples]$ glite-es-activity-info -e cream-47.pd.infn.it CR_ES799188399 **** ActivityID = CR_ES799188399 ID=https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService?CR_ES799188399 Name=sleep60 OtherInfo={} CreationTime=1332250577 (Tue Mar 20 14:36:17 2012) Validity=N/A ***** Extension #0: LocalID=CR_ES799188399 Key=ACTIVITY_HISTORY Value=ACTIVITY_HISTORY ***** Extension #1: LocalID=CR_ES799188399 Key=STAGE_IN_URI Value=gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/79/CR_ES799188399/ISB ***** Extension #2: LocalID=CR_ES799188399 Key=STAGE_OUT_URI Value=gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/79/CR_ES799188399/OSB BaseType= Type=SINGLE IDFromEndpoint=https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService?CR_ES799188399 LocalIDFromManager=lsf/20120320/607375 JobDescription=emi:adl State={ACCEPTED, PREPROCESSING, PROCESSING-ACCEPTING, PROCESSING-QUEUED, PROCESSING-RUNNING, TERMINAL} RestartState={} ExitCode=0 ComputingManagerExitCode=N/A Error={} WaitingPosition=N/A UserDomain=dteam Owner=CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL LocalOwner=dteam004 RequestedTotalWallTime=N/A RequestedTotalCPUTime=N/A RequestedSlots=N/A RequestedApplicationEnvironment={} StdIn=N/A StdOut=N/A StdErr=N/A LogDir=N/A ExecutionNode=prod-wn-003.pn.pd.infn.it Queue=creamtest2 UsedTotalWallTime=N/A UsedMainMemory=N/A SubmissionTime=1332250577 (Tue Mar 20 14:36:17 2012) ComputingManagerSubmissionTime=1332250577 (Tue Mar 20 14:36:17 2012) StartTime=1332250588 (Tue Mar 20 14:36:28 2012) ComputingManagerEndTime=1332250648 (Tue Mar 20 14:37:28 2012) EndTime=1332250648 (Tue Mar 20 14:37:28 2012) WorkingAreaEraseTime=N/A ProxyExpirationTime=N/A SubmissionHost=N/A SubmissionClientName=N/A OtherMessages= [sgaravat@cream-50 ADLExamples]$TBC | |||||||
Pause and ResumeCreate a long activity: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 1848 to 1848 | ||||||||
TBD | ||||||||
Added: | ||||||||
> > |
Pre and Post ExecutablesConsider this ADL:[sgaravat@cream-50 ADLExamples]$ cat prepost.adl <ActivityDescription> <ActivityIdentification> <Name>prepost</Name> <Description>prepost</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/hostname</Path> <Argument>-f</Argument> </Executable> <Output>prepost.out</Output> <PreExecutable> <Path>/bin/touch</Path> <Argument>/tmp/file1</Argument> </PreExecutable> <PreExecutable> <Path>/bin/touch</Path> <Argument>/tmp/file2</Argument> </PreExecutable> <PostExecutable> <Path>/bin/touch</Path> <Argument>/tmp/file3</Argument> </PostExecutable> <PostExecutable> <Path>/bin/touch</Path> <Argument>/tmp/file4</Argument> </PostExecutable> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <OutputFile> <Name>prepost.out</Name> </OutputFile> </DataStaging> </ActivityDescription>Submit it: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it prepost.adl ***************************************** ActivityID = CR_ES121359049 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Mon Mar 19 09:36:28 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/12/CR_ES121359049/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/12/CR_ES121359049/OSB}Wait the termination of the job and retrieve the output file: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES121359049 ***************************************** JobID = CR_ES121359049 Status = TERMINAL Attributes = {CLIENT_STAGEOUT_POSSIBLE} Timestamp = Mon Mar 19 09:36:38 2012 Description = reason=0 [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [Globus Toolkit 5.2.0] ready. 230 User dteam004 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/12/CR_ES121359049/OSB UberFTP> ls drwx------ 3 dteam004 dteam 4096 Mar 19 09:36 . drwx------ 4 dteam004 dteam 4096 Mar 19 09:36 .. -rw-r--r-- 1 dteam004 dteam 26 Mar 19 09:36 prepost.out UberFTP> get prepost.out prepost.out: 26 bytes in 0.012021 Seconds (2.112 KB/s) UberFTP> bye 221 Goodbye.Check where the job was executed: [sgaravat@cream-50 ADLExamples]$ cat prepost.out prod-wn-002.pn.pd.infn.itVerify that in these WNs the files created by the pre and post executables have been created: [sgaravat@cream-50 ADLExamples]$ ssh root@prod-wn-002.pn.pd.infn.it The authenticity of host 'prod-wn-002.pn.pd.infn.it (192.168.132.102)' can't be established. RSA key fingerprint is ac:fb:ee:57:ec:16:90:82:e7:de:36:ef:cb:0e:f6:95. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'prod-wn-002.pn.pd.infn.it,192.168.132.102' (RSA) to the list of known hosts. root@prod-wn-002.pn.pd.infn.it's password: Last login: Sun Mar 18 09:50:57 2012 from cream-47.pd.infn.it [root@prod-wn-002 ~]# ls -al /tmp/file* -rw-r--r-- 1 dteam004 dteam 0 Mar 19 09:36 /tmp/file1 -rw-r--r-- 1 dteam004 dteam 0 Mar 19 09:36 /tmp/file2 -rw-r--r-- 1 dteam004 dteam 0 Mar 19 09:36 /tmp/file3 -rw-r--r-- 1 dteam004 dteam 0 Mar 19 09:36 /tmp/file4 | |||||||
Activity with EnvironmentConsider this activity: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 279 to 279 | ||||||||
to understand how to save and check the submission scripts. | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
CPU Allocation Test 2 | ||||||||
Line: 309 to 309 | ||||||||
with S equal to the value published as GlueHostArchitectureSMPSize . | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
CPU Allocation Test 3 | ||||||||
Line: 341 to 341 | ||||||||
with S equal to the value published as GlueHostArchitectureSMPSize . | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
CPU Allocation Test 4 | ||||||||
Line: 375 to 375 | ||||||||
R = C % G | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
CPU Allocation Test 5 | ||||||||
Line: 412 to 412 | ||||||||
R = C % H | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
CPU Allocation Test 6 | ||||||||
Line: 438 to 438 | ||||||||
PBS -l nodes=C | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
JobStatus test | ||||||||
Line: 455 to 455 | ||||||||
Verify the proper functionality of the --from and -to option. Specify a time range where a single job was submitted, and verify that only the status of this job is returned. | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
Line: 533 to 533 | ||||||||
After 24 hours recheck the status of the job with glite-ce-job-status . The job should not be found. Verify in the CREAM CE in the CREAM sandbox dir that a directory for this job doesn't exist anymore. | ||||||||
Changed: | ||||||||
< < | Status: Not Implemented | |||||||
> > | Status: Implemented in the Robot based testsuite | |||||||
Line: 743 to 743 | ||||||||
Proxy renewal | ||||||||
Changed: | ||||||||
< < | TBD | |||||||
> > | Create a 1 hour proxy and delegate it:
[sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam -valid 01:00 Enter GRID pass phrase: Your identity: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto Creating temporary proxy ..................... Done Contacting voms2.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr] "dteam" Done Creating proxy ............................. Done Your proxy is valid until Sun Mar 18 11:59:28 2012 [sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 6694176412145996Verify with glite-es-delegation-info that the proxy lasts 1 hour: [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-info -e cream-47.pd.infn.it 6694176412145996 Lifetime = Sun Mar 18 11:58:35 2012 Issuer = CN=proxy,CN=proxy,CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=IT Subject = CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=ITCreate a 2 hours proxy and renew the previously delegated proxy: [sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam -valid 02:00 Enter GRID pass phrase: Your identity: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto Creating temporary proxy .................................... Done Contacting voms2.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr] "dteam" Done Creating proxy ............................................................... Done Your proxy is valid until Sun Mar 18 13:00:27 2012 [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-renew -e cream-47.pd.infn.it 6694176412145996 Delegation with identifier [6694176412145996] successfully renewedVerify with glite-es-delegation-info that the proxy lasts 2 hours: [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-info -e cream-47.pd.infn.it 6694176412145996 Lifetime = Sun Mar 18 12:59:36 2012 Issuer = CN=proxy,CN=proxy,CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=IT Subject = CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=IT | |||||||
Activity without data staging | ||||||||
Line: 1321 to 1369 | ||||||||
Activity with Input and Output with multiple Sources (both wrong) | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | TBD | |||||||
Status: Not Implemented | ||||||||
Line: 1567 to 1615 | ||||||||
Status: Not Implemented | ||||||||
Changed: | ||||||||
< < | Proxy renewal con 2 deleghe | |||||||
> > | Proxy renewal of multiple delegations | |||||||
Changed: | ||||||||
< < | [sgaravat@cream-50 ~]$ voms-proxy-init -voms dteam -valid 00:30Enter GRID pass phrase: | |||||||
> > | Create a short proxy:
[sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam -valid 00:30 Enter GRID pass phrase: | |||||||
Your identity: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto | ||||||||
Changed: | ||||||||
< < | Creating temporary proxy ....................... Done Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "dteam" Done Creating proxy ........................................ Done | |||||||
> > | Creating temporary proxy ..................... Done Contacting voms2.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr] "dteam" Done Creating proxy .................................................. Done Your proxy is valid until Sun Mar 18 10:12:19 2012 Delegate it twice, i.e. create two delegations: | |||||||
Changed: | ||||||||
< < | Your proxy is valid until Thu Mar 15 15:53:20 2012 [sgaravat@cream-50 ~]$ cd ADLExamples/ | |||||||
> > | ||||||||
[sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it | ||||||||
Changed: | ||||||||
< < | DelegationID = 7409072324574691 [sgaravat@cream-50 ADLExamples]$ emacs -nw proxyrenewal.adl | |||||||
> > | DelegationID = 5670349996819731 | |||||||
[sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it | ||||||||
Changed: | ||||||||
< < | DelegationID = 2700215137909804 [sgaravat@cream-50 ADLExamples]$ emacs -nw proxyrenewal.adl[sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it proxyrenewal.adl | |||||||
> > | DelegationID = 6261618400431184
Consider this ADL (the delegationids are the ones returned by the glite-es-delegate-proxy commands):
[sgaravat@cream-50 ADLExamples]$ cat proxyrenewal.adl <ActivityDescription> <ActivityIdentification> <Name>Proxy Renewal</Name> <Description>Proxy Renewal</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>proxyrenewal.sh</Path> </Executable> <Input>file.inp</Input> <Output>file.out</Output> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <ClientDataPush>true</ClientDataPush> <InputFile> <Name>file.inp</Name> <Source> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.inp</URI> <DelegationID>5670349996819731</DelegationID> </Source> </InputFile> <OutputFile> <Name>file.out</Name> <Target> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.out</URI> <DelegationID>6261618400431184</DelegationID> </Target> </OutputFile> </DataStaging> </ActivityDescription> [sgaravat@cream-50 ADLExamples]$ cat proxyrenewal.sh #!/bin/sh sleep 3600 /usr/bin/teeCreate the input file gsiftp://cream-35.pd.infn.it/tmp/file.inp and submit this activity:
sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it proxyrenewal.adl | |||||||
*************************************** | ||||||||
Changed: | ||||||||
< < | ActivityID = CR_ES702776033 | |||||||
> > | ActivityID = CR_ES898737831 | |||||||
ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {CLIENT_STAGEIN_POSSIBLE} | ||||||||
Changed: | ||||||||
< < | Timestamp = Thu Mar 15 15:24:19 2012 | |||||||
> > | Timestamp = Sun Mar 18 09:47:58 2012 | |||||||
Description = ETNSC = | ||||||||
Changed: | ||||||||
< < | STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/70/CR_ES702776033/ISB} | |||||||
> > | STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/89/CR_ES898737831/ISB} | |||||||
SESSION Dir = {} | ||||||||
Changed: | ||||||||
< < | STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/70/CR_ES702776033/OSB} [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. | |||||||
> > | STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/89/CR_ES898737831/OSB}
Upload the proxyrenewal.sh input file and notify the service:
[sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [Globus Toolkit 5.2.0] ready. | |||||||
230 User dteam004 logged in. | ||||||||
Changed: | ||||||||
< < | UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/70/CR_ES702776033/ISB | |||||||
> > | UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/89/CR_ES898737831/ISB | |||||||
UberFTP> put proxyrenewal.sh | ||||||||
Changed: | ||||||||
< < | proxyrenewal.sh: 34 bytes in 0.015364 Seconds (2.161 KB/s) | |||||||
> > | proxyrenewal.sh: 34 bytes in 0.011920 Seconds (2.785 KB/s) | |||||||
UberFTP> bye 221 Goodbye. | ||||||||
Changed: | ||||||||
< < | [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES702776033:CLIENT-DATAPUSH-DONE | |||||||
> > | [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES898737831:CLIENT-DATAPUSH-DONE | |||||||
Changed: | ||||||||
< < | [sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam Enter GRID pass phrase: wrong pass phrase Function: proxy_init_cred | |||||||
> > | After 10 minutes create a long proxy and renew the 2 delegations: | |||||||
[sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam Enter GRID pass phrase: Your identity: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto | ||||||||
Changed: | ||||||||
< < | Creating temporary proxy .................................... Done | |||||||
> > | Creating temporary proxy ......................................... Done | |||||||
Contacting voms2.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr] "dteam" Done | ||||||||
Changed: | ||||||||
< < | Creating proxy ................................................. Done | |||||||
> > | Creating proxy .................................................................... Done | |||||||
Changed: | ||||||||
< < | Your proxy is valid until Fri Mar 16 03:36:11 2012 [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-renew -e cream-47.pd.infn.it 2700215137909804 Delegation with identifier [2700215137909804] successfully renewed [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-renew -e cream-47.pd.infn.it 7409072324574691 Delegation with identifier [7409072324574691] successfully renewed | |||||||
> > | Your proxy is valid until Sun Mar 18 21:51:31 2012 | |||||||
Added: | ||||||||
> > | [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-renew -e cream-47.pd.infn.it 5670349996819731 Delegation with identifier [5670349996819731] successfully renewed [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-renew -e cream-47.pd.infn.it 6261618400431184 Delegation with identifier [6261618400431184] successfully renewed | |||||||
Changed: | ||||||||
< < | xxxxxx | |||||||
> > | After 30 minutes check the job status which should be TERMINAL without attributes:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES898737831 ***************************************** JobID = CR_ES898737831 Status = TERMINAL Attributes = {} Timestamp = Sun Mar 18 10:49:42 2012 Description = reason=0Verify also that the output file gsiftp://cream-35.pd.infn.it/tmp/file.out has been created. | |||||||
Submission of multiple activities | ||||||||
Line: 1725 to 1846 | ||||||||
Validations | ||||||||
Added: | ||||||||
> > | TBD | |||||||
Activity with Environment | ||||||||
Added: | ||||||||
> > | Consider this activity:
[sgaravat@cream-50 ADLExamples]$ cat environment.adl <ActivityDescription> <ActivityIdentification> <Name>env</Name> <Description>env</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/env</Path> </Executable> <Output>env.out</Output> <Environment> <Name>colore</Name> <Value>rosso</Value> </Environment> <Environment> <Name>forma</Name> <Value>rombo</Value> </Environment> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <OutputFile> <Name>env.out</Name> </OutputFile> </DataStaging> </ActivityDescription>Submit it: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it environment.adl ***************************************** ActivityID = CR_ES953523652 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Sun Mar 18 11:22:47 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/95/CR_ES953523652/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/95/CR_ES953523652/OSB}When the status is TERMINAL with CLIENT_STAGEOUT_POSSIBLE retrieve the output file:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES953523652 ***************************************** JobID = CR_ES953523652 Status = TERMINAL Attributes = {CLIENT_STAGEOUT_POSSIBLE} Timestamp = Sun Mar 18 11:22:51 2012 Description = reason=0 [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [Globus Toolkit 5.2.0] ready. 230 User dteam004 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/95/CR_ES953523652/OSB UberFTP> ls drwx------ 3 dteam004 dteam 4096 Mar 18 11:22 . drwx------ 4 dteam004 dteam 4096 Mar 18 11:22 .. -rw-r--r-- 1 dteam004 dteam 3179 Mar 18 11:22 env.out UberFTP> get env.out env.out: 3179 bytes in 0.012435 Seconds (249.658 KB/s) UberFTP> bye 221 Goodbye.Verify that in output file the two variables are defined: [sgaravat@cream-50 ADLExamples]$ grep -i colore env.out colore=rosso [sgaravat@cream-50 ADLExamples]$ grep -i forma env.out forma=rombo | |||||||
Pause and Resume |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 1569 to 1569 | ||||||||
Proxy renewal con 2 deleghe | ||||||||
Changed: | ||||||||
< < | [sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam -valid 00:30 Enter GRID pass phrase: | |||||||
> > | [sgaravat@cream-50 ~]$ voms-proxy-init -voms dteam -valid 00:30Enter GRID pass phrase: | |||||||
Your identity: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto | ||||||||
Changed: | ||||||||
< < | Creating temporary proxy ............................................................... Done | |||||||
> > | Creating temporary proxy ....................... Done | |||||||
Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "dteam" Done | ||||||||
Changed: | ||||||||
< < | Creating proxy ....................................... Done | |||||||
> > | Creating proxy ........................................ Done | |||||||
Changed: | ||||||||
< < | Your proxy is valid until Tue Mar 13 12:30:38 2012 | |||||||
> > | Your proxy is valid until Thu Mar 15 15:53:20 2012 [sgaravat@cream-50 ~]$ cd ADLExamples/ | |||||||
[sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it | ||||||||
Changed: | ||||||||
< < | DelegationID = 2415012188170419 | |||||||
> > | DelegationID = 7409072324574691 | |||||||
[sgaravat@cream-50 ADLExamples]$ emacs -nw proxyrenewal.adl [sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it | ||||||||
Changed: | ||||||||
< < | DelegationID = 8383865496467339 | |||||||
> > | DelegationID = 2700215137909804 | |||||||
[sgaravat@cream-50 ADLExamples]$ emacs -nw proxyrenewal.adl[sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ | ||||||||
Added: | ||||||||
> > | [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it proxyrenewal.adl *************************************** ActivityID = CR_ES702776033 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {CLIENT_STAGEIN_POSSIBLE} Timestamp = Thu Mar 15 15:24:19 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/70/CR_ES702776033/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/70/CR_ES702776033/OSB} [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam004 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/70/CR_ES702776033/ISB UberFTP> put proxyrenewal.sh proxyrenewal.sh: 34 bytes in 0.015364 Seconds (2.161 KB/s) UberFTP> bye 221 Goodbye. [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES702776033:CLIENT-DATAPUSH-DONE [sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam Enter GRID pass phrase: wrong pass phrase Function: proxy_init_cred [sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam Enter GRID pass phrase: Your identity: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto Creating temporary proxy .................................... Done Contacting voms2.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms2.hellasgrid.gr] "dteam" Done Creating proxy ................................................. Done Your proxy is valid until Fri Mar 16 03:36:11 2012 | |||||||
[sgaravat@cream-50 ADLExamples]$ | ||||||||
Added: | ||||||||
> > | [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-renew -e cream-47.pd.infn.it 2700215137909804 Delegation with identifier [2700215137909804] successfully renewed [sgaravat@cream-50 ADLExamples]$ glite-es-delegation-renew -e cream-47.pd.infn.it 7409072324574691 Delegation with identifier [7409072324574691] successfully renewed xxxxxx | |||||||
Submission of multiple activities |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 1319 to 1319 | ||||||||
Status: Not Implemented | ||||||||
Added: | ||||||||
> > | Activity with Input and Output with multiple Sources (both wrong) | |||||||
Added: | ||||||||
> > |
Status: Not Implemented
Activity with Input and Output with multiple Sources (one wrong, one correct)Delegate a proxy:[sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 7658329806304154Consider the following ADL (the delegationid is the one returned by the previous command): [sgaravat@cream-50 ADLExamples]$ cat datastag8.adl <ActivityDescription> <ActivityIdentification> <Name>cat</Name> <Description>cat</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/cat</Path> </Executable> <Input>file.inp</Input> <Output>file.out</Output> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <InputFile> <Name>file.inp</Name> <Source> <URI>gsiftp://host1.domain1/tmp/file.inp</URI> <DelegationID>7658329806304154</DelegationID> </Source> <Source> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.inp</URI> <DelegationID>7658329806304154</DelegationID> </Source> </InputFile> <OutputFile> <Name>file.out</Name> <Target> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.out</URI> <DelegationID>7658329806304154</DelegationID> </Target> </OutputFile> </DataStaging> </ActivityDescription>Create the input file gsiftp://cream-35.pd.infn.it/tmp/file.inp and submit the activity:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it datastag8.adl ***************************************** ActivityID = CR_ES475196853 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Thu Mar 15 11:39:07 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/47/CR_ES475196853/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam004/47/CR_ES475196853/OSB}Check the status which should eventually be TERMINAL :
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES475196853 ***************************************** JobID = CR_ES475196853 Status = TERMINAL Attributes = {} Timestamp = Thu Mar 15 11:39:18 2012 Description = reason=0Verify that the output file gsiftp://cream-35.pd.infn.it/tmp/file.out has been created.
Status: Not Implemented | |||||||
Activity with Input and Output with multiple TargetsCreate a delegation: |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 1495 to 1495 | ||||||||
[sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ | ||||||||
Added: | ||||||||
> > | Submission of multiple activities | |||||||
Changed: | ||||||||
< < | [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it proxyrenewal.adl | |||||||
> > | Consider the follow ADL:
[sgaravat@cream-50 ADLExamples]$ cat multi.adl <CreateActivities> <ActivityDescription> <ActivityIdentification> <Name>sleep60</Name> <Description>sleep 60</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/sleep</Path> <Argument>60</Argument> </Executable> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> </ActivityDescription> <ActivityDescription> <ActivityIdentification> <Name>sleep60</Name> <Description>sleep 60</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/sleep</Path> <Argument>600</Argument> </Executable> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> </ActivityDescription> </CreateActivities>Submit it (two jobs should be submitted): [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it multi.adl | |||||||
*************************************** | ||||||||
Changed: | ||||||||
< < | ActivityID = CR_ES276293409 | |||||||
> > | ActivityID = CR_ES063075266 | |||||||
ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING | ||||||||
Changed: | ||||||||
< < | Status Attrs = {CLIENT_STAGEIN_POSSIBLE} Timestamp = Tue Mar 13 12:05:50 2012 | |||||||
> > | Status Attrs = {} Timestamp = Tue Mar 13 16:12:02 2012 | |||||||
Description = ETNSC = | ||||||||
Changed: | ||||||||
< < | STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/27/CR_ES276293409/ISB} | |||||||
> > | STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/06/CR_ES063075266/ISB} | |||||||
SESSION Dir = {} | ||||||||
Changed: | ||||||||
< < | STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/27/CR_ES276293409/OSB} [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/27/CR_ES276293409/ISB UberFTP> put proxy_renewal.sh proxy_renewal.sh: 34 bytes in 0.015349 Seconds (2.163 KB/s) UberFTP> bye 221 Goodbye. [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES276293409:CLIENT-DATAPUSH-DONE | |||||||
> > | STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/06/CR_ES063075266/OSB} *************************************** ActivityID = CR_ES016651242 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Tue Mar 13 16:12:03 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/01/CR_ES016651242/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/01/CR_ES016651242/OSB} | |||||||
Added: | ||||||||
> > | Check their status using a single command: | |||||||
Added: | ||||||||
> > | [sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES016651242 CR_ES063075266 ***************************************** JobID = CR_ES016651242 Status = PROCESSING_RUNNING Attributes = {} Timestamp = Tue Mar 13 16:12:15 2012 Description = ***************************************** JobID = CR_ES063075266 Status = TERMINAL Attributes = {} Timestamp = Tue Mar 13 16:13:10 2012 Description = reason=0 [sgaravat@cream-50 ADLExamples]$ | |||||||
Validations | ||||||||
Line: 1529 to 1595 | ||||||||
Added: | ||||||||
> > | Pause and ResumeCreate a long activity:[sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it activity_sleep60.adl ***************************************** ActivityID = CR_ES679500221 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Tue Mar 13 16:25:08 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/67/CR_ES679500221/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/67/CR_ES679500221/OSB}Wait some minutes and then pause it: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-pause -e cream-47.pd.infn.it CR_ES679500221Wait some minutes and the check its status which should be PROCESSING_RUNNING with CLIENT_PAUSED as attribute:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES679500221 ***************************************** JobID = CR_ES679500221 Status = PROCESSING_RUNNING Attributes = {CLIENT_PAUSED} Timestamp = Tue Mar 13 16:25:33 2012 Description =Resume it: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-resume -e cream-47.pd.infn.it CR_ES679500221Wait some minutes and then check its status again which should be PROCESSING_RUNNING without attributes: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES679500221 ***************************************** JobID = CR_ES679500221 Status = PROCESSING_RUNNING Attributes = {} Timestamp = Tue Mar 13 16:26:16 2012 Description = CancelSubmit a long activity:[sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it activity_sleep60.adl ***************************************** ActivityID = CR_ES619765347 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Tue Mar 13 15:59:25 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/61/CR_ES619765347/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/61/CR_ES619765347/OSB}Wait a while and then cancel it: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-cancel -e cream-47.pd.infn.it CR_ES619765347Check the status that eventually should be TERMINAL with xxx_CANCEL as attribute:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES619765347 ***************************************** JobID = CR_ES619765347 Status = TERMINAL Attributes = {PROCESSING_CANCEL} Timestamp = Tue Mar 13 16:00:04 2012 Description = cancelled by the user WipeSubmit an activity and wait that the status is TERMINAL:[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES668400340 ***************************************** JobID = CR_ES668400340 Status = TERMINAL Attributes = {} Timestamp = Tue Mar 13 15:51:24 2012 Description = reason=0Issue the wipe: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-wipe -e cream-47.pd.infn.it CR_ES668400340Retry a status, which should report that the activity is not found: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES668400340 ***************************************** JobID = CR_ES668400340 Message = Activity not found! Timestamp = Tue Mar 13 15:51:57 2012 Description = N/A FailCode = N/AVerify that the job sandbox directory has been removed | |||||||
Regression testsSee: http://wiki.italiangrid.it/twiki/bin/view/CREAM/RegressionTestWorkPlan |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 1477 to 1477 | ||||||||
Proxy renewal con 2 deleghe | ||||||||
Added: | ||||||||
> > | [sgaravat@cream-50 ADLExamples]$ voms-proxy-init -voms dteam -valid 00:30 Enter GRID pass phrase: Your identity: /C=IT/O=INFN/OU=Personal Certificate/L=Padova/CN=Massimo Sgaravatto Creating temporary proxy ............................................................... Done Contacting voms.hellasgrid.gr:15004 [/C=GR/O=HellasGrid/OU=hellasgrid.gr/CN=voms.hellasgrid.gr] "dteam" Done Creating proxy ....................................... Done Your proxy is valid until Tue Mar 13 12:30:38 2012 [sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 2415012188170419 [sgaravat@cream-50 ADLExamples]$ emacs -nw proxyrenewal.adl [sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 8383865496467339 [sgaravat@cream-50 ADLExamples]$ emacs -nw proxyrenewal.adl[sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it proxyrenewal.adl *************************************** ActivityID = CR_ES276293409 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {CLIENT_STAGEIN_POSSIBLE} Timestamp = Tue Mar 13 12:05:50 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/27/CR_ES276293409/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/27/CR_ES276293409/OSB} [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/27/CR_ES276293409/ISB UberFTP> put proxy_renewal.sh proxy_renewal.sh: 34 bytes in 0.015349 Seconds (2.163 KB/s) UberFTP> bye 221 Goodbye. [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES276293409:CLIENT-DATAPUSH-DONE | |||||||
Validations |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 855 to 855 | ||||||||
Activity with Input and Output: Client Data Push and Client Data Pull | ||||||||
Changed: | ||||||||
< < | datastag0.adl | |||||||
> > | Consider this ADL:
<ActivityDescription> <ActivityIdentification> <Name>cat</Name> <Description>cat</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/cat</Path> </Executable> <Input>file.inp</Input> <Output>file.out</Output> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <ClientDataPush>true</ClientDataPush> <OutputFile> <Name>file.out</Name> </OutputFile> </DataStaging> </ActivityDescription>Submit it: $ glite-es-activity-create -e cream-47.pd.infn.it datastag0.adl ***************************************** ActivityID = CR_ES853730468 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {CLIENT_STAGEIN_POSSIBLE} Timestamp = Tue Mar 13 09:20:33 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/85/CR_ES853730468/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/85/CR_ES853730468/OSB}Stage the input files in the STAGEIN Dir: [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/85/CR_ES853730468/ISB UberFTP> put file.inp file.inp: 18 bytes in 0.015343 Seconds (1.146 KB/s) UberFTP> bye 221 Goodbye.Notify the service that the stagein was done: [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES853730468:CLIENT-DATAPUSH-DONECheck the status that eventually should be TERMINAL with CLIENT_STAGEOUT_POSSIBLE as attribute:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES853730468 ***************************************** JobID = CR_ES853730468 Status = TERMINAL Attributes = {CLIENT_STAGEOUT_POSSIBLE} Timestamp = Tue Mar 13 09:21:22 2012 Description = reason=0Retrieve the output files from the STAGEOUT Dir: [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/85/CR_ES853730468/OSB UberFTP> ls drwx------ 3 dteam042 dteam 4096 Mar 13 09:21 . drwx------ 4 dteam042 dteam 4096 Mar 13 09:21 .. -rw-r--r-- 1 dteam042 dteam 18 Mar 13 09:21 file.out UberFTP> get file.out file.out: 18 bytes in 0.010151 Seconds (1.732 KB/s) UberFTP> bye 221 Goodbye.Notify the service that the stageout was done: [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES853730468:CLIENT-DATAPULL-DONECheck the job status which should be TERMINAL without attributes:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES853730468 ***************************************** JobID = CR_ES853730468 Status = TERMINAL Attributes = {} Timestamp = Tue Mar 13 09:21:23 2012 Description = reason=0Status: Not Implemented | |||||||
Activity with Input and Output: Server Data Push and Server Data Pull | ||||||||
Changed: | ||||||||
< < | datastag1.adl | |||||||
> > | Delegate a proxy:
[sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 32141661326088133Consider this JDL (the DelegationID should be the one returned by the glite-es-delegate-proxy operation): [sgaravat@cream-50 ADLExamples]$ cat datastag1.adl <ActivityDescription> <ActivityIdentification> <Name>cat</Name> <Description>cat</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/cat</Path> </Executable> <Input>file.inp</Input> <Output>file.out</Output> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <InputFile> <Name>file.inp</Name> <Source> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.inp</URI> <DelegationID>32141661326088133</DelegationID> </Source> </InputFile> <OutputFile> <Name>file.out</Name> <Target> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.out</URI> <DelegationID>32141661326088133</DelegationID> </Target> </OutputFile> </DataStaging> </ActivityDescription>Create the input file gsiftp://cream-35.pd.infn.it/tmp/file.inp .
Submit the activity:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it datastag1.adl ***************************************** ActivityID = CR_ES691768495 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Tue Mar 13 09:39:34 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/69/CR_ES691768495/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/69/CR_ES691768495/OSB}Check the job status which should eventually be TERMINAL :
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES691768495 ***************************************** JobID = CR_ES691768495 Status = TERMINAL Attributes = {} Timestamp = Tue Mar 13 09:39:45 2012 Description = reason=0Verify that the specified output file ( gsiftp://cream-35.pd.infn.it/tmp/file.out ) has been produced.
Status: Not Implemented | |||||||
Activity with Input and Output: Server and Client Data Push, Server and Client Data Pull | ||||||||
Changed: | ||||||||
< < | datastag2.adl | |||||||
> > | Delegate a proxy:
[sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 3368110324080861Consider this ADL (the DelegationID) must be the one returned by the glite-es-delegate-proxy command: [sgaravat@cream-50 ADLExamples]$ cat datastag2.adl <ActivityDescription> <ActivityIdentification> <Name>cat</Name> <Description>cat</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>myscript.sh</Path> </Executable> <Output>myscript.out</Output> <Error>myscript.err</Error> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <ClientDataPush>true</ClientDataPush> <InputFile> <Name>file.inp</Name> <Source> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.inp</URI> <DelegationID>3368110324080861</DelegationID> </Source> </InputFile> <OutputFile> <Name>myscript.out</Name> <Target> <URI>gsiftp://cream-35.pd.infn.it/tmp/myscript.out</URI> <DelegationID>3368110324080861</DelegationID> </Target> </OutputFile> <OutputFile> <Name>myscript.err</Name> </OutputFile> </DataStaging> </ActivityDescription>Create the input file gsiftp://cream-35.pd.infn.it/tmp/file.inp and submit the activity:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it datastag2.adl ***************************************** ActivityID = CR_ES526044183 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {CLIENT_STAGEIN_POSSIBLE} Timestamp = Tue Mar 13 10:01:29 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/52/CR_ES526044183/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/52/CR_ES526044183/OSB}Upload the input file in the STAGEIN Dir and notify the service that the upload was done: [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/52/CR_ES526044183/ISB [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/52/CR_ES526044183/ISB UberFTP> put myscript.sh myscript.sh: 50 bytes in 0.015672 Seconds (3.116 KB/s) UberFTP> bye 221 Goodbye. [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES526044183:CLIENT-DATAPUSH-DONECheck the status which eventually should be TERMINAL with CLIENT_STAGEOUT_POSSIBLE as attribute:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES526044183 ***************************************** JobID = CR_ES526044183 Status = TERMINAL Attributes = {CLIENT_STAGEOUT_POSSIBLE} Timestamp = Tue Mar 13 10:02:25 2012 Description = reason=0Download the output files from the StageOUT Dir and notify the service: [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/52/CR_ES526044183/OSB UberFTP> ls drwx------ 3 dteam042 dteam 4096 Mar 13 10:02 . drwx------ 4 dteam042 dteam 4096 Mar 13 10:02 .. -rw-r--r-- 1 dteam042 dteam 55 Mar 13 10:02 myscript.err UberFTP> get myscript.err myscript.err: 55 bytes in 0.012255 Seconds (4.383 KB/s) UberFTP> bye 221 Goodbye. [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES526044183:CLIENT-DATAPULL-DONECheck the status which should be TERMINAL without attributes:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES526044183 ***************************************** JobID = CR_ES526044183 Status = TERMINAL Attributes = {} Timestamp = Tue Mar 13 10:02:26 2012 Description = reason=0Verify that the output file gsiftp://cream-35.pd.infn.it/tmp/myscript.out has been produced.
Status: Not Implemented | |||||||
Activity with Input and Output: Server and Client Data Push, Server and Client Data Pull, and multiple Delegations | ||||||||
Changed: | ||||||||
< < | datastag3.adl | |||||||
> > | Perform two delegations:
[sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 059683951543786695 [sgaravat@cream-50 ADLExamples]$ [sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 5352938890620005Consider this ADL (the 2 delegationids must be the ones returned by the glite-es-delegate-proxy commands): [sgaravat@cream-50 ADLExamples]$ cat datastag3.adl <ActivityDescription> <ActivityIdentification> <Name>cat</Name> <Description>cat</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>myscript.sh</Path> </Executable> <Output>myscript.out</Output> <Error>myscript.err</Error> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <ClientDataPush>true</ClientDataPush> <InputFile> <Name>file.inp</Name> <Source> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.inp</URI> <DelegationID>059683951543786695</DelegationID> </Source> </InputFile> <OutputFile> <Name>myscript.out</Name> <Target> <URI>gsiftp://cream-35.pd.infn.it/tmp/myscript.out</URI> <DelegationID>5352938890620005</DelegationID> </Target> </OutputFile> <OutputFile> <Name>myscript.err</Name> </OutputFile> </DataStaging> </ActivityDescription>Create the input file gsiftp://cream-35.pd.infn.it/tmp/file.inp and submit the activity:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it datastag3.adl ***************************************** ActivityID = CR_ES034507131 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {CLIENT_STAGEIN_POSSIBLE} Timestamp = Tue Mar 13 10:15:11 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/03/CR_ES034507131/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/03/CR_ES034507131/OSB}Upload the input files in the STAGEIN Dir and notify the service: [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it 220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/03/CR_ES034507131/ISB UberFTP> put myscript.sh myscript.sh: 50 bytes in 0.015260 Seconds (3.200 KB/s) UberFTP> bye 221 Goodbye. [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES034507131:CLIENT-DATAPUSH-DONECheck the activity status which eventually should be TERMINAL with CLIENT_STAGEOUT_POSSIBLE as attribute:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES034507131 ***************************************** JobID = CR_ES034507131 Status = TERMINAL Attributes = {CLIENT_STAGEOUT_POSSIBLE} Timestamp = Tue Mar 13 10:16:05 2012 Description = reason=0Download the output files from the StageOUT Dir and notify the service: [sgaravat@cream-50 ADLExamples]$ uberftp cream-47.pd.infn.it220 cream-47.pd.infn.it GridFTP Server 6.5 (gcc64, 1323378368-83) [unknown] ready. 230 User dteam042 logged in. UberFTP> cd /var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/03/CR_ES034507131/OSB UberFTP> ls drwx------ 3 dteam042 dteam 4096 Mar 13 10:16 . drwx------ 4 dteam042 dteam 4096 Mar 13 10:16 .. -rw-r--r-- 1 dteam042 dteam 55 Mar 13 10:16 myscript.err UberFTP> get myscript.err myscript.err: 55 bytes in 0.011562 Seconds (4.645 KB/s) UberFTP> bye 221 Goodbye. [sgaravat@cream-50 ADLExamples]$ glite-es-notify-service -e cream-47.pd.infn.it CR_ES034507131:CLIENT-DATAPULL-DONECheck the status which should be TERMINAL without attributes:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES034507131 ***************************************** JobID = CR_ES034507131 Status = TERMINAL Attributes = {} Timestamp = Tue Mar 13 10:16:05 2012 Description = reason=0Verify that the output file gsiftp://cream-35.pd.infn.it/tmp/myscript.out has been created.
Status: Not Implemented | |||||||
Activity with Input and Output with multiple Targets | ||||||||
Changed: | ||||||||
< < | datastag5.adl | |||||||
> > | Create a delegation:
[sgaravat@cream-50 ADLExamples]$ glite-es-delegate-proxy -e cream-47.pd.infn.it DelegationID = 6749966998262459Consider this ADL, where the delegationid is the one returned by the glite-es-delegate-proxy command:
[sgaravat@cream-50 ADLExamples]$ cat datastag5.adl <ActivityDescription> <ActivityIdentification> <Name>cat</Name> <Description>cat</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/cat</Path> </Executable> <Input>file.inp</Input> <Output>file.out</Output> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <InputFile> <Name>file.inp</Name> <Source> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.inp</URI> <DelegationID>6749966998262459</DelegationID> </Source> </InputFile> <OutputFile> <Name>file.out</Name> <Target> <URI>gsiftp://cream-47.pd.infn.it/tmp/file.out</URI> <DelegationID>6749966998262459</DelegationID> <Mandatory>true</Mandatory> </Target> <Target> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.out</URI> <DelegationID>6749966998262459</DelegationID> <Mandatory>true</Mandatory> </Target> </OutputFile> </DataStaging> </ActivityDescription>Create the input file gsiftp://cream-35.pd.infn.it/tmp/file.inp and submit the activity:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it datastag5.adl ***************************************** ActivityID = CR_ES417521144 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING Status Attrs = {} Timestamp = Tue Mar 13 10:33:14 2012 Description = ETNSC = STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/41/CR_ES417521144/ISB} SESSION Dir = {} STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/41/CR_ES417521144/OSB}Check the job status which eventually should be TERMINAL without attributes:
[sgaravat@cream-50 ADLExamples]$ glite-es-activity-status -e cream-47.pd.infn.it CR_ES417521144 ***************************************** JobID = CR_ES417521144 Status = TERMINAL Attributes = {} Timestamp = Tue Mar 13 10:33:26 2012 Description = reason=0Verify that the output files gsiftp://cream-47.pd.infn.it/tmp/file.out and gsiftp://cream-35.pd.infn.it/tmp/file.out have been both created.
Status: Not Implemented | |||||||
Activity with Input and Output specifying a non existing delegationid | ||||||||
Changed: | ||||||||
< < | datastagnodel.adl | |||||||
> > | Consider this ADL (where the specified delegationid doesn't exist):
[sgaravat@cream-50 ADLExamples]$ cat datastagnodel.adl <ActivityDescription> <ActivityIdentification> <Name>cat</Name> <Description>cat</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>myscript.sh</Path> </Executable> <Output>myscript.out</Output> <Error>myscript.err</Error> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> <DataStaging> <ClientDataPush>true</ClientDataPush> <InputFile> <Name>file.inp</Name> <Source> <URI>gsiftp://cream-35.pd.infn.it/tmp/file.inp</URI> <DelegationID>xyz</DelegationID> </Source> </InputFile> <OutputFile> <Name>myscript.out</Name> <Target> <URI>gsiftp://cream-35.pd.infn.it/tmp/myscript.out</URI> <DelegationID>xyz</DelegationID> </Target> </OutputFile> <OutputFile> <Name>myscript.err</Name> </OutputFile> </DataStaging> </ActivityDescription>and try to submit it. An error should be returned: [sgaravat@cream-50 ADLExamples]$ glite-es-activity-create -e cream-47.pd.infn.it datastagnodel.adl ***************************************** ActivityID = FAULT: Message=[delegation [delegId=xyz; dn=CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT; localUser=dteam042] not found!] Timestamp=[1331631651] ActivityMgrURI = Status = N/A ETNSC = STAGEIN Dir = {} SESSION Dir = {} STAGEOUT Dir = {}Status: Not Implemented Proxy renewal con 2 delegheValidations | |||||||
Activity with Environment |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 745 to 745 | ||||||||
TBD | ||||||||
Changed: | ||||||||
< < | Activity submission without data staging | |||||||
> > | Activity without data staging | |||||||
Submit an activity where in the Application part there is just the Executable without failifExitCodeNotEqualTo . | ||||||||
Line: 800 to 800 | ||||||||
Status: Not Implemented | ||||||||
Changed: | ||||||||
< < | Activity submission with failifExitCodeNotEqualTo | |||||||
> > | Activity with failifExitCodeNotEqualTo | |||||||
Submit an activity where in the Application part there is just the Executable with failifExitCodeNotEqualTo . | ||||||||
Line: 853 to 853 | ||||||||
Status: Not Implemented | ||||||||
Changed: | ||||||||
< < | Activity submission with Input and Output: Client Data Push and Client Data Pull | |||||||
> > | Activity with Input and Output: Client Data Push and Client Data Pull | |||||||
datastag0.adl | ||||||||
Changed: | ||||||||
< < | Activity submission with Input and Output: Server Data Push and Server Data Pull | |||||||
> > | Activity with Input and Output: Server Data Push and Server Data Pull | |||||||
datastag1.adl | ||||||||
Changed: | ||||||||
< < | Activity submission with Environment | |||||||
> > |
Activity with Input and Output: Server and Client Data Push, Server and Client Data Pulldatastag2.adlActivity with Input and Output: Server and Client Data Push, Server and Client Data Pull, and multiple Delegationsdatastag3.adlActivity with Input and Output with multiple Targetsdatastag5.adlActivity with Input and Output specifying a non existing delegationiddatastagnodel.adlActivity with Environment | |||||||
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 770 to 770 | ||||||||
$ glite-es-activity-create -e cream-38.pd.infn.it activity_sleep60.adl | ||||||||
Added: | ||||||||
> > | $ glite-es-activity-create -e cream-47.pd.infn.it activity_sleep60.adl | |||||||
*************************************** | ||||||||
Changed: | ||||||||
< < | ActivityID = CR_ES096117205 ActivityMgrURI = https://cream-38.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = ACCEPTED | |||||||
> > | ActivityID = CR_ES156078531 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING | |||||||
Status Attrs = {} | ||||||||
Changed: | ||||||||
< < | Timestamp = Tue Feb 28 15:42:05 2012 | |||||||
> > | Timestamp = Mon Mar 12 12:16:33 2012 | |||||||
Description = ETNSC = | ||||||||
Changed: | ||||||||
< < | STAGEIN Dir = {} | |||||||
> > | STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/15/CR_ES156078531/ISB} | |||||||
SESSION Dir = {} | ||||||||
Changed: | ||||||||
< < | STAGEOUT Dir = {} | |||||||
> > | STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/15/CR_ES156078531/OSB} | |||||||
Eventually check with glite-es-activity-status the state which should be TERMINAL without attributes: | ||||||||
Changed: | ||||||||
< < | $ glite-es-activity-status -e cream-38.pd.infn.it CR_ES096117205 Sending ActivityStatus request for ActivityID(s) {CR_ES096117205} to service [https://cream-38.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService] | |||||||
> > | $ glite-es-activity-status -e cream-47.pd.infn.it CR_ES156078531 | |||||||
*************************************** | ||||||||
Changed: | ||||||||
< < | JobID = CR_ES096117205 | |||||||
> > | JobID = CR_ES156078531 | |||||||
Status = TERMINAL Attributes = {} | ||||||||
Changed: | ||||||||
< < | Timestamp = Tue Feb 28 15:43:10 2012 | |||||||
> > | Timestamp = Mon Mar 12 12:17:42 2012 | |||||||
Description = reason=0 | ||||||||
Line: 824 to 824 | ||||||||
Changed: | ||||||||
< < | $ glite-es-activity-create -e cream-38.pd.infn.it activity_sleep60_failif.adl | |||||||
> > | $ glite-es-activity-create -e cream-47.pd.infn.it activity_sleep60_failif.adl | |||||||
*************************************** | ||||||||
Changed: | ||||||||
< < | ActivityID = CR_ES776810952 ActivityMgrURI = https://cream-38.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = ACCEPTED | |||||||
> > | ActivityID = CR_ES908177323 ActivityMgrURI = https://cream-47.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = PREPROCESSING | |||||||
Status Attrs = {} | ||||||||
Changed: | ||||||||
< < | Timestamp = Tue Feb 28 15:52:51 2012 | |||||||
> > | Timestamp = Mon Mar 12 12:18:57 2012 | |||||||
Description = ETNSC = | ||||||||
Changed: | ||||||||
< < | STAGEIN Dir = {} | |||||||
> > | STAGEIN Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/90/CR_ES908177323/ISB} | |||||||
SESSION Dir = {} | ||||||||
Changed: | ||||||||
< < | STAGEOUT Dir = {} | |||||||
> > | STAGEOUT Dir = {gsiftp://cream-47.pd.infn.it/var/cs-es/dteam/CN_Massimo_Sgaravatto_L_Padova_OU_Personal_Certificate_O_INFN_C_IT_dteam_Role_NULL_Capability_NULL_dteam042/90/CR_ES908177323/OSB} | |||||||
Eventually check with glite-es-activity-status the state which should be TERMINAL with attribute APP-FAILURE : | ||||||||
Changed: | ||||||||
< < | $ glite-es-activity-status -e cream-38.pd.infn.it CR_ES776810952 Sending ActivityStatus request for ActivityID(s) {CR_ES776810952} to service [https://cream-38.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService] | |||||||
> > | $ glite-es-activity-status -e cream-47.pd.infn.it CR_ES908177323 | |||||||
*************************************** | ||||||||
Changed: | ||||||||
< < | JobID = CR_ES776810952 | |||||||
> > | JobID = CR_ES908177323 | |||||||
Status = TERMINAL Attributes = {APP_FAILURE} | ||||||||
Changed: | ||||||||
< < | Timestamp = Tue Feb 28 15:53:54 2012 | |||||||
> > | Timestamp = Mon Mar 12 12:20:01 2012 | |||||||
Description = Executable exitCode 0 instead of 1 Status: Not Implemented | ||||||||
Changed: | ||||||||
< < | Activity submission with Input, Output, Client Data Push and Client Data Pull | |||||||
> > | Activity submission with Input and Output: Client Data Push and Client Data Pulldatastag0.adlActivity submission with Input and Output: Server Data Push and Server Data Pulldatastag1.adl | |||||||
Activity submission with Environment |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 46 to 46 | ||||||||
System tests | ||||||||
Changed: | ||||||||
< < | Basic functionality tests | |||||||
> > | Basic functionality tests for legacy interface | |||||||
Simple Submission Test | ||||||||
Line: 714 to 714 | ||||||||
Status: Not Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > |
Basic functionality tests for EMI-ES interfaceDelegationDelegate a proxy with theglite-es-delegate-proxy command.
It should return a delegationid.
E.g.:
glite-es-delegate-proxy -e cream-38.pd.infn.it DelegationID = 5655008298193933Check with the glite-es-delegation-info command about this delegationid. In particular check the lifetime field which should match the expiration time of the proxy in the UI:
$ glite-es-delegation-info -e cream-38.pd.infn.it 5655008298193933 Lifetime = Tue Feb 28 21:14:46 2012 Issuer = CN=proxy,CN=proxy,CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=IT Subject = CN=Massimo Sgaravatto,L=Padova,OU=Personal Certificate,O=INFN,C=IT Proxy renewalTBDActivity submission without data stagingSubmit an activity where in the Application part there is just the Executable withoutfailifExitCodeNotEqualTo .
$ cat activity_sleep60.adl <ActivityDescription> <ActivityIdentification> <Name>sleep60</Name> <Description>sleep 60</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/sleep</Path> <Argument>60</Argument> </Executable> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> </ActivityDescription> $ glite-es-activity-create -e cream-38.pd.infn.it activity_sleep60.adl ***************************************** ActivityID = CR_ES096117205 ActivityMgrURI = https://cream-38.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = ACCEPTED Status Attrs = {} Timestamp = Tue Feb 28 15:42:05 2012 Description = ETNSC = STAGEIN Dir = {} SESSION Dir = {} STAGEOUT Dir = {}Eventually check with glite-es-activity-status the state which should be TERMINAL without attributes:
$ glite-es-activity-status -e cream-38.pd.infn.it CR_ES096117205 Sending ActivityStatus request for ActivityID(s) {CR_ES096117205} to service [https://cream-38.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService] ***************************************** JobID = CR_ES096117205 Status = TERMINAL Attributes = {} Timestamp = Tue Feb 28 15:43:10 2012 Description = reason=0Status: Not Implemented Activity submission with failifExitCodeNotEqualToSubmit an activity where in the Application part there is just the Executable withfailifExitCodeNotEqualTo .
$ cat activity_sleep60_failif.adl <ActivityDescription> <ActivityIdentification> <Name>sleep60</Name> <Description>sleep 60</Description> <Type>single</Type> </ActivityIdentification> <Application> <Executable> <Path>/bin/sleep</Path> <Argument>60</Argument> <FailIfExitCodeNotEqualTo>1</FailIfExitCodeNotEqualTo> </Executable> </Application> <Resources> <QueueName>creamtest2</QueueName> </Resources> </ActivityDescription> $ glite-es-activity-create -e cream-38.pd.infn.it activity_sleep60_failif.adl ***************************************** ActivityID = CR_ES776810952 ActivityMgrURI = https://cream-38.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService Status = ACCEPTED Status Attrs = {} Timestamp = Tue Feb 28 15:52:51 2012 Description = ETNSC = STAGEIN Dir = {} SESSION Dir = {} STAGEOUT Dir = {}Eventually check with glite-es-activity-status the state which should be TERMINAL with attribute APP-FAILURE :
$ glite-es-activity-status -e cream-38.pd.infn.it CR_ES776810952 Sending ActivityStatus request for ActivityID(s) {CR_ES776810952} to service [https://cream-38.pd.infn.it:8443/ce-cream-es/services/ActivityManagementService] ***************************************** JobID = CR_ES776810952 Status = TERMINAL Attributes = {APP_FAILURE} Timestamp = Tue Feb 28 15:53:54 2012 Description = Executable exitCode 0 instead of 1Status: Not Implemented Activity submission with Input, Output, Client Data Push and Client Data PullActivity submission with Environment | |||||||
Regression testsSee: http://wiki.italiangrid.it/twiki/bin/view/CREAM/RegressionTestWorkPlan |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 541 to 541 | ||||||||
Verify the functionality of the glite-ce-proxy-renew command. | ||||||||
Changed: | ||||||||
< < | Submit a job lasting 1 hour using a proxy valid 30 minutes. | |||||||
> > | Submit a job lasting 20 minutes using a proxy valid 10 minutes. | |||||||
Changed: | ||||||||
< < | After 15 minutes renew the proxy with the glite-ce-proxy-renew command. | |||||||
> > |
After 10 minutes create on the UI a long proxy, and renew the proxy with the glite-ce-proxy-renew command. | |||||||
Verify the final job status which should eventually be DONE-OK |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 701 to 701 | ||||||||
Status: Not Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | LB testSubmit a job to CREAM through the gLite-WMS and wait till the job is Done status Check the logging-info output of this job: among the logged events there should be 3 events logged asLRMS as source:
| |||||||
Regression testsSee: http://wiki.italiangrid.it/twiki/bin/view/CREAM/RegressionTestWorkPlan |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 690 to 690 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | Blparser restart testConfigure a CREAM CE using the old blah blparser. Stop the blparser and after a few seconds (e.g. 10) restart it. Wait for 2 minute and try a job submission. The should run and complete properly. Status: Not Implemented in the Robot based testsuite | |||||||
Regression tests |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 764 to 764 | ||||||||
Deleted: | ||||||||
< < | Inter-component testsTBD | |||||||
Nagios probeFor testing nagios probes for worker nodes see here, tests description for nagios probes for direct cream job submission is here |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 240 to 240 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Changed: | ||||||||
< < | CPUNumber test | |||||||
> > | CPU Allocation Test 1 | |||||||
Changed: | ||||||||
< < | Execute /bin/uname -a.Set the jdl attribute CPUNumber to a certain number. The submission is expected to fail for a value of 0 (this is treated as the corect behaviour).On the other hand,it is expected to succeed and the final job state should be done-ok,if it has any other >=1 value. NOTE: The glite-ce-job-submit will succeed for an unsupported value (e.g. not enough cpus available on site) but will fail eventually and the final state of the job will be aborted (with a message such as: BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Job exceeds queue resource limits MSG=cannot locate feasible nodes-) N/A (jobId = CREAM918215196) | |||||||
> > | Submit a job where in the JDL there is: | |||||||
Changed: | ||||||||
< < | TBC | |||||||
> > | WholeNodes=true; SMPGranularity=G; Hostnumber=H; | |||||||
Changed: | ||||||||
< < | HostNumber test | |||||||
> > | with H > 1. | |||||||
Changed: | ||||||||
< < | Execute /bin/uname -a.Set the jdl attribute HostNumber to a certain number. The submission is expected to fail for a value of 0 (this is treated as the corect behaviour).On the other hand,it is expected to succeed and the final job state should be done-ok,if it has any other >=1 value. NOTE: The glite-ce-job-submit will succeed for an unsupported value (e.g. not enough cpus available on site) but will fail eventually and the final state of the job will be aborted (with a message such as: [BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Job exceeds queue resource limits MSG=cannot locate feasible nodes-) N/A (jobId = CREAM150008664)] | |||||||
> > | Verify that in the submission script there is | |||||||
Changed: | ||||||||
< < | TBC | |||||||
> > |
| |||||||
Changed: | ||||||||
< < | SMPGranularity Test | |||||||
> > | BSUB -n S*H BSUB -R "span[ptile=S] BSUB -x | |||||||
Changed: | ||||||||
< < | Execute /bin/uname -a.Set the jdl attribute SMPGranularity to a certain number. The submission is expected to fail for a value of 0 (this is treated as the corect behaviour).On the other hand,it is expected to succeed and the final job state should be done-ok,if it has any other >=1 value. NOTE: The glite-ce-job-submit will succeed for an unsupported value (e.g. not enough cpus available on site) but will fail eventually and the final state of the job will be aborted (with a message such as: [BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Job exceeds queue resource limits MSG=cannot locate feasible nodes-) N/A (jobId = CREAM348964588)] | |||||||
> > |
| |||||||
Added: | ||||||||
> > | PBS -l nodes=H:ppn=S PBS -W x=NACCESSPOLICY:SINGLEJOB | |||||||
Changed: | ||||||||
< < | TBC | |||||||
> > | with S equal to the value published as GlueHostArchitectureSMPSize . | |||||||
Deleted: | ||||||||
< < | WholeNode Test | |||||||
Changed: | ||||||||
< < | Execute /bin/uname -a.Set the jdl attribute WholeNodes to True and False. The submission is expected to succeed for both values and the final job state should be done-ok. | |||||||
> > | See: | |||||||
Changed: | ||||||||
< < | TBC | |||||||
> > | http://wiki.italiangrid.it/twiki/bin/view/CREAM/TroubleshootingGuide#5_1_Saving_the_batch_job_submiss | |||||||
Added: | ||||||||
> > | to understand how to save and check the submission scripts. | |||||||
Changed: | ||||||||
< < | HostNumber-SMPGranularity-WholeNodes combo test | |||||||
> > | Status: Not Implemented | |||||||
Changed: | ||||||||
< < |
| |||||||
> > | CPU Allocation Test 2 | |||||||
Changed: | ||||||||
< < | TBC | |||||||
> > | Submit a job where in the JDL there is: | |||||||
Added: | ||||||||
> > | WholeNodes=true; SMPGranularity=G;Verify that in the submission script there is
BSUB -n S BSUB -R "span[hosts=1]" BSUB -x
PBS -l nodes=1:ppn=S PBS -W x=NACCESSPOLICY:SINGLEJOBwith S equal to the value published as GlueHostArchitectureSMPSize .
Status: Not Implemented
CPU Allocation Test 3Submit a job where in the JDL there is:WholeNodes=true; HostNumber=H;with H>1. Verify that in the submission script there is
BSUB -n S*H BSUB -R "span[ptile=S]" BSUB -x
PBS -l nodes=H:ppn=S PBS -W x=NACCESSPOLICY:SINGLEJOBwith S equal to the value published as GlueHostArchitectureSMPSize .
Status: Not Implemented
CPU Allocation Test 4Submit a job where in the JDL there is:WholeNodes=false; SMPGranularity=G; CPUNumber=C;Verify that in the submission script there is
BSUB -n C BSUB -R "span[ptile=G]"
PBS -l nodes=N:ppn=G { [+1:ppn=R] if r>0 }with: N = C / G R = C % GStatus: Not Implemented CPU Allocation Test 5Submit a job where in the JDL there is:WholeNodes=false; HostNumber=H; CPUNumber=C;with H>1. Verify that in the submission script there is
BSUB -n C BSUB -R "span[ptile={ N if R=0 ; N+1 if R>0 }]"
PBS -l nodes=H-R:ppn=N { [+R:ppn=N+1] if R>0 }with: N = C / H R = C % HStatus: Not Implemented CPU Allocation Test 6Submit a job where in the JDL there is:WholeNodes=false; CPUNumber=C;Verify that in the submission script there is
BSUB -n C
PBS -l nodes=CStatus: Not Implemented | |||||||
Deleted: | ||||||||
< < | Status: Implemented in the Robot based testsuite | |||||||
JobStatus testVerify the proper functionality of the glite-ce-job-status command with different level of verbosity and different options. | ||||||||
Line: 412 to 576 | ||||||||
Check if the resource bdii publishes all the relevant objectclasses for both glue1 and glue2 | ||||||||
Changed: | ||||||||
< < | ldapsearch -h cream-38 -x -p 2170 -b "o=grid" objectclass=GlueSubCluster | |||||||
> > | ||||||||
Added: | ||||||||
> > | ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=grid" objectclass=GlueCE | |||||||
Changed: | ||||||||
< < | TBD | |||||||
> > |
ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=grid" objectclass=GlueVOView | |||||||
Added: | ||||||||
> > |
| |||||||
Added: | ||||||||
> > | ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=grid" objectclass=GlueCluster
ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=grid" objectclass=GlueSubCluster
ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ComputingService
ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.CREAM))"
ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Manager
ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2Share
ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" objectclass=GLUE2ExecutionEnvironment
ldapsearch -h <CREAM CE hostname> -x -p 2170 -b "o=glue" "(&(objectclass=GLUE2ComputingEndPoint)(GLUE2EndpointInterfaceName=org.glite.ce.ApplicationPublisher))"Status: Not Implemented | |||||||
Banning test | ||||||||
Line: 436 to 659 | ||||||||
Admin manage job test | ||||||||
Changed: | ||||||||
< < | TBD | |||||||
> > | Check that a user who is not admin can't check the status of jobs submitted by another user. Check that a user who is admin can check the status of jobs submitted by another user. Status: Implemented in the Robot based testsuite | |||||||
Service-info test |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 48 to 48 | ||||||||
Basic functionality tests | ||||||||
Added: | ||||||||
> > | Simple Submission TestSubmit a job which simply does "/bin/uname -a". Check the final job status which should be DONE-OK. Status: Implemented in the Robot based testsuite | |||||||
InputSandbox TestExecute a bash shell script. | ||||||||
Line: 125 to 134 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | OutputData testTry OutputData JDL attributes considering all the possible combinations. To do that, you can consider a JDL such as this one:[ executable="/bin/sleep"; arguments="25"; Stdoutput = "env.out" ; StdError = "env.err" ; InputSandbox = { "/etc/passwd", "ssh1.sh", "gsiftp://cream-18.pd.infn.it:2811/etc/hostname.txt", "file:///etc/fstab" }; outputsandbox={"out.out", "passwd", "ssh1.sh", "hostname.txt", "fstab"}; OutputSandboxBaseDestURI="gsiftp://localhost"; OutputData={ [ OutputFile="passwd"; LogicalFileName = "lfn:/sgaravat/passwd"; ], [ OutputFile="hostname.txt"; ], [ OutputFile="ssh1.sh"; StorageElement="prod-se-01.pd.infn.it"; ], [ OutputFile="fstab"; LogicalFileName="lfn:/sgaravat/fstab"; StorageElement="prod-se-01.pd.infn.it"; ] }; ]Once the job is in DONE-OK , retrieve the OSB files using the glite-ce-job-output command.
Check the result of the data upload operations in the file DSUpload_
Not Implemented | |||||||
Sandbox staging Test | ||||||||
Line: 198 to 252 | ||||||||
TBC | ||||||||
Added: | ||||||||
> > | SMPGranularity TestExecute /bin/uname -a.Set the jdl attribute SMPGranularity to a certain number. The submission is expected to fail for a value of 0 (this is treated as the corect behaviour).On the other hand,it is expected to succeed and the final job state should be done-ok,if it has any other >=1 value. NOTE: The glite-ce-job-submit will succeed for an unsupported value (e.g. not enough cpus available on site) but will fail eventually and the final state of the job will be aborted (with a message such as: [BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Job exceeds queue resource limits MSG=cannot locate feasible nodes-) N/A (jobId = CREAM348964588)] TBCWholeNode TestExecute /bin/uname -a.Set the jdl attribute WholeNodes to True and False. The submission is expected to succeed for both values and the final job state should be done-ok. TBC | |||||||
HostNumber-SMPGranularity-WholeNodes combo test | ||||||||
Line: 209 to 277 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | JobStatus testVerify the proper functionality of the glite-ce-job-status command with different level of verbosity and different options. Verify that with-L 0 it is reported the "Status".
Verify that with -L 1 it is reported the "Status", the "Job status changes" and the "Issued commands".
Verify that with -L 1 it is reported the "Status", the "Job status changes", the "Issued commands", the "Worker Node", the "Deleg Proxy ID", the "DelegProxyInfo", "Local User", "JDL".
Verify the status of 2 jobs, with ids specified in the command line and with ids read from a file (option -i ).
Verify the proper functionality of the --from and -to option. Specify a time range where a single job was submitted, and verify that only the status of this job is returned.
Status: Not Implemented
| |||||||
List testPerform a glite-ce-job-list. | ||||||||
Line: 237 to 323 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > |
Suspend/Resume TestSubmit a job. Wait until it's state is REALLY-RUNNING and then suspend it. Case LSF batch system: It's state should be HELD. Then resume the same job.It's status should be REALLY-RUNNING.The final status should be DONE-OK. Case Torque batch system: It's state should still be REALLY-RUNNING.Resume the job and expect an error.It's status should be REALLY-RUNNING.The final status should be DONE-OK. Status: Implemented in the Robot based testsuite | |||||||
Enable/disable job submission testhis test case tests the proper functionality of the glite-ce-allowed-submission and glite-ce-enable/disable-submission commands, for admin and non-admin users. The test executes the following steps: | ||||||||
Line: 262 to 361 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | Automatic job purger testModify theJOB_PURGE_POLICY attribute in the configuration file /etc/glite-ce-cream/cream-config.xml setting 0 days for CANCELLED .Then restart tomcat.
Submit a long job and then cancel it. Verify that the job status is cancelled.
After 24 hours recheck the status of the job with glite-ce-job-status . The job should not be found. Verify in the CREAM CE in the CREAM sandbox dir that a directory for this job doesn't exist anymore.
Status: Not Implemented
Proxy renewal testVerify the functionality of theglite-ce-proxy-renew command.
Submit a job lasting 1 hour using a proxy valid 30 minutes.
After 15 minutes renew the proxy with the glite-ce-proxy-renew command.
Verify the final job status which should eventually be DONE-OK
Status: Not Implemented
Automatic proxy purger testDelegate a proxy valid 1 hour Submit a job using that delegatioid. This should work. Try again the submission using the same delegationid after 24 hours. This should not work (the error message should say that the delegation was not found) Status: Not ImplementedAuthz testTry functionality of CREAM with both Argus based authorizations and gJAF based authorizations. To do that simply perform the "Simple Submission Test", "Delegation test", "List test" and "Cancel test" first using a CREAM configured using gJAF, and then using a CREAM configured using ARGUS.Resource BDII testCheck if the resource bdii publishes all the relevant objectclasses for both glue1 and glue2 ldapsearch -h cream-38 -x -p 2170 -b "o=grid" objectclass=GlueSubCluster TBD | |||||||
Banning test | ||||||||
Line: 284 to 441 | ||||||||
Service-info testVerify the output of glite-ce-service-info command for both verbosity levels. | ||||||||
Changed: | ||||||||
< < | TBC | |||||||
> > | TBD | |||||||
Limiter test | ||||||||
Line: 312 to 469 | ||||||||
Performance and scalability tests | ||||||||
Added: | ||||||||
> > | Submission and cancellation with pollingSubmit 1000 simple jobs (without sandbox transfers) in bunch of 50 jobs and then cancel them. Check the status of these jobs using the queryevent operation. All jobs should eventually have CANCELLED as final state. Status: Implemented in the old testsuitecream-test-monitored-cancel -r 30 -n 1000 -m 50 -C 50 -l log4py.conf -j simple.jdl -R cream-35.pd.infn.it:8443/cream-lsf-creamtest2 Submission with polling and sandbox transferSubmit 1000 jobs (with sandbox transfers) in bunch of 50 jobs. Check the status of these jobs using the queryevent operation. All jobs should eventually have DONE-OK as final state. Status: Implemented in the old testsuitecream-test-monitored-submit -r 30 -n 1000 -m 50 -C 50 -l log4py.conf -j testsandbox.jdl -R cream-35.pd.infn.it:8443/cream-lsf-creamtest2 Simple submission with polling, lease updated and proxy renewalSubmit 100 jobs lasting 6000 seconds in bunch of 10 jobs, with an initial lease of 1200 seconds and with an initial proxy valid 20 minutes. Renew the lease and the proxy. Check the status of these jobs using the queryevent operation. All jobs should eventually have DONE-OK as final state. Status: Implemented in the old testsuitecream-test-monitored-lease-updated -r 60 -n 100 -m 10 -C 10 -l log4py.conf -W 1200 --vo dteam --valid 00:20 -R cream-35.pd.infn.it:8443/cream-lsf-creamtest2 | |||||||
Standard compliance and conformance testsGlue 1 compliance | ||||||||
Line: 332 to 537 | ||||||||
Inter-component tests | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | TBD | |||||||
Added: | ||||||||
> > | Nagios probe | |||||||
Added: | ||||||||
> > | For testing nagios probes for worker nodes see here, tests description for nagios probes for direct cream job submission is here | |||||||
Added: | ||||||||
> > | Robot based Testsuite | |||||||
Changed: | ||||||||
< < | Introduction | |||||||
> > | Information about the Robot Based Testsuite is available at: | |||||||
Changed: | ||||||||
< < | The CREAM testsuite is a set of python scripts that interacts with the CREAM command line tools in order to perform several functional tests.
Installation and setup | |||||||
> > | https://twiki.cern.ch/twiki/bin/view/EMI/CREAMRobotFuncTests
Old TestsuiteThe old CREAM testsuite is a set of python scripts that interacts with the CREAM command line tools in order to perform several functional tests.Installation and setupThe easiest way to deploy the old testsuite is to have a UI node already available. | |||||||
Deleted: | ||||||||
< < | The easiest way to deploy the testsuite is to have a UI node already available, for further details refer to the Generic Installation and Configuration Guide. | |||||||
Changed: | ||||||||
< < | The testsuite can be installed using yum creating a file called testsuites.repo in the yum.repos.d directory with the following definition: | |||||||
> > | The old testsuite can then be installed using yum creating a file called testsuites.repo in the yum.repos.d directory with the following definition: | |||||||
[ETICS-name-CREAM-service-testsuite] name=ETICS Repository of CREAM-service-testsuite baseurl=http://etics-repository.cern.ch:8080/repository/pm/registered/repomd/name/CREAM-service-testsuite_1_0_7 | ||||||||
Line: 363 to 576 | ||||||||
After the installation it is suggested to check if the environment variable GLITE_LOCATION points to the correct gLite installation directory, i.e. the one containing the bin folder with the CREAM clients. | ||||||||
Changed: | ||||||||
< < | Testsuite and ETICS | |||||||
> > | Old Testsuite and ETICS | |||||||
Changed: | ||||||||
< < | The testsuite can be downloaded and build directly from the ETICS framework. For any details concerning the ETICS client installation refer to the User Guide or to the twiki site. | |||||||
> > | The old testsuite can be downloaded and build directly from the ETICS framework. For any details concerning the ETICS client installation refer to the User Guide or to the twiki site. | |||||||
The following list of commands is required in order to retrieve and build the latest stable release:
etics-workspace-setup | ||||||||
Line: 374 to 586 | ||||||||
etics-checkout --config glite-testsuites-cream_R_1_0_7_0 --project-config glite_branch_3_1_0 org.glite.testsuites.cream etics-build org.glite.testsuites.cream | ||||||||
Changed: | ||||||||
< < | Releases and Changelog | |||||||
> > | Releases and Changelog | |||||||
| ||||||||
Line: 388 to 600 | ||||||||
| ||||||||
Changed: | ||||||||
< < | Work plan | |||||||
> > | Old Testsuite description | |||||||
The set of test can be divided into two main categories, according to the type of status detection mechanism for a job:
| ||||||||
Line: 405 to 614 | ||||||||
Changed: | ||||||||
< < | Proxy management | |||||||
> > |
Proxy management | |||||||
Each test can be run using either an external user voms-proxy or with an internal management of the voms-proxy. | ||||||||
Line: 414 to 624 | ||||||||
The external voms-proxy path is defined with the environment variable X509_USER_PROXY, the main default is /tmp/x509_uuid. With the internal management of the voms-proxy the testsuite keeps track of the renewal of that credential, the user has just to provide a valid personal certificate and private key. The environment variables required for enabling this mode are: X509_USER_CERT and X509_USER_KEY; when this mode is selected each test requires the definition of the VO to be used (option --vo) and the voms-proxy-init client must be properly configured. | ||||||||
Changed: | ||||||||
< < | Delegation management | |||||||
> > |
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. | ||||||||
Changed: | ||||||||
< < | Isolation and interference tests | |||||||
> > |
Isolation and interference tests | |||||||
One of the basic requirements for a test is to be isolated; each test handles only its own jobs and resources in general (delegated proxies, lease tokens, etc.) with no interferences from other tests.
Multiple tests can be executed in parallel in order to detect interferences on the service side; for example the cream-test-monitored-lease-expired test can be run together with cream-test-monitored-submit for discovering a wrong lease management for the jobs submitted by the latter. | ||||||||
Deleted: | ||||||||
< < | Nagios probeFor testing nagios probes for worker nodes see here, tests description for nagios probes for direct cream job submission is here | |||||||
Changed: | ||||||||
< < | Hints for test tuning | |||||||
> > | Hints for test tuning | |||||||
| ||||||||
Changed: | ||||||||
< < | Proposed test plan | |||||||
> > |
Proposed tests | |||||||
The set of tests described in this section is used for the pre-certification of the latest version of the CREAM CE and can be considered a template for external testers. In the following the CREAM CE under test is cream-12.pd.infn.it (port 8443) with Torque as batch system and cream_A as assigned queue, the hostname and port must be replaced with the correct values according to the arrangement of the testbed; the VO dteam is used. | ||||||||
Line: 530 to 736 | ||||||||
| ||||||||
Deleted: | ||||||||
< < |
Missing tests
ContactsFor any trouble concerning the test suite or the test plan please contacts: cream-support@lists.infn.it |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 92 to 92 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | OutputSandbox localhost and get-output Test
OutputSandboxDestURI Test
OutputSandboxBaseDestURI Test
Sandbox staging TestThis test case tests the two different Sandbox staging operations available for the /etc/glite-ce-cream/cream-config.xml, LRMS and GSIFTP.
| |||||||
Delegation tests | ||||||||
Line: 127 to 171 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | Prologue testExecute two bash shell scripts, one for the job and the other as a prologue. The prologue script creates a file with a certain string, which is collected by the job as an output file Submit the jdl. Check the final state which should be DONE-OK. Check the output file which should have the designated string. Status: Implemented in the Robot based testsuite | |||||||
CPUNumber testExecute /bin/uname -a.Set the jdl attribute CPUNumber to a certain number. The submission is expected to fail for a value of 0 (this is treated as the corect behaviour).On the other hand,it is expected to succeed and the final job state should be done-ok,if it has any other >=1 value. NOTE: The glite-ce-job-submit will succeed for an unsupported value (e.g. not enough cpus available on site) but will fail eventually and the final state of the job will be aborted (with a message such as: BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Job exceeds queue resource limits MSG=cannot locate feasible nodes-) N/A (jobId = CREAM918215196) | ||||||||
Line: 150 to 209 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | List testPerform a glite-ce-job-list. Perform a job submission Perform again a glite-ce-job-list The returned jobid shouldn't exist in the in the job list command output before the submission and should exist afterwards. Status: Implemented in the Robot based testsuite | |||||||
Cancel test
| ||||||||
Line: 159 to 230 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | Manual cancel test
| |||||||
Enable/disable job submission test | ||||||||
Line: 176 to 253 | ||||||||
| ||||||||
Added: | ||||||||
> > | Status: Implemented in the Robot based testsuite
Purge test
| |||||||
Banning test |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work plan | ||||||||
Line: 48 to 48 | ||||||||
Basic functionality tests | ||||||||
Added: | ||||||||
> > | InputSandbox TestExecute a bash shell script. The script is stored on the UI. The jdl attribute InputSandbox is used. Firstly submit the jdl and then wait for final job state which should be DONE-OK. Status: Implemented in the Robot based testsuiteRemote InputSandbox TestExecute a bash shell script. The script is stored in a gridftp server. The jdl attribute InputSandbox is used. First upload the executable script. Then submit the jdl and check the the final state which should be DONE-OK. Status: Implemented in the Robot based testsuiteInputSandboxBaseURI TestSubmit a job where the executable is a bash shell script. The script is stored in a gridftp server. The jdl attribute InputSandboxBaseURI is used. First upload the executable script in the considered gridftp server. Then submit the jdl. Check the final state which should be DONE-OK. Status: Implemented in the Robot based testsuite | |||||||
Delegation tests
| ||||||||
Line: 57 to 102 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | Environment testConsider a job where the jdl sets an environmental variable and the executable is a script which prints the value of that variable. Submit the jdl. Check the the final state which should be DONE-OK. Check the output file which should have the designated variable. Status: Implemented in the Robot based testsuiteEpilogue testExecute two bash shell scripts, one for the job and the other as an epilogue. The epilogue script creates a file with a certain string, which is collected by the job as an output file Submit the jdl. Check the final state which should be DONE-OK. Check the output file which should have the designated string. Status: Implemented in the Robot based testsuite | |||||||
CPUNumber testExecute /bin/uname -a.Set the jdl attribute CPUNumber to a certain number. The submission is expected to fail for a value of 0 (this is treated as the corect behaviour).On the other hand,it is expected to succeed and the final job state should be done-ok,if it has any other >=1 value. NOTE: The glite-ce-job-submit will succeed for an unsupported value (e.g. not enough cpus available on site) but will fail eventually and the final state of the job will be aborted (with a message such as: BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Job exceeds queue resource limits MSG=cannot locate feasible nodes-) N/A (jobId = CREAM918215196) TBC | ||||||||
Added: | ||||||||
> > | HostNumber testExecute /bin/uname -a.Set the jdl attribute HostNumber to a certain number. The submission is expected to fail for a value of 0 (this is treated as the corect behaviour).On the other hand,it is expected to succeed and the final job state should be done-ok,if it has any other >=1 value. NOTE: The glite-ce-job-submit will succeed for an unsupported value (e.g. not enough cpus available on site) but will fail eventually and the final state of the job will be aborted (with a message such as: [BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Job exceeds queue resource limits MSG=cannot locate feasible nodes-) N/A (jobId = CREAM150008664)] TBC | |||||||
HostNumber-SMPGranularity-WholeNodes combo test
| ||||||||
Line: 114 to 191 | ||||||||
Status: Implemented in the Robot based testsuite | ||||||||
Added: | ||||||||
> > | Admin manage job testTBD | |||||||
Service-info testVerify the output of glite-ce-service-info command for both verbosity levels. TBC | ||||||||
Added: | ||||||||
> > | Limiter testSet a limiter threshold to a value which will trigger it. Wait for the limiter script to be run automatically. Submit and job and expect failure. Reset the limiter to the original values. Wait for the limiter script to be run automatically. Submit a command and expect success Status: Implemented in the Robot based testsuite | |||||||
Regression tests |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Changed: | ||||||||
< < | CREAM Test work plan | |||||||
> > | CREAM Test work plan
Unit testsTBDDeployment testsInstallationThe following should be tested:
ConfigurationThe configuration via yaim should be tested. The following scenarios should be tested (they are documented in CREAM System Administrator Guide):
System testsBasic functionality testsDelegation tests
CPUNumber testExecute /bin/uname -a.Set the jdl attribute CPUNumber to a certain number. The submission is expected to fail for a value of 0 (this is treated as the corect behaviour).On the other hand,it is expected to succeed and the final job state should be done-ok,if it has any other >=1 value. NOTE: The glite-ce-job-submit will succeed for an unsupported value (e.g. not enough cpus available on site) but will fail eventually and the final state of the job will be aborted (with a message such as: BLAH error: submission command failed (exit code = 1) (stdout:) (stderr:qsub: Job exceeds queue resource limits MSG=cannot locate feasible nodes-) N/A (jobId = CREAM918215196) TBCHostNumber-SMPGranularity-WholeNodes combo test
Cancel test
Enable/disable job submission testhis test case tests the proper functionality of the glite-ce-allowed-submission and glite-ce-enable/disable-submission commands, for admin and non-admin users. The test executes the following steps:
Banning testFor a CREAM-CE configured using gJAF:
Service-info testVerify the output of glite-ce-service-info command for both verbosity levels. TBCRegression testsSee: http://wiki.italiangrid.it/twiki/bin/view/CREAM/RegressionTestWorkPlanPerformance and scalability testsStandard compliance and conformance testsGlue 1 complianceGlue 1 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. Status: Implemented in the Robot based testsuiteGlue 2 complianceGlue 2 compliance of the information published by the CREAM-CE resource bdii should be tested. This should be done using [[https://tomtools.cern.ch/confluence/display/IS/GLUEValidator]GlueValidator]]. Status: Implemented in the Robot based testsuiteInter-component tests | |||||||
Introduction |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work planIntroduction | ||||||||
Line: 87 to 88 | ||||||||
One of the basic requirements for a test is to be isolated; each test handles only its own jobs and resources in general (delegated proxies, lease tokens, etc.) with no interferences from other tests.
Multiple tests can be executed in parallel in order to detect interferences on the service side; for example the cream-test-monitored-lease-expired test can be run together with cream-test-monitored-submit for discovering a wrong lease management for the jobs submitted by the latter. | ||||||||
Added: | ||||||||
> > |
Nagios probeFor testing nagios probes for worker nodes see here, tests description for nagios probes for direct cream job submission is here | |||||||
Hints for test tuning
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work planIntroduction | ||||||||
Line: 6 to 6 | ||||||||
The CREAM testsuite is a set of python scripts that interacts with the CREAM command line tools in order to perform several functional tests.
| ||||||||
Changed: | ||||||||
< < | Operations/Installation and setup | |||||||
> > | Installation and setup | |||||||
Changed: | ||||||||
< < | The easiest way to deploy the testsuite is to have a UI node already available, for further details refer to the Generic Operations/Installation and Configuration Guide. | |||||||
> > | The easiest way to deploy the testsuite is to have a UI node already available, for further details refer to the Generic Installation and Configuration Guide. | |||||||
The testsuite can be installed using yum creating a file called testsuites.repo in the yum.repos.d directory with the following definition:
[ETICS-name-CREAM-service-testsuite] |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
CREAM Test work planIntroduction | ||||||||
Line: 6 to 6 | ||||||||
The CREAM testsuite is a set of python scripts that interacts with the CREAM command line tools in order to perform several functional tests.
| ||||||||
Changed: | ||||||||
< < | Installation and setup | |||||||
> > | Operations/Installation and setup | |||||||
Changed: | ||||||||
< < | The easiest way to deploy the testsuite is to have a UI node already available, for further details refer to the Generic Installation and Configuration Guide. | |||||||
> > | The easiest way to deploy the testsuite is to have a UI node already available, for further details refer to the Generic Operations/Installation and Configuration Guide. | |||||||
The testsuite can be installed using yum creating a file called testsuites.repo in the yum.repos.d directory with the following definition:
[ETICS-name-CREAM-service-testsuite] |
Line: 1 to 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
CREAM Test work planIntroductionThe CREAM testsuite is a set of python scripts that interacts with the CREAM command line tools in order to perform several functional tests.Installation and setupThe easiest way to deploy the testsuite is to have a UI node already available, for further details refer to the Generic Installation and Configuration Guide. The testsuite can be installed using yum creating a file called testsuites.repo in the yum.repos.d directory with the following definition:[ETICS-name-CREAM-service-testsuite] name=ETICS Repository of CREAM-service-testsuite baseurl=http://etics-repository.cern.ch:8080/repository/pm/registered/repomd/name/CREAM-service-testsuite_1_0_7 protect=0 enabled=1 gpgcheck=0and then running yum update yum install glite-testsuites-creamAfter the installation it is suggested to check if the environment variable GLITE_LOCATION points to the correct gLite installation directory, i.e. the one containing the bin folder with the CREAM clients. Testsuite and ETICSThe testsuite can be downloaded and build directly from the ETICS framework. For any details concerning the ETICS client installation refer to the User Guide or to the twiki site. The following list of commands is required in order to retrieve and build the latest stable release:etics-workspace-setup etics-get-project org.glite etics-checkout --config glite-testsuites-cream_R_1_0_7_0 --project-config glite_branch_3_1_0 org.glite.testsuites.cream etics-build org.glite.testsuites.cream Releases and Changelog
Work plan |
Simple submission with polling |
---|
cream-test-monitored-submit -r 30 -n 1000 -m 50 -C 50 -l log4py.conf -j simple.jdl -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy |
Simple submission with notifications |
cream-test-notified-submit -r 30 -n 1000 -m 50 -C 50 -p 9000 -l log4py.conf -j simple.jdl -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy |
Submission and cancellation with polling |
cream-test-monitored-cancel -r 30 -n 1000 -m 50 -C 50 -l log4py.conf -j simple.jdl -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy. |
Submission and cancellation with notifications |
cream-test-notified-cancel -r 30 -n 1000 -m 50 -C 50 -p 9000 -l log4py.conf -j simple.jdl -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy. |
Submission with polling and sandbox transfer |
cream-test-monitored-submit -r 30 -n 1000 -m 50 -C 50 -l log4py.conf -j testsandbox.jdl -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy. The output sandbox on the CE must be checked and removed manually. |
Submission with notifications and sandbox transfer |
cream-test-notified-submit -r 30 -n 1000 -m 50 -C 50 -p 9000 -l log4py.conf -j testsandbox.jdl -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy. The output sandbox on the CE must be checked and removed manually. |
Simple submission with polling and proxy renewal |
cream-test-monitored-submit -r 60 -n 50 -m 10 -C 10 -l log4py.conf -j long.jdl --vo dteam --valid 00:20 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The variables X509_USER_CERT and X509_USER_KEY must point to the location of the user certificate and private key, passphrase is required |
Simple submission with notifications and proxy renewal |
cream-test-notified-submit -r 60 -n 50 -m 10 -C 10 -p 9000 -l log4py.conf -j long.jdl --vo dteam --valid 00:20 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The variables X509_USER_CERT and X509_USER_KEY must point to the location of the user certificate and private key, passphrase is required. |
Simple submission with polling and proxy expired |
cream-test-monitored-proxy-expired -r 60 -n 50 -m 10 -C 10 -l log4py.conf --vo dteam --valid 00:20 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The variables X509_USER_CERT and X509_USER_KEY must point to the location of the user certificate and private key, passphrase is required. |
Simple submission with polling and lease expired |
cream-test-monitored-lease-expired -r 60 -n 50 -m 10 -C 10 -l log4py.conf -W 1200 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy. One lease token is defined for all jobs. |
Simple submission with notifications and lease expired |
cream-test-notified-lease-expired -r 60 -n 50 -m 10 -C 10 -l log4py.conf -W 1200 -p 9000 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy.One lease token is defined for all jobs |
Simple submission with polling, lease expired and proxy renewal |
cream-test-monitored-lease-expired -r 60 -n 50 -m 10 -C 10 -l log4py.conf -W 1800 --vo dteam --valid 00:20 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The variables X509_USER_CERT and X509_USER_KEY must point to the location of the user certificate and private key, passphrase is required.One lease token is defined for all jobs. |
Simple submission with notifications, lease expired and proxy renewal |
cream-test-notified-lease-expired -r 60 -n 50 -m 10 -C 10 -l log4py.conf -W 1800 -p 9000 --vo dteam --valid 00:20 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The variables X509_USER_CERT and X509_USER_KEY must point to the location of the user certificate and private key, passphrase is required.One lease token is defined for all jobs. |
Simple submission with polling and lease updated |
cream-test-monitored-lease-updated -r 60 -n 50 -m 10 -C 10 -l log4py.conf -W 1200 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy.One lease token is defined for all jobs. |
Simple submission with notifications and lease updated |
cream-test-notified-lease-updated -r 60 -n 50 -m 10 -C 10 -l log4py.conf -W 1200 -p 9000 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The renewal process is disabled, the variable X509_USER_PROXY must point to a 12-hours long proxy.One lease token is defined for all jobs. |
Simple submission with polling, lease updated and proxy renewal |
cream-test-monitored-lease-updated -r 60 -n 50 -m 10 -C 10 -l log4py.conf -W 1800 --vo dteam --valid 00:20 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The variables X509_USER_CERT and X509_USER_KEY must point to the location of the user certificate and private key, passphrase is required.One lease token is defined for all jobs. |
Simple submission with notifications, lease updated and proxy renewal |
cream-test-notified-lease-updated -r 60 -n 50 -m 10 -C 10 -l log4py.conf -W 1800 -p 9000 --vo dteam --valid 00:20 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The variables X509_USER_CERT and X509_USER_KEY must point to the location of the user certificate and private key, passphrase is required.One lease token is defined for all jobs. |
Proxy renewal for job in IDLE |
cream-test-monitored-submit -r 60 -n $TOTAL -m $PART -C $PART -l log4py.conf -j onehoursleep.jdl --vo dteam --valid 00:45 -R cream-12.pd.infn.it:8443/cream-pbs-cream_A |
The variables X509_USER_CERT and X509_USER_KEY must point to the location of the user certificate and private key, passphrase is required. The variable $PART is an integer greater than the number of jobs which can be run concurrently in the batch system, the variable $TOTAL is a multiple of $PART. |
Logging and Bookkeeping integration: tests of the notifications sent by the job wrapper to the local logger (if installed) and in the next future for direct CREAM-LB integration.