[slurm-dev] User management

[Simpson Lachlan]

Hola,

Out of interest, what do people recommend wrt user management on the cluster?

If user and groups need to match across all machines, it would surely be easiest to manage through something like FreeIPA?

Cheers
L.
This email (including any attachments or links) may contain
confidential and/or legally privileged information and is
intended only to be read or used by the addressee. If you
are not the intended addressee, any use, distribution,
disclosure or copying of this email is strictly
prohibited.
Confidentiality and legal privilege attached to this email
(including any attachments) are not waived or lost by
reason of its mistaken delivery to you.
If you have received this email in error, please delete it
and notify us immediately by telephone or email. Peter
MacCallum Cancer Centre provides no guarantee that this
transmission is free of virus or that it has not been
intercepted or altered and will not be liable for any delay
in its receipt.

[Novosielski, Ryan]

We use LDAP. 

____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS      |---------------------*O*---------------------
||_// Biomedical | Ryan Novosielski - Senior Technologist
|| \\ and Health | novo...@rutgers.edu- 973/972.0922 (2x0922)
||  \\  Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark
    `'

[Loris Bennett]

"Novosielski, Ryan" <novo...@ca.rutgers.edu> writes:

> We use LDAP.

One component of FreeIPA seems to be an LDAP server has the snappy name
"389 Directory Server", which I hadn't been aware of but will probably
do the job. We use OpenLDAP.

Cheers,

Loris

--
Dr. Loris Bennett (Mr.)
ZEDAT, Freie Universität Berlin Email loris....@fu-berlin.de

[Trey Dockendorf]

We use 389 Directory Server for our LDAP and SSSD for clients, works well.

- Trey

=============================

Trey Dockendorf 

Systems Analyst I 

Texas A&M University 

Academy for Advanced Telecommunications and Learning Technologies 

Phone: (979)458-2396 

Email: trey...@tamu.edu 

Jabber: trey...@tamu.edu

[Janne Blomqvist]

On 2016-01-13 23:54, Trey Dockendorf wrote:
> We use 389 Directory Server for our LDAP and SSSD for clients, works well.
>

We also use sssd on the clients, but instead of running or own LDAP(+kerberos) infrastructure, we use the university Active Directory.

--
Janne Blomqvist, D.Sc. (Tech.), Scientific Computing Specialist
Aalto University School of Science, PHYS & NBE
+358503841576 || janne.b...@aalto.fi

[Loris Bennett]

Janne Blomqvist <janne.b...@aalto.fi> writes:

> On 2016-01-13 23:54, Trey Dockendorf wrote:
>> We use 389 Directory Server for our LDAP and SSSD for clients, works
>> well.
>>
> We also use sssd on the clients, but instead of running or own
> LDAP(+kerberos) infrastructure, we use the university Active
> Directory.

We actually do something like this in that we manage relationships
between HPC users and research groups using Grouper
(http://www.internet2.edu/products-services/trust-identity-middleware/grouper/).
This information is used to create an HPC LDAP DIT on the central
university LDAP server. We then sync this DIT with a DIT on local LDAP
servers running on the admin nodes of our cluster.

Cheers,

Loris