GOCDB/Transfer Mechanism

From EGIWiki
< GOCDB
Revision as of 17:26, 15 June 2011 by Jcasson (talk | contribs) (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…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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