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
pandoc:introduction-to-vsc:02_connecting_to_vsc:connecting_to_vsc [2020/10/20 08:09] – Pandoc Auto-commit pandocpandoc:introduction-to-vsc:02_connecting_to_vsc:connecting_to_vsc [2023/03/27 08:22] (current) – [Connecting to VSC] goldenberg
Line 7: Line 7:
 ====== Project and User Account ====== ====== Project and User Account ======
  
-{{..:folie_01_1_connect.png?0x600}}+{{.:folie_01_1_connect.png?0x600}}
  
 ===== Prerequisites ===== ===== Prerequisites =====
  
-In order to be able to login VSC you need * a user account ➠ project leader (re-)sets * username * [[https://service.vsc.ac.at/clusteruser/login/|password]] * phone number for receiving OTP * to be inside university network * either physically * or via VPN-connection to your university * to use a terminal program, e.g. xterm (LINUX), terminal (OSX), putty (originally designed for the Windows platform, however, can also be used on other platforms: https:%%//%%www.putty.org), …+In order to be able to login VSC you need  
 +  * a user account  
 +    * ➠ project leader (re-)sets  
 +      * username  
 +      * [[https://service.vsc.ac.at/clusteruser/login/|password]]  
 +  * phone number for receiving OTP  
 +  * to be inside university network either: 
 +    * physically  
 +    * or via VPN-connection to your university  
 +  * to use a terminal program, e.g. xterm (LINUX), terminal (OSX), putty (originally designed for the Windows platform, however, can also be used on other platforms: https:%%//%%www.putty.org), …
  
  
- 
----- 
  
  
 ====== Project and User Account ====== ====== Project and User Account ======
  
-{{..:folie_01_3_connect.png?0x150}}+{{.:folie_01_3_connect.png?0x150}}
  
 Let us have a look at the first part, in the figure above denoted by a green box: connecting from the local machine to the remote VSC login nodes. Let us have a look at the first part, in the figure above denoted by a green box: connecting from the local machine to the remote VSC login nodes.
Line 33: Line 40:
 ===== Terminals: ===== ===== Terminals: =====
  
-linux: xterm, mac: terminal ## alternative terminal connection <html><font color=#cc3300></html> ''%%PuTTY%%'' <html></font></html> {{..:putty.png?0x670}}+linux: xterm, mac: terminal ## alternative terminal connection <html><font color=#cc3300></html> ''%%PuTTY%%'' <html></font></html> {{.:putty.png?0x670}}
  
 As stated before, putty was originally designed for the Windows platform, however, can also be used on other platforms, you can download it from: https:%%//%%www.putty.org) As stated before, putty was originally designed for the Windows platform, however, can also be used on other platforms, you can download it from: https:%%//%%www.putty.org)
Line 43: Line 50:
 ====== Connecting to VSC ====== ====== Connecting to VSC ======
  
-{{..:folie_04_ssh_l31.png?0x600}} +{{.:folie_04_ssh_l31.png?0x600}}
- +
-VSC-3 has 5 login servers named l31, …, l35.+
  
 VSC-4 has 10 named l40, …, l49. VSC-4 has 10 named l40, …, l49.
 +
 +VSC-5 has 10 named l50, …, l56. (57 to 59 are currently unavailable)
  
 Login via Login via
  
 <code bash> <code bash>
-# VSC-3 
-[...]$ ssh <me>@vsc-3.vsc.ac.at 
 # VSC-4 # VSC-4
-[...]$ ssh <me>@vsc-4.vsc.ac.at+[...]$ ssh <me>@vsc4.vsc.ac.at 
 +# VSC-5 
 +[...]$ ssh <me>@vsc5.vsc.ac.at
 </code> </code>
-assigns you to a VSC-3 oder VSC-4 login node per round robin manner.+assigns you to a VSC-4 oder VSC-5 login node per round robin manner. 
 + 
 +In PuTTY you first configure the connection like in the image at the top, and when connecting, you only need to type the username and not the server address too.
  
 **Note:** In the following we use “me” as representative username, please replace that by your own username and omit the “smaller/greater than” signs, i.e., write myusername@vsc……! **Note:** In the following we use “me” as representative username, please replace that by your own username and omit the “smaller/greater than” signs, i.e., write myusername@vsc……!
Line 67: Line 76:
 ====== Connecting to VSC ====== ====== Connecting to VSC ======
  
-{{..:folie_05_ssh_l31.png?0x600}}+{{.:folie_05_ssh_l31.png?0x600}}
  
 You may have reason to login to a specific login server: You may have reason to login to a specific login server:
  
 <code bash> <code bash>
-# VSC-3 
-[...]$ ssh <me>@l31.vsc.ac.at 
-                .. 
-[...]$ ssh <me>@l35.vsc.ac.at 
 # VSC-4 # VSC-4
 [...]$ ssh <me>@l40.vsc.ac.at [...]$ ssh <me>@l40.vsc.ac.at
                 ..                 ..
 [...]$ ssh <me>@l49.vsc.ac.at [...]$ ssh <me>@l49.vsc.ac.at
 +# VSC-5
 +[...]$ ssh <me>@l50.vsc.ac.at
 +                ..
 +[...]$ ssh <me>@l56.vsc.ac.at
 </code> </code>
 This may be necessary for trouble shooting. This may be necessary for trouble shooting.
Line 138: Line 147:
 ====== again and again ====== ====== again and again ======
  
-{{..:folie_07_oida.png?0x200}}+{{.:folie_07_oida.png?0x200}}
  
 The OTP-key holds for 12h and for the IP you login. However, each time you want to have a new shell on the cluster you will be asked to type the password. Is there a way out? The OTP-key holds for 12h and for the IP you login. However, each time you want to have a new shell on the cluster you will be asked to type the password. Is there a way out?
Line 148: Line 157:
 ====== ssh-keys ====== ====== ssh-keys ======
  
-{{..:folie_08_ssh_keys.png?0x600}}+{{.:folie_08_ssh_keys.png?0x600}}
  
 Using ssh-keys is a possible which enables to open several shells on the cluster by using a passphrase only once. Using ssh-keys is a possible which enables to open several shells on the cluster by using a passphrase only once.
Line 160: Line 169:
 ====== ssh-keys ====== ====== ssh-keys ======
  
-{{..:sshkeys_v03.png?0x600|how to set up ssh-keys on client and login node}}+{{.:sshkeys_v03.png?0x600|how to set up ssh-keys on client and login node}}
  
 [[https://wiki.vsc.ac.at/doku.php?id=doku:vpn_ssh_access|WIKI-link: ssh-keys]] [[https://wiki.vsc.ac.at/doku.php?id=doku:vpn_ssh_access|WIKI-link: ssh-keys]]
Line 169: Line 178:
 ====== ssh-keys — tunneling ====== ====== ssh-keys — tunneling ======
  
-{{..:folie_09_ssh_keys.png?0x600}}+{{.:folie_09_ssh_keys.png?0x600}}
  
 You may want to jump (tunnel) over a host which is between your local machine and VSC. Then you need to copy your key to both machines, the jump host and VSC. You may want to jump (tunnel) over a host which is between your local machine and VSC. Then you need to copy your key to both machines, the jump host and VSC.
Line 179: Line 188:
 ====== ssh-keys — tunneling ====== ====== ssh-keys — tunneling ======
  
-{{..:sshkeys_3servers_v03.png?0x600|how to set up ssh-keys on client and login node}}+{{.:sshkeys_3servers_v03.png?0x600|how to set up ssh-keys on client and login node}}
  
 <code bash> <code bash>
Line 202: Line 211:
 ====== Backup Policy ====== ====== Backup Policy ======
  
-{{..:folie_10_backup.png?0x600}}+{{.:folie_10_backup.png?0x600}}
  
 for details see [[https://service.vsc.ac.at/slides/introduction-to-vsc/08_storage_infrastructure/storage_infrastructure.html#(3)|Storage]] for details see [[https://service.vsc.ac.at/slides/introduction-to-vsc/08_storage_infrastructure/storage_infrastructure.html#(3)|Storage]]
Line 212: Line 221:
 ====== Sync and Copy ====== ====== Sync and Copy ======
  
-{{..:folie_11_scp_rsyn.png?0x200}}+{{.:folie_11_scp_rsyn.png?0x200}}
  
 If you copy with scp you always copy everything. On one hand, it may take ages until everything is copied, on the other hand, you may waste storage if there had only been minor modifications in your data. For that reason you may use rsync which first compares source and destination directory/file structure, subsequently only copying what did actually change. This saves time and disc space. If you copy with scp you always copy everything. On one hand, it may take ages until everything is copied, on the other hand, you may waste storage if there had only been minor modifications in your data. For that reason you may use rsync which first compares source and destination directory/file structure, subsequently only copying what did actually change. This saves time and disc space.
Line 224: Line 233:
 <code bash> <code bash>
 scp <source> <destination> scp <source> <destination>
-scp <me>@vsc3.vsc.ac.at:~/<myfile.c> .+scp <me>@vsc4.vsc.ac.at:~/<myfile.c> .
 scp myfile.c <me>@vsc4.vsc.ac.at:~/ scp myfile.c <me>@vsc4.vsc.ac.at:~/
 </code> </code>
Line 238: Line 247:
 ====== Copy — alternative via FileZilla ====== ====== Copy — alternative via FileZilla ======
  
-{{..:filezilla_10.png?0x600|FileZilla}}+{{.:filezilla_10.png?0x600|FileZilla}}
  
 For using FileZilla, make sure that you choose “interactive login”. This is necessary to be able to login via two factor authentication. If you are already logged into the cluster via, e.g., PuTTY or another terminal program, you can also login via a normal session because the OTP is only asked once in 12h per cluster (VSC-3 or VSC-4) and IP address. For using FileZilla, make sure that you choose “interactive login”. This is necessary to be able to login via two factor authentication. If you are already logged into the cluster via, e.g., PuTTY or another terminal program, you can also login via a normal session because the OTP is only asked once in 12h per cluster (VSC-3 or VSC-4) and IP address.
Line 248: Line 257:
 ====== Copy — alternative via winscp ====== ====== Copy — alternative via winscp ======
  
-{{..:winscp.png?0x600|winscp}}+{{.:winscp.png?0x600|winscp}}
  
  
  • pandoc/introduction-to-vsc/02_connecting_to_vsc/connecting_to_vsc.1603181398.txt.gz
  • Last modified: 2020/10/20 08:09
  • by pandoc