...
Upgrade Date | Old Partition | New Partition | Lmod Architecture | Comments | ||
|---|---|---|---|---|---|---|
6 January Completed | – | | | – | ||
6 January Completed | – | | | – | ||
6 January Completed | – | | | – | ||
6 January Completed | – | | | – | ||
6 January Completed | – | | | – | ||
6 January Completed | – | | | – | ||
21 April Completed | | - | | - | ||
10 March Completed | | - | | - | ||
10 March Completed | | | | - | ||
17 March | | | | - | ||
20 March 12 May | | | | - 20 | ||
March 12 May | | | | - 20 | ||
March 12 May | | | | - | ||
24 March | | | | absorbed into Hawkcpu | ||
24 March | | |||||
14 May | | | | | ||
19 May | | | | absorbed into Haswell | 24 March | |
21 May | | | | - | 27 March | |
21 May | | | | absorbed into Hawkcpu | ||
21 May | | | | - 31 | ||
March 21 May | | | | - 3 | ||
April 21 May | | | | - 7 | ||
April 21 May | | | | |
When the upgrade is complete, the vast majority of the older hardware on the cluster will be centralized in a single haswell partition with a corresponding Lmod architecture module called haswell25v1. Users will be able to target specific hardware within this partition by using the typical SLURM flags to select the number of nodes, cores, and amount of memory, if necessary.
...