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/Regionalisation/PI Updates"

From EGIWiki
Jump to navigation Jump to search
imported>Krakow
 
(No difference)

Latest revision as of 12: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.