Difference between revisions of "GOCDB/Release4/Architecture"
Jump to navigation
Jump to search
m (Created page with '== Overall architecture == Following EGI requirements, Grid Operations Database release 4 (GOCDB4 or GOCDB in short) acts as a service deployed and available both at central and…') |
m |
||
Line 1: | Line 1: | ||
== Overall architecture == | == Overall architecture == | ||
Following EGI requirements, Grid Operations Database release 4 (GOCDB4 | 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/|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]. | |||
'' |
Revision as of 16:43, 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.
[1] comes along in two flavors, a read-only Central Visualisation Portal and a writeable Input System.