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
Next revision Both sides next revision
public:processing_at_juropa [2014-09-29 12:40]
Stefan Froehlich [Acquiring Data]
public:processing_at_juropa [2015-08-10 09:42]
Stefan Froehlich [Juropa decommisioned]
Line 1: Line 1:
 +===== Juropa decommissioned =====
 +The information below is only for backup and some install info might still be useful to other people.
 +The new system is Jureca and you can find the info (link when i have one).
 +
 ===== Installation and Processing on Juropa ====== ===== Installation and Processing on Juropa ======
 Here will be some notes on the Juropa installation and how to use the software on Juropa at the Juelich Supercomuting Centre.\\ Here will be some notes on the Juropa installation and how to use the software on Juropa at the Juelich Supercomuting Centre.\\
Line 36: Line 40:
 [[http://​dgi-2.d-grid.de/​zertifikate.php]] [[http://​dgi-2.d-grid.de/​zertifikate.php]]
 ==== SRM Copy from Juropa ==== ==== SRM Copy from Juropa ====
-There is guide from Hanno Holties which is sadly not applicable ​to Juropa ​anymoreBut it still contains useful information [[http://​www.lofar.org/​operations/​doku.php?​id=public:​srmclientinstallation&#​walkthrough]])\\ +There are two possible ways to create proxies on Juropa. ​With the ltools and grid-proxy-init commands or with voms-proxy-init.\\ 
-Only the following ​steps are necessary on Juropa:\\+The main difference is the authentication at the VO serverThe voms-proxy-init can directly get a user role as input where as the grid-proxy-init can not. For grid-proxy-init the user roles are compared to a local file that is synchronized with the SARA server once per day. So you have to wait until the next day after registering with the Lofar VO in order to use your proxies.\\ 
 +== grid-proxy-init == 
 +To use the grid-proxies simple follow these steps:\\
 Store your private key in ''​$HOME/​.globus/​userkey.pem''​\\ Store your private key in ''​$HOME/​.globus/​userkey.pem''​\\
 Execute:\\ <​code>​chmod 600 $HOME/​.globus/​userkey.pem</​code>​ Execute:\\ <​code>​chmod 600 $HOME/​.globus/​userkey.pem</​code>​
Line 46: Line 52:
 <​code>​grid-proxy-init -bits 2048</​code>​ <​code>​grid-proxy-init -bits 2048</​code>​
 Test data retrieval:​\\ <​code>​srmcp -server_mode=passive srm://​srm.grid.sara.nl/​pnfs/​grid.sara.nl/​data/​lofar/​ops/​fifotest/​file1M file:///​file1M</​code>​ Test data retrieval:​\\ <​code>​srmcp -server_mode=passive srm://​srm.grid.sara.nl/​pnfs/​grid.sara.nl/​data/​lofar/​ops/​fifotest/​file1M file:///​file1M</​code>​
-When copying data with the --jobfile option, keep in mind that there is a 30min cpu limit on the login node. Meaning your srmcp should be shorter that 30min.+When copying data with the --jobfile option, keep in mind that there is a 30min cpu limit on the login node. Meaning your srmcp should be shorter that 30min.\\ 
 +\\ 
 +== voms-proxy-init == 
 +To use voms-proxies handle your keys and certificate as above and source the script  
 +<​code>​. /​lustre/​jhome17/​htb00/​htb003/​lofar_grid/​init_java6.sh</​code>​ 
 +Optional: Set proxy environment variable to custom location:\\ <​code>​export X509_USER_PROXY=<​proxy_location></​code>​ 
 +Generate a proxy:\\ <​code>​voms-proxy-init -voms lofar:/​lofar/​user</​code>​ 
 +Test data retrieval:​\\ <​code>​srmcp -server_mode=passive srm://​srm.grid.sara.nl/​pnfs/​grid.sara.nl/​data/​lofar/​ops/​fifotest/​file1M file:///​file1M</​code>​
 ==== LOFAR Software ==== ==== LOFAR Software ====
 The LOFAR Software Framework is installed in the home directory of user htb003. You load the environment with The LOFAR Software Framework is installed in the home directory of user htb003. You load the environment with
  • Last modified: 2017-03-08 15:27
  • (external edit)