Difference between revisions of "GOCDB/Release4/Regionalisation/PI Updates"
< GOCDB | Release4 | Regionalisation
Jump to navigation
Jump to search
imported>Krakow |
|
(No difference)
|
Revision as of 13:33, 18 December 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
GOC DB menu: | Home • | Documentation Index • |
Back to GOCDB/Release4/Regionalisation
Introduction
By introducing an EGI scope into GOCDB there is logically a non-EGI scope available for data. This will be used to store topology information for GOCDB objects that aren't a part of EGI. However this non-EGI data will be used by other tools and should be exposed.
Currently the GOCDB PI exposes only EGI data and by default the GOCDB PI will continue to show only EGI data. In order to access data that isn't in the EGI scope an optional scope parameter will be added. For example:
e.g. https://goc.egi.eu/gocdbpi/public/?method=get_site_list&tag=REGIONAL.PUBLISHED
The central instance of GOCDB will provide one scope parameter.