|
|
| (One intermediate revision by the same user not shown) |
| Line 4: |
Line 4: |
| [[Category:GOCDB]] | | [[Category:GOCDB]] |
|
| |
|
| Link to pdf overview comming soon.
| | Executive Summary/Overview: https://wiki.egi.eu/w/images/d/d3/GOCDB5_Grid_Topology_Information_System.pdf |
| | |
| ==Summary==
| |
| GOCDB5 is an information system for recording Grid topology data such as service endpoints, sites, downtimes and users. GOCDB is the central topology database for the EGI project. The GOCDB5 codebase uses standards and best practices (MVC, services architecture, unit testing, ORM) to provide a stable, easily customisable product.
| |
| | |
| GOCDB5 supports multiple projects and is used to manage the relationships between different Grid entities using a well constrained relational schema. It includes a comprehensive role-based permissions model and each instance supports project specific business rules. Users request roles over entities such as sites or projects. Role requests can be subsequently granted or revoked by those holding a role over the entity. The core domain model closely resembles a sub-set of the GLUE 2 information model and includes Projects, Admin-Domains, Sites, ServiceGroups/VirtualSites, Services, Downtimes, Users and Roles (there are a number of key differences as explained later on).
| |
| | |
| The tool provides a web portal for editing information and a REST style programmatic interface (PI) for querying data in XML. A flexible tag-cloud mechanism allows Grid entities to be tagged with one or more scope-tags. This allows resources to be tagged and grouped into multiple categories without duplication of information – this is essential to maintain the integrity of topology information across different infrastructures and projects. Different scope tags can be defined according to requirement, for example, tags can be defined to reflect different projects, infrastructure groupings and sub-projects or ventures. Resources can be flexibly ‘filtered-by-tag’ when querying for data via the programmatic interface (PI).
| |
| | |
| GOCDB5 supports multiple databases out-of-the-box through the use of the Doctrine Object Relational Mapping library (ORM). A comprehensive DBUnit test suite ensures out of the box compatibility with Oracle and MySQL. Other databases such as Postgres should also be supported via Doctrine with a change to the DB connection settings. GOCDB also provides an administration interface for common admin tasks.
| |
| | |
| An authentication abstraction layer has been integrated to allow different authentication mechanisms to be supported using a pluggable ‘AuthenticationProvider’ interface. Implementations are provided for x509 and username/password.
| |
| | |
| GOCDB5 was released into production in EGI on 2nd October. Post v5 release work is focussing on a flexible extensibility mechanism for defining custom properties using key-value pairs and a GLUE 2 XML rendering of the GOCDB5 data. New attributes will be added to the GOCDB5 entities to give greater coverage of GLUE 2 attributes.
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.