WARNING 20/Sep/2016: In ARC 5.1.3 there is a collision with the new version of OpenSSL (if you are really on Ubuntu 16/*) that occasionally, in spite of fixes and updates, failes with arcproxy when it tries to get attributes from the VOMS server. If this happens for you, please try to use the command voms-proxy-init from the package voms-clients.
voms-proxy-init--debug --rfc --voms gen.vo.sling.si --vomses .arc/vomses \ --certdir /etc/grid-security/certificates
Installation of ARC Client in preparation of a test job for Ubuntu Trusty 14.04 (English-language instructions version).
Our first step is setting-up the NorduGrid deb package repository for our Ubuntu installation:
wget http://download.nordugrid.org/repos/latest/ubuntu/dists/trusty/main/binary-amd64/nordugrid-release_13.11~trusty1_all.deb dpkg -i nordugrid-release_13.11~trusty1_all.deb wget -q -O - http://download.nordugrid.org/DEB-GPG-KEY-nordugrid.asc | apt-key add -
Then we can install the needed packages:
apt-get install nordugrid-arc-client nordugrid-arc-plugins-globus
Then we need to install the meta-package for CA root distributions used for authetication from the EGI-trustanchors repository:
vi /etc/apt/sources.list #append this lines #### EGI Trust Anchor Distribution #### deb http://repository.egi.eu/sw/production/cas/1/current egi-igtf core wget -q -O - https://dist.eugridpma.info/distribution/igtf/current/GPG-KEY-EUGridPMA-RPM-3 | apt-key add - apt-get update apt-get install ca-policy-egi-core
Then create s subdirectory .arc in your HOME directory where your personal certificates and other data will be kept (used to be .globus in older installations and instructions):
You should have obtained your grid certifikate, enlisted in the VOMS service at Gen.VO.SLING.SI and exported the certificate from your browser into a .p12 file already in the Authentication and Authorization step.
Now you need to transform the certiciate and key in .pem format, make sure the key is only readable by you and move both files in your ~/.arc directory:
openssl pkcs12 -in usercert.p12 -clcerts -nokeys -out usercert.pem openssl pkcs12 -in usercert.p12 -nocerts -nodes -out userkey.pem chmod 400 userkey.pem chmod 644 usercert.pem mv userkey.pem ~/.arc/ mv usercert.pem ~/.arc/
The next step is requried to inform your ARC client about the location and name of Slovenian VOMS server and gen.vo.sling.si VO. You need to create suitable files ~/.arc/vomsdir/voms.sling.si.lsc and ~/.arc/vomses :
cd ~/.arc mkdir vomsdir echo -e "/C=SI/O=SiGNET/O=SLING/CN=voms.sling.si\n/C=SI/O=SiGNET/CN=SiGNET CA" > vomsdir/voms.sling.si.lsc echo -e '"gen.vo.sling.si" "voms.sling.si" "15001" "/C=SI/O=SiGNET/O=SLING/CN=voms.sling.si""gen.vo.sling.si"' > vomses #this should result in the following file contents: cat ~/.arc/vomsdir/voms.sling.si.lsc /C=SI/O=SiGNET/O=SLING/CN=voms.sling.si /C=SI/O=SiGNET/CN=SiGNET CA cat ~/.arc/vomses "gen.vo.sling.si" "voms.sling.si" "15001" "/C=SI/O=SiGNET/O=SLING/CN=voms.sling.si""gen.vo.sling.si"
Then you can create a proxy certificate. If there are AC errors, perhaps you have not yet enrolled in Gen.VO.SLING.SI or your membership has not been approved yet (you should have received an e-mail notification).
(Use man arcproxy to see other options.)
arcproxy -S gen.vo.sling.si Your identity: /C=SI/O=SiGNET/O=ARNES/CN=Ime Priimek Contacting VOMS server (named gen.vo.sling.si): voms.sling.si on port: 15001 Proxy generation succeeded Your proxy is valid until: 2014-04-24 01:03:10
Then you can create a simple job description file and submit the test job. (Note that here your job is not executing a start-up script but simply running a system program and returning its results.)
vi test.xrsl & (executable = /usr/bin/env) (jobname = "test") (stdout=test.log) (join=yes) (gridtime=1000) (gmlog=log) (memory=2000) arcsub -c jost.arnes.si -S org.nordugrid.gridftpjob -o joblist.xml test.xrsl -d DEBUG ... Job submitted with jobid: gsiftp://jost.arnes.si:2811/jobs/4fQLDmY3BxjnmmR0Xox1SiGmABFKDmABFKDmvxHKDmABFKDmiPhU9m
(If you have succeeded in creating a proxy with no AC errors and the cluster returns an authorization error, it is probable that you have submitted the job shortly after enrolling with VOMS and the cluster has not yet synchronized its metadata.)
You can check the status of your jobs now. (Note that it will take some time to include your new job i the system info – typically a few minutes.)
arcstat -c jost.arnes.si
When your job is in FINISHED state, you can get the resulting files (automatically deleting them on server). Note that your files only wait for retrieval a limited time (tipically a week).
arcget gsiftp://jost.arnes.si:2811/jobs/4fQLDmY3BxjnmmR0Xox1SiGmABFKDmABFKDmvxHKDmABFKDmiPhU9m Results stored at: 4fQLDmY3BxjnmmR0Xox1SiGmABFKDmABFKDmvxHKDmABFKDmiPhU9m Jobs processed: 1, successfully retrieved: 1, successfully cleaned: 1 # or: arcget -a #(to get files from all finished jobs) # or: arcget -i joblist.xml #(to get files from all jobs in the list)
At this point, you are ready to submit real jobs. Typically, a real job will either use pre-installed software (contact administrators at firstname.lastname@example.org) or your own programs (perhaps compiled in the job). Real jobs also include data (from local files or remote repositories). Please see offical NorduGrid ARC manuals.