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/Release4/Development"
Jump to navigation
Jump to search
| Line 17: | Line 17: | ||
<!-- | <!-- | ||
===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: | * 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] | ||
--> | --> | ||
Revision as of 14:42, 1 December 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.
- See: [GOCDB development items is available in the EGI RT ticket tracker]
- Feedback received on the new system is given at: GOCDB/Release4/Feedback
Release v4.5: GUI improvements and MVC/Query2XML full rollout
- ~Jan 2013
- Relevant RT: 1017, 1092, 1102, 1423, 1696, 4374, 4465, 4466
Multiple Endpoints Per Service
Render GOCDB data in GLUE2 Format
Extensiblity mechanism (Key-Value pair property bags)
- RT: https://rt.egi.eu/rt/Ticket/Display.html?id=3764
- GOCDB/Release4/Development/ExtensibilityMechanism
- 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.
Update Site Certification and Target Infrastructure Rules
- GOCDB/Release4/Development/conditionalCertificationStatusRules
- This involves conditional enforcement of site certification status transition rules depending on the Site's Target Infrastructure (Production or Test).
Support for a new RDBMS
- GOCDB currenlty relies heavily on Oracle PLSQL. Support is required for a new open source database.
Longer Term / Unconfirmed Roadmap
- [Not confirmed] Support for VOs (maybe query SEs by supported VO)
[Not confirmed] Regionalisation- RT: https://rt.egi.eu/rt/Ticket/Display.html?id=2788
- GOCDB4 Regionalisation Status and Plans - More details on regionalisation and progress of Standalone deployments within NGIs.
- GOCDB/Release4/Regionalisation/Transfer_Mechanism
- GOCDB/Release4/Regionalisation/Data_Transfer_Format
- GOCDB/Release4/Regionalisation/PI_Updates
- [Not confirmed] VO Feed for ATP GOCDB/Release4/Development/VSites/VOFeedXML
- Use the Service Groups (VSites) to build a VO feed for ATP.