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.

GOCDB Regionalisation Plans

From EGIWiki
Revision as of 16:04, 4 March 2011 by Jcasson (talk | contribs)
Jump to navigation Jump to search

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

- Confirmed Development

A GOCDB instance needs to differentiate between EGI and non-EGI data. A new group named EGI will be created along with tools 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 GOCDB

- On-Going Development

We will continue to release a regional instance of the GOCDB. This regional instance will be supported regardless of whether a synchronisation mechanism is implemented.

Use Cases

  • Completely customisable
  • Central support available

Regional/Central Synchronisation

- Potential Development

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

Use Cases

  • NGIs customise their own GOCDB
  • EGI data published to the central GOCDB
  • Single point for data input

Central Customisations

- Potential Development

The regional customisations to GOCDB would be implemented centrally. The customisations would be delivered only to specified NGIs through the grouping tools developed in "Separate EGI and Non-EGI Data".

This plan is preferable if the effort to implement NGI customisation requests is less than the effort to develop and support a synchronisation mechanism and support the NGIs in implementing the customisations themselves.

A regional non-synchronising GOCDB would still be available for NGIs with esoteric requirements.

Drop the Central Read Portal