Using Salt/Ansible/Chef/Puppet/Engine is another way to get it done. Define your users in states/playbooks/whatever and don't bother with painful LDAP or ancient NIS solutions.

--
Jeff White
HPC Systems Engineer
Information Technology Services - WSU

On 04/10/2017 09:39 AM, Alexey Safonov wrote:
Re: [slurm-dev] LDAP required?
If you don't want to share passwd and setup LDAP which is complex task you can setup NIS. It will take 30 minutes of your time

Alex

11 апр. 2017 г. 0:35 пользователь "Raymond Wan" <rwan.w...@gmail.com <mailto:rwan.w...@gmail.com>> написал:


    Dear all,

    I'm trying to set up a small cluster of computers (i.e., less than 5
    nodes).  I don't expect the number of nodes to ever get larger than
    this.

    For SLURM to work, I understand from web pages such as
    https://slurm.schedmd.com/accounting.html
    
<https://urldefense.proofpoint.com/v2/url?u=https-3A__slurm.schedmd.com_accounting.html&d=DwMFaQ&c=C3yme8gMkxg_ihJNXS06ZyWk4EJm8LdrrvxQb-Je7sw&r=DhM5WMgdrH-xWhI5BzkRTzoTvz8C-BRZ05t9kW9SXZk&m=pHFr5OO6Rs6OVpGK-ABDCawrftYPAsXU-3jcnPxli7s&s=pKOva3EaAqpu1SQdiMYOdDVs5YShjTHnK4NZN4TiA6k&e=>
    that UIDs need to be shared
    across nodes.  Based on this web page, it seems sharing /etc/passwd
    between nodes appears sufficient.  The word LDAP is mentioned at the
    end of the paragraph as an alternative.

    I guess what I would like to know is whether it is acceptable to
    completely avoid LDAP and use the approach mentioned there? The
    reason I'm asking is that I seem to be having a very nasty time
    setting up LDAP.  It doesn't seem as "easy" as I thought it would be
    [perhaps it was my fault for thinking it would be easy...].

    If I can set up a small cluster without LDAP, that would be great.
    But beyond this web page, I am wondering if there are suggestions for
    "best practices".  For example, in practice, do most administrators
    use LDAP?  If so and if it'll pay off in the end, then I can consider
    continuing with setting it up...

    Thanks a lot!

    Ray


Reply via email to