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 9: | Line 9: | ||
<!--* Feedback received on the new system is given at: [[GOCDB/Release4/Feedback]]--> | <!--* Feedback received on the new system is given at: [[GOCDB/Release4/Feedback]]--> | ||
=== | ===GOCDB v5 - Supports different RDBMS=== | ||
* [[Doctrine]] | * Support for multiple RDBMs using Doctrine ORM [[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 ( | ** 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 (early Sept). | ||
* RT: https://rt.egi.eu/rt/Ticket/Display.html?id=4516 | ** RT: https://rt.egi.eu/rt/Ticket/Display.html?id=4516 | ||
===GOCDB v5 - Extend Scoping to Support Multiple Projects/Target Infrastructures=== | |||
* [[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). | |||
<!-- | <!-- | ||
| Line 21: | Line 24: | ||
== Post v5 Roadmap == | == Post v5 Roadmap == | ||
<!-- | <!-- | ||
===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] | ||
--> | --> | ||
===Multiple Endpoints Per Service=== | ===Multiple Endpoints Per Service=== | ||
Revision as of 15:32, 5 August 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.
GOCDB v5 - Supports different RDBMS
- Support for multiple RDBMs using Doctrine ORM 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 (early Sept).
- RT: https://rt.egi.eu/rt/Ticket/Display.html?id=4516
GOCDB v5 - Extend Scoping to Support Multiple Projects/Target Infrastructures
- GOCDB/Release4/Development/conditionalCertificationStatusRules
- This involves extending the current scoping logic so a single GOCDB instance can support sites and services belonging to multiple Target Infrastructures (scopes).
Post v5 Roadmap
Multiple Endpoints Per Service
Render GOCDB data in GLUE2 Format
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
- 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] 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.