EGEE VO Registration

From EGI Knowledge Base

This article reproduces in part the contents of the EGEE document VO Registration Procedure.

[edit] Registration Prerequisites

Creating and operating a VO requires commitments from both the VO and the infrastructure. The registration, configuration and integration processes are not trivial and should only be undertaken if the VO is likely to persist more than a six months. VOs with short lifetime should use another infrastructure like the GILDA t-infrastructure.

[edit] Preparatory steps for setting up a new VO

1. Become familiar with grid technology and the EGEE/LCG infrastructure. Attending one of the many EGEE/LCG tutorials or experimenting with the GILDA t-infrastructure are excellent ways to do so.
2. Verify that there is no other existing VO which covers your application or organisation. Often there are existing regional VOs which can be expanded to include the full membership of an application. This information can be found on the Core Infrastructure Centre (CIC) portal.
3. Review the documentation describing the policies which govern the operation of a VO including the VO Security Acceptable Use Policy (AUP).
4. Ensure that the person managing the VO has a personal certificate issued by an accepted CA.

[edit] Registration Procedure

To register a new VO you use the web interface which will guide you through the registration process and prompt you for the required information. You will need to provide the following information:

1. Name of the VO.
   To avoid problems with conflicting VO names, new VOs should use a DNS-based naming scheme, as soon as this is technically feasible. EGEE VOs are suggested to use names in the format <VOname>.vo.eu-egee.org.
2. The VO's AUP, which should reside in the VO id card space of the CIC portal. The document should be uploaded by the VO manager. Major VO AUP changes should trigger a re-registration of the VO and its members.
3. Contact information for the VO manager (see VO Security Policy document).
4. Contact information for security representative (see VO Security Policy document).
5. Textual description of the VO and its aims.
6. Link to any relevant web sites for the VO.
7. The scientific discipline of the VO (e.g. HEP, Biomed, Earth Sciences, Astrophysics, Computational Chemistry, Fusion, Other).
8. Indication of the size of the VO (number of active users and number impacted by the grid use).
9. Average resource consumption per job (CPU, memory, network, temporary disk space) and number of concurrent jobs.
10. Average sizes of input and output files and the number of those stored on the grid. Also the permanence of those files.

After submission of this information the following bodies will be contacted in parallel automatically:

• The EGEE/LCG Operations Advisory Group (OAG) to review the provided information, evaluate the feasibility of the VO’s AUP, help with the VO name registration and approve the new VO.
• The EGEE NA3 to cover training needs, if necessary.

If there are no objections from the various EGEE activities, the request will be approved by the OAG within three business days. If there are concerns, you will be contacted by an OAG representative for further information or clarifications. You may contact the OAG chairs during this process to understand the status of the VO creation request.