On Wednesday, 7 November 2018 3:46:01 PM AEDT Brian Andrus wrote:
> Ah. I was getting ahead of myself. I used 'limits' and I have no limits
> configured, only associations. Changed it to just associations and all is
> good.
Excellent! Well spotted..
--
Chris Samuel : http://www.csamuel.org/
Ah. I was getting ahead of myself. I used 'limits' and I have no limits
configured, only associations.
Changed it to just associations and all is good.
On Tue, Nov 6, 2018 at 8:34 PM Brian Andrus wrote:
> Hmm. ok, so using unmatched accounts makes a fail:
> (on cluster1)
> $ srun -n16 -A Prod--
Hmm. ok, so using unmatched accounts makes a fail:
(on cluster1)
$ srun -n16 -A Prod--pty bash
*srun: error: Unable to allocate resources: Invalid account or
account/partition combination specified*
But using a valid account also fails:
$ srun -n16 -A projectA --pty bash
*srun: error: Unable to a
On 7/11/18 2:44 pm, Brian Andrus wrote:
Ah just scontrol reconfigure doesn't actually make it take effect.
Restarting slurmctld did it.
Phew! Glad to hear that's sorted out.. :-)
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
Ah just scontrol reconfigure doesn't actually make it take effect.
Restarting slurmctld did it.
On Tue, Nov 6, 2018 at 7:07 PM Christopher Samuel wrote:
> On 7/11/18 1:57 pm, Brian Andrus wrote:
>
> > Ah. I thought I had set that.
> > So I did and now it is:
> > AccountingStorageEnforce = associ
On 7/11/18 1:57 pm, Brian Andrus wrote:
Ah. I thought I had set that.
So I did and now it is:
AccountingStorageEnforce = associations,limits
But I am still able to request and get resources on cluster3 using
projectA as my account..
Heck, I just tried using a fake account (account=asdas) and
Ah. I thought I had set that.
So I did and now it is:
AccountingStorageEnforce = associations,limits
But I am still able to request and get resources on cluster3 using projectA
as my account..
Heck, I just tried using a fake account (account=asdas) and it worked...
"That ain't right..." - Guy Fle
On 7/11/18 7:35 am, Brian Andrus wrote:
I am able to submit using account=projectB on cluster3. ???
Since 'projectB' is a child of account ' DevOps', which is only
associated with cluster1 and cluster2, shouldn't I be denied the ability
to run using that accout on cluster3?
What does this sa
All,
Ok, I set up a few clusters in slurmdb. They are not federated.
I set up some accounts too. One primary for each cluster, plus a few child
accounts (project codes)
Something like:
sacctmgr add account DevOps Cluster=cluster1,cluster2
sacctmgr -add account projectA Parent=DevOps
sacctmgr -add
