VO Services

Goals

Setting up and operating a VO is a complex task that requires an important effort for ensuring a high quality of services. Many tools and services are available in EGI that rely on the VO information, and sometimes, procedures are neither easily available nor complete. The EGI VO Services subtask aims at supporting VOs in the whole process of start-up, management and operation, pointing out to tools, services, documentation and procedural guidelines to maximize the usage of the resources.

The VO services activity is carried out by LIP in Portugal and UPV in Spain. The activities are summarized in four main points:

• VO Management Support: To set up a central documentation point with procedures, FAQ and a single contact point.
• Promote VO activities: To ease the access to tools and services to foster production quality by the users of a VO.
• VO Infrastructure Monitoring: To aid setting up tools for monitoring the resources under the point of view of the VO.
• VO Infrastructure Usage: To support the monitoring on the usage of the resources by the users from a VO or a VRC.

Workplans

Each six months the VO services unit elaborates a workplan to be approved and retified by UCB.

• Activity Summary and 6 months Workplan (Month 6)

USAG Presentations

• USAG Fev 2011
• USAG Nov 2010

Procedures, protocols and documentation

This page contains links to documents that will guide new emerging communities on selecting the services and tools they would need in the daily operation of the VO.

Operation protocols and procedures

• VO Registration Process in EGI
• VO Management Frequently Asked Questions

Complementary documentation

• Core VO services evaluation (version 1.0.2)
• Survey on monitoring tools (version 1.0.5)
• Ganga + Diane + minidashboard evaluation (version 1.0.2)

Services

Categories_of_VO_services

In this frame, one of the needs that new communities have is the support of core services. Among those core services, we can identify:

1. EGI central VO services: Those services already in place by the infrastructure, hold centrally and which will be automatically supported. Examples are the new VO monitoring database (evolution of CIC), accounting portals or information systems.
2. EGI distributed VO core services: Those services set-up at the NGI level by previous agreements with users. Those services require dedicated hardware resources and continuous monitoring. Among those services we can list VOMS, WMS, LFC, PxServer, UI.
3. VO local services: Services that require lower hardware resources, are less critical and can be operated at the VO-side from the very beginning. Among them we can cite thematic Wikis, monitoring visualization portals, etc.

Resources at point 1 are provided by default by EGI-InSPIRE. Resources at point 3 are provided by the user communities. Resources at point 2 are quite critical and cannot be easily provided by the VO community. Since there are some commitment from NGIs in this activities, we will start to claim for NGI effort in order to support such services.

In order to ask for access of a VO to a given catch all service, please open a ticket on the VO Services Support Unit in GGUS (also see Support section)

Catch-all services mapping

Service	Country / NGI	Link
VOMS	Greece / HELLASGRID	https://voms.hellasgrid.gr:8443/vomses/Siblings.do
WMS
PX Server
LFC
UI

Tools under testing

• VO Centric Nagios

Support

The introduction of the VO Services Support Unit in GGUS will guide VO managers during the VO registration and unregistration, deploying technical services and to communicate requests in terms of service requirements.

• GGUS VO Services Support Unit FAQ

Revision history

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