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 4: Line 4:




== 1) Data Grouping/Scoping (Separate EGI and Non-EGI Data in Regional-Standalone and Central GOCDB) ==
== 1) Data Grouping/Scoping ==
'''(Separate EGI and Non-EGI Data in Regional-Standalone and Central GOCDB)'''
* Confirmed Development
* Confirmed Development
A GOCDB instance (central or regional) 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).
A GOCDB instance (central or regional) 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).
Line 10: Line 11:
'''Notes:'''
'''Notes:'''
* This will require GUI enhancements, allowing sites to opt-in or opt-out of the EGI group, and new request parameters for restricting the PI queries based on group memberships (e.g. “method=get_site_list_by_group&group=EGI” or “&group=local” or “&group=any”).
* This will require GUI enhancements, allowing sites to opt-in or opt-out of the EGI group, and new request parameters for restricting the PI queries based on group memberships (e.g. “method=get_site_list_by_group&group=EGI” or “&group=local” or “&group=any”).
* This development is a '''pre-requisite in order to subsequently publish the appropriate data for a''' [[#Regional-Synchronised GOCDB]].  
* This development is a '''pre-requisite in order to subsequently publish the appropriate data for a''' [[#3) Regional-Synchronised GOCDB]].  


'''Use Cases:'''
'''Use Cases:'''
Line 16: Line 17:
* Single point to input/query data for EGI and local/regional data.  
* Single point to input/query data for EGI and local/regional data.  
* Regional GOCDB installation not required (e.g. for NGIs without effort to install/maintain a regional gocdb).
* Regional GOCDB installation not required (e.g. for NGIs without effort to install/maintain a regional gocdb).


== 2) Regional-Standalone GOCDB ==
== 2) Regional-Standalone GOCDB ==
Line 36: Line 39:
* It may be necessary to have two-way synchronisation, where the central instance would also update regional instances: https://rt.egi.eu/rt/Ticket/Display.html?id=1094.
* It may be necessary to have two-way synchronisation, where the central instance would also update regional instances: https://rt.egi.eu/rt/Ticket/Display.html?id=1094.
* NGI extensions and ''custom data would not be synchronised'' with the central GOCDB, therefore;
* NGI extensions and ''custom data would not be synchronised'' with the central GOCDB, therefore;
* [[#Separate EGI and Non-EGI Data (Data Grouping/Scoping)]] is necessary in order to publish the appropriate data.  
* [[#1) Data Grouping/Scoping]] is necessary in order to publish the appropriate data.  


'''Use Cases:'''
'''Use Cases:'''

Revision as of 18:27, 17 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. In order to achieve 3), both 1) and 2) are required first.


1) Data Grouping/Scoping

(Separate EGI and Non-EGI Data in Regional-Standalone and Central GOCDB)

  • Confirmed Development

A GOCDB instance (central or regional) 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).

Notes:

  • This will require GUI enhancements, allowing sites to opt-in or opt-out of the EGI group, and new request parameters for restricting the PI queries based on group memberships (e.g. “method=get_site_list_by_group&group=EGI” or “&group=local” or “&group=any”).
  • This development is a pre-requisite in order to subsequently publish the appropriate data for a #3) Regional-Synchronised GOCDB.

Use Cases:

  • Users can centrally include/exclude sites/SEs from the from the whole EGI infrastructure as required (provides extensible data visibility/scoping according to groupings).
  • Single point to input/query data for EGI and local/regional data.
  • Regional GOCDB installation not required (e.g. for NGIs without effort to install/maintain a regional gocdb).


2) Regional-Standalone GOCDB

  • Confirmed Development

We will continue to release a standalone instance of the GOCDB for regional NGI use. This regional instance will be supported regardless of other developments. We will ensure that future developments don't conflict with requirements from NGIs by capturing the NGIs requirements.

Use Cases:

  • Customisable by NGIs
  • Support available centrally


3) Regional-Synchronised GOCDB

  • Long Term Development

A regional-standalone GOCDB instance will synchronise is EGI scoped regional data with the central instance.

This would allow NGIs to deploy their own GOCDB, customise it and publish EGI data (constrained by XML schema) to the central portal. Publishing of this data would have to be transactional, most probably via a schema constrained WS/REST interface (preferable over asynch messaging which would require response queues + ACKs). The central portal would be the definitive source for all EGI information.

Notes:

Use Cases: