Difference between revisions of "GOCDB/Release4/Development"

From EGIWiki
Jump to: navigation, search
(Support for a new RDBMS)
(Longer Term / Unconfirmed Roadmap)
Line 20: Line 20:
  
 
== Longer Term / Unconfirmed Roadmap ==
 
== Longer Term / Unconfirmed Roadmap ==
===Multiple Endpoints Per Service===
 
* RT: https://rt.egi.eu/rt/Ticket/Display.html?id=3347
 
* [[GOCDB/Release4/Development/MultipleGRIS]]
 
 
<!--
 
<!--
 
===Redevelop the xml_output module to implement nested XML collections===  
 
===Redevelop the xml_output module to implement nested XML collections===  
 
* 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: [GOCDB/Release4/Regionalisation/Data_Transfer_Format]
 
* 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: [GOCDB/Release4/Regionalisation/Data_Transfer_Format]
 
-->
 
-->
 
===Extensiblity mechanism (Key-Value pair property bags)===
 
* RT: https://rt.egi.eu/rt/Ticket/Display.html?id=3764
 
* [[GOCDB/Release4/Development/ExtensibilityMechanism]] <br/>
 
* Simiar to the GLUE2 extensibility mechanim, the core GOCDB entities (NGIs, Sites, Services, ServiceGroups, Endpoints) will be extended so that they can define an optional set of custom key-value pairs with PI query support.
 
  
 
===Extend Scoping to Support Multiple Projects/Target Infrastructures===
 
===Extend Scoping to Support Multiple Projects/Target Infrastructures===
 
* [[GOCDB/Release4/Development/conditionalCertificationStatusRules]] <br/>
 
* [[GOCDB/Release4/Development/conditionalCertificationStatusRules]] <br/>
 
* This involves extending the current scoping logic so a single GOCDB instance can support sites and services belonging to multiple Target Infrastructures (scopes).
 
* This involves extending the current scoping logic so a single GOCDB instance can support sites and services belonging to multiple Target Infrastructures (scopes).
 +
 +
===Multiple Endpoints Per Service===
 +
* RT: https://rt.egi.eu/rt/Ticket/Display.html?id=3347
 +
* [[GOCDB/Release4/Development/MultipleGRIS]]
  
 
===Render GOCDB data in GLUE2 Format===  
 
===Render GOCDB data in GLUE2 Format===  
 
* [[GOCDB/Release4/Development/GLUE2Compatibility]].
 
* [[GOCDB/Release4/Development/GLUE2Compatibility]].
 +
 +
===Add downtime PI method===
 +
* [Not confirmed] Programatic/writable PI query to insert downtimes as an alternative to the portal GUI.
 +
* Probably would use GLUE2 XML as message format (GFD is in prep).
 +
* RT: https://rt.egi.eu/rt/Ticket/Display.html?id=4935
 +
 +
===Extensiblity mechanism (Key-Value pair property bags)===
 +
* RT: https://rt.egi.eu/rt/Ticket/Display.html?id=3764
 +
* [[GOCDB/Release4/Development/ExtensibilityMechanism]] <br/>
 +
* Simiar to the GLUE2 extensibility mechanim, the core GOCDB entities (NGIs, Sites, Services, ServiceGroups, Endpoints) will be extended so that they can define an optional set of custom key-value pairs with PI query support.
 +
  
 
* [Not confirmed] Support for VOs (maybe query SEs by supported VO)
 
* [Not confirmed] Support for VOs (maybe query SEs by supported VO)
* [Not confirmed] Programatic/writable PI queries to insert/update data as an alternative to the portal GUI
 
 
 
* <strike>[Not confirmed] Regionalisation
 
* <strike>[Not confirmed] Regionalisation
 
** RT: https://rt.egi.eu/rt/Ticket/Display.html?id=2788
 
** RT: https://rt.egi.eu/rt/Ticket/Display.html?id=2788

Revision as of 12:48, 7 February 2013

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


GOC DB menu: Home 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.

Support for a new RDBMS

  • Doctrine
  • GOCDB currently relies heavily on Oracle PLSQL. Support is required for a new open source database. We are currently developing a new DB agnostic GOCDB back-end using an ORM mapping framework called Doctrine. This is planned for release in GOCDB v5 (~April/May).


Longer Term / Unconfirmed Roadmap

Extend Scoping to Support Multiple Projects/Target Infrastructures

Multiple Endpoints Per Service

Render GOCDB data in GLUE2 Format

Add downtime PI method

Extensiblity mechanism (Key-Value pair property bags)