These instructions are primarily valid for ARC 13.02 client tools (as in EMI 3 Monte Bianco), but are also applicable for ARC 12.05 (as in EMI 2 Matterhorn) and ARC 11.05 (as in EMI 1 Kebnekaise).
ARC client is distributed in many ways for a variety of platforms by several distributors. Normally, it is available in standard Linux repositories (Fedora, EPEL, Debian, Ubuntu), but newer versions may be available from the NorduGrid repository.
Every Grid tool, including ARC client, requires installation of public certificates of Certificate Authorities (CA). In case you do not have such installed yet, obtain them from either of the following providers:
These certificates are necessary to use international Grid infrastructures. Make sure your national CA certificates are always present. If your project makes use of own internal certificates, install them as well (contact your project support team for details). If there are some CAs that are banned by your local policies, make sure to remove their certificates from your computer.
For Linux users with system administrator privileges, recommended installation method is via use of repositories. The reason for this is complex dependencies of packages, which are best handled by repositories. The following repositories are relevant:
Standalone packages so far exist only for ARC 11.05u2
For Linux users without privileges, NorduGrid provides pre-compiled standalone binary client packages, which can be obtained from the NorduGrid downloads site for a large number of systems.
Although rpm- and deb-packages, as well as source tarballs, can be downloaded individually from repositories listed above, it is not recommended to attempt installation from these, unless you have suficient expertise and a very good reason not to use YUM, APT or standalone. Contact Grid support in case you need assistance in installing ARC client from source code or individual Linux packages.
In case you have previously installed ARC client that provided ngsub, ngget, ngcp and other ng* tools, please remove it in order to avoid potential conflicts and confusion!
Metapackage nordugrid-arc-client-tools conveniently provides both legacy and new ARC client. If you need both, configure YUM or APT repository for ARC, EMI or EGI UMD, and execute: yum install nordugrid-arc-client-tools or apt-get install nordugrid-arc-client-tools depending on your system.
If the metapackage nordugrid-arc-client-tools is not available, install the following packages: nordugrid-arc-client nordugrid-arc-plugins-needed nordugrid-arc-plugins-globus ca-policy-igtf-classic ca-policy-igtf-mics ca-policy-igtf-slcs fetch-crl
If you chose to upgrade nordugrid-arc-client package without removing it, always make sure you install also the following:
Once you configured YUM or APT repository for ARC, EMI or EGI UMD, execute: yum install nordugrid-arc-client-tools or apt-get install nordugrid-arc-client-tools depending on your system.
If the metapackage nordugrid-arc-client-tools is not available, install the following packages: nordugrid-arc-client nordugrid-arc-plugins-needed nordugrid-arc-plugins-globus
You always need to install IGTF CA certificates. Metapackages normally install them automatically, but if it did not happen, or if you did not use metapackages, install these certificates like this:yum install ca_policy_igtf-classic ca_policy_igtf-mics ca_policy_igtf-slcs
or, for Debian and Ubuntu: (note absent underscores):apt-get install ca-policy-igtf-classic ca-policy-igtf-mics ca-policy-igtf-slcs
Standalone packages so far exist only for ARC 11.05u2
Standalone tarball contains not just ARC client tools, but also a number of external tools, utilities and libraries needed for successful work on Grid. It also comes complete with the CA certificates. The list below outlines contents of the tarball:
Put the downloaded tarball in a directory of your choice and execute tar xvzf nordugrid-arc-standalone-<version->.tgz This will create a new directory nordugrid-arc-standalone-<version> and the tarball can hereafter safely be removed.
Enter the unpacked directory:
and set up the environment by executing one of the following:
for bash or zsh: source setup.sh for csh or tcsh: source setup.csh for ksh or any other shell where the source command is not defined: . ./setup.sh Upon first execution, this will print a lot of informational output. Make sure there are no "error" or "failure" messages.
Each user must edit configuration file in: $HOME/.arc/client.conf Initial contents of this file can be copied from either the common configuration at /etc/arc/client.conf or from the template in <standalone-path>/etc/arc/client.conf depending whether you installed the client from Linux repositories or from the standalone tarball.
IMPORTANT! Always specify your Grid infrastructure entry point in [registry/<alias>] block (ARC 12.05) or defaultservices attribute of [common] block (ARC 11.05)!
Different Grid infrastructures or Virtual Organisations have different entry points, not known to ARC developers. Ask your local Grid expert what is the correct value in your case.
In ARC 12.05, Grid entry points are described in [registry/<alias>] blocks, one block per entry point. An example of a working block in ARC 12.05 is:
url = ldap://index2.nordugrid.org:2135/Mds-Vo-name=NorduGrid,o=grid
registryinterface = org.nordugrid.ldapegiis
default = yes
In ARC 11.05, Grid entry points are denoted with index prefix. An example of a working [common] block in ARC 11.05 is:
defaultservices=index:ARC0:ldap://index1.nordugrid.org:2135/Mds-Vo-name=NorduGrid,o=grid index:ARC0:ldap://index2.nordugrid.org:2135/Mds-Vo-name=NorduGrid,o=grid index:ARC0:ldap://index3.nordugrid.org:2135/Mds-Vo-name=NorduGrid,o=grid index:ARC0:ldap://index4.nordugrid.org:2135/Mds-Vo-name=NorduGrid,o=grid index:ARC0:ldap://index1.ndgf.org:2135/Mds-Vo-name=NDGF,o=grid index:ARC0:ldap://index2.ndgf.org:2135/Mds-Vo-name=NDGF,o=grid index:ARC0:ldap://arc-emi.grid.upjs.sk:2135/Mds-Vo-name=ARC-EMI,o=grid index:ARC1:http://asimov.grid.niif.hu:60002/isis computing:ARC1:https://knowarc1.grid.niif.hu:60000/arex computing:CREAM:ldap://cream.grid.upjs.sk:2170/o=grid computing:UNICORE:https://testbed5.grid.upjs.sk:8080/KnowARC-testbed/services/BESFactory?res=default_bes_factory
Please read the client manual for explanation of configuration options.
In order to use Grid client tools to access Grid services, you must be properly authorised. In brief, the following steps are necessary:
Make sure you have a valid personal Grid certificate, typically located in $HOME/.globus/usercert.pem and a private key $HOME/.globus/userkey.pem
usercert.pem must be world-readable (Linux file access permissions 644), while userkey.pem must be readable only by the owner (mode 400).
Acceptable certificates are issued by the national Certificate Authorities (CA) endorsed by the International Grid Trust Federation (IGTF). In case you have no certificate, find your respective authority through the IGTF Web site and contact them for instructions on how to obtain the certificate.
For more information about certificates and related things read "Grid Certificate Mini How-to".
Every Virtual Organisation (VO) has own procedures and policies. Please contact your VO support team for membership instructions.
Create Grid login - proxy certificate - with arcproxy
For a quick check of your installation, use arctest command: e.g. arctest -J 1 Allow for a couple of minutes for the job to find its place on the Grid, and check its status by using: arcstat -a Once status suggests the job has finished, do: arccat -a If everything works, you will see "hello, grid" message!
The following documents are necessary for all ARC users:
For questions, suggestions, feature requests and bug reports, use the Global Grid Support System.