| [DESY Home] [DESY IT Home] [DESY IT Physics Computing] [Grid Computing at DESY] | [DESY Computing Seminar] | [Imprint] |
| Grid Computing at DESY | |
|---|
| [Home] |
[Mon/Admin  ]
| [Grid@DESY] [Certs & VOs] [VOMS] [User Guide] [Install Guide] | [Talks & Posters] | [Glossary] [Documentation] [Links] |
In order to ensure response in case of problems, use the
Global Grid User Support (GGUS)
and/or your VO support rather than private e-mail contacts or internal mailing lists.
For registration refer to the list of VOs supported at DESY.
Important: Please use the glite 3.2 UI exclusively! Some newer services are not able to handle VOMS proxies which are created on the unsupported glite 3.1 UI (see below).
The default (from February 15th, 2012 on) production gLite 3.2 version (3.2.11-1.sl5) was built exclusively for SL5/64-bit [x86_64] (e.g. pal.desy.de). It will work on the SL5/64-bit workgroup servers of the NAF as well.
> source /afs/desy.de/project/glite/UI/etc/profile.d/grid-env.sh > source /afs/desy.de/project/glite/UI/etc/profile.d/grid-env.csh
The gLite 3.1 UI support by European Middelware Initiative (EMI), which took over
from EGEE, retired!
Consequently, VOMS proxies created on this old UIs do not work with new installations,
e.g. WMS' ("Warning - The WMProxy Server does not support delegation 1").
Standard updates ended 14.10.2010.
Security updates ended 30.04.2011.
See gLite 3.1 Retirement Calendar
and gLite Support Calendar.
The last gLite 3.1 version, which was built for SL4/32-bit [i686] and is unfortunately still needed for SL5/32-bit [i686]. It remains available for the time being and as long as security aspects allow but might not deliver full functionality anymore (see above).
> source /afs/desy.de/project/glite/UI/etc/profile.d/grid-env-3.1.sh > source /afs/desy.de/project/glite/UI/etc/profile.d/grid-env-3.1.csh
Older version are also available as well as the (tcsh versions *.csh):
> . /afs/desy.de/project/glite/UI/etc/profile.d/grid-env-3.2.10-1.sl5.sh > . /afs/desy.de/project/glite/UI/etc/profile.d/grid-env-3.2.8-0.sl5.sh
We collect here a sample of commands which could be used for first
tests.
For a complete description of commands refer to the
gLite 3.2 User Guide.
The DECH Regional Support Team has compiled a Grid primer, which works at SCAI for the VO dech.
The primary entry point for Grid user support is the Global Grid User Support (GGUS). Please send questions or report problems to this URL.
[top]
See Grid Certification and VOs at DESY for details.
[top]
Create a proxy, using your standard Grid certificate in ~/.globus/usercert.pem and ~/.globus/userkey.pem :
voms-proxy-init -verify -debug -vomsvoms-proxy-info -verify -debug -all
If the user belongs to a group within the VO and/or holds a special role, use the following commands with the correct entries:
voms-proxy-init -verify -debug -voms myvo:/myvo voms-proxy-init -verify -debug -voms myvo:/myvo/mygroup voms-proxy-init -verify -debug -voms myvo:/myvo/Role=myrole voms-proxy-init -verify -debug -voms myvo:/myvo/mygroup/Role=myotherrole
It is possible to explicilty give the path of the cert, extend the validity time, or change the the standard location of the proxy given in X509_USER_PROXY:
voms-proxy-init -verify -debug -cert mycert.pem -key mykey.pem voms-proxy-init -verify -debug -valid 170:00 voms-proxy-init -verify -debug -file myproxy.pem
[top]
> lcg-infosites --vo dteam > lcg-infosites --vo dteam all > lcg-infosites --vo dteam ce | se | lfc | wms > lcg-info -vo ilc --list-ce --attrs Memory,MaxWCTime,MaxCPUTime,FreeCPUs,RunningJobs,OS,OSVersion,OSRelease --query CE="grid-ce5.desy.de:2119/jobmanager-lcgpbs-desy > lcg-info --list-se --attrs SE --query SE="dcache-se-desy.desy.de" > lcg-info --vo ilc --sed --list-service --query ServiceType=org.glite.wms
Tests:
> ldapsearch -xLLL -p2170 -h grid-giis.desy.de -b o=grid '(&(GlueSiteUniqueID=*)(GlueSiteOtherInfo=GRID=*))' GlueSiteOtherInfo
[top]
The usual way to run jobs in the Grid is by way of GLITE middleware.
Refer to the list of VOs managed at DESY.
Login to your favorite UI and make sure you have an AFS token:
> ssh _UI_ > tokens > klog
Set the path to the GLITE commands which are at DESY available via AFS (SL5 64_bit):
> source /afs/desy.de/project/glite/UI/etc/profile.d/grid-env.sh or > source /afs/desy.de/project/glite/UI/etc/profile.d/grid-env.csh
Your user certificate should be present:
> ls $HOME/.globus usercert.pem userkey.pem
Example for a job description language file, e.g. env.jdl:
VirtualOrganisation = "the_vo_you_belong_to";
Executable = "env.sh";
Arguments = " ";
StdOutput = "out";
StdError = "err";
InputSandbox = {"env.sh"};
OutputSandbox = {"out","err"};
#Rank = ( other.GlueCEStateWaitingJobs == 0 ? other.GlueCEStateFreeCPUs : -other.GlueCEStateWaitingJobs);
In our example a shell script is used as an executable, e.g. env.sh:
#! /bin/sh ######################################################################### /bin/hostname -f /bin/date /usr/bin/id /bin/pwd /bin/ls -al /bin/df . /usr/bin/env $GLOBUS_LOCATION/bin/voms-proxy-info -all #########################################################################
Since id of 2007 the new GLITE workload management system (WMS) is in place and should be used. It requires VOMS-proxies:
> glite-wms-job-list-match -a> glite-wms-job-submit -a > glite-wms-job-submit -a -r > glite-wms-job-status > glite-wms-job-logging-info > glite-wms-job-output
The job output will be stored in a directory in /tmp. In our example the output directory should contain files for stdin and stdout:
> ls -ltr /tmp err out
To keep track of jobIds, one can specify a file which is used as a repository of jobIds:
> glite-wms-job-submit -a -o> glite-wms-job-status -o > glite-wms-job-output -o
CREAM:
> glite-ce-job-submit -a -r grid-cr5.desy.de:8443/cream-pbs-desy cream.jdl > glite-ce-job-status
[top]
For the DESY VOs, the LCG File Catalog (LFC) is available.
The LFC offers features such as directory structures and ACL. and shows better performance.
Finding the apprpriate LFC:
lcg-infosites --vo _VO_ lfc
Enabling the usage of LFC: (chose your favorite VO or use the generic host name)
export LFC_HOST=`lcg-infosites --volfc`
List the LFC for a VO:
lcg-infosites --vo _VO_ lfc
Available commands on the UI are:
lfc-chmod lfc-getacl lfc-mkdir lfc-setacl lfc-chown lfc-ln lfc-rename lfc-setcomment lfc-delcomment lfc-ls lfc-rm
List contents:
lfc-ls -l /grid lfc-ls -lR /grid lfc-ls -lR /grid/_VO_
Creating a hierachical file system structure. Note: It has to start with lfn:/grid/_VO_:
lfc-mkdir -p /grid/_VO_/test
List access rights:
lfc-getacl /grid/_VO_/test
Example: (we use here the VO 'ilc') (Note: you must hold a valid proxy AND a be a member of the particular VO!)
> export LFC_HOST=`lcg-infosites --volfc` > lcg-cr -v --vo ilc file:/bin/sh -l lfn:/grid/ilc/test/ag_test1 -d dcache-se-desy.desy.de > lfc-ls -l -R /grid/ilc/test /grid/ilc/test: -rwxrwxr-x 1 41775 flc 585428 Jan 26 10:08 ag_test1 > lfc-getacl /grid/ilc/test # file: /grid/ilc/test # owner: 41775 # group: flc user::rwx group::rwx #effective:rwx other::r-x default:user::rwx default:group::rwx default:other::r-x
[top]
List replicas:
> lcg-lr -v --vo dteam lfn:/grid/dteam/desy/DESYTestFile > lcg-lg -v --vo dteam lfn:/grid/dteam/desy/DESYTestFile
Copy and register a file:
> lcg-cr -v --vo dteam -l lfn:/grid/dteam/desy/test4711 file:$PWD/file4711 guid:94462221-4871-4a45-ab31-2f3ce46e0cdb
Copy a file back:
> lcg-cp -v --vo dteam lfn:/grid/dteam/desy/test4711 file:/tmp/test4711
Replicate a file to another SE:
> lcg-rep -v --vo dteam lfn:/grid/dteam/desy/test4711 -d grid-se2.desy.de
List replicas associated with a LFN.
> lcg-lr -v --vo dteam lfn:/grid/dteam/desy/test4711
Using 'lcg-fetch' requires the following variables to be set:
export LFC_HOST=`lcg-infosites --volfc` export STORAGE_DIR=$PWD voms-proxy-init -voms _vo_ lcg-fetch -v --vo _vo_ --SE _se_ --tar _file-to-be-copied_
Access can be tested by means of local protocols used at DESY, such as dCache copy dccp:
> dccp -d2 gsidcap://...
A global basic Grid protocol used by all high-level protocols is GridFTP:
> globus-url-copy gsiftp://...
A high-level Grid management protocol is the Java-based SRM:
> mkdir -p $HOME/.srmconfig > srmcp -debug=true srm://...[top]
[Software Installation Management Guide]
VO tags: (requires Role-lcgadmin)
lcg-tags --ce grid-ce5.desy.de -vo ilc --add -tag VO-ilc-test01 lcg-tags --ce grid-ce5.desy.de -vo ilc --list lcg-tags --ce grid-ce5.desy.de -vo ilc --remove -tag VO-ilc-test01 lcg-info --vo ilc --list-ce --attrs Tag --query 'Tag=VO-ilc-test01'[top]
Note: lcg-CEs are gone. Most of the commands will not work anymore!
In order to test the validity of the certificate some simple Globus commands could be used.
Use the GridFTP (client on UI, server on CE):
> globus-url-copy -dbg gsiftp:///bin/sh file:/dev/null ...
Test if authentication works wioth your proxy:
> globusrun -a -r
Use Globus to run an executable on the DESY CE to check to which account your certificate is mapped: (works usually within DESY only due to the firewall on your site)
> globus-job-run"/bin/hostname" > globus-job-run "/usr/bin/id"
Use Globus to run an executable in PBS:
> globus-job-run/jobmanager-fork "/bin/hostname" > globus-job-run /jobmanager-lcgpbs "/bin/hostname; /usr/bin/id" > globus-job-run /jobmanager-lcgpbs -q desy "/bin/hostname; /usr/bin/id"
[top]
| Last modified: Thu Dec 1 11:30:20 MET 2005 | by the DESY Grid Team: http://grid.desy.de/ |