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 Regionalisation Plans"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
= Regionalisation Plans =
= Regionalisation Plans =
== Introduction ==
== Introduction ==
Our current regionalisation status is described in [[GOCDB/Release4/Regionalisation | GOCDB4 Regionalisation Status]]. This page describes our future plans for regionalisation.
Our future plans for regionalisation are described here. To see our cur current regionalisation status please visit [[GOCDB/Release4/Regionalisation | GOCDB4 Regionalisation Status]]. .


== Plan ==
== Separate EGI and Non-EGI Data ==
A GOCDB instance needs to differentiate between EGI and non-EGI data. This functionality will be implemented in the near future enabling the centrally run GOCDB to contain both EGI and non-EGI data. (This is described as "Design A" in https://rt.egi.eu/rt/Ticket/Display.html?id=943#txn-52051)
A GOCDB instance needs to differentiate between EGI and non-EGI data. A new group named EGI will be created along with tool to insert / remove data to and from a specified group. With this functionality in place NGIs will be able to store and retrieve both local and EGI level sites in the central GOCDB. (This plan is from "Design A" in https://rt.egi.eu/rt/Ticket/Display.html?id=943#txn-52051).
 
== Regional/Central Synchronisation ==
A long term goal for GOCDB is to synchronise regional GOCDB data to the central instance.

Revision as of 15:13, 4 March 2011

Regionalisation Plans

Introduction

Our future plans for regionalisation are described here. To see our cur current regionalisation status please visit GOCDB4 Regionalisation Status. .

Separate EGI and Non-EGI Data

A GOCDB instance needs to differentiate between EGI and non-EGI data. A new group named EGI will be created along with tool to insert / remove data to and from a specified group. With this functionality in place NGIs will be able to store and retrieve both local and EGI level sites in the central GOCDB. (This plan is from "Design A" in https://rt.egi.eu/rt/Ticket/Display.html?id=943#txn-52051).

Regional/Central Synchronisation

A long term goal for GOCDB is to synchronise regional GOCDB data to the central instance.