GOCDB

GOCDB
Name	GOCDB
Type	Repository
Established	2008
Owner	European Grid Infrastructure
Location	Europe

GOCDB is a central registry and repository used by research infrastructures to publish, discover, and maintain information about operational resources, sites, and services. It serves as a canonical inventory for infrastructures that coordinate distributed computing and scientific facilities, enabling interoperability among projects such as European Grid Infrastructure, EGI, Open Science Grid, Helix Nebula, and Pan-European Research Network. The platform underpins operational activities for communities including CERN, DESY, Max Planck Society, CNRS, and INFN by providing authoritative topology, contact, and status data.

Overview

GOCDB functions as an authoritative topology database and service registry that catalogs resources like computing clusters, storage elements, network endpoints, and monitoring probes used by projects such as Worldwide LHC Computing Grid, ATLAS experiment, CMS experiment, LHCb, and ALICE. It records relationships among entities such as sites, services, endpoints, and accounts for administrative domains like STFC, KIT, and Forschungszentrum Jülich. Operators and administrators from institutions including University of Oxford, University of Cambridge, Université Paris-Saclay, and ETH Zurich use the repository to coordinate support processes with organizations such as OASIS, OGF, and TERENA. The registry supports discovery by tools developed by Nagios, Zabbix, and Grafana Labs integrations, facilitating operational awareness for projects including Gaia, SKA, and EuroHPC.

History and Development

The registry emerged in the context of initiatives led by EGEE and later EGI to harmonize resource information across European and international infrastructures. Early contributions came from collaborations among CERN, Rutherford Appleton Laboratory, INFN, and TRIUMF to address operational fragmentation evident in projects like LCG. Subsequent development cycles incorporated features requested by communities such as BioMedIT, ELIXIR, and CLARIN, and governance models influenced by policy bodies including European Commission programmes and Horizon 2020. The software evolved alongside middleware efforts from gLite, ARC, UNICORE, and HTCondor, integrating with monitoring stacks used by MonALISA and SAM.

Architecture and Components

The architecture comprises a web-based portal, a programmatic API, a database backend, and synchronization agents. Core components mirror operational roles found in institutions like INFN CNAF, GridPP, SARA, and NIKHEF and include modules for topology, service endpoints, site contacts, and change history. The API supports machine clients used by orchestration tools developed at CERN IT, KIT IT Center, and SURFnet, and the backend integrates with relational systems employed at Oracle Corporation deployments and open-source stacks used by Debian and Ubuntu Server administrators. Authentication and delegation mechanisms reference identity providers such as eduGAIN, InCommon, and GLUE schema conventions.

Data Model and Information Sources

The registry implements a schema for representing sites, services, endpoints, and certificates aligned with standards adopted by W3C, IETF, and the Open Grid Forum. Information originates from authoritative sources including regional operations centres like ROC teams across Europe, inventory systems at CERN, configuration management databases maintained by Red Hat, and discovery data from monitoring tools such as Nagios and Zabbix. The data model accommodates attributes required by experiments like ATLAS and CMS (e.g., service types, support contacts, operational status) and supports plugin adapters for metadata harvested from software such as Puppet, Ansible, and SaltStack inventories.

Use Cases and Applications

Administrators and support engineers at organizations like GridPP, NDGF, PSNC, and CESNET use the registry to coordinate incident response, capacity planning, and service certification for collaborations including LHCb Computing Grid and PanDa workload management. Researchers rely on topology information when configuring clients for data transfer tools like FTS and Globus, and platform teams integrate registry records into dashboards built with Grafana and alerting pipelines powered by Prometheus. Project managers in Horizon Europe consortia consult the inventory for reporting and audit purposes, while software projects such as Rucio and DIRAC query the API for resource discovery.

Governance and Access Control

Governance involves stakeholder representation from infrastructures such as EGI, Open Science Grid, and national research and education networks like GÉANT and SURFnet. Operational policies follow community agreements influenced by frameworks from European Commission programmes and working groups affiliated with OpenAIRE. Access control leverages federated identity systems including eduGAIN and project-managed accounts from institutions like CERN and DESY, combined with role-based permissions reflecting administrative roles at site managers and support teams across participating organizations.

Integration and Interoperability

Interoperability is achieved through standardized APIs, adherence to schemas like GLUE, and connectors for orchestration tools used by Kubernetes, OpenStack, and VMware ESXi deployments at sites such as CERN Data Centre and Julich Supercomputing Centre. The registry integrates with monitoring frameworks from Nagios and MonALISA, ticketing systems like Request Tracker and JIRA, and identity federations such as eduGAIN. This enables seamless workflows between middleware stacks (e.g., gLite, ARC) and modern resource managers (e.g., Slurm, HTCondor), supporting multi-disciplinary collaborations spanning experiments like LIGO, IceCube, and observatories coordinated by European Southern Observatory.

Category:Computing infrastructure