Difference between revisions of "GOCDB/Release4/Architecture"
Line 3: | Line 3: | ||
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. | 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. | ||
[[https://goc.gridops.org/ | [[https://goc.gridops.org/ GOCDB4]] comes along in two flavors, a ''read-only'' [[https://goc.gridops.org/portal/ GOCDB4 Central Visualisation Portal]] and a ''writeable'' [[https://gocdb4.esc.rl.ac.uk/portal GOCDB4 Input System]]. | ||
== Internal architecture and components == | == Internal architecture and components == |
Revision as of 15:19, 20 December 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
I/O and Business Logic components
I/O XML interfaces to the database
- generic access software
- specifically formatted (link to http://goc.grid.sinica.edu.tw/gocwiki/PROM_XML_Data_Format , obsolete)
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:GOCDB@TF.pdf | slides | Slides on GOCDB4 architecture and status presented during http://www.egi.eu/EGITF2010 conference, Sept 2010 | Gilles Mathieu | 16sep10 |
Media:GOCDB4_slides_ISGC2010.pdf | slides | Slides on GOCDB4 architecture and status presented during ISGC2010 conference, March 2010 | Gilles Mathieu, John Casson | 01mar10 |
Media:GOCDB4_paper_ISGC2010.pdf | paper | article on GOCDB4 architecture and status submitted to ISGC2010 conference, March 2010 | Gilles Mathieu, John Casson | 01mar10 |
Media:GOCDB4_poster_EGEE09.pdf | poster | poster on GOCDB4 architecture presented at EGEE'09 conference, September 2009 | Gilles Mathieu, John Casson | 15sep09 |
links and contact
- You can find more information about GOCDB in general on the GOCDB general documentation index
- For any question please contact GOCDB development team