Difference between revisions of "NGI services in GOCDB"
Jump to navigation
Jump to search
Action status
Line 200: | Line 200: | ||
|- | |- | ||
| <span style="vertical-align: middle;">[https://goc.egi.eu/portal/index.php?Page_Type=View_Object&object_id=20301&grid_id=0 NGI_RO]</span> | | <span style="vertical-align: middle;">[https://goc.egi.eu/portal/index.php?Page_Type=View_Object&object_id=20301&grid_id=0 NGI_RO]</span> | ||
| <br> | | [https://goc.egi.eu/portal/index.php?Page_Type=View_Object&object_id=120358&grid_id=0 NGI_RO_SERVICES]<br> | ||
| <br> | | OK<br> | ||
| <br> | | <br> | ||
|- | |- |
Revision as of 15:18, 29 January 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Page provides current status of core services grouping action.
This action was started to make possible to calculate availability and reliability of NGIs based on ava/rel of its core services.
NGI core services can be grouped in two ways:
- by creating NGI_XX_SERVICES site
- by creating NGI_XX_SERVICES service group
Core services added to NGI_XX_SERVICES should be ONLY those which are under NGI responsibility and provide production quality (no testing instances).
Action approved on OMB meeting : https://indico.egi.eu/indico/conferenceDisplay.py?confId=617
Service types
Service type which should be registered in NGI_XX_Services site
Central operational tools
- ngi.SAM (Mandatory)
NGI should also register custom core services like accounting, helpdesk etc. (if registered in GOC DB).
QCG
- QCG.Broker
UNICORE
- unicore6.Gateway
- unicore6.Registry
- unicore6.ServiceOrchestrator
- unicore6.UVOSAssertionQueryService
- unicore6.WorkflowFactory
ARC
- none
GLOBUS
- MyProxy
GLITE
- Top-BDII
- WMS
- Central-LFC
- MyProxy
- VOMS
Action status
todo: 10 NGIs