Difference between revisions of "Dteam vo"

From EGIWiki
Jump to: navigation, search
(Become a member)
 
(18 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}}  
+
{{Template:Op menubar}}  
 +
{{Template:Doc_menubar}}  
 +
{{TOC_right}}  
 +
 
 +
[[Category:Catch All Grid Core Services]]
  
 
= General Information  =
 
= General Information  =
  
The DTEAM VO is an infrastructure VO that MUST be enabled by all EGI Resource Centres that support the VO concept for user authentication, as stated in the [https://documents.egi.eu/document/31 Resource Centre Operational Level Agreement]. It is meant for testing and troubleshooting of grid capabilities across EGI Resource Centres. Usage of the DTEAM VO is subject to the EGI [[SPG:Documents|Security Policies]].  
+
The DTEAM VO is an infrastructure VO that MUST be enabled by all EGI Resource Centres that support the VO concept for user authentication, as stated in the [https://documents.egi.eu/document/31 Resource Centre Operational Level Agreement]. It is meant for testing and troubleshooting of capabilities across EGI Resource Centres. Usage of the DTEAM VO is subject to the EGI [[SPG:Documents|Security Policies]].  
  
*[http://operations-portal.egi.eu/vo/downloadAUP/file/dteam-AcceptableUsePolicy-20110926-1316993681969.txt DTEAM AUP].
+
* DTEAM AUP: Find on the VO page in the Operation Portal: https://operations-portal.egi.eu/vo/view/voname/dteam
 
*'''Get support''': in order to get support about the DTEAM VO please [http://helpdesk.egi.eu/ open a ticket], select type ''Operations'', and set ''concerned VO'' to ''dteam''. If you have privileges, assign it to the Support Unit ''VOsupport unit''.
 
*'''Get support''': in order to get support about the DTEAM VO please [http://helpdesk.egi.eu/ open a ticket], select type ''Operations'', and set ''concerned VO'' to ''dteam''. If you have privileges, assign it to the Support Unit ''VOsupport unit''.
  
= Recipes for VO/ROC/NGI/Site managers =
+
= Become a member =
 
 
== What users filling the '''dteam''' VO Registration form should do ==
 
  
Select the appropriate '''Representative''' and '''Group''' for themselves. The Representative corresponding to their region is offered in a drop-down menu.
+
Open the following link
  
''Example: dteam users from Greece should select Kostas Koumantaros or Ioannis Liabotis as their Representative and /dteam/NGI_GRNET as their Group.''
+
*[https://voms2.hellasgrid.gr:8443/voms/dteam DTEAM VOMS-Admin]
  
Everybody is automatically registered under the root group /dteam in addition to any Group they might select. Nobody can de-assign them from this "root group" unless they get "Denied", in the first place or, later on, "Suspended", by the VO-Admin, in which case they can't run any Grid jobs and they get deleted from the VOMS database.  
+
fill in the requested information and after reading the dteam AUP confirm that you abide to this policy and press the submit button.  
  
When users select additional Groups, the GroupOwners have nothing to do, if they have no objection. Users may select GroupRoles within a given Group as well.  
+
In order to verify your email address an email will be sent to you (if you cannot find the verification email in your inbox please make sure to also check your spam folder). By following the link given within the verification email you will have to select the appropriate NGI/Group manager who will handle your request and press the "Continue" button at the bottom of the page. The NGI/Group Manager you selected will be notified of your request and should handle it.
  
== What the VO-Admin can do ==
+
== What users filling the '''dteam''' VO Registration form should do ==
  
Everything including VO member suspension/removal that nobody else can do!
+
Select the appropriate '''Group Manager''' (depending on NGI origin) for themselves. The Manager corresponding to their NGI/region is offered in a bullet-list menu.
  
If you try to remove a member and the box-to-tick is grey, this means that the member has some authority (GroupOwner/Manager or Representative). You 'll have to remove that funtion first from him/her via "Manage VO Admin Roles".
+
'''Example:'''
 +
<blockquote style="background-color: lightgrey; border: solid thin grey; padding: 5px;">dteam users from Greece should select Kostas Koumantaros as their Group Manager</blockquote>
  
To remove the GroupOwner/Manager autority, use control/click on the relevant Group/Role (it will be blue)!
+
Everybody is automatically registered under the root group /dteam. Nobody can de-assign them from this "root group" unless they get "Denied", in the first place or, later on, "Suspended", by the VO-Admin, in which case they can't run any Grid jobs and they get deleted from the VOMS database.
  
== What the Representative can do ==
+
Users may select additional Groups, SubGroups and Roles within their NGI Group from their [https://voms2.hellasgrid.gr:8443/voms/dteam/user/home.action VO Home page].
  
Approve Candidates during the initial registration and handle Expired users.
+
'''Examples:'''
 +
<blockquote style="background-color: lightgrey; border: solid thin grey; padding: 5px;">dteam users from Greece should select to be added to /dteam/NGI_GRNET Group</blockquote>
 +
<blockquote style="background-color: lightgrey; border: solid thin grey; padding: 5px;">dteam users from Greece who want Production Role should request the/dteam/NGI_GRNET/Role=production role</blockquote>
  
To do this, the Representative should either click on the link (s)he got in the email notification or go to the web interface, open the "Members" sub-menu, click on "Set status", search for "New" candidates and approve those assigned to him/her.
+
= Recipes for VO/ROC/NGI/Group/Site managers  =
  
The Representative selected by the user can assign another Representative before approving, as appropriate.
+
== What the VO-Admin can do ==
 
 
''Example: a DTEAM VO Candidate from a Russian LCG Site selected the SWE ROC manager as Representative. Gonzalo (SWE) can replace himself with Alexander (RDIG).''
 
 
 
== What the GroupOwners can do ==
 
 
 
Group Owners can create groups/group roles and assign new Group Owner/Manager roles to member within the subgroups. If they decided that the user doesn't belong to their group(s) they can de-assign him/her at any time.
 
 
 
''Example: If Sven from DECH selects additional group /dteam/see, Kostas can move him out.''
 
 
 
== What the GroupManagers can do ==
 
 
 
They can deassign users from their group at any time.
 
 
 
http://cern.ch/dimou/lcg/vomrs/Groups-Roles.doc contains EGEE era implementation details and plans on Groups/Roles. As VOMRS fuctionality will be implemented in VOMS this document is becoming obsolete.
 
 
 
== Proposed distribution of responsibilities ==
 
 
 
{| border="1"
 
|-
 
! Operations manager and deputy
 
! Operations centre staff
 
! Site staff
 
|-
 
| GroupOwner,GroupManager, VO Representative
 
| GroupManager
 
| Group Member
 
|}
 
 
 
= Mini How-To =
 
 
 
*To (De)Assign someone as Representative go to "Manage VO Admin Roles".
 
*To (De)Assign someone as GroupOwner go to "Manage VO Admin Roles", search for the VO member and select the Group (s)he should own.
 
*To Change Representative for all members go to "Change Representative", Select the right DN from the drop dowm menu, click on each member.
 
*To receive email notification for actions you need to take go to "Subscription" and select what you wish to be notified about.
 
  
{| border="1"
+
Everything including VO member suspension/removal and ACLs configuration that nobody else can do!
|-
 
!
 
! VO Admin
 
! Representative
 
! GroupOwner
 
! GroupManager
 
|-
 
| Candidate
 
| remove
 
|
 
|
 
|
 
|-
 
| Applicant
 
| Remove/approve/deny Assign/deassign to/from group and group role
 
| Remove/approve/suspend/expire
 
| Assign/deassign to/from group and group role
 
|-
 
| Member
 
| Remove/approve/suspend/expire Assign/deassign to/from group and group role
 
| expire from Institute but not from the VO
 
| assign/deassign to/from group and group role
 
| assign/deassign to/from group and group role
 
|-
 
| Member’s certificate
 
| Remove/approve/deny/suspend
 
|
 
| assign/deassign to/from group and group role
 
| assign/deassign to/from group and group role
 
|}
 
  
= Resources =
+
== What the NGI/Group Manager can do ==
  
*VOMRS Tutorials: http://www.uscms.org/SoftwareComputing/Grid/VO/tutorials.html
+
* Approve Candidates during the initial registration.  
*VOMRS Online Documentation: http://computing.fnal.gov/docs/products/vomrs/
 
  
= Acknowledgements  =
+
<blockquote style="background-color: white; border: solid thin grey; padding: 5px; color: red;">
 +
NOTE: Once an NGI/Group Manager approves a user request he/she should make sure to add this person to the corresponding group he/she manages, plus any other subgroups as applicable.
 +
</blockquote>
  
Information provided in this page was collected from M. Dimou's VOMRS [http://dimou.web.cern.ch/dimou/lcg/registrar/TF/vomrs-tips.html tips page], with material provided by Tanya Levshina (VOMRS Project Leader and developer).
+
* Add/remove members to specific NGI/Group he/she is in charge of.

Latest revision as of 15:15, 13 March 2018

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators


General Information

The DTEAM VO is an infrastructure VO that MUST be enabled by all EGI Resource Centres that support the VO concept for user authentication, as stated in the Resource Centre Operational Level Agreement. It is meant for testing and troubleshooting of capabilities across EGI Resource Centres. Usage of the DTEAM VO is subject to the EGI Security Policies.

Become a member

Open the following link

fill in the requested information and after reading the dteam AUP confirm that you abide to this policy and press the submit button.

In order to verify your email address an email will be sent to you (if you cannot find the verification email in your inbox please make sure to also check your spam folder). By following the link given within the verification email you will have to select the appropriate NGI/Group manager who will handle your request and press the "Continue" button at the bottom of the page. The NGI/Group Manager you selected will be notified of your request and should handle it.

What users filling the dteam VO Registration form should do

Select the appropriate Group Manager (depending on NGI origin) for themselves. The Manager corresponding to their NGI/region is offered in a bullet-list menu.

Example:

dteam users from Greece should select Kostas Koumantaros as their Group Manager

Everybody is automatically registered under the root group /dteam. Nobody can de-assign them from this "root group" unless they get "Denied", in the first place or, later on, "Suspended", by the VO-Admin, in which case they can't run any Grid jobs and they get deleted from the VOMS database.

Users may select additional Groups, SubGroups and Roles within their NGI Group from their VO Home page.

Examples:

dteam users from Greece should select to be added to /dteam/NGI_GRNET Group

dteam users from Greece who want Production Role should request the/dteam/NGI_GRNET/Role=production role

Recipes for VO/ROC/NGI/Group/Site managers

What the VO-Admin can do

Everything including VO member suspension/removal and ACLs configuration that nobody else can do!

What the NGI/Group Manager can do

  • Approve Candidates during the initial registration.

NOTE: Once an NGI/Group Manager approves a user request he/she should make sure to add this person to the corresponding group he/she manages, plus any other subgroups as applicable.

  • Add/remove members to specific NGI/Group he/she is in charge of.