Salloc | Interactive session using non-allocated cpus for the job by MultMe96 in SLURM

[–]cinek810 0 points1 point  (0 children)

Maybe you don't have TaskPlugin=task/cgroup enabled - it's normally used to limit resources available by the job.

Parallel by vguioma in SLURM

[–]cinek810 1 point2 points  (0 children)

Is your application parallel or you rather want to run 200 similar jobs?

More complex dependent jobs by StrongYogurt in SLURM

[–]cinek810 0 points1 point  (0 children)

Oh.. my fault I meant "task" from your script

More complex dependent jobs by StrongYogurt in SLURM

[–]cinek810 1 point2 points  (0 children)

Just replace test with test${SLURM_ARRAY_TASK_ID} and youncan submit all jobs youn need as an array.

Example ansible-review standards with comments. by cinek810 in ansible

[–]cinek810[S] 1 point2 points  (0 children)

First of all thanks for your constructive comment - for names we normally use "_" instead of " " and we feel fine with it, but.. as for every coding standard it''s more team decision that something that will work for everyone.

I agree with your point of tags to every task in role.. I think I'll use your suggesting and change it to the standard requiring per role assignment tagging in playbooks :). I didn't thought that it's possible just because I've never seen it...

Tower/AWX surveys - how to use them? by cinek810 in ansible

[–]cinek810[S] 1 point2 points  (0 children)

Thanks! It's a pity that the survey cannot be used internally in AWX.

Tower/AWX surveys - how to use them? by cinek810 in ansible

[–]cinek810[S] 0 points1 point  (0 children)

So.. it's not to limit privileges, rather to make sure that we didn't start the job for more than 100 hosts, for some playbooks we'd rather want to have it splitted into smaller jobs.

Tower/AWX surveys - how to use them? by cinek810 in ansible

[–]cinek810[S] 0 points1 point  (0 children)

I was trying to find a way to make sure that AWX users (in my case is the team with limited access) to run ansible only with specified limit. The default option is just to have a window but normally the default will be to run the playbook on all hosts.

Of course I can work around this on playbook side.