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/PI Updates"
< GOCDB
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
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. | 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. We will change all GOCDB PI queries to include a scope parameter: | |||
e.g. https://goc.gridops.org/gocdbpi/public/?method=get_site_list&scope=EGI | |||
Revision as of 11:44, 17 June 2011
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. We will change all GOCDB PI queries to include a scope parameter:
e.g. https://goc.gridops.org/gocdbpi/public/?method=get_site_list&scope=EGI