public:grid_srm_software_installation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:grid_srm_software_installation [2015-11-17 13:54] – add CentOS 7 instructions + fix a few minor issues amesfoortpublic:grid_srm_software_installation [2024-05-10 12:14] (current) – Hanno Holties
Line 1: Line 1:
- 
 ====== GRID storage access tools installation ====== ====== GRID storage access tools installation ======
  
-//This page describes the procedure to set up the tools for working directly on the srm storage. You may want to consider using the staging and download services provided by Astron if you just want to retrieve data from the archive: [[http://www.lofar.org/wiki/doku.php?id=public:lta_howto]].//+**//:!: Several sections in this page are deprecated or obsolete. In particular, users are advised to avoid SRM clients and globus client software and instead look into using the [[https://dmc-docs.web.cern.ch/dmc-docs/gfal2/gfal2.html|gfal]] client library and command line tools. SURF provides good [[https://doc.grid.surfsara.nl/en/latest/Pages/Advanced/grid_storage.html|documentation on usage of grid storage client software]].// **
  
-//You might also be interested in the [[public:srmclientinstallation|portable package of GRID storage access tools]], which offers the same functionality but does not require root access.// +//This page describes the procedure to set up the tools for working directly on the srm storage. You may want to consider using the staging and download services provided by Astron if you just want to retrieve data from the archive: [[http://www.lofar.org/wiki/doku.php?id=public:lta_howto|http://www.lofar.org/wiki/doku.php?id=public:lta_howto]].//The following documentation was developed for the installation of a GRID tools and certificates on an Ubuntu 12.04 system using a bash shell (using .bashrc as a configuration script). We have not tested the installation using csh derivatives but it is to be expected that not all scripts will work. Thanks to Martin van den Akker for providing notes of his installation procedure.
- +
-The following documentation was developed for the installation of a GRID tools and certificates on an Ubuntu 12.04 system using a bash shell (using .bashrc as a configuration script). We have not tested the installation using csh derivatives but it is to be expected that not all scripts will work. Thanks to Martin van den Akker for providing notes of his installation procedure.+
  
 Sites that provide packages and further information on installation of grid middleware on linux based systems: Sites that provide packages and further information on installation of grid middleware on linux based systems:
  
   * [[http://repository.egi.eu|Software repository of the European Grid Infrastructure]]   * [[http://repository.egi.eu|Software repository of the European Grid Infrastructure]]
-  * [[http://www.ige-project.eu/downloads/software/releases/downloads|Initiative for Globus in Europe]] 
-  * [[http://glite.cern.ch|Home of the gLite software suite]] (gLite UI provides a typical client installation) 
  
-NB We have tested the installation as described below only on Ubuntu 12 and CentOS 7. Please let us know if you have feedback or if you can contribute instructions on installations in different environments. +NB We have tested the installation as described below only on Ubuntu 12 and CentOS 7. Please let us know if you have feedback or if you can contribute instructions on installations in different environments. You might also first need to obtain a [[:public:grid_certificate|GRID certificate]]. 
-You might also first need to obtain a [[GRID certificate]].+
 ===== Installation of software packages ===== ===== Installation of software packages =====
  
Line 25: Line 20:
  
 Ubuntu Ubuntu
-  sudo apt-get install globus-gass-copy-progs+<code> 
 + 
 +sudo apt-get install globus-gass-copy-progs 
 + 
 +</code>
  
 CentOS CentOS
-  sudo yum install globus-gass-copy-progs+ 
 +<code> 
 +sudo yum install globus-gass-copy-progs 
 + 
 +</code>
  
 ==== voms client software ==== ==== voms client software ====
Line 35: Line 38:
  
 Ubuntu Ubuntu
-  sudo apt-get install voms-clients+ 
 +<code> 
 +sudo apt-get install voms-clients 
 + 
 +</code>
  
 CentOS CentOS
-  sudo yum install voms-clients-cpp+ 
 +<code> 
 +sudo yum install voms-clients-cpp 
 + 
 +</code>
  
 ==== Certificates for the Grid Certificate Authorities (CA) ==== ==== Certificates for the Grid Certificate Authorities (CA) ====
  
-Execute the following commands to install the certificates from the +Execute the following commands to install the certificates from the site of the European Grid Infrastructure (EGI) (root permissions are required).
-site of the European Grid Infrastructure (EGI) (root permissions are +
-required).+
  
 Ubuntu Ubuntu
-  sudo add-apt-repository 'deb http://repository.egi.eu/sw/production/cas/1/current egi-igtf core' + 
-  sudo apt-get update +Note 2021-05-19: newer versions of Ubuntu require to first add the appropriate GPG key for the EGI repository: 
-  sudo apt-get install ca-policy-egi-core+ 
 +<code> 
 +wget -q -O - https://dist.eugridpma.info/distribution/igtf/current/GPG-KEY-EUGridPMA-RPM-3 | sudo apt-key add - 
 + 
 +</code> 
 +<code> 
 + 
 +sudo add-apt-repository 'deb http://repository.egi.eu/sw/production/cas/1/current egi-igtf core' 
 +sudo apt-get update 
 +sudo apt-get install ca-policy-egi-core 
 + 
 +</code>
  
 CentOS CentOS
-  wget http://repository.egi.eu/sw/production/cas/1/current/repo-files/EGI-trustanchors.repo + 
-  sudo mv EGI-trustanchors.repo /etc/yum.repos.d/ +<code> 
-  sudo yum install ca-policy-egi-core+wget http://repository.egi.eu/sw/production/cas/1/current/repo-files/EGI-trustanchors.repo 
 +sudo mv EGI-trustanchors.repo /etc/yum.repos.d/ 
 +sudo yum install ca-policy-egi-core 
 + 
 +</code>
  
 ==== srmtools ==== ==== srmtools ====
Line 61: Line 85:
  
   - Download srmtools   - Download srmtools
-    *  {{public:srmclient-2.6.28.tar.gz|srmclient-2.6.28.tar.gz}}  (Java7, Java8)  +      * {{:public:srmclient-2.6.28.tar.gz|srmclient-2.6.28.tar.gz}}  (Java7, Java8) 
-    * {{public:srmclient-2.2.25.tar.gz|srmclient-2.2.25.tar.gz}}  (Java6) +      * {{:public:srmclient-2.2.25.tar.gz|srmclient-2.2.25.tar.gz}}  (Java6) 
-  - Extract and install the srmtools, e.g. in ''/opt/''\\ This will create a subdirectory, e.g. ''srmclient-2.6.28'', containing the required files.\\ Note that the srm package may be installed anywhere (e.g. in your home directory). +  - Extract and install the srmtools, e.g. in ''/opt/'' \\ This will create a subdirectory, e.g. ''srmclient-2.6.28'', containing the required files. \\ Note that the srm package may be installed anywhere (e.g. in your home directory). 
-  - Set the relevant environment path variables, e.g. in .bashrc (modify version number if applicable):\\ ''export SRM_PATH=<Install Directory>/srmclient-2.6.28/usr/share/srm''\\ ''export PATH=<Install Directory>/srmclient-2.6.28/usr/bin:$PATH''+  - Set the relevant environment path variables, e.g. in .bashrc (modify version number if applicable): \\ ''export SRM_PATH=<Install Directory>/srmclient-2.6.28/usr/share/srm'' \\ ''export PATH=<Install Directory>/srmclient-2.6.28/usr/bin:$PATH''
  
 NB The srm client tools depend on JAVA. There is a known issue with openjava version 7. If you have this version of JAVA installed, or otherwise get JAVA exceptions when running an srm command, please install another JAVA VM. Java-7-oracle is known to work. It is possible to have multiple JAVA VM installations and it is thus not required to replace an existing installation: if the default VM installation does not work with srm, another VM may be configured to be used by setting the following environment parameter: NB The srm client tools depend on JAVA. There is a known issue with openjava version 7. If you have this version of JAVA installed, or otherwise get JAVA exceptions when running an srm command, please install another JAVA VM. Java-7-oracle is known to work. It is possible to have multiple JAVA VM installations and it is thus not required to replace an existing installation: if the default VM installation does not work with srm, another VM may be configured to be used by setting the following environment parameter:
 +<code>
  
-  export JAVA_HOME=/usr/lib/jvm/java-7-oracle/jre+export JAVA_HOME=/usr/lib/jvm/java-7-oracle/jre 
 + 
 +</code>
  
 The JAVA VM used by default in Ubuntu and CentOS can be selected using the following command: The JAVA VM used by default in Ubuntu and CentOS can be selected using the following command:
  
-  sudo update-alternatives --config java+<code> 
 +sudo update-alternatives --config java 
 + 
 +</code>
  
 ==== Certificate Revocation List retrieval (optional) ==== ==== Certificate Revocation List retrieval (optional) ====
Line 79: Line 109:
  
 Ubuntu Ubuntu
-  sudo apt-get install fetch-crl+ 
 +<code> 
 +sudo apt-get install fetch-crl 
 + 
 +</code>
  
 CentOS CentOS
-  sudo yum install fetch-crl+ 
 +<code> 
 +sudo yum install fetch-crl 
 + 
 +</code>
  
 NB This is not required unless you intend to allow others to access your system by providing their grid certificate. NB This is not required unless you intend to allow others to access your system by providing their grid certificate.
Line 92: Line 130:
 Add the following string for the LOFAR Virtual Organization (VO) to the vomses file (any filename is fine). Add the following string for the LOFAR Virtual Organization (VO) to the vomses file (any filename is fine).
  
-  "lofar" "voms.grid.sara.nl" "30019" "/O=dutchgrid/O=hosts/OU=sara.nl/CN=voms.grid.sara.nl" "lofar"+<code> 
 +"lofar" "voms.grid.sara.nl" "30019" "/O=dutchgrid/O=hosts/OU=sara.nl/CN=voms.grid.sara.nl" "lofar"
  
-You can find this string also on the following website https://voms.grid.sara.nl:8443/voms/lofar/configuration/configuration.action in the text block under //VOMSES string for this VO//\\ The vomses file should be placed in one of the following default locations: ''/etc/vomses'', ''$HOME/.voms/vomses'', ''$HOME/.glite/vomses''+</code> 
 + 
 +You can find this string also on the following website [[https://voms.grid.sara.nl:8443/voms/lofar/configuration/configuration.action|https://voms.grid.sara.nl:8443/voms/lofar/configuration/configuration.action]] in the text block under //VOMSES string for this VO// \\ The vomses file should be placed in one of the following default locations: ''/etc/vomses'', ''$HOME/.voms/vomses'', ''$HOME/.glite/vomses''
  
 ==== List of certificates for voms.grid.sara.nl.lsc ==== ==== List of certificates for voms.grid.sara.nl.lsc ====
  
 Put the following strings: Put the following strings:
 +<code>
 +
 +/O=dutchgrid/O=hosts/OU=sara.nl/CN=voms.grid.sara.nl
 +/C=NL/O=NIKHEF/CN=NIKHEF medium-security certification auth
  
-  /O=dutchgrid/O=hosts/OU=sara.nl/CN=voms.grid.sara.nl +</code>
-  /C=NL/O=NIKHEF/CN=NIKHEF medium-security certification auth+
  
 in the file (root permissions required): in the file (root permissions required):
  
-  /etc/grid-security/vomsdir/lofar/voms.grid.sara.nl.lsc+<code> 
 +/etc/grid-security/vomsdir/lofar/voms.grid.sara.nl.lsc
  
-NB If this step is skipped or nor configured correctly ''voms-proxy-init'' will work but finish with warnings.+</code> 
 + 
 +NB If this step is skipped or nor configured correctly ''voms-proxy-init''  will work but finish with warnings.
  
 ==== Environment (optional) ==== ==== Environment (optional) ====
  
-You may want to provide the following settings in ''.bashrc'' or another initialisation/startup script if the relevant files are not in the default locations (defaults provided below).+You may want to provide the following settings in ''.bashrc''  or another initialisation/startup script if the relevant files are not in the default locations (defaults provided below).
  
-  export X509_USER_CERT=$HOME/.globus/usercert.pem +<code> 
-  export X509_USER_KEY=$HOME/.globus/userkey.pem +export X509_USER_CERT=$HOME/.globus/usercert.pem 
-  export X509_CERT_DIR=/etc/grid-security/certificates +export X509_USER_KEY=$HOME/.globus/userkey.pem 
-  export X509_VOMS_DIR=/etc/grid-security/vomsdir +export X509_CERT_DIR=/etc/grid-security/certificates 
-  export X509_USER_PROXY=$HOME/.proxy +export X509_VOMS_DIR=/etc/grid-security/vomsdir 
-  export VOMS_USERCONF=$HOME/.glite +export X509_USER_PROXY=$HOME/.proxy 
-  +export VOMS_USERCONF=$HOME/.glite 
 + 
 +</code> 
 + 
 +**Note:**  For (t)csh, use *.csh init scripts and 'setenv <key> <value>' instead of 'export <key>=<value>'.
  
 ==== CRL cron job (optional) ==== ==== CRL cron job (optional) ====
Line 128: Line 179:
  
 This creates a proxy (valid for 48 hours, increase if needed) in your home directory: This creates a proxy (valid for 48 hours, increase if needed) in your home directory:
 +
 <file> <file>
 voms-proxy-init -valid 48:00 -voms lofar:/lofar/user -out ~/.proxy voms-proxy-init -valid 48:00 -voms lofar:/lofar/user -out ~/.proxy
 +
 </file> </file>
  
 You can test that everything works by copying this file from surfsara to your working directory: You can test that everything works by copying this file from surfsara to your working directory:
 +
 <file> <file>
 srmcp -server_mode=passive srm://srm.grid.sara.nl/pnfs/grid.sara.nl/data/lofar/ops/fifotest/file1M file://`pwd`/file1M srmcp -server_mode=passive srm://srm.grid.sara.nl/pnfs/grid.sara.nl/data/lofar/ops/fifotest/file1M file://`pwd`/file1M
 +
 </file> </file>
  
 If your firewall allows incoming connections to non-standard ports, you can try this command without the server_mode option which will enable utilization of multiple streams to increase performance. If your firewall allows incoming connections to non-standard ports, you can try this command without the server_mode option which will enable utilization of multiple streams to increase performance.
  
-If you have the [[public:grid_srm_software_installation#globus_client_software|gridftp client software]] installed and in your path, it provides superior performance as compared to the native JAVA gridftp client that is provided by srmcp. In order to utilize this, download {{:public:lta-url-copy.sh.gz|lta-url-copy.sh.gz}}, unzip it and use the command:+If you have the [[:public:grid_srm_software_installation#globus_client_software|gridftp client software]] installed and in your path, it provides superior performance as compared to the native JAVA gridftp client that is provided by srmcp. In order to utilize this, download {{:public:lta-url-copy.sh.gz|lta-url-copy.sh.gz}}, unzip it and use the command:
 <file> <file>
 +
 srmcp -use_urlcopy_script=true -urlcopy=./lta-url-copy.sh -server_mode=passive srm://srm.grid.sara.nl/pnfs/grid.sara.nl/data/lofar/ops/fifotest/file1M file://`pwd`/file1M srmcp -use_urlcopy_script=true -urlcopy=./lta-url-copy.sh -server_mode=passive srm://srm.grid.sara.nl/pnfs/grid.sara.nl/data/lofar/ops/fifotest/file1M file://`pwd`/file1M
 +
 </file> </file>
-**Note:** You may have to force the use of TLS, (export GLOBUS_GSSAPI_FORCE_TLS=1 or in /etc/grid-security/gsi.conf set FORCE_TLS=true) to make this work.+ 
 +**Note:**  You may have to force the use of TLS, (export GLOBUS_GSSAPI_FORCE_TLS=1 or in /etc/grid-security/gsi.conf set FORCE_TLS=true) to make this work. 
 + 
  • Last modified: 2015-11-17 13:54
  • by amesfoort