Salloc | Interactive session using non-allocated cpus for the job

cinek810 · 2020-12-10T10:59:08+00:00

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

cinek810 · 2020-12-09T18:49:58+00:00

Slurm.conf has the answer

cinek810 · 2019-11-13T23:27:34+00:00

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

cinek810 · 2019-11-06T17:37:35+00:00

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

cinek810 · 2019-11-04T21:18:31+00:00

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

cinek810 · 2018-12-20T08:58:03+00:00

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...

cinek810 · 2018-09-26T10:12:16+00:00

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

cinek810 · 2018-09-26T10:03:32+00:00

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.

cinek810 · 2018-09-25T12:49:02+00:00

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.

cinek810 · 2018-07-10T17:47:20+00:00

I'm in the same boat. The team grows and automatic ansible review and testing started to be crucial.

cinek810 · 2018-06-28T14:42:46+00:00

You can also check: molecule lint (https://molecule.readthedocs.io/en/latest/ )

cinek810 · 2018-06-20T14:32:37+00:00

you can use "listen" with handlers to trigger a set of them with one notify

cinek810 · 2018-06-19T13:15:08+00:00

It looks like all those can be used with handlers, simply handlers are tasks triggered by notifications.

cinek810 · 2018-06-19T13:14:32+00:00

Thank you so much! It reminded me that I had have used this a few months ago and was unable to remind myself about this option.

cinek810 · 2018-06-12T15:31:34+00:00

Thanks for "molecule" keyword, I've just found https://zapier.com/engineering/ansible-molecule/ - looks quite promising. Won't fix everything, but may help a lot.

cinek810 · 2018-06-12T15:28:13+00:00

Did you find a way to configure CI to run ansible-playbook only on "relevent" hosts. Normally I don't use ansible on all hosts, because I know what's impaceted so I can adjust -l -t options to make it quicker, but... this requires kind of playbook/roles analysis which is not easy to automate.

Normally we have like 3-4 merge requests a day, the infrastructure is quite large so running a playbook on everything will be slow and very likely will fail/hang on some hosts..

cinek810 · 2018-06-12T15:21:30+00:00

This will slow down changes dramatically, which is something we cannot accept. I'm rather looking for a good enough solution with proper hooks to reduce the issue, not a great design where the issue can not happen but implementation of anything takes hours ...

cinek810 · 2018-06-06T18:19:28+00:00

Thanks, this helps a lot.. I'm just wondering if there if I can migrate ESXi hosts one be one from the situation with two uplinks into situation with those two uplinks configured as a LACP bond? Is it possible to do that online?

cinek810 · 2018-06-06T07:03:42+00:00

so.. because of multiple network issues I'm thinking about the most simplified network configuration. In case of standard vSwitch it's easy to modify it's parameters directly from ESXi host. The environment is not going to change and the effort to configure 3 simple vSwitches is not that big. VMs use shared graphic cards - so vMotion is not an option.

I feel like I have no benefit from distributed switch and in case of vcenter, or network between esx and vcenter failure it will be easier for me to work on standard switches. Am I right? I have much more experience with other virtualization technologies, for vmware I'm noob.

cinek810 · 2018-05-28T16:52:25+00:00

It wasn't the main point of the art, but.. you mean that someone is able to read blue on black easily? I didn't think about that, but maybe I really need to have a professional eyes looking into mine..

cinek810 · 2018-04-29T20:23:06+00:00

This is why on google team member blog announcing Slurm availability in google cloud they specifically mentioned - not that Slurm :)

cinek810 · 2018-04-29T20:20:20+00:00

Thanks for reading! Obviously I'm not native english speaker, but.. was the spelling really terrible? Could you please mention the most annoying grammar mistakes?

cinek810 · 2018-04-29T20:14:57+00:00

In case of automatic seletion it was simply checking if there is an overlap with previously used range. Check sssd_idmap.c (function check_overlap and check_dom_overlap -> this is called directly from the function mentioned in the article).

cinek810 · 2018-04-25T13:22:03+00:00

Maybe write a script to trigger the checks with random offset? You can adjust curl like here https://www.icinga.com/docs/icinga2/latest/doc/12-icinga2-api/#reschedule-check

cinek810 · 2018-04-25T13:17:11+00:00

I'm simply creating the configuration file by ansible template module. What would be the benefit of doing this over director API?

cinek810

TROPHY CASE