The wiki is in the process of being deprecated and migrated to other supports.

Dteam vo

From EGIWiki
Revision as of 15:05, 15 September 2011 by Tferrari (talk | contribs)
Jump to navigation Jump to search
Main 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

Migration of the dteam VO from CERN to EGI VOMS (AUTH/NGI_GRNET)

  1. Sync dteam Greece with dteam CERN.
  2. Advise sites to add the new VOMS server to their configuration. They need to be told new site-info.def definitions to replace these:

'dteam 15004 \
/DC=ch/DC=cern/OU=computers/ dteam 24' \
'dteam 15004 \
/DC=ch/DC=cern/OU=computers/ dteam 24'" 


'/DC=ch/DC=cern/CN=CERN Trusted Certification Authority' \
'/DC=ch/DC=cern/CN=CERN Trusted Certification Authority'"

with these:


'dteam 15004 \
/C=GR/O=HellasGrid/ dteam 24' \
'dteam 15004 \
/C=GR/O=HellasGrid/ dteam 24'" 


'/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006' \
'/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006'"

Run yaim after changing site-info.def.The new "lsc" files should be and with the following contents, respectively:

/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006
/C=GR/O=HellasGrid/OU=Certification Authorities/CN=HellasGrid CA 2006
  1. Sites also need an rpm containing the host cert(s) of the new VOMS server(s) at least for the WMS, while it still requires the certs of supported VOs. We could add those certs to lcg-vomscerts to smoothen the transition, but it may be better for EGI to control its own rpm. 11/10/2010 lcg-vomscerts has been already updated. Version 6.1.0 and later contains the new certs. Latest[1] as of 11/11/2010.
  1. Wait a bit (1 month sounds reasonable).
  1. Close registrations at CERN. service stop vomrs should do.
  1. Sync dteam Greece with dteam CERN.
  1. Advise new users to register with Greece.
  1. Remove CERN dteam. This will take place on Wednesday January 26.
  1. Advise sites to drop CERN dteam configuration.

General information about the VO

The dteam VO started in EGEE as a VO for operations. General Grid security policies as defined the the documents at [2] are applicable. Currently the AUP [3] (which needs update for EGI terminology) states:

This acceptable Use Policy applies to all members of the DTEAM Virtual Organization, hereafter referred to as the VO, with reference to use of the LCG/EGEE Grid infrastructure, hereafter referred to as the Grid. The ROC managers' coordination committee is the body that owns and gives authority to this policy.

The goal of the VO is to facilitate the deployment of a stable production Grid infrastructure. To this end, members of this VO -who have to be associated with a registered site and be involved in its operation- are allowed to run tests which validate the correct configuration of their site. Site performance evaluation and/or monitoring programs may also be run under the DTEAM VO with the approval of the Site Manager, subject to the agreement of the affected sites' management.

During all times at which they are utilising Grid resources, in testing or performing productions for validation, the Members and Managers of the VO agree to be bound by the Grid Acceptable Usage Rules, VO Security Policy and other relevant Grid Policies, and to use the Grid only in the furtherance of the stated goals of the VO.

How to get support

Open a GGUS ticket, select Operations as type, and set concerned VO to dteam. If you have privileges, assign it to the VOsupport unit.

Recipes for VO/ROC/NGI/Site managers

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. Example: dteam users from Greece should select Kostas Koumantaros or Ioannis Lambiotis as their Representative and /dteam/NGI_GRNET as their Group. 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. 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.

What the VO-Admin can do:

Everything including VO member suspension/removal that nobody else can do! NB!!!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". To remove the GroupOwner/Manager autority, use control/click on the relevant Group/Role (it will be blue)!

What the Representative can do:

Approve Candidates during the initial registration and handle Expired users. 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.

The Representative selected by the user can assign another Representative before approving, as appropriate. 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. contains EGEE era implementation details and plans on Groups/Roles. As VOMRS fuctionality will be implemented in VOMS this document is becoming obsolete.

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.

VOMRS Tutorials:

VOMRS Online Documentation:

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

Info obtained from Maria Dimou VOMRS tips page, with material provided by Tanya Levshina (VOMRS Project Leader and developer)