Repository navigation
Description
Add Slurm accounting to the Slurm appliance
Description
Today the Slurm appliance supports a self-configuring controller/worker cluster, but completed job history and usage statistics are not persisted through SlurmDB.
This feature removes that limitation, by adding a SlurmDBD-based job accounting to the existing OneSlurm Service appliance.
Service OneSlurm should have three roles: one Controller, scalable Workers,
and one Accounting VM running MariaDB and slurmdbd. Controller connects to
SlurmDBD over the private Service network to persist job and usage records.
Accounting also generates and retains the shared MUNGE key and hosts the local
LDAP server when appliance-managed LDAP is selected.
Accounting is mandatory for every Slurm Cluster instantiation.
Accounting owns database initialization, key distribution, and effective identity
configuration, with its own VM resources, disk lifecycle, and backup policy.
Controller and Workers are identity/MUNGE clients. This replaces the
controller-local topology within the same feature request.
Use case
Users running shared HPC clusters need standard Slurm accounting workflows:
- inspect completed job history with
sacct; - manage accounting entities with
sacctmgr; - generate usage reports with
sreport; - retain job and usage records after jobs leave the active scheduler state.
This is needed for operational visibility, usage reporting, and basic
chargeback-style workflows in Slurm clusters.
Scope
- Request type: Modification to existing appliance and add a new Slurm Accounting appliance
- Affected appliance(s): Service OneSlurm, Service Slurm Controller, Service Slurm Worker, new Service Slurm Accounting
- Base OS distro: Ubuntu 26.04 LTS
Technical Details
ONEAPP_*context parameters:ONEAPP_SLURM_ACCOUNTING_DB_NAME(slurm_acct_dbby default)ONEAPP_SLURM_ACCOUNTING_DB_USER(slurmby default)ONEAPP_SLURM_ACCOUNTING_DB_PASSWORD(generated when empty)
- Architecture support: x86_64 and aarch64
- Dependencies on other appliances or services: a new appliance role with the database and SlurmDBD.
- Custom build requirements: install MariaDB,
slurmdbd, and the distro Slurm
MySQL plugin package.
Interface Changes
Add x86_64 and aarch64 Service Slurm Accounting Marketplace entries and reference
them from the three-role service templates. Move existing LDAP server/
identity input mappings from Controller to Accounting without changing names or
defaults.
Update the wiki with mandatory topology, bootstrap/readiness, role-specific
checks, local/external LDAP, initial deployment versus restart behavior, and
Accounting VM persistence/backup limitations for database, directory and key. No
purge/retention inputs are added.
Update the OneSlurm wiki to describe:
- accounting defaults;
- how to disable accounting;
- validation commands for
mariadb,slurmdbd,sacctmgr,sacct, and
sreport; - manual SlurmDBD retention tuning for admins who need purge/archive policy.
Progress Status
- Code committed
- Testing - QA
- Documentation (Release notes - resolved issues, compatibility, known issues)
Activity
F OpenNebula#396: Install Slurm from the oneslurm PPA
Merge pull request #2 from pablodelarco/fix/396-slurm-ppa
F OpenNebula#396: Store GPU usage in Slurm accounting
Merge pull request #3 from pablodelarco/fix/396-slurm-gpu-accounting