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 72: Line 72:


= Reference documentation =
= Reference documentation =
https://twiki.cern.ch/twiki/bin/view/EGEE/VomsInstallGuide_32
* https://twiki.cern.ch/twiki/bin/view/EGEE/VomsInstallGuide_32
https://twiki.cern.ch/twiki/bin/view/EGEE/VomsAdminUserGuide
* https://twiki.cern.ch/twiki/bin/view/EGEE/VomsAdminUserGuide
https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide320
* https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide320
http://glite.web.cern.ch/glite/packages/R3.2/sl5_x86_64/deployment/glite-VOMS_mysql/glite-VOMS_mysql-known-issues.asp
* http://glite.web.cern.ch/glite/packages/R3.2/sl5_x86_64/deployment/glite-VOMS_mysql/glite-VOMS_mysql-known-issues.asp


* [https://twiki.cern.ch/twiki/bin/view/Main/VOMSCore VOMS Core Trouble Shooting]
* [https://twiki.cern.ch/twiki/bin/view/Main/VOMSCore VOMS Core Trouble Shooting]
Line 82: Line 82:
* [https://edms.cern.ch/file/973684/1/voms-guide.pdf VOMS official user guide ]
* [https://edms.cern.ch/file/973684/1/voms-guide.pdf VOMS official user guide ]
* [https://edms.cern.ch/file/974094/1/voms-admin-user-guide.pdf VOMS-Admin official user guide ]
* [https://edms.cern.ch/file/974094/1/voms-admin-user-guide.pdf VOMS-Admin official user guide ]
http://dimou.web.cern.ch/dimou/lcg/registrar/TF/vomrs-tips.html
* http://dimou.web.cern.ch/dimou/lcg/registrar/TF/vomrs-tips.html


https://twiki.cern.ch/twiki/bin/view/EGEE/VomsAdminUserGuide
* https://twiki.cern.ch/twiki/bin/view/EGEE/VomsAdminUserGuide
 
* https://twiki.cern.ch/twiki/bin/view/EGEE/VOSupport
"It is not clear to the LOFAR VO manager what tasks are expected from a VO manager and what options/services are available to the VO manager. Is there a document providing guidelines on this? For example, how to retrieve and distribute information about (un)scheduled downtimes of relevant sites, what information to provide to new users about getting GGUS support, when should issues be communicated to EGI and when to the involved NGIs (lofar is a pan-european organisation that involves multiple NGIs), etcetera. "
* https://twiki.cern.ch/twiki/bin/view/EGEE/VOSupportFAQ
 
* https://twiki.cern.ch/twiki/bin/view/EGEE/VOSoftwareInstallation
 
* https://twiki.cern.ch/twiki/bin/view/EGEE/VOSupport_VOTools
https://twiki.cern.ch/twiki/bin/view/EGEE/VOSupport
* http://www.nesc.ac.uk/talks/725/EGEE%20VO%20Management_FSchaer.ppt
 
https://twiki.cern.ch/twiki/bin/view/EGEE/VOSupportFAQ
 
https://twiki.cern.ch/twiki/bin/view/EGEE/VOSoftwareInstallation
 
https://twiki.cern.ch/twiki/bin/view/EGEE/VOSupport_VOTools
 
http://www.nesc.ac.uk/talks/725/EGEE%20VO%20Management_FSchaer.ppt


= Revision history =
= Revision history =

Revision as of 20:57, 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

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.

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.

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 [1]


How to install a VOMS Server?



dddd

  1. ddd
  • 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