Straight to the Point¶
Access to the cluster requires the creation of a user account. To request one, please refer to the contact page. Once your account has been provisioned, you can connect to Dalek via SSH.
Info
This page provides a summary of the key information required to connect to Dalek. A detailed, step-by-step guide is available on the following page. If you are not familiar with SSH tunneling or public/private key authentication, it is recommended to read the step-by-step procedure first.
SSH Configuration File¶
To facilitate the SSH usage, it is strongly advise to copy-paste the following
lines into your $HOME/.ssh/config file and to replace the [USER_DALEK]
placeholder with your Dalek login (3 times).
Unfold the Details box just below to see the config file:
| ~/.ssh/config | |
|---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 | |
Unfold the Details box just below to see the config file:
| ~/.ssh/config | |
|---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 | |
Once it is done, you can simply connect to the frontend by doing:
Danger
Please change your password at your first connection to the frontend node by running the following command:
To directly connect to a compute node, you can do (here az4-n4090-0 node):
To connect to a compute node, there are three possible suffixes supported in the previous SSH configuration file. The philosophy is to encapsulate, first the connection to the Dalek frontend (with the proxy jump via the gateway if needed) and then, do the following depending on the suffix:
.srun: Allocates a node via SLURMsruncommand (in interactive mode): Reserves one CPU (= 1 CPU HW thread in SLURM) and no GPU. Here is an example of use:.srex: Allocates a node via SLURMsruncommand (in interactive mode) and in exclusive mode: Reserves all the available resources (= all the available CPU HW threads + all the available GPUs). Here is an example of use:.ssh: Connects to a node via SSH, this requires the node to be firstly reserved in exclusively mode via SLURM. This is convenient to open additional TTYs on a node. Here is an example of use:
Info
The first login to a node can take some time because the previous command
will wake up the node before to allocate it to you. Generally it takes
around 30 seconds and can take up to 3 minutes if the node is
poweroff.
Frontend and Compute Nodes Keys¶
The frontend node keys are:
ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBKovQsvC0IctIDNLTgdnfnb6Bz7N1ycBHnT3IaXRQElYiyfn6mbxUtuMZOzdDVdYUYbxuUfUMad87UX1a/Fo1Xo=
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICdGC0x1+9M0YkBjWEyyKqu8lalCZNffGs9BnGX/YPpx
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCzg5tgpCFCIE9fpri349+VG4sB38zSc7Nt/UZotwPndWQ0+hg1KzmGWGd5xkUNBFo7keS+pzy7Vr+2k6m3GgOu0ZYhY7b2X6HwSuGxOVY4vkp3fIrZvZcpNEM8YIdiM7JXqzQUfNaRnQI9AueaM52sR+rJHcKIegialepyuhzl8KXNEvLLcMR59DAr0WmRaBD2LWzVUGcBJRCNjRXsPiJfZ1uYxGrri2Oa7YxVTRd50bjKzRIKcBCvNYgF6mhTqq+wthRlLv0k07ixWS1VHW7WX3LC3CiNkqz/f68ZPb5m67KOG+rX1QKdyTJhQLwL7xGuTCclDxUWsowaFjAcwVQL4jN21iVlQZppcJllwEZUlqzLPMcZiuqeOJqZkBvn27iE2RgTfqpThS9yxnxAF5JyBm98vReMpYYxRdiHWciGS4LkPzabQm9ALq9nUemkg2rUQrKfE40Jc9t0CKZ3RK0nAtT0+XDeihxFdKQRnEUXcOJ9DaQbc/R+X3Yvn73s9E8=
Compute nodes have the following permanent public key files. You can add the to
your ~/.ssh/known_hosts file:
az4-a7900-1.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIC4dX/AR+gMgKx0lNBJ1dFBbo6DTQ6VUvF+bYBXSktRQ
az4-a7900-2.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHaZLU7JupgFlXShElzDXtW+TfDk7kcfXZwtGNe5HbWE
az4-a7900-3.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJ4TKggY/XHIioktxKy+Vb2exPKneo62uv7NegFO17GJ
az4-n4090-0.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJDLHIO73Oy0ta520/MmDksuIYUR70Ro1U59SSy6n8n+
az4-n4090-1.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIN8cIY6iM3gBMmBEKixT92mfNB+LnJWdCWAEumcFknPs
az4-n4090-2.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICRJzFAt672zAai8/W0hklrAgO7oGnwrr2NzcTOgzw0Y
az4-n4090-3.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIEqOsbPC/yK+ViC7EHhrWBAQeUpw3YM6/JpJ4aUVI2z4
az5-a890m-0.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHsQFDB38BKtH/DFSJtdEzwzUoaseRm3RotsyT4IiqSu
az5-a890m-1.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIKPHkhQD3wZ4HMVtcLbX9EKigFwyAAj7ZCjoKnsMBGmB
az5-a890m-2.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDltGdIWUA934JFd5kZBjkF+dhMT+TJmd1hh++IQBr4r
az5-a890m-3.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICtTRzPlk7TEdeq9wz06v1ZRuO7IBeGIjTZBHQNIKIht
iml-ia770-0.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDYjR2kDu6+she6xgZG/ESCAZqBRxkLSCy80WEz4qAaz
iml-ia770-1.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIChFOzBz+4jzbsVrTC74hK5xPDdAOy8SU9cCU33uoqk7
iml-ia770-2.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGFPQBRwJJbPH7+W4azyosk/YCN/AaZ4DP75VAcZaO0r
iml-ia770-3.dalek ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIB0q4hG+bXSHjUFKYHMzxUQwHYDEOI3/6vnhgxQt5FQL
Info
The node keys have been changed in October 2025, you can safely remove the
previous ones from you known_hosts file if you have connected to a node
before. Otherwise, if you encounter an error connecting to a node, please
check that the public key matches and contact the cluster administrator
otherwise.