[slurm-dev] Slurm release schedule update

Several Slurm enhancements planned for the next major release will not be available for a December release. The major organizations performing SLurm development have decided that the best course of action is to delay the next major release until March 2014. This will provide sufficient ti

[slurm-dev] Question concerning variables/environment

I noticed during some testing there are a number of SLURM_* variables that are not passed from the prolog's environment to the task-prolog's environment and further into the job's environment. eg. SLURM_PARTITION, SLURM_JOB_GID etc Is there a way to force these variables to be passed along

[slurm-dev] Re: new version of mpirun-mic script

I have absolutely no objections to this. My initial version was fairly quick and dirty to get things working on our cluster. I've been planning to revise it but have not had the chance. Thanks for your efforts. :) Best regards, Olli-Pekka -- Olli-Pekka Lehto Development Manager Computing Plat

[slurm-dev] Re: Load balancing

See SelectTypeParameters=CR_LLN in "man slurm.conf" Quoting HUMMEL Michel : I read here : http://thread.gmane.org/gmane.comp.distributed.slurm.devel/4380/focus=4381 Load balancing between nodes will be possible in the future Slurm v13.12 in December. I am testing the 13.13.pre4, is it po

[slurm-dev] Load balancing

I read here : http://thread.gmane.org/gmane.comp.distributed.slurm.devel/4380/focus=4381 Load balancing between nodes will be possible in the future Slurm v13.12 in December. I am testing the 13.13.pre4, is it possible to test load balancing with this version, otherwise how can I test it pleas

[slurm-dev] Re: Secure access to SlurmDB

Yes those 2 lines are not needed in the slurm.conf when using the slurmdbd. Ulf Markwardt wrote: >On 15.11.2013 12:52, Bjørn-Helge Mevik wrote: >> >> If you switch to use slurmdbd, the password goes into slurmdbd.conf, >> which only exists on the head node, and only needs to be readable by >root.

[slurm-dev] Re: Secure access to SlurmDB

On 15.11.2013 12:52, Bjørn-Helge Mevik wrote: If you switch to use slurmdbd, the password goes into slurmdbd.conf, which only exists on the head node, and only needs to be readable by root. we already have this in slurm.conf: AccountingStorageType=accounting_storage/slurmdbd AccountingStorageU

[slurm-dev] new version of mpirun-mic script

Hi all! We have a small test cluster of 44 compute nodes and we have 4 cnodes with 2 MICs per node. So, I would like to share with you my latest version of mpirun-mic script. It is based on the script that was created by Mr. Olli-Pekka Lehto. The users are happy with that script and if you would

[slurm-dev] Re: Secure access to SlurmDB

If you switch to use slurmdbd, the password goes into slurmdbd.conf, which only exists on the head node, and only needs to be readable by root. -- Bjørn-Helge Mevik, dr. scient, Department for Research Computing, University of Oslo

[slurm-dev] Secure access to SlurmDB

Dear list, I want to to use a secure password to access the Slurm database. This password has to be put in slurm.conf (AccountingStoragePass) and slurm.conf has to be consistent thoughout the cluster (see description in slurm.conf.html). Can we set the file access rights so that only the use

[slurm-dev] Re: Slurm configuration problem --Age factor not working @ all

Dear Loris, This is what I exactly want. My job waited for 1 day but its Age remains 0 . I want some nonzero value in age column. I suspect that multifactor for age factor is not working. but sprio -w shows that its set properly.Please help me with this. -- Regards, Yogendra _

[slurm-dev] Re: Slurm configuration problem --Age factor not working @ all

Dear Yogendra, writes: > [root@hpca ~]# scontrol show config  | grep PriorityWeightAge > > PriorityWeightAge   = 1000 > > [root@hpca ~]# sprio -w > >   JOBID   PRIORITY    AGE    JOBSIZE > > Weights  1000   1000 > > [root@hpca ~]# sprio -l > >   JOBID USER   PRIO