|
After this tutorial you will be able to submit a job that lasts more than 12 hours.
Creating a proxy every 12 hours is both annoying and problematic for long-running jobs.
Wouldn't it be great if I could put my certificates on some server and let it have the headache with issuing proxies?
That's where MyProxy comes in.
Getting MyProxy
Rather than storing your X.509 credentials (certificate and private key) on each machine you use, you can store them on a MyProxy server and retrieve a proxy credential from the MyProxy repository when needed.
Each VO has its own MyProxy server(s). The environment variable MYPROXY_SERVER usually holds the MyProxy server name
| Gilda tutorial users | Grid users |
|---|---|
| MyProxy server is grid001.ct.infn.it | MyProxy server is depends on your VO. SEE VO uses myproxy.grid.auth.gr |
|
% myproxy-init -s MyProxyServerName -d -n |
From now on you can use the server to issue proxies for
you automatically to ensure that your job continues to run past
the expiration time of the proxy.
How do we do that?
You need to specify this attribute in the JDL file:
| MyProxyServer = “MyProxyServerName"; |
You can query the time left for your MyProxy using
|
% myproxy-info -s MyProxyServerName -d |
You can always remove your MyProxy using
|
% myproxy-destroy -s MyProxyServerName -d |
Lets learn about Data Management now