Besso¶
Besso is a small Alps cluster that provides development resources for porting software for selected customers. It is provided as is, without the same level of support as the main platform clusters.
Storage and file systems¶
Besso uses the HPCP filesystems and storage policies.
Getting started¶
Logging into Besso¶
To connect to Besso via SSH, first refer to the ssh guide.
~/.ssh/config
Add the following to your SSH configuration to enable you to directly connect to besso using ssh besso.
Software¶
uenv¶
Besso is a development and testing system, for which CSCS does not provide supported applications.
Instead, the prgenv-gnu programming environment is provided for the both the a100 and mi200 node types.
Containers¶
Besso supports container workloads using the Container Engine.
To build images, see the guide to building container images on Alps.
Cray Modules¶
Warning
The Cray Programming Environment (CPE), loaded using module load cray, is no longer supported by CSCS.
CSCS will continue to support and update uenv and the Container Engine, and users are encouraged to update their workflows to use these methods at the first opportunity.
The CPE is still installed on Besso, however it will receive no support or updates, and will be replaced with a container in a future update.
Running jobs on Besso¶
Slurm¶
Besso uses Slurm as the workload manager, which is used to launch and monitor workloads on compute nodes.
There are multiple Slurm partitions on the system:
- the
a100partition contains NVIDIA A100 GPU nodes - the
mi200partition contains AMD Mi250x GPU nodes - the
normalpartition contains all of the nodes in the system.
| name | max nodes per job | time limit |
|---|---|---|
a100 |
2 | 24 hours |
mi200 |
2 | 24 hours |
normal |
4 | 24 hours |
See the Slurm documentation for instructions on how to run jobs.
FirecREST¶
Besso can also be accessed using FirecREST at the https://api.cscs.ch/mwa/firecrest/v2 API endpoint.
Maintenance and status¶
There is no regular scheduled maintenance for this system.