Difference between revisions of "GOCDB/Release4/Development"

From EGIWiki
Jump to: navigation, search
(Support for Virtual Site Entities (VSite))
(The GOCDB role/permissions model will be updated)
Line 32: Line 32:
 
** Scope Specific Search
 
** Scope Specific Search
 
-->
 
-->
===The GOCDB role/permissions model will be updated===  
+
===Update Roles and Permissions===  
in order to cater for a finer grained permissions currently emerging as a new EGI requirement. More information available here: [[GOCDB/Release4/Development/NewRoles]]
+
[[GOCDB/Release4/Development/NewRoles]]
  
 
===Establish a central GOCDB readonly failover===
 
===Establish a central GOCDB readonly failover===

Revision as of 19:22, 1 February 2012

<< Back to GOCDB/Documentation_Index

Current Developments

The developments we are currently working on are listed below. They come from the agreed development list, as defined by the Operational Tools Advisory Group (OTAG) who filters and prioritizes user requests.
(related: [GOCDB development items is available in the EGI RT ticket tracker])

Update Roles and Permissions

GOCDB/Release4/Development/NewRoles

Establish a central GOCDB readonly failover

A central GOCDB webportal failover will be installed at Fraunhofer ITWM. A DNS switch for the 'goc.egi.eu' domain between the production server and the failover server is in place. Once installed, the failover will be readonly in order to prevent data-synchronization problems.

Support for Virtual Site Entities (VSite)

GOCDB/Release4/Development/VSites

Support Multiple GRIS Endpoints

GOCDB/Release4/Development/MultipleGRIS

Redevelop the xml_output module to implement nested XML collections [not confirmed]

probably using the Query2XML package. This is necessary because the existing XML Output module will only generate flat XML documents (e.g. that often map to individual DB entities). Currently SQL joins/associations between Sites, SEs and URLs cannot be represented as hierarchical/nested XML documents (for example, consider nesting multiple EndpointLocation objects and URLs within a single ServiceEndpoint element, see: Media:GocdbGlue2UnicoreV2.pdf). It is likely that this is a requirement for regionalisation to implement the proposed XML 'synch' docs described at: https://wiki.egi.eu/wiki/GOCDB/Release4/Regionalisation/Data_Transfer_Format

Regionalisation

Feedback

Feedback received on the new system is given at: GOCDB/Release4/Feedback

Development Roadmap