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 "GOCDB/Release4/Architecture"

From EGIWiki
Jump to navigation Jump to search
m
m
Line 51: Line 51:
{| {{egi-table}}
{| {{egi-table}}
! Document !! type !! Description !! author !! date  
! Document !! type !! Description !! author !! date  
|-
| [[Media:Example.ogg]]
|-
|-
|}
|}

Revision as of 17:13, 15 November 2010

Overall architecture

Following EGI requirements, Grid Operations Database release 4 (GOCDB4) acts as a service deployed and available both at central and local level. While "regional GOCDBs" can be installed and maintained by regions, NGIs or local grids, a central module will gather this information and provide it to any tool or user that needs a central view of EGI resources and related information.

GOCDB4 comes along in two flavors, a read-only GOCDB4 Central Visualisation Portal and a writeable GOCDB4 Input System.

Internal architecture and components

In the overall architecture described above, regional and central modules are built exactly the same way. They come as a set of components that can be deployed and configured to act as a central or local service.

GOCDB4 comprises of the following core components:

  • A database schema
  • Internal components Allowing for business logic
  • A set of interfaces that provide access to the database to any other component

Database and schema

The PROM concept

GOCDB4 data schema is designed in an object fashion. This object model is implemented at database level using a methodology known as Pseudo-Relational Object Model (PROM). This model, designed and architected by Peter Colclough, is described at PROM.

GOCDB4 data schema

GOCDB4_DB_Schema

I/O and Business Logic components

I/O XML interfaces to the database

Interfaces

The general idea is to keep interfaces to GOCDB4 and data exchange formats as standard as possible. A basic set of well defined interfaces will allow for the following:

  • Data exchange between GOCDB4 and User Interfaces, portals and displays
  • Internal communication between GOCDB4 modules
  • Communication between central GOCDB4 module and external regional modules
  • Communication between GOCDB4 modules and third-party tools

REST interface (GOCDBPI)

GOCDB_Technical_Documentation#PI

More information

Documents

Document type Description author date
Media:Example.ogg