[slurm-users] restrict application to a given partition
John Hearns
hearnsj at googlemail.com
Mon Jan 15 06:31:22 MST 2018
Juan, me kne-jerk reaction is to say 'containerisation' here.
However I guess that means that Slurm would have to be able to inspect the
contents of a container, and I do not think that is possible.
I may be very wrong here. Anyone?
However have a look at thre Xalt stuff from TACC
https://www.tacc.utexas.edu/research-development/tacc-projects/xalt
https://github.com/Fahey-McLay/xalt
Xalt is intended to instrument your cluster and collect information on what
software is being run and exactly what libraries are being used.
I do not think it has any options for "Nope! You may not run this
executable on this partition"
However it might be worth contacting the authors and discussing this.
On 15 January 2018 at 14:20, Juan A. Cordero Varelaq <
bioinformatica-ibis at us.es> wrote:
> But what if the user knows the path to such application (let's say python
> command) and executes it on the partition he/she should not be allowed to?
> Is it possible through lua scripts to set constrains on software usage such
> as a limited shell, for instance?
>
> In fact, what I'd like to implement is something like a limited shell, on
> a particular node for a particular partition and a particular program.
>
>
>
> On 12/01/18 17:39, Paul Edmon wrote:
>
>> You could do this using a job_submit.lua script that inspects for that
>> application and routes them properly.
>>
>> -Paul Edmon-
>>
>>
>> On 01/12/2018 11:31 AM, Juan A. Cordero Varelaq wrote:
>>
>>> Dear Community,
>>>
>>> I have a node (20 Cores) on my HPC with two different partitions: big
>>> (16 cores) and small (4 cores). I have installed software X on this node,
>>> but I want only one partition to have rights to run it.
>>> Is it then possible to restrict the execution of an specific application
>>> to a given partition on a given node?
>>>
>>> Thanks
>>>
>>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20180115/aeb6ed8c/attachment-0001.html>
More information about the slurm-users
mailing list