cluster:214
Differences
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 | ||
|
cluster:214 [2022/08/03 09:13] hmeij07 [Amber22] |
cluster:214 [2023/08/17 13:52] hmeij07 [Upgrading] |
||
|---|---|---|---|
| Line 397: | Line 397: | ||
| ==== Upgrading ==== | ==== Upgrading ==== | ||
| - | Figure out an upgrade process before going production (don't forget any chroot images and rebuild images). | + | Figure out an upgrade process before going production. |
| + | |||
| + | * **Do you actually want to upgrade OpenHPC? | ||
| + | * v2.5 deploys ww4.x (maybe not want this, containers) | ||
| + | * chroot images and rebuild images | ||
| + | * slurm complications? | ||
| < | < | ||
| Line 406: | Line 411: | ||
| </ | </ | ||
| + | **Upgrade history** | ||
| + | * OS only, June 2022 | ||
| + | * OS only, August 2023 (440+ days up) | ||
| + | * | ||
| ==== example modules ==== | ==== example modules ==== | ||
| Line 531: | Line 540: | ||
| </ | </ | ||
| - | ** Example script run.centos for cpui or gpu run** (queues mwgpu, exx96) | + | ** Example script run.centos for cpus or gpu run** (queues mwgpu, exx96) |
| < | < | ||
| Line 641: | Line 650: | ||
| ==== Amber22 ==== | ==== Amber22 ==== | ||
| - | |||
| - | First establish a successful run with the **run.rocky** script for Amber20 (listed above). Then change the module in your script. | ||
| - | |||
| - | < | ||
| - | |||
| - | module load amber/22 | ||
| - | |||
| - | # if the module does not show up in the output of your console | ||
| - | |||
| - | module avail | ||
| - | |||
| - | # treat your module cache as out of date | ||
| - | |||
| - | module --ignore_cache avail | ||
| - | |||
| - | </ | ||
| Amber22 is somehow incompatible with CentOS/ | Amber22 is somehow incompatible with CentOS/ | ||
| Line 674: | Line 667: | ||
| </ | </ | ||
| - | First establish a success full run with the **run.centos** script for Amber20 (listed above). Then edit the script and apply these edits. We had to use a specific compatible '' | + | First establish a successful run with the **run.rocky** script for Amber20 (listed above). Then change the module in your script. (for queues amber128 [n78] and test [n100-n101] for gpus and mw128 and tinymem for cpus) |
| + | |||
| + | < | ||
| + | |||
| + | module load amber/22 | ||
| + | |||
| + | # if the module does not show up in the output of your console | ||
| + | |||
| + | module avail | ||
| + | |||
| + | # treat your module cache as out of date | ||
| + | |||
| + | module --ignore_cache avail | ||
| + | |||
| + | </ | ||
| + | |||
| + | First establish a success full run with the **run.centos** script for Amber20 (listed above, for cpus or gpus on queues mwgpu and exx96). | ||
| + | |||
| + | Then edit the script and apply these edits. We had to use a specific compatible '' | ||
| < | < | ||
cluster/214.txt · Last modified: 2023/08/18 12:19 by hmeij07
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
