1 / 6

VO Registration procedure

VO Registration procedure. https://edms.cern.ch/document/503245 Joint Security Policy Group Meeting EGEE Conference Den Haag 2004-11-25. What we want to achieve.

kaelem
Download Presentation

VO Registration procedure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VO Registration procedure https://edms.cern.ch/document/503245 Joint Security Policy Group Meeting EGEE Conference Den Haag 2004-11-25 Maria Dimou IT/GD

  2. What we want to achieve • List the necessary steps a new Virtual Organisation (VO) should take in order to be registered, configured and integrated in the LCG2/EGEE infrastructure, by providing advice on: • Naming the VO. • Getting approval for support from the Grid sites. • Choosing the location of a (de)centralised Registration database. • Choosing the technology (LDAP/VOMS) of the VO database (VODB). • Choosing the tool for adding members in the VO. • Propagating the VO to the Grid sites. Maria Dimou IT/GD

  3. VO set-up scenari • July 2004 EGEE NA4 presentation explains the options in detail: http://agenda.cern.ch/askArchive.php?base=agenda&categ=a041952&id=a041952s5t1/transparencies In summary these options offer to use: • The present Registration Database currently provided by the LCG Deployment Team for several LCG/EGEE VOs. • A Registration database combined with your: • LDAP-based VODB or • VOMS-based VODB. Maria Dimou IT/GD

  4. Entering users in a VO (I) • “Inherit” an existing LDAP VODB, and copy it, every few hours, into a VOMS database, using the synchronisation scripts. • Let your users apply for VODB membership via the web VOMS or VOMRS administration interface. This offers an integrated solution for Registration and VODB update and will be used by the EGEE VOs, e.g. BIOMED, SEE-GRID. The VO manager will approve/deny these applications using the same tool. Maria Dimou IT/GD

  5. Entering users in a VO (II) • Let your users apply for VODB membership via the default web VOMRS administration interface. This offers an integrated solution for Registration and VODB update for the non-LHC VOs, e.g. STAR. The VO manager will approve/deny these applications using the same tool. • Let your users apply for VODB membership via a special configuration of the web VOMRS administration interface. This will offer a VODB update mechanism (pending VO manager’s approval) provided the user’s data are successfully matched against his/her entry in a (separate) Registration database. This solution will be used by the 4 LHC Experiment VOs. Maria Dimou IT/GD

  6. Telling the sites about the new VO • Grid-map file generation on CE,SE,RB for: • LDAP-based VODB. • VOMS-based VODB. • Edit other configuration files with VO info related to: • BDII • UI • Configure LCAS/LCMAPS with VO-related parameters. • RLS set-up, if desired. Maria Dimou IT/GD

More Related