ClusterCockpit/cc-examples
1
0
Fork 0
mirror of https://github.com/ClusterCockpit/cc-examples.git synced 2024-12-26 05:29:06 +01:00
Code Issues Packages Projects Releases Wiki Activity
0d4e698846
cc-examples/fau-systems
History
Jan Eitzinger 0d4e698846 Update README.md
2023-06-13 08:45:44 +02:00
..
cc-backend FAU config 2023-06-13 07:26:59 +02:00
cc-metric-collector FAU config 2023-06-13 07:26:59 +02:00
cc-metric-store FAU config 2023-06-13 07:26:59 +02:00
job-archive FAU config 2023-06-13 07:26:59 +02:00
README.md Update README.md 2023-06-13 08:45:44 +02:00

README.md

ClusterCockpit at NHR@FAU

NHR@FAU provides a production instance of ClusterCockpit for support personel and users. Authentication is via an LDAP directory as well as via our HPC Portal (homegrown account management platform) using JWT tokens.

You can find an overview about all clusters here.

Some systems run with exclusive nodes, others have node sharing enabled. There are CPU systems (Fritz, Meggie, Woody, TinyuFat) as well as GPU enabled clusters (Alex, TinyGPUs).

NHR@FAU uses the following stack:

  • cc-metric-collector as node agent
  • cc-metric-store as temporal metric timeseries cache. We use one instance for all clusters.
  • cc-backend
  • A homegrown python script running on the management nodes for providing job meta data from Slurm
  • Builtin sqlite database for job meta and user data (currently 11GB)
  • Job Archive without retention using compressed data.json files (around 700GB)

We also push the metric data to an InfluxDB instance for debugging purposes.

The backend and metric store run on the same dedicated Dell server running Ubuntu Linux:

  • Two Intel Xeon(R) Platinum 8352Y with 32 cores each
  • 512 GB Main memory capacity
  • A NVMe Raid with two 7TB disks

This configuration is probably complete overkill, but we wanted to be on the safe side.