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 "2018-bidding/service-registry"

From EGIWiki
Jump to navigation Jump to search
m (Changed the types of header used)
m
Line 5: Line 5:
== Introduction  ==
== Introduction  ==


EGI relies on a central registry (GOCDB) to record information about different entities such as the Operations Centres, the Resource Centres, service endpoints and the contact information and roles of people responsible for operations at different levels. GOCDB is a source of information for many other operational tools, such as ARGO, the Accounting Portal, the Operations Portal, etc.  
EGI relies on a central registry (GOCDB) to record information about the topology of an e-Infrastructure. This includes entities such as Operations Centres, Resource Centres, service endpoints and their downtimes, contact information and roles of users responsible for operations at different levels. The service enforces a number of business rules and defines different grouping mechanisms and object-tagging for the purposes of fine-grained resource filtering. GOCDB is a source of information for many other operational tools, such as ARGO, the Accounting Portal, the Operations Portal, etc.  


== Technical description  ==
== Technical description  ==


The GOCDB front-end is hosted by a Virtual Machine providing Enterprise RedHat OS, Apache2 webserver, PHP5, and nagios/ganglia monitoring components for in-house production monitoring. GOCDB must be deployed in a master-slave distributed high availability configuration. The two instances cannot be deployed on the same site.  
The GOCDB service must be deployed in master-slave distributed high-availability configuration. The two instances cannot be deployed on the same site. Monitoring components have to be integrated within the in-house production monitoring system.


=== Coordination  ===
=== Coordination  ===
Line 20: Line 20:
*Provisioning of a high availability configuration  
*Provisioning of a high availability configuration  
*A test infrastructure to verify interoperability and the impact of software upgrades on depending systems
*A test infrastructure to verify interoperability and the impact of software upgrades on depending systems
*Implementing all the measures for mitigating the risks listed in the Availability and Continuity Plan for GOCDB


=== Maintenance  ===
=== Maintenance  ===
Line 30: Line 31:
=== Support  ===
=== Support  ===


Support through the EGI helpdesk to users of GOCDB and to the operators of other depending systems.  
Support is provided via EGI Service Desk Support Unit: GOC DB (http://helpdesk.egi.eu/).


'''Support hours''': eight hours a day , Monday to Friday – excluding public holidays of the hosting organization.  
'''Support hours''': eight hours a day, Monday to Friday – excluding public holidays of the hosting organization.  


== Service level targets  ==
== Service level targets  ==


*Minimum availability/reliability: 99%/99%  
*Minimum availability/reliability: 99% / 99%  
*Response to incident records in GGUS within support hours: Medium (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)
*Response to incident records in GGUS within support hours: Medium (see https://wiki.egi.eu/wiki/FAQ_GGUS-PT-QoS-Levels#Medium_service)



Revision as of 16:35, 4 November 2019

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


EGI Core services menu: Services PHASE I Services PHASE II Services PHASE III Bids Payments Travel procedure Performance


Go back to the EGI Core Activities Bidding page. 

Service name: Service registry (GOCDB)

Introduction

EGI relies on a central registry (GOCDB) to record information about the topology of an e-Infrastructure. This includes entities such as Operations Centres, Resource Centres, service endpoints and their downtimes, contact information and roles of users responsible for operations at different levels. The service enforces a number of business rules and defines different grouping mechanisms and object-tagging for the purposes of fine-grained resource filtering. GOCDB is a source of information for many other operational tools, such as ARGO, the Accounting Portal, the Operations Portal, etc.

Technical description

The GOCDB service must be deployed in master-slave distributed high-availability configuration. The two instances cannot be deployed on the same site. Monitoring components have to be integrated within the in-house production monitoring system.

Coordination

This activity is responsible for the coordination of the system operation and upgrade activities with those partners that are in charge of operating other systems that depend on it.

Operations

  • Daily running of the system
  • Provisioning of a high availability configuration
  • A test infrastructure to verify interoperability and the impact of software upgrades on depending systems
  • Implementing all the measures for mitigating the risks listed in the Availability and Continuity Plan for GOCDB

Maintenance

  • Bug fixing, proactive maintenance, improvement of the system
  • Coordination of software maintenance activities with other technology providers that provide software for the EGI Core Infrastructure or remote systems deployed by integrated and peer infrastructures that interoperate with the central EGI components of the system
  • Requirements gathering
  • Documentation

Support

Support is provided via EGI Service Desk Support Unit: GOC DB (http://helpdesk.egi.eu/).

Support hours: eight hours a day, Monday to Friday – excluding public holidays of the hosting organization.

Service level targets

Effort

Bids planning a total effort of about 6 Person Months/year would allow these service and activities to be addressed appropriately.