Cream CE Job Submittion
1. Authentication
1.1 Checking your certificate
[user01@ui-1 ~]$ grid-cert-info
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 34 (0x22)
Signature Algorithm: sha1WithRSAEncryption
Issuer: O=GRIDSEED, DC=seed, DC=grid, CN=GRIDSEED CA 1
Validity
Not Before: Jul 28 18:53:54 2009 GMT
Not After : Jul 28 18:53:54 2010 GMT
Subject: O=GRIDSEED, DC=seed, DC=grid, OU=Personal Certificate, CN=pipoo4 lillo323423
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public Key: (2048 bit)
Modulus (2048 bit):
00:c4:e6:a6:30:dd:b1:d4:34:a2:7e:ba:df:a3:c5:
6e:84:ad:37:f3:e0:96:4f:49:b6:0f:06:8f:ae:88:
ea:4f:70:07:36:8b:e8:7e:c2:99:a0:e5:ef:88:63:
89:75:3f:09:e4:68:6d:01:13:5f:0b:4f:c7:fe:6b:
79:70:33:9b:88:bd:1f:3f:0a:0a:c1:8d:76:36:3c:
c8:3d:5d:8b:60:5e:8b:c8:f0:ca:34:74:cc:ce:ec:
7f:23:f4:0a:be:39:ca:53:9c:25:a7:7c:11:12:2e:
26:a5:b7:61:57:42:e5:dc:73:95:5b:52:ae:fe:d6:
69:9d:7c:42:fc:77:b2:8a:ac:8e:91:f9:5b:64:86:
fd:93:60:d6:8e:b8:fc:c5:a6:40:73:61:3a:d3:6d:
9e:c6:36:01:f1:85:b9:21:86:f2:77:36:92:10:d2:
da:78:0e:e4:8d:4d:1e:e1:3e:a9:77:e4:2f:ae:e6:
4c:97:4f:df:34:42:17:79:4f:33:2d:b0:9a:b7:58:
1d:63:67:57:c1:dc:95:3f:b8:ae:8a:7d:ea:2d:8b:
b6:e6:62:78:4c:46:7c:8c:c1:00:eb:5c:75:43:ad:
15:a4:3c:13:2c:82:ec:4e:76:83:ad:6a:cf:52:0b:
1f:2e:d1:2e:62:40:22:6e:17:c8:d1:f6:84:7e:b1:
b0:17
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Basic Constraints: critical
CA:FALSE
X509v3 Key Usage: critical
Digital Signature, Key Encipherment, Data Encipherment
X509v3 Extended Key Usage:
TLS Web Client Authentication, E-mail Protection
X509v3 CRL Distribution Points:
URI:http://voms-2.grid.seed/ca/ca.crl
X509v3 Certificate Policies:
Policy: 1.3.6.1.4.1.10403.10.1.7
Policy: 1.2.840.113612.5.2.2.1
X509v3 Subject Key Identifier:
37:74:FC:EC:9A:FB:71:29:0B:88:34:B0:BC:89:E6:5A:C3:51:D3:73
X509v3 Authority Key Identifier:
keyid:B8:06:98:6E:26:73:57:29:7D:A9:46:0F:6E:02:9A:03:2E:60:5D:16
DirName:/O=GRIDSEED/DC=seed/DC=grid/CN=GRIDSEED CA 1
serial:00
X509v3 Subject Alternative Name:
email:pippo@nowhere
Signature Algorithm: sha1WithRSAEncryption
3f:15:31:4b:74:8a:c3:ba:19:90:0c:3e:a4:3c:ab:ab:57:25:
be:21:a0:d8:5b:59:aa:69:32:1b:31:58:36:21:6d:c0:bf:02:
e0:ed:6e:6d:18:a3:b8:bb:a6:ce:e4:5f:e1:b7:7c:12:b4:c0:
b2:49:96:99:8f:96:47:d8:08:a4:c7:b9:78:43:f3:3d:f6:4a:
53:c3:38:6f:e7:0e:49:9f:d7:c9:9c:1c:0f:7a:83:79:3e:b0:
71:24:20:ef:7a:b9:e6:8f:72:fe:4e:7f:ad:7a:90:6a:56:2a:
d5:2e:49:3c:0a:a1:35:97:84:b1:66:b9:d4:c6:26:eb:81:c9:
8a:42:e1:68:6a:88:26:4b:60:46:b7:46:f1:ba:7f:8b:89:ca:
64:95:43:78:0c:04:57:8f:36:57:75:d0:57:1b:fa:b5:7d:be:
2e:55:2d:c4:88:70:bd:5c:99:8e:04:5f:bb:8b:5d:6d:e8:7d:
d4:00:3c:50:b2:04:18:46:08:fd:83:0c:73:d5:ca:e9:31:5d:
ad:91:63:cc:7a:5f:b1:20:02:ca:9a:95:30:22:bd:5f:20:fb:
38:b0:9b:a5:7b:86:53:a9:46:58:12:da:1e:43:e7:53:71:40:
03:49:b3:2d:e1:cc:fd:a0:27:fd:a7:ee:9c:c1:f6:60:9f:cf:
d7:9d:43:3b
There are three interesting things to check here:
- dates of creation and of expiration
- the name and subject of the Certification Authority which issued the certificate,
- the Common Name (CN) of the certificate owner, and the certificate subject, which uniquely identifies the certificate owner.
1.2 Creation of a proxy with voms extensions
We are now ready to create a proxy from our certificate: by means of it we can now start interacting with the grid. The proxy will use Voms extensions for only Virtual Organization enabled on Gridseed: gridseed.
Please remember that the pass phrase requested is again gridseed
[user01@ui-1 ~]$ voms-proxy-init -voms gridseed Enter GRID pass phrase: Your identity: /O=GRIDSEED/DC=seed/DC=grid/OU=Personal Certificate/CN=pipoo4 lillo323423 Creating temporary proxy ....................................................... Done Contacting voms-2.grid.seed:15000 [/O=GRIDSEED/DC=seed/DC=grid/OU=Host Certificate/CN=voms-2.grid.seed] "gridseed" Done Creating proxy .......................................................... Done Your proxy is valid until Fri Jul 31 04:02:40 2009
1.3 Check your voms proxy
Once that your proxy has been created, you can gather info on it through the voms-proxy-info command. Specify it with -all option: this will show also the VO related infos added by the VOMS server, such as belonging groups or roles. You may note also two different lifetimes : first is related to the proxy itself, the second one is referred to the AC infos added by the VOMS server. They have to be valid both in order to be fully enabled to perform operations.
[user01@ui-1 ~]$ voms-proxy-info --all subject : /O=GRIDSEED/DC=seed/DC=grid/OU=Personal Certificate/CN=pipoo4 lillo323423/CN=proxy issuer : /O=GRIDSEED/DC=seed/DC=grid/OU=Personal Certificate/CN=pipoo4 lillo323423 identity : /O=GRIDSEED/DC=seed/DC=grid/OU=Personal Certificate/CN=pipoo4 lillo323423 type : proxy strength : 1024 bits path : /tmp/x509up_u504 timeleft : 11:59:20 === VO gridseed extension information === VO : gridseed subject : /O=GRIDSEED/DC=seed/DC=grid/OU=Personal Certificate/CN=pipoo4 lillo323423 issuer : /O=GRIDSEED/DC=seed/DC=grid/OU=Host Certificate/CN=voms-2.grid.seed attribute : /gridseed/Role=NULL/Capability=NULL timeleft : 11:59:19 uri : voms-2.grid.seed:15000
2. Submit your first job
2.1 Short introduction
Please consider that job submission via WMS to CREAM currently is not supported. However it is possible to submit jobs directly to CREAM via the CREAM-CLI, Please check for the updates
2.2 My first jdl file
The following simple JDL file is preloaded in the /opt/examples/GettingStarted directory of the ui-1. Create it using your favourite text editor (pico, nano, emacs, vi) and name it hello.jdl.
[
Type = "Job";
JobType = "Normal";
Executable = "/bin/hostname";
StdOutput = "message.txt";
StdError = "error.txt";
InputSandbox = { "/bin/hostname" } ;
OutputSandbox = {"message.txt", "error.txt"};
OutputSandboxBaseDestUri = "gsiftp://ce-2.grid.seed/tmp";
]
2.3 Credentials delegation
All the interactions with WMS are actually done through the WMProxy web service that requires a proxy itself. This is actually done by means of credential delegation procedure. There are two options here:
- The user can manually perform this operation using the command below and specifying the delegationId to be associated with the delegated proxy:
[user01@ui-1 ~]$ glite-ce-delegate-proxy -e ce-2.grid.seed mydelid0001 2009-07-30 15:29:41,630 WARN - No configuration file suitable for loading. Using built-in configuration 2009-07-30 15:29:44,095 NOTICE - Proxy with delegation id [mydelid0001] succesfully delegated to endpoint [https://ce-2.grid.seed:8443//ce-cream/services/gridsite-delegation]
2.4 Job Submission
We are now ready to submit our simple job by means of glite-wms-job-submit command. We will use -d flag (for the delegated proxy and -o to save the job identfier on a file to later check the status of our job.
[user01@ui-1 ~]$ glite-ce-job-submit -D mydelid0001 \ -r ce-2.grid.seed:8443/cream-pbs-default creamtest.jdl 2009-07-30 15:36:54,622 WARN - No configuration file suitable for loading. Using built-in configuration https://ce-2.grid.seed:8443/CREAM943310731
2.5 Job Status
In order to know about the job status another command is available: glite-wms-job-status; this command requires as ipnut the Job Identifiers and then queries LB (Logging and Bookkeeping service) on the status of the job. No delegation is needed for this command.
glite-ce-job-status -L 1 https://ce-2.grid.seed:8443/CREAM943310731
2009-07-30 15:37:43,577 WARN - No configuration file suitable for loading. Using built-in configuration
****** JobID=[https://ce-2.grid.seed:8443/CREAM943310731]
Current Status = [DONE-OK]
ExitCode = [0]
Grid JobID = [N/A]
Job status changes:
-------------------
Status = [REGISTERED] - [Thu 30 Jul 2009 15:37:03] (1248961023)
Status = [PENDING] - [Thu 30 Jul 2009 15:37:06] (1248961026)
Status = [IDLE] - [Thu 30 Jul 2009 15:37:06] (1248961026)
Status = [REALLY-RUNNING] - [Thu 30 Jul 2009 15:36:22] (1248960982)
Status = [DONE-OK] - [Thu 30 Jul 2009 15:36:24] (1248960984)
Issued Commands:
-------------------
*** Command Name = [JOB_REGISTER]
Command Category = [JOB_MANAGEMENT]
Command Status = [SUCCESSFULL]
*** Command Name = [JOB_START]
Command Category = [JOB_MANAGEMENT]
Command Status = [SUCCESSFULL]