Difference between revisions of "Managing ETH groups"

From ScientificComputing
Jump to: navigation, search
(Managing groups)
(Updates to pointers for ISGs.)
Line 7: Line 7:
  
 
Keep the following points in mind:
 
Keep the following points in mind:
<!--;LDAPS and AD groups
+
;Type of group
: For consistency it is recommended to export it to AD (Active Directory), too.
+
:The NETHZ group needs to be exported to '''LDAPS'''. For consistency it is recommended to export it to AD (Active Directory), too.
;Syncing changes
+
;Sync the changes
:Don't forget to click on the [[Media:Aktualisieren-link.png|''aktualisieren'']] link after making changes.
+
:You '''need''' to click on the [[Media:Aktualisieren-link.png|''aktualisieren'']] link for the changes to take effect!
;Changing group names
+
;Do not change the group name
:Avoid changing the name of any NETHZ group.
+
:Avoid changing the name of any NETHZ group or contact us if you plan to do so.
;LDAPS hierarchy
+
;Use only the ETH-wide LDAPS subtree
:An ISG-defined group will be in the<br><tt>ou=custom,ou=groups,ou=nethz,ou=id,ou=auth,o=ethz,c=ch</tt><br>subtree of LDAPS.-->
+
:An ETH-wide group defined by any ISG will be in the<br><tt>ou=custom,ou=groups,ou=nethz,ou=id,ou=auth,o=ethz,c=ch</tt><br>subtree of LDAPS. Groups specific to a department '''can not''' be used.
{| class="wikitable"
+
<!--{| class="wikitable"
 
|LDAPS and AD groups || For consistency it is recommended to export it to AD (Active Directory), too.
 
|LDAPS and AD groups || For consistency it is recommended to export it to AD (Active Directory), too.
 
|-
 
|-
Line 23: Line 23:
 
|-
 
|-
 
|LDAPS hierarchy || An ISG-defined group will be in the<br><tt>ou=custom,ou=groups,ou=nethz,ou=id,ou=auth,o=ethz,c=ch</tt><br>subtree of LDAPS.
 
|LDAPS hierarchy || An ISG-defined group will be in the<br><tt>ou=custom,ou=groups,ou=nethz,ou=id,ou=auth,o=ethz,c=ch</tt><br>subtree of LDAPS.
|}
+
|}-->
  
 
We can only use groups from the
 
We can only use groups from the

Revision as of 14:54, 28 November 2016

Introduction

Using NETHZ groups for user management is the recommended practice on our HPC clusters. A NETHZ group exported to LDAPS can be used to manage file permissions as well as user membership in a shareholder group. A common scenario is a group DEPT-ISG-GROUP that includes all members in the group's Leitzahl as well as semester students and visiting guests.

Managing NETHZ groups for use on our HPC clusters

Our cluster can make use of NETHZ groups. As an ISG you can define a group in the NETHZ admin tool (main screen→Admin Tasks→Gruppen verwalten) and export it to LDAPS. Don't forget to click on the aktualisieren link after updating the group!

Keep the following points in mind:

Type of group
The NETHZ group needs to be exported to LDAPS. For consistency it is recommended to export it to AD (Active Directory), too.
Sync the changes
You need to click on the aktualisieren link for the changes to take effect!
Do not change the group name
Avoid changing the name of any NETHZ group or contact us if you plan to do so.
Use only the ETH-wide LDAPS subtree
An ETH-wide group defined by any ISG will be in the
ou=custom,ou=groups,ou=nethz,ou=id,ou=auth,o=ethz,c=ch
subtree of LDAPS. Groups specific to a department can not be used.

We can only use groups from the

ou=groups,ou=nethz,ou=id,ou=auth,o=ethz,c=ch

subtree in LDAPS. That is the only way that we can provide service to and use services from the whole of ETH yet guarantee there are no collisions among group names or ids. From these, we only use the lz and custom NETHZ subtrees:

ou=lz,ou=groups,ou=nethz,ou=id,ou=auth,o=ethz,c=ch

and

ou=custom,ou=groups,ou=nethz,ou=id,ou=auth,o=ethz,c=ch

Please contact us if you have any questions regarding using NETHZ and/or LDAPS groups with our HPC clusters.

Defining share membership

By default only members of your LZ (Leitzahl) group are members of your share. You can manage membership in your shareholder group using LDAPS groups exported from NETHZ. Any number of LDAPS groups can be associated with your share. In addition, individual users can be added to the share or blocked from the share.

New and parting users

New members of the specified LDAPS group(s) will be automatically associated with your share while members who lose membership in the specified LDAPS groups are removed from your shareholder group. By default users are removed after 1 month, though can be changed upon request. These individual changes to the shareholder groups are only for share management and not file permission management.

Delegating management

You can also name one or more people to be the share manager. This person is then generally our contact person regarding the share and, more importantly, has authority to request or confirm changes to the share. In addition a manager also gets the monthly accounting report for the share. You can also request that a user receives the monthly accounting report but no management authority.