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:testnodes [2014/03/21 19:27] florido [Accessing the Testing nodes] |
iridium_cluster:testnodes [2014/06/03 09:45] florido [Setup the work environment] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Iridium Cluster Testing nodes ====== | + | ====== Interactive access to the cluster: Iridium Cluster Testing nodes ====== |
+ | |||
+ | > **Q:** Why do I need this? | ||
+ | >> **A:** You need this if you want to test your code on some powerful machine. | ||
The cluster has two testing nodes accessible from anywhere that should be used for testing your code. | The cluster has two testing nodes accessible from anywhere that should be used for testing your code. | ||
Line 19: | Line 22: | ||
<code>ssh myusername@pptest-iridium.lunarc.lu.se</code> | <code>ssh myusername@pptest-iridium.lunarc.lu.se</code> | ||
- | ==== setup the work environment ==== | + | One can speed up access to the cluster by using the ssh ''config'' file (read [[:it_tips:ssh#Speedup connection with the ssh config file|here]] for detailed explanation). You can copy-paste the following into your ''.ssh/config'' file **and modify it to your needs**: |
+ | |||
+ | ---- | ||
+ | |||
+ | **Particle physics:** | ||
+ | <code> | ||
+ | # access pptest-iridium | ||
+ | Host pptest-iridium | ||
+ | HostName pptest-iridium.lunarc.lu.se | ||
+ | User <username on iridium> | ||
+ | ForwardX11 yes | ||
+ | |||
+ | # directly access iridium node X (change X to your preferred node!) | ||
+ | Host iridiumnX | ||
+ | User <Username on iridium> | ||
+ | ForwardX11 yes | ||
+ | ProxyCommand ssh -q pptest-iridium.lunarc.lu.se -W nX:22 | ||
+ | </code> | ||
+ | |||
+ | **Example:** My username is //guest03//. In the template above, I would change all the <Username …> to //guest03//, and //nX// to //n12//. | ||
+ | |||
+ | then to login to n12 I will do: | ||
+ | |||
+ | ssh iridiumn12 | ||
+ | |||
+ | And I will have to input 2 passwords: one for pptest-iridium and one for the node. | ||
+ | |||
+ | The number of passwords can be reduced if one uses a [[_it_tips:ssh#Reduce passwords using a private/public ssh key pair|private/public ssh key pair.]] | ||
+ | |||
+ | ---- | ||
+ | |||
+ | **Nuclear physics:** | ||
+ | <code> | ||
+ | # access nptest-iridium | ||
+ | Host nptest-iridium | ||
+ | HostName nptest-iridium.lunarc.lu.se | ||
+ | User <username on iridium> | ||
+ | ForwardX11 yes | ||
+ | |||
+ | # directly access iridium node X (change X to your preferred node!) | ||
+ | Host iridiumnX | ||
+ | User <Username on iridium> | ||
+ | ForwardX11 yes | ||
+ | ProxyCommand ssh -q nptest-iridium.lunarc.lu.se -W nX:22 | ||
+ | </code> | ||
+ | |||
+ | **Example:** My username is //guest03//. In the template above, I would change all the <Username …> to //guest03//, and //nX// to //n12//. | ||
+ | |||
+ | then to login to n12 I will do: | ||
+ | |||
+ | ssh iridiumn12 | ||
+ | |||
+ | And I will have to input 2 passwords: one for nptest-iridium and one for the node. | ||
+ | |||
+ | The number of passwords can be reduced if one uses a [[_it_tips:ssh#Reduce passwords using a private/public ssh key pair|private/public ssh key pair.]] | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Setup the work environment ==== | ||
Administrators provided scripts for quick setup of your work enviroment. | Administrators provided scripts for quick setup of your work enviroment. | ||
- | Just execute the command in the column //Script to run// at the shell prompt, or add it to your ''.bashrc'' or ''.bash_profile'' file so that is executed every time you login. | + | Just execute the command in the column //Script to run// at the shell prompt, or add it to your ''.bash_profile'' file so that is executed every time you login. |
+ | **NOTE:** do NOT add these scripts to ''.bashrc'' as suggested previously or you will not be able to rsync/scp. Contents of ''.bashrc'' are NOT supposed to generate output, but unfortunately some of these scripts do. | ||
The following are active now: | The following are active now: | ||
^ 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 needed environment variables for ATLAS experiment, and present a selection of other environments that the user can setup. | |
+ | ^ Various other environments through //module// | <code>module avail</code> | Will show a list of available environments. To enable one, execute the command <code>module load <name of environment></code> More info on modules on http://modules.sourceforge.net/ | | ||
+ | |||
+ | |||
+ | ==== Local disk space on the test nodes ==== | ||
+ | |||
+ | Every node has a local ''/tmp'' temporary disk space that can be used for computations. The contents of such space will be deleted regularly. Users can put any sort of data there. | ||