Merge branch 'merge-preview-in-main' into 'main'

Automated merge from preview to main

See merge request !905

doc.zih.tu-dresden.de/docs/access/key_fingerprints.md

@@ -52,53 +52,17 @@ The following hostnames can be used to access ZIH systems:
 All of these login nodes share common keys. When connecting, please make sure that the fingerprint
 shown matches one of the table.
 
-#### login1.barnard.hpc.tu-dresden.de
+#### login[1-4].barnard.hpc.tu-dresden.de
 
 | Key type | Fingerprint                                         |
 |:---------|:----------------------------------------------------|
-| RSA      | SHA256:c3Gs+WH1STvogyR9jTAPH8vhc5Ue75XsYlyCFbLDhJU  |
-| RSA      | MD5:73:dc:bc:79:dc:1b:bf:e8:cb:1b:f5:1f:5e:6d:64:19 |
-| ECDSA    | SHA256:8Coljw7yoVH6HA8u+K3makRK9HfOSfe+BG8W/CUEPp0  |
-| ECDSA    | MD5:63:9a:67:68:37:85:31:77:a4:e6:0b:da:8c:d9:2f:96 |
-| ED25519  | SHA256:Ws/vbrp5e/Ay+fcVzhsL0jupjGkDdn1cJ+SX6gQB6Bs  |
-| ED25519  | MD5:7f:5c:e6:2b:6f:94:24:9b:0f:2f:1d:bc:40:6b:59:c7 |
-{: summary="List of valid fingerprints for Barnard login1 node"}
-
-#### login2.barnard.hpc.tu-dresden.de
-
-| Key type | Fingerprint                                         |
-|:---------|:----------------------------------------------------|
-| RSA      | SHA256:ZYQvEUc493+BETiJZ/jwqp/rHCM+IW1Trf6FdcSrqX4  |
-| RSA      | MD5:f8:1f:b6:f2:02:81:b9:ee:ce:99:71:ee:35:ad:32:fc |
-| ECDSA    | SHA256:01KP44mEMzswqdrkgA7ViO62Atdk8pAib/pmLBgetyk  |
-| ECDSA    | MD5:d9:33:27:26:00:c9:81:cf:bb:45:43:dc:05:e8:1f:43 |
-| ED25519  | SHA256:BewwkydtP2riZPShvNzAOWm+dQtdOq535j7Vow1HbRQ  |
-| ED25519  | MD5:18:8b:cd:1e:2e:9a:6c:8c:ee:b5:c9:3e:68:a3:4a:3f |
-{: summary="List of valid fingerprints for Barnard login2 node"}
-
-#### login3.barnard.hpc.tu-dresden.de
-
-| Key type | Fingerprint                                         |
-|:---------|:----------------------------------------------------|
-| RSA      | SHA256:+VSqQp+6LZrZXOHPuDhxd2ti9mam/gDLSbn5kH0S2UI  |
-| RSA      | MD5:19:16:ce:34:0e:2c:5f:37:42:06:f7:55:7d:19:cf:1a |
-| ECDSA    | SHA256:qZbC5BDKrTvE3J6qgGJLQwxtjfYy6pmrI7teEjFnHiE  |
-| ECDSA    | MD5:b1:19:a6:bf:9e:95:ce:ee:fd:ab:b3:ee:5e:d7:e0:a7 |
-| ED25519  | SHA256:ATNHOAZNjWHAXMwTWgxMvB9DIZ5bZurneN4sBKGSsz8  |
-| ED25519  | MD5:ee:cb:cc:ff:be:15:f2:e8:8e:ac:ef:da:a1:f9:48:33 |
-{: summary="List of valid fingerprints for Barnard login3 node"}
-
-#### login4.barnard.hpc.tu-dresden.de
-
-| Key type | Fingerprint                                         |
-|:---------|:----------------------------------------------------|
-| RSA      | SHA256:IYpo+qHKOIs4TEftlDp63QlQr85xlcgbapfMsbCeZDE  |
-| RSA      | MD5:a7:3d:c3:be:53:62:7f:fc:5a:b5:6b:ba:8c:83:6e:4c |
-| ECDSA    | SHA256:nnUzS1Zu9+yaXf8ayDIwmfXabPtyvdr5c3Hvp+/zXhs  |
-| ECDSA    | MD5:69:f9:54:60:24:79:22:cb:7f:ba:d0:90:f5:0f:4a:5d |
-| ED25519  | SHA256:1QXw+IC51iT55LiE/7JJEXL7Jm1GZjk+/7OjaYfWXUY  |
-| ED25519  | MD5:17:8c:ea:26:dc:f0:43:61:a8:4d:06:e3:8e:f7:27:29 |
-{: summary="List of valid fingerprints for Barnard login4 node"}
+| RSA      | SHA256:lVQOvnci07jkxmFnX58pQf3cD7lz1mf4K4b9jZrAlVU  |
+| RSA      | MD5:5b:39:ae:03:3a:60:15:21:4b:e8:ba:72:52:b8:a1:ad |
+| ECDSA    | SHA256:Xan2MYazewT0V5agNazaQfWzLKBD3P48zRwR6reoXhI  |
+| ECDSA    | MD5:02:fd:ab:c8:39:f9:94:cc:3f:e0:7e:78:5f:76:b8:4c |
+| ED25519  | SHA256:Gn4n5IX9eEvkpOGrtZzs9T9yAfJUB200bgRchchiKAQ  |
+| ED25519  | MD5:e8:10:96:67:e8:4c:fd:87:f0:c6:4e:e8:1f:53:a9:be |
+{: summary="List of valid fingerprints for Barnard login[1-4] node"}
 
 ??? example "Connecting with SSH"
 

doc.zih.tu-dresden.de/docs/jobs_and_resources/barnard_test.md

@@ -18,7 +18,7 @@ All users and projects from Taurus now can work on Barnard.
 They can use `login[2-4].barnard.hpc.tu-dresden.de` to access the system
 from campus (or VPN). [Fingerprints](/access/key_fingerprints/#barnard)
 
-All users have **new empty HOME** file systems, this means you have first have to...
+All users have **new empty HOME** file systems, this means you have first to...
 
 ??? "... install your public ssh key on the system"
 

doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md

@@ -132,6 +132,7 @@ resource requirements and control communication.
     | `-a, --array=<arg>`        | Submit an array job ([examples](slurm_examples.md#array-jobs)) |
     | `-w <node1>,<node2>,...`   | Restrict job to run on specific nodes only |
     | `-x <node1>,<node2>,...`   | Exclude specific nodes from job |
+    | `--switches=<count>[@max-time]` | Optimum switches and max time to wait for optimum |
     | `--test-only`              | Retrieve estimated start time of a job considering the job queue; does not actually submit the job nor run the application |
 
 !!! note "Output and Error Files"
@@ -152,6 +153,16 @@ If you want to place your job onto specific nodes, there are two options for doi
 `-p, --partition=<name>` to specify a host group aka. [partition](partitions_and_limits.md) that fits
 your needs. Or, use `-w, --nodelist=<host1,host2,..>` with a list of hosts that will work for you.
 
+### Number of Switches
+
+You can fine tune your job by specifying the number of switches desired for the job allocation and
+optionally the maximum time to wait for that number of switches. The corresponding option to
+`sbatch` is `--switches=<count>[@max-time]`. The job remains pending until it either finds an
+allocation with desired switch count or the time limit expires. Acceptable time formats include
+"minutes", "minutes:seconds", "hours:minutes:seconds", "days-hours", "days-hours:minutes" and
+"days-hours:minutes:seconds". For a detailed explanation, please refer to the
+[sbatch online documentation](https://slurm.schedmd.com/sbatch.html#OPT_switches).
+
 ## Interactive Jobs
 
 Interactive activities like editing, compiling, preparing experiments etc. are normally limited to