Difference between revisions of "GOCDB/Release4/Development"

From EGIWiki
Jump to: navigation, search
(Longer Term / Unconfirmed Roadmap)
(Replaced content with "{{Template:Op menubar}} {{Template:GOCDB_menubar}} This page has moved to GOCDB/Roadmap")
(28 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Template:Op menubar}}
{{Template:Op menubar}}
==Current Developments==
This page has moved to [[GOCDB/Roadmap]]
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.<br/>
* See: [[https://rt.egi.eu/rt/Search/Results.html?Format=%27%20%20%20%3Cb%3E%3Ca%20href%3D%22__WebPath__%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__id__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3A%23%27%2C%0A%27%3Cb%3E%3Ca%20href%3D%22__WebPath__%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__Subject__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3ASubject%27%2C%0A%27__Status__%27%2C%0A%27__QueueName__%27%2C%0A%27__OwnerName__%27%2C%0A%27__Priority__%27%2C%0A%27__NEWLINE__%27%2C%0A%27%27%2C%0A%27%3Csmall%3E__Requestors__%3C%2Fsmall%3E%27%2C%0A%27%3Csmall%3E__CreatedRelative__%3C%2Fsmall%3E%27%2C%0A%27%3Csmall%3E__ToldRelative__%3C%2Fsmall%3E%27%2C%0A%27%3Csmall%3E__LastUpdatedRelative__%3C%2Fsmall%3E%27%2C%0A%27%3Csmall%3E__TimeLeft__%3C%2Fsmall%3E%27&Order=ASC|ASC|ASC|ASC&OrderBy=id|||&Query=Queue%20%3D%20%27requirements%27%20AND%20%28%20%20Status%20%3D%20%27new%27%20OR%20Status%20%3D%20%27open%27%20OR%20Status%20%3D%20%27accepted%27%20OR%20Status%20%3D%20%27developed%27%20OR%20Status%20%3D%20%27stalled%27%20OR%20Status%20%3D%20%27feedback%27%20%29%20AND%20%27CF.{Category%20%28level%202%29}%27%20LIKE%20%27GOCDB%20%28Operational%20Tools%29%27%20AND%20Queue%20%3D%20%27requirements%27%20AND%20%27CF.{Category%20%28level%201%29}%27%20LIKE%20%27Operational%20Tools%27&RowsPerPage=50&SavedChartSearchId=new&SavedSearchId=RT%3A%3AUser-3851-SavedSearch-1174 GOCDB development items is available in the EGI RT ticket tracker]]
* Feedback received on the new system is given at: [[GOCDB/Release4/Feedback]]
===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).
===Release v4.5: GUI improvements and MVC/Query2XML full rollout===
* ~Jan 2013 depending on above
* Relevant RT: 1017, 1092, 1102, 1423, 1696, 4374, 4465, 4466
== Longer Term / Unconfirmed Roadmap ==
===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]
===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).
===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===
* [[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)
* <strike>[Not confirmed] Regionalisation
** RT: https://rt.egi.eu/rt/Ticket/Display.html?id=2788
**[[GOCDB/Release4/Regionalisation|GOCDB4 Regionalisation Status and Plans]] - More details on regionalisation and progress of Standalone deployments within NGIs.
* [Not confirmed] VO Feed for ATP [[GOCDB/Release4/Development/VSites/VOFeedXML]]
** Use the Service Groups (VSites) to build a VO feed for ATP.
<!--** [[GOCDB/Release4/Development/VSites#VO_Feed_for_ATP]]-->
! development item !! Estimated release !! Estimated date
| Provide a production quality package for GOCDB regional module || 4.0d7 || Oct 2010
| Improvement of GOCDB failover system and backend replication || 4.0.1 || May 2011
| New service endpoint URL associations for new service types (see above) || ? || April/June 2011
| Re-develop GUI Logic (see above) || ? || Sept 2011 (EGI-Y2)
| Update/refactor role model for finer grained permissions (see above) || ? || EGI-Y2
| Data scoping by tagging GOCDB entities (see above) || ? || EGI-Y2
| Regionalisation [[GOCDB/Release4/Regionalisation]] || ? || EGI-Y2/3
| Work on GOCDB and Operations Portal common front end || ? || EGI-Y2
| GOCDB interface to the dynamic information system (BDII/GluE) || ? || EGI-Y3
| Consolidation and polishing of the web admin interface for GOCDB regional module || 4.0.2 || Mar 2011
| Provide a SOAP interface to GOCDB in parallel to GOCDBPI || 4.0.2 || Mar 2011
| Provide a MySQL version of the GOCDB regional module || 4.1 || May 2011
| GOCDB interface to MyEGEE framework or equivalent || ? || EGI-Y2

Latest revision as of 10:04, 2 April 2015