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/Transfer Mechanism"

From EGIWiki
Jump to navigation Jump to search
(Created page with '= Transfer Mechanism<br> = == Introduction<br> == The mechanism to transfer data from a regional GOCDB to a central GOCDB is separated into two parts: regional instance ta…')
 
Line 5: Line 5:
The mechanism to transfer data from a regional GOCDB&nbsp;to a central GOCDB is separated into two parts: regional instance tasks and central instance tasks.<br>
The mechanism to transfer data from a regional GOCDB&nbsp;to a central GOCDB is separated into two parts: regional instance tasks and central instance tasks.<br>


== Regional Instance Tasks<br> ==
== Regional Instance Tasks<br> ==


Whenever a CRUD (create, replace, update, delete) operation is performed on a fundamental GOCDB&nbsp;objects (site, service endpoint, downtime, user, user role) the regional GOCDB&nbsp;will record the event. This record will include the object Id, the type of operation&nbsp;(CRUD)&nbsp;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.<br>
Whenever a CRUD (create, replace, update, delete) operation is performed on a fundamental GOCDB&nbsp;objects (site, service endpoint, downtime, user, user role) the regional GOCDB&nbsp;will record the event. This record will include the object Id, the type of operation&nbsp;(CRUD)&nbsp;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.<br>  


This table will be used to create a set of PI&nbsp;queries exposing EGI data that has changed in a regional GOCDB:
This table will be used to create a set of PI&nbsp;queries exposing EGI data that has changed in a regional GOCDB:  


* gocdbpi/?method=synchronise_egi_sites
*gocdbpi/?method=synchronise_egi_sites


* gocdbpi/?method=synchronise_egi_service_endpoints
*gocdbpi/?method=synchronise_egi_service_endpoints


* gocdbpi/?method=synchronise_egi_downtimes
*gocdbpi/?method=synchronise_egi_downtimes


* gocdbpi/?method=synchronise_egi_users
*gocdbpi/?method=synchronise_egi_users


* gocdbpi/?method=synchronise_egi_roles
*gocdbpi/?method=synchronise_egi_roles


<br>
<br>

Revision as of 16:27, 15 June 2011

Transfer Mechanism

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 objects (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 a regional GOCDB:

  • gocdbpi/?method=synchronise_egi_sites
  • gocdbpi/?method=synchronise_egi_service_endpoints
  • gocdbpi/?method=synchronise_egi_downtimes
  • gocdbpi/?method=synchronise_egi_users
  • gocdbpi/?method=synchronise_egi_roles