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/Transfer Mechanism"
| Line 11: | Line 11: | ||
*gocdbpi/?method=synchronise_egi_data | *gocdbpi/?method=synchronise_egi_data | ||
The central GOCDB will periodically read from these queries and acknowledge | The central GOCDB will periodically read from these queries and acknowledge<br> | ||
<br> | |||
Revision as of 12:07, 16 June 2011
Introduction
The mechanism to transfer data from a regional GOCDB to a central GOCDB is separated into two parts: regional instance tasks and central instance tasks.
Regional Instance Tasks
Whenever a CRUD (create, replace, update, delete) operation is performed on a fundamental GOCDB object (site, service endpoint, downtime, user, user role) the regional GOCDB will record the event. This record will include the object Id, the type of operation (CRUD) and the date and time at which the object was modified. The record will also show whether the object has been successfully synchronised with the central GOCDB via a synchronisation boolean. By default the synchronisation field will be false.
This table will be used to create a set of PI queries exposing EGI data that has changed in the regional GOCDB:
- gocdbpi/?method=synchronise_egi_data
The central GOCDB will periodically read from these queries and acknowledge