Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "FAQ VO Management"

From EGIWiki
Jump to navigation Jump to search
Line 45: Line 45:


=== I want to start my project VO. What should I do? ===
=== I want to start my project VO. What should I do? ===
Please read the [https://documents.egi.eu/document/278 '''VO Registration Process in EGI'''] documentation. That documentation will guide you through the process of requesting VOMS server support (if you do not have any) to set-up your VO, registering your VO in the EGI CIC portal, and make the EGI project aware that your VO exists. Do not forget to establish a well defined '''Acceptable User Policy'''.
Please read the [https://documents.egi.eu/document/278 '''VO Registration Process in EGI'''] documentation. That documentation will guide you through the process of requesting VOMS server support (if you do not have any), registering your VO in the EGI CIC portal, and make the EGI project aware that your VO exists. Do not forget to establish a well defined '''Acceptable User Policy'''.


==='''What is the VO Acceptable User Policy (AUP)?'''===
==='''What is the VO Acceptable User Policy (AUP)?'''===

Revision as of 21:45, 10 December 2010

Title VO Management Frequently Asked Questions
Document link to be determined
Last modified
Policy Group Acronym
Policy Group Name NA3.4 Technical Services - VO Services
Contact Person Goncalo Borges
Document Status DRAFT
Approved Date
Procedure Statement a concise statement of the rationale for the policy or procedure, including if appropriate, reference to external regulations, further policy discussion, etc. Summary (one paragraph) clearly stating the important policy/procedure content


Frequently Asked Questions

Common Operations

Why do I need a VO?

If you are part of a research community whose members are geographically apart, belong to independent organizations, and collaborate via electronic means to achieve a common goal, probably you are already part of a Virtual Organization (VO) without knowing. However, on GRIDs, VOs have the specificity that VO members share computing resources. If the computing resources in your instute are not sufficient are always very busy, maybe the establishment of a VO within your research community is a good solution for you.

How is the VO membership managed?

In GRIDS, VO members can access computing resources in institutes where they are not known. Therefore, the VO membership has to be closely managed by a trustworthy partner, and via a dedicated service called VO Management Service (VOMS) where all VO users must be registered.

How can I install a VOMS service?

Before installing your VOMS service, you should be aware of the effort and cost on its operation, as well as on the requirements for the service deployment. Those variables are quantified in the Core VO services evaluation document. If you decide that you can not afford to deploy this service, EGI may offer the possibility to host your VO in a catch-all service (please see the section [1]).

https://twiki.cern.ch/twiki/bin/view/EGEE/VomsInstallGuide_32

I want to start my project VO. What should I do?

Please read the VO Registration Process in EGI documentation. That documentation will guide you through the process of requesting VOMS server support (if you do not have any), registering your VO in the EGI CIC portal, and make the EGI project aware that your VO exists. Do not forget to establish a well defined Acceptable User Policy.

What is the VO Acceptable User Policy (AUP)?

An acceptable use policy (AUP; also sometimes acceptable usage policy or Fair Use Policy) is a set of rules applied by the VO that restrict the ways in which the network site or system may be used. For more details please check [2]

I've set up my project VO. How do I get computing resources?

In most of the places, VOs do not own physical resources but they own a right to use them. That right is earned according to the funding that sites receive from projects where VO members are involved. Therefore, sites do allocate a share of their ressources to a given VO depending on the funding they receive from local projects associated to that VO. This is the normal procedure on how newly VOs provide resources to the GRID. The GRID spirit behind is that everyone can use everybody resources as long as these resources aren't really needed.

If the VO has very few members without computing resources, there is always the possibility to ask external sites to support this VO. However, external sites only accept to do that if they get something in exchange. It can be fame, pride of serving a great cause, pride of helping find a cure to cancer or even money. If you have something to offer, sites will probably consider opening their resources to your VO.

Which users should be accepted in my VO?

It is unlikely that a user who has no affiliation with a VO will be allowed to use this VO since he (or his institute) has to contribute to the VO (with resources or in any other form) in return. The VO Manager should try to find out if a user request is valid (for example, if it is coming from an institute which already contributes to the VO infrastructure), or if the user is interested in contributing to the enhancement of the VO infrastructure. The VO should have a well defined Acceptable User Policy (AUP) which could guide the VO manager under this procedure. The ultimate decision to accept or deny a user request is always from the VO Manager.



  • How to install a VOMS Server?
  • How to register a VO?
  • When can a VO start operation in EGI?
  • How to make changes to the VO card in the CIC Portal?
  • How to comunicate with the VO sites?
  • How to ask for a VO specific support unit in GGUS?
  • How can the VO Manager ask for GGUS support access?
  • How should VO users open a GGUS ticket?
  • How can a VO Manager install VO specific software in a remote site?
  • How to report malfunctioning middleware?
  • How to ask for enahancements?
  • How to report issues to EGI and NGIs?

Technical Operations

  • VOMS replication


Reference documentation

Revision history

Version Authors Date Comments
1.00 Goncalo Borges 2010-12-09 Initial draft