Those pieces of information are available from squeue / sacct as long as you’re
happy to have a wrapper which does the aggregation part for you. The commands
I parse for our stat summaries are:
scontrol show nodes
squeue -r -O jobid,username,minmemory,numcpus,nodelist
sacct -a -S [one_month_a
I need to account for jobs composed of multiple jobs launched on multiple
federated (and non-federated) clusters, which therefore have different job IDs.
What are the best practices to prevent users from bypassing this tracking?
NICE SRL, viale Monte Grappa 3/5, 20124 Milano, Italia, Registro
For those that are interested, I was able to resolve this by doing the
following:
- Remove the "get_user_environment" attribute from the "jobs" attribute.
- Add an additional attribute to the "environment" attribute titled
"SLURM_GET_USER_ENV" and setting that equal to 1.
Example before change:
This thread when a bunch of different directions. However I ran with
Jeffrey's suggestion and wrote up a profile.d script along with other
supporting scripts to pull the data. The setup I put together is here
for the community to use as they see fit:
https://github.com/fasrc/puppet-slurm_stats
We are pleased to announce the availability of Slurm versions 24.05.3
and 23.11.10.
Version 24.05.3 fixes a potential database problem when deleting a qos.
This bug only existed in 24.05.
Both versions have fixes for jobs potentially being stuck when using
cloud nodes when some nodes are pow
On 15/8/24 10:55 am, jpuerto--- via slurm-users wrote:
Any ideas on whether there's a way to mirror this functionality in v0.0.40?
Sorry for not seeing this sooner, I don't I'm afraid!
All the best,
Chris
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an ema
On 22/8/24 11:18 am, jpuerto--- via slurm-users wrote:
Do you have a link to that code? Haven't had any luck finding that repo
It's here (on the 23.11 branch):
https://github.com/SchedMD/slurm/tree/slurm-23.11/src/slurmrestd/plugins/openapi/dbv0.0.38
--
slurm-users mailing list -- slurm-user
On 27/8/24 10:26 am, jpuerto--- via slurm-users wrote:
Is anyone in contact with the development team?
Folks with a support contract can submit bugs at
https://support.schedmd.com/
I feel that this is pretty basic functionality that was removed from the REST API without
warning. Consideri
On 26/8/24 8:40 am, Di Bernardini, Fabio via slurm-users wrote:
Hi everyone, for accounting reasons, I need to create only one job
across two or more federated clusters with two or more srun steps.
The limitations for heterogenous jobs say:
https://slurm.schedmd.com/heterogeneous_jobs.html#li