[slurm-users] Create users

[Damien François]

Just to add my 2c to the discussion: at our site, we use a utility we wrote [1] that monitors our LDAP and triggers Ansible playbooks upon addition or modification in the list of users. We have playbooks to setup the different directories for the user in the many filesystems, along with the respective quotas, setup SSH keys, and register to Slurm. To register to Slurm, we use a Slurm user module for Ansible [2].

damien

[1] https://github.com/damienfrancois/slufl2
[2] https://github.com/dylex/ansible-hpc/blob/master/slurm.py



> On 13 Sep 2018, at 16:41, Paul Edmon <pedmon at cfa.harvard.edu> wrote:
> 
> So the Lua script I posted only does it for people who submit to the cluster.  To do it for all users it should just be a simple bash script to do that, I don't have one put together though.
> 
> -Paul Edmon-
> 
> On 09/13/2018 10:29 AM, Eric F. Alemany wrote:
>> Hi Paul
>> 
>> You said 
>> 
>> “Another way would be to make all your Linux users and then map that in to Slurm using sacctmgr.”
>> 
>> I am curious to know how you do that.
>> 
>> Thank you
>> 
>> Best
>> Eric 
>> 
>> ._____________________________________________________________________________________________________
>> 
>> Eric F.  Alemany
>> System Administrator for Research
>> 
>> Division of Radiation & Cancer  Biology
>> Department of Radiation Oncology
>> 
>> Stanford University School of Medicine
>> Stanford, California 94305
>> 
>> Tel:1-650-498-7969 <tel:1-650-498-7969>  No Texting
>> Fax:1-650-723-7382 <tel:1-650-723-7382>
>> 
>> On Sep 13, 2018, at 01:09, Loris Bennett <loris.bennett at fu-berlin.de <mailto:loris.bennett at fu-berlin.de>> wrote:
>> 
>>> Hi Paul,
>>> 
>>> I'd be interested in seeing your Lua submit script, if you're willing to
>>> share.
>>> 
>>> Until now I had thought that the most elegant way of setting up Slurm
>>> users would be via a PAM module analogous to pam_mkhomedir, the simplest
>>> option being to use pam_script.
>>> 
>>> However, given that we do have users who somehow never get round to
>>> submitting a job before their HPC access expires, setting up the Slurm
>>> account when the first job is submitted seems quite appealing.
>>> 
>>> Cheers,
>>> 
>>> Loris
>>> 
>>> Paul Edmon <pedmon at cfa.harvard.edu <mailto:pedmon at cfa.harvard.edu>> writes:
>>> 
>>>> So useradd is adding a Linux user, which sacctmgr creates a Slurm user.
>>>> 
>>>> What we do is that we run AD for our Linux user managment. We then in our job submit lua script look to see if the user has an account in slurm and if they don't we create it.
>>>> 
>>>> Another way would be to make all your Linux users and then map that in to Slurm using sacctmgr.
>>>> 
>>>> It really depends on if your Slurm users are a subset of your regular users or not.
>>>> 
>>>> -Paul Edmon-
>>>> 
>>>> On 9/12/2018 12:21 PM, Andre Torres wrote:
>>>> 
>>>> Hi all,
>>>> 
>>>> I’m new to slurm and I’m confused regarding user creation. I have an installation with 1 login node and 5 compute nodes. If I create a user across all the nodes with the same uid and gid I can execute jobs but
>>>> I can’t understand the difference between user creation with “useradd” command and the “sacctmgr” command 
>>>> 
>>>> sacctmgr create account name=test
>>>> 
>>>> sacctmgr create user jdoe account=test
>>>> 
>>>> Also, is there anyway of creating a user at login node and replicate to the compute nodes ? What is the best practice for user creation ?
>>>> 
>>>> Thanks in advance
>>>> 
>>>> 
>>> -- 
>>> Dr. Loris Bennett (Mr.)
>>> ZEDAT, Freie Universität Berlin         Email loris.bennett at fu-berlin.de <mailto:loris.bennett at fu-berlin.de>
>>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20180913/672d3a13/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3536 bytes
Desc: not available
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20180913/672d3a13/attachment.bin>