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 "VO Services"
| Line 22: | Line 22: | ||
# 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. | # 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. | 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. | ||
* Catch-all services (in progress) | * Catch-all services (in progress) | ||
Revision as of 17:42, 9 December 2010
Goals
The EGI-InSPIRE project aims at supporting both “Heavy user communities” (HUC) and new emerging communities. HUC are directly supported through specific tasks in the SA3 activity. New emerging communities are lacking from this organization and resources, and take-off can fail if assistance is not provided. The VO Services subtask in NA3 aims at providing documentation and services to these emerging communities.
Documents and Protocols
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
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:
- 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.
- 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.
- 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.
- Catch-all services (in progress)
- VOMS.
- WMS.
- LFC.
- PxServer.
- UI.
- Test services (in progress)
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.