User Tools

Site Tools


iridium_cluster:howtos_users

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
iridium_cluster:howtos_users [2013/08/26 16:10]
florido
iridium_cluster:howtos_users [2013/08/27 19:27]
florido [Speedup login by using ssh keys]
Line 137: Line 137:
 ^ Environment | Script to run | Description | ^ Environment | Script to run | Description |
 ^ ATLAS Experiment environment | ''​setupATLAS''​ | Will setup all the neeeded environment variables for ATLAS experiment, and present a selection of other environments that the user can setup. | ^ ATLAS Experiment environment | ''​setupATLAS''​ | Will setup all the neeeded environment variables for ATLAS experiment, and present a selection of other environments that the user can setup. |
 +
 +===== Tips'​n'​Tricks =====
 +
 +Suggestions on how to make your life easier when using the cluster.
  
 ==== Tips to speedup logging in ==== ==== Tips to speedup logging in ====
Line 193: Line 197:
 == References: == == References: ==
   * http://​sshmenu.sourceforge.net/​articles/​transparent-mulithop.html   * http://​sshmenu.sourceforge.net/​articles/​transparent-mulithop.html
 +
 +==== Speedup login by using ssh keys ====
 + 
 +An alternative method of authenticating via ssh is by using ssh keys. It will ease the pain of writing many passwords. The only password you will need is to unlock your key.
 +
 +:!: ** PLEASE DO NOT USE PASSWORDLESS KEYS. IT IS A GREAT SECURITY RISK. ** :!:
 +
 +Read about them here:
 +
 +https://​wiki.archlinux.org/​index.php/​SSH_Keys
 +
 +
 +==== How not to loose all your job because you closed a ssh terminal ====
 +
 +Use **screen**. //GNU screen// is an amazing tool that opens a remote terminal that is independent on your ssh connection. If the connection drops or you accidentally close the ssh window, it will still run your jobs on the cluster.
 +
 +A quick and dirty tutorial can be read [[:​it_tips#​screen|here]],​ but there'​s plenty more on the internet.
  
 ---- ----
Line 200: Line 221:
 Please read the section [[#Common files organization]] before going through this section. Please read the section [[#Common files organization]] before going through this section.
  
-Instructions ​are coming soon+==== Rules of thumb ==== 
 + 
 +:!: **Please read this carefully.** :!: 
 + 
 +When moving data to the shared folders, please follow these common sense rules: 
 +  * Create folders for everything you want to share. 
 +  * If the data has been produced by you, is nice to create a folder with your name and place everything in it. 
 +  * If the data belongs to some specific experiment, dataset or the like, create a folder name that is consistent with that and that is easy for everybody to understand what that is about. 
 +  * Don't overdo. Only copy data you/your colleagues need. This is a shared facility. 
 +  * Don't remove other user's files unless you advice them and they'​re ok with it. This is a shared facility. 
 +  * Don't expect contents of the ''​scratch''​ folder to be always there. We still have no policy for that but we will have meetings in which we decide about it. 
 + 
 +==== Data transfer solutions ==== 
 + 
 +Here's some solutions to move data to the cluster. 1-3 are generic data transfer tools. 4-5 are GRID oriented data transfer tools (mostly for Particle Physicists) 
 + 
 +These marked with 8-) are my favourite ​ --- //​[[:​Florido Paganelli]] 2013/08/27 20:20// 
 + 
 +=== Solution 1: scp,​sftp,​lsftp === 
 + 
 +  * **Pros:**  
 +    * easy 
 +    * only needs terminal 
 +    * available almost everywhere 
 +    * progress indicator 
 +  * **Cons:**  
 +    * not reliable. If connection goes down one must restart the entire transfer. 
 +    * does **not work** with GRID storage 
 +    * slow 
 + 
 +//​Example://​ 
 + 
 +Moving ''​ubuntu-12.04.2-desktop-amd64.iso''​ from my local machine to ''​n12.iridium''​ 
 + 
 +<​code>​ 
 +  scp ubuntu-12.04.2-desktop-i386.iso n12.iridium:/​nfs/​shared/​pp/​ 
 +</​code>​ 
 + 
 +=== Solution 2: rsync  === 
 + 
 +8-) 
 + 
 +  * **Pros:**  
 +    * Reliable. If connection goes down will resume from where it stopped. 
 +    * Minimizes amount of transferred data by compressing it 
 +    * only needs terminal 
 +    * available on most GNU/Linux platforms 
 +    * a bit faster 
 +  * **Cons:** 
 +    * Awkward command line 
 +    * bad logs 
 +    * poor progress indicator on many files 
 +    * available on windows but needs special installation 
 +    * does **not work** with GRID storage 
 + 
 +//​Example://​ 
 + 
 +Moving ''​ubuntu-12.04.2-desktop-amd64.iso''​ from my local machine to ''​n12.iridium''​ 
 + 
 +<​code>​ 
 +  rsync -avz --progress ubuntu-12.04.2-desktop-amd64.iso n12.iridium:/​nfs/​software/​pp/​ 
 +</​code>​ 
 + 
 + 
 +=== Solution 3: FileZilla === 
 + 
 +  * **Pros:** 
 +    * Reliable. Tries to resume if connection went down. 
 +    * Visual interface 
 +    * Available for both GNU/Linux and windows 
 +  * **Cons:** 
 +    * Visual interface :D 
 +    * good logs 
 +    * progress bar ^_^  
 +    * does **not work** with GRID storage 
 + 
 +More about it: https://​filezilla-project.org/​download.php?​type=client 
 + 
 +=== Solution 4: NorduGrid ARC tools (arccp, arcls, arcrm) === 
 + 
 +  * **Pros:** 
 +    * works with GRID storage 
 +  * **Cons:** 
 +    * doesn'​t work with ATLAS datasets (yet ;-) ) 
 +    * uncommon command line interface 
 + 
 +//​Example://​ 
 +<​code>​ 
 + 
 +</​code>​ 
 + 
 + 
 +=== Solution 5: dq2 tools === 
 + 
 +  * **Pros:** 
 +    * works with GRID storage 
 +  * **Cons:** 
 +    * works with ATLAS datasets 
 +    * uncommon command line interface (but some are used to it) 
 + 
 +//​Example://​ 
 +<​code>​ 
 + 
 +</​code>​ 
  
 ---- ----
iridium_cluster/howtos_users.txt · Last modified: 2013/10/15 15:57 by florido

Accessibility Statement