-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Started adapting instructions for PDC
- Loading branch information
Showing
10 changed files
with
99 additions
and
77 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -17,96 +17,106 @@ The reason we will teach you two ways is that some parts of this course will req | |
|
||
## SSH connection | ||
|
||
Let's look at the text-based SSH approach first. This type of connection work just fine even on slow internet connections since it only transmitts small amounts of text when you work with it. You will need an SSH program to do this, which fortunately is included in most major operating systems: | ||
Let's look at the text-based SSH approach first. This type of connection work just fine even on slow internet connections since it only transmitts small amounts of text when you work with it. You will need a terminal and an SSH program to do this, which fortunately is included in most major operating systems: | ||
|
||
- {{< fa brands linux >}} Linux: Use Terminal (Included by default) | ||
- {{< fa brands apple >}} OSX: Use Terminal (Included by default) | ||
- {{< fa brands windows >}} Windows: Use Powershell or Command prompt, both should be installed by default | ||
|
||
::: {.callout-note} | ||
Where `username` is mentioned, change to your user name. | ||
::: | ||
### Setting up SSH keys | ||
|
||
Fire up the available SSH program and enter the following: | ||
(If you already have done this once, please proceed to the [next section](#connecting-to-pdc-using-ssh) instead.) | ||
|
||
Before you can connect to PDC you will have to create SSH keys and tell PDC which key they should allow you to login with, and which computer it should be allowed to be used from. You will only have to create and register SSH keys once. Start by opening your terminal program (see list above) and follow these steps: | ||
|
||
1. Generate a key pair. | ||
```bash | ||
$ ssh [email protected] | ||
ssh-keygen | ||
``` | ||
and accept the default names it suggests by just pressing enter on the question about `file in which to save the key`. When it asks for a password, provide the password you will use to unlock the key each time you use it. Repeat the password when asked to in the next question. Once that is done it will say something like | ||
|
||
Enter your password when prompted. As you type, nothing will show on the screen. No stars, no dots. It is supposed to be that way. Just type the password and press enter, it will be fine. | ||
```bash | ||
user@computerName ~ $ ssh-keygen | ||
Generating public/private ed25519 key pair. | ||
Enter file in which to save the key (/home/user/.ssh/id_ed25519): | ||
Enter passphrase (empty for no passphrase): | ||
Enter same passphrase again: | ||
Your identification has been saved in /home/user/.ssh/id_ed25519 | ||
Your public key has been saved in /home/user/.ssh/id_ed25519.pub | ||
The key fingerprint is: | ||
SHA256:6T19rVfxVndEpmHHY0vZc8/Xu03iDBYjS04//rOOvks user@computerName | ||
The key's randomart image is: | ||
+--[ED25519 256]--+ | ||
| oo*| | ||
| . @=| | ||
| +oB| | ||
| .+ o oO| | ||
| S+ + o O| | ||
| . .o.= .o=| | ||
| . ooE=.+=| | ||
| o.o+oo| | ||
| .===+ | | ||
+----[SHA256]-----+ | ||
``` | ||
Now your screen should look something like this: | ||
The cool thing with SSH keys ([public-key cryptography](https://en.wikipedia.org/wiki/Public-key_cryptography)) like this is that they consist of two parts. One is the public key, which you can publish on the internet for everyone to see. The other part is the private part, which should be kept hidden from everyone, like a password. The public key is given to, in this case, PDC and they will let anyone who has the private key in. Print your public key to the terminal and copy the text so that you can use it in the next step. | ||
```bash | ||
cat ~/.ssh/id_ed25519.pub | ||
``` | ||
dahlo@dahlo-xps ~ $ ssh [email protected] | ||
Last login: Fri May 18 15:03:59 2018 from mi04.icm.uu.se | ||
_ _ ____ ____ __ __ _ __ __ | ||
| | | | _ \| _ \| \/ | / \ \ \/ / | System: rackham4 | ||
| | | | |_) | |_) | |\/| | / _ \ \ / | User: dahlo | ||
| |_| | __/| __/| | | |/ ___ \ / \ | | ||
\___/|_| |_| |_| |_/_/ \_\/_/\_\ | | ||
############################################################################### | ||
To register our public key we will go to [PDCs login portal](https://loginportal.pdc.kth.se/). Following a link from that page, you will login by first logging in to your SUPR account and then validating your identity to PDC through SUPR. | ||
User Guides: http://www.uppmax.uu.se/support/user-guides | ||
FAQ: http://www.uppmax.uu.se/support/faq | ||
![](assets/ssh_keys_pdc_001.png) | ||
Write to [email protected], if you have questions or comments. | ||
Press `Add new key` | ||
![](assets/ssh_keys_pdc_002.png) | ||
dahlo@rackham4 ~ $ | ||
``` | ||
|
||
Now you are connected to UPPMAX and can start working. | ||
Paste the public key content you printed to the terminal with `cat` before into the `SSH public key` field in the form, and give a `Key name` of your choosing, then press `Save`. | ||
## Remote desktop | ||
![](assets/ssh_keys_pdc_003.png) | ||
You can work on UPPMAX interactively through a graphical-user-interface (GUI) desktop environment using ThinLinc. | ||
You have now added your public key and told PDC that it should be allowed to login using this key when you are connecting form the IP (`385.142.529.933` in the screenshot above) you have at the moment. Since you might get new IPs for your computer each time you connect to the internet, we will have to add a broader list of allowed IPs for this key. Press `Add address` on the entry for the key you just added. | ||
We have a ThinLinc server running at one of the login nodes which allows users to run a remote desktop. It can be reached from a web browser (Chrome and Firefox are the recommended web browsers) or from the ThinLink App. For more details please look here: <a href="https://uppmax.uu.se/support-sv/user-guides/thinlinc-graphical-connection-guide/" target="_blank" rel="noopener noreferrer">https://uppmax.uu.se/support-sv/user-guides/thinlinc-graphical-connection-guide/</a> | ||
![](assets/ssh_keys_pdc_004.png) | ||
### Web browser | ||
Add `*.liu.se` to the field `define one yourself`. This will allow you to use this key as long as you are connecting from anywhere at Linköping university. If you want to use this key from your home university in the future you can add a similar pattern that matches your home university's (or internet provider) hostname (e.g. `*.uu.se`, `*.kth.se` or `*.telia.com`). | ||
|
||
To be able to login via a web browser you will have to set up two-factor authentication first. Follow the <a href="https://www.uppmax.uu.se/support/user-guides/setting-up-two-factor-authentication/" target="_blank" rel="noopener noreferrer">instructions at the UPPMAX homepage</a>, and once you are done you can continue below. | ||
![](assets/ssh_keys_pdc_005.png) | ||
|
||
1. Go to the login page, <a href="https://rackham-gui.uppmax.uu.se/" target="_blank" rel="noopener noreferrer">https://rackham-gui.uppmax.uu.se/</a> | ||
2. Enter your UPPMAX username. | ||
3. Enter your UPPMAX password, followed by your current two-factor authentication code. | ||
Eg. if your password is `hunter2` and your current two-factor authentication code is `123456` you will enter `hunter2123456` as your password. | ||
|
||
![](assets/thinlinc_00.png){width="200px"} | ||
### Connecting to PDC using SSH | ||
|
||
4. It will ask you which profile you want to use, so first press the `Forward` button. Then you can choose which desktop environment you want to use. `Xfce` is pretty straight-forward and easy to use, but feel free to try either of them. You get to choose every time you login so it's not a permanent choice. | ||
|
||
![](assets/thinlinc_01.png){width="200px"} | ||
::: {.callout-note} | ||
Where `username` is mentioned, change to your PDC user name. | ||
::: | ||
|
||
5. Once your desktop has been loaded, start a terminal either by clicking the black terminal icon at the bottom of the screen, or by pressing the `Applications` button in the top left corner and select `Terminal Emulator`. | ||
Fire up the available SSH program and enter the following: | ||
|
||
![](assets/thinlinc_02.png){width="200px"} | ||
```bash | ||
$ ssh [email protected] | ||
``` | ||
|
||
### ThinLink App | ||
Enter your password when prompted. As you type, nothing will show on the screen. No stars, no dots. It is supposed to be that way. Just type the password and press enter, it will be fine. | ||
|
||
1. If you haven't already done so, download the ThinLinc client matching your local computer (i.e Windows, Linux, MacOS X or Solaris) from <a href="https://www.cendio.com/thinlinc/download" target="_blank" rel="noopener noreferrer">https://www.cendio.com/thinlinc/download</a> and install it. | ||
2. Launch the ThinLinc client. You should see a form where you can enter your username and password, and possibly a server name. If you only see this simple form as shown below, you can click **Advanced** to be able to set the server name. | ||
Now your screen should look something like this: | ||
|
||
![](assets/thinlinc_03.png){width="200px"} | ||
```bash | ||
user@computerName ~ $ ssh [email protected] | ||
Enter passphrase for key '/home/user/.ssh/id_ed25519': | ||
Last login: Mon Oct 23 21:11:35 2024 from 385-142-529-933.bredband.obe.net | ||
3. Change the **Server** setting to `rackham-gui.uppmax.uu.se`. | ||
4. Change the **Name** setting to your UPPMAX username. | ||
5. Set the **Password** setting to your UPPMAX password. | ||
6. You do not need to change any other settings. | ||
7. You will first come to the `ThinLinc profile chooser`. Press the `Forward` button to continue. Then you can choose which desktop environment you want to use. `Xfce` is pretty straight-forward and easy to use, but feel free to try either of them. You get to choose every time you login so it's not a permanent choice. | ||
8. Press the **Connect** button. | ||
9. If you connect for the first time you will see the "The server's host key is not cached ..." dialog. | ||
--== Welcome to Dardel! ==-- | ||
![](assets/thinlinc_01.png){width="200px"} | ||
username@login1 ~ $ | ||
``` | ||
|
||
10. Once your desktop has been loaded, start a terminal either by clicking the black terminal icon at the bottom of the screen, or by pressing the `Applications` button in the top left corner and select `Terminal Emulator`. | ||
Now you are connected to PDC and can start working. | ||
|
||
![](assets/thinlinc_02.png){width="200px"} | ||
|
||
11. **Two factor authentication:** The ThinLinc client connects over SSH which means it **may** be required to present a two factor authentication code. If you need to use this when logging in with SSH you also need to use it when logging in with ThinLinc (it depends on where you connect from). The ThinLinc client does not know how to ask for the two factor code, so you will need to use the grace time feature. To do this, first you have to connect with regular SSH and present the required two factor code. Once you have logged in over SSH you can safely exit again. The login server will remember that you just logged in for a few minutes and will not ask for two factor authentication again, so make sure you do not wait too long to connect with the ThinLinc client. | ||
## Remote desktop | ||
|
||
## After connection to UPPMAX | ||
You can work on PDC interactively through a graphical-user-interface (GUI) desktop environment using ThinLinc. | ||
|
||
From this point forward there is no difference between the two different ways of connection to UPPMAX. Both ways result in you having a terminal running on UPPMAX and from UPPMAX point of view they are the same. | ||
We have a ThinLinc server running at one of the login nodes which allows users to run a remote desktop. It can be reached using the ThinLink App. For more details please look here: <a href="https://intra.kth.se/en/2.79567/support/documents/login/interactive_hpc.html" target="_blank" rel="noopener noreferrer">https://intra.kth.se/en/2.79567/support/documents/login/interactive_hpc.html</a> |
Oops, something went wrong.