iridium_cluster:data
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
iridium_cluster:data [2014/06/04 09:33] florido |
iridium_cluster:data [2016/06/28 13:34] (current) florido [Generic storage] |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| //Example:// | //Example:// | ||
| - | Moving ''ubuntu-12.04.2-desktop-amd64.iso'' from my local machine to ''n12.iridium'' | + | Moving ''ubuntu-12.04.2-desktop-amd64.iso'' from my local machine to ''n12.iridium'' shared folders |
| <code bash> | <code bash> | ||
| Line 59: | Line 59: | ||
| * available on windows but needs special installation | * available on windows but needs special installation | ||
| * does **not work** with GRID storage | * does **not work** with GRID storage | ||
| + | |||
| + | Syntax: | ||
| + | <code bash> | ||
| + | rsync -avz -e 'ssh -l <username>' --progress source destination | ||
| + | </code> | ||
| + | |||
| + | However, the progress indicator is not very good and most of the time slows down | ||
| + | the transfers in the purpose of writing to standard output. | ||
| + | Therefore I suggest you either **redirect the standard error and output**: | ||
| + | |||
| + | <code bash> | ||
| + | rsync -avz -e 'ssh -l <username>' --progress source destination &> rsyncoutput.log | ||
| + | </code> | ||
| + | |||
| + | Or even better, use **rsync own log file** instead: | ||
| + | <code bash> | ||
| + | rsync -avz -e 'ssh -l <username>' --log-file=rsyncoutput.log source destination | ||
| + | </code> | ||
| + | |||
| + | check the contents of the logfile now and then to see the status: | ||
| + | <code bash> | ||
| + | tail rsyncoutput.log | ||
| + | </code> | ||
| + | |||
| + | |||
| //Examples:// | //Examples:// | ||
| - | Moving ''ubuntu-12.04.2-desktop-amd64.iso'' from my local machine to ''n12.iridium'' | + | Moving ''ubuntu-12.04.2-desktop-amd64.iso'' from my local machine to ''pptest-iridium'' shared folders |
| <code bash> | <code bash> | ||
| Line 70: | Line 95: | ||
| Note on the trailing slashes **/**: | Note on the trailing slashes **/**: | ||
| - | **without** trailing slash on source **will create** //localdir// remotely: | + | source **without** trailing slash on source **will create** //localdir// remotely: |
| <code bash> | <code bash> | ||
| rsync -avz -e 'ssh -l pflorido' --progress localdir pptest-iridium.iridium:/nfs/software/pp/ | rsync -avz -e 'ssh -l pflorido' --progress localdir pptest-iridium.iridium:/nfs/software/pp/ | ||
| </code> | </code> | ||
| - | **with** trailing slash on source **will NOT create** //localdir// remotely but will **copy the contents** of //localdir// remotely | + | source **with** trailing slash on source **will NOT create** //localdir// remotely but will **copy the contents** of //localdir// remotely |
| <code bash> | <code bash> | ||
| rsync -avz -e 'ssh -l pflorido' --progress localdir/ pptest-iridium.iridium:/nfs/software/pp/ | rsync -avz -e 'ssh -l pflorido' --progress localdir/ pptest-iridium.iridium:/nfs/software/pp/ | ||
| Line 115: | Line 140: | ||
| - | === Solution 5: dq2 tools === | + | === Solution 5: Rucio or dq2 tools === |
| * **Pros:** | * **Pros:** | ||
| * works with GRID storage | * works with GRID storage | ||
| * **Cons:** | * **Cons:** | ||
| - | * works with ATLAS datasets | + | * works only with ATLAS datasets |
| - | //Example:// | + | If you have and ATLAS dataset, the best is to transfer it to the local |
| - | <code> | + | LUND Grid storage first, and then to the cluster directly if needed. |
| + | To do that you need to submit a DaTRi request | ||
| - | </code> | + | This page contains all you need to know on how to use the local storage: |
| + | http://www.hep.lu.se/grid/localgroupdisk.html | ||
| + | |||
| + | To move the dataset from any ATLAS grid storage to Iridium, you are recommended to use Rucio, the successor of DQ2. Use the following: | ||
| + | |||
| + | To enable RUCIO tools, you'll need to: | ||
| + | - copy and configure you GRID certificate on Iridium. | ||
| + | - run ''setupATLAS'' | ||
| + | - run ''localSetupRucioClients'' | ||
| + | - login to the GRID using ''arcproxy -S atlas'' or ''voms-proxy-init'' as one would do on //lxplus.cern.ch//. | ||
| + | |||
| + | The RUCIO official documentation is here: http://rucio.cern.ch/cli_examples.html | ||
| + | |||
| + | If you still want to use dq2 tools, here's how: | ||
| + | |||
| + | To enable dq2 tools, you'll need to: | ||
| + | - copy and configure you GRID certificate on Iridium. | ||
| + | - run ''setupATLAS'' | ||
| + | - run ''localSetupDQ2Client'' | ||
| + | - login to the GRID using ''arcproxy'' or ''voms-proxy-init'' as one would do on //lxplus.cern.ch// . | ||
| + | Information about dq2 on CERN Twiki (only visible if you have a CERN account): | ||
| + | https://twiki.cern.ch/twiki/bin/view/AtlasComputing/DQ2ClientsHowTo | ||
| ---- | ---- | ||
iridium_cluster/data.1401874407.txt.gz · Last modified: 2014/06/04 09:33 by florido
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
