This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
iridium_cluster:data [2014/05/13 15:02] florido |
iridium_cluster:data [2014/06/04 11:16] florido [GRID 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 60: | Line 60: | ||
* does **not work** with GRID storage | * does **not work** with GRID storage | ||
- | //Example:// | + | Syntax: |
+ | <code bash> | ||
+ | rsync -avz -e 'ssh -l <username>' --progress source destination | ||
+ | </code> | ||
+ | |||
+ | |||
+ | //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> | ||
- | rsync -avz --progress ubuntu-12.04.2-desktop-amd64.iso n12.iridium:/nfs/software/pp/ | + | rsync -avz -e 'ssh -l pflorido' --progress ubuntu-12.04.2-desktop-amd64.iso pptest-iridium.lunarc.lu.se:/nfs/software/pp/ |
</code> | </code> | ||
+ | Note on the trailing slashes **/**: | ||
+ | |||
+ | source **without** trailing slash on source **will create** //localdir// remotely: | ||
+ | <code bash> | ||
+ | rsync -avz -e 'ssh -l pflorido' --progress localdir pptest-iridium.iridium:/nfs/software/pp/ | ||
+ | </code> | ||
+ | |||
+ | source **with** trailing slash on source **will NOT create** //localdir// remotely but will **copy the contents** of //localdir// remotely | ||
+ | <code bash> | ||
+ | rsync -avz -e 'ssh -l pflorido' --progress localdir/ pptest-iridium.iridium:/nfs/software/pp/ | ||
+ | </code> | ||
+ | |||
+ | Trailing slash on destination doesn't have any effect. | ||
=== Solution 3: FileZilla === | === Solution 3: FileZilla === | ||
Line 89: | Line 108: | ||
* **Pros:** | * **Pros:** | ||
* works with GRID storage | * works with GRID storage | ||
+ | * similar to cp | ||
* **Cons:** | * **Cons:** | ||
* doesn't work with ATLAS datasets (yet ;-) ) | * doesn't work with ATLAS datasets (yet ;-) ) | ||
- | * uncommon command line interface | ||
See also http://www.hep.lu.se/grid/localgroupdisk.html for more information on how to use Lund local GRID storage. | See also http://www.hep.lu.se/grid/localgroupdisk.html for more information on how to use Lund local GRID storage. | ||
Line 108: | Line 127: | ||
* **Cons:** | * **Cons:** | ||
* works with ATLAS datasets | * works with ATLAS datasets | ||
- | * uncommon command line interface (but some are used to it) | ||
- | //Example:// | + | To enable dq2 tools, you'll need to: |
- | <code> | + | - 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// . | ||
- | </code> | + | Information about dq2 on CERN Twiki (only visible if you have a CERN account): |
+ | https://twiki.cern.ch/twiki/bin/view/AtlasComputing/DQ2ClientsHowTo | ||
---- | ---- |