Difference between revisions of "GOCDB/Release4/Development"

Revision as of 15:55, 18 April 2012

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])

Support Multiple Endpoints Per Service

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

GOCDB4 Regionalisation Status and Plans - More details on regionalisation and progress of Standalone deployments within NGIs.

Feedback

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

Development Roadmap

v4.1 Released 01 Nov 2011 https://www.sysadmin.hep.ac.uk/svn/grid-monitoring/tags/gocdb/GOCDB-4.1/gocdb/changeLog.txt
v4.2 Released 25 Nov 2011 (includes Scoping) https://www.sysadmin.hep.ac.uk/svn/grid-monitoring/tags/gocdb/GOCDB-4.2/gocdb/changeLog.txt
Central GOCDB failover in place, end Dec 2011.
v4.3 Finer grained roles/permissions, Jan 2012
v4.4 Virtual Sites (VSites), ~March 2012
[Not confirmed] Replace current XML output module to cater for nested XML collections
[Not confirmed] Generating valid GLUE2 XML document from GOCDB data, see: GOCDB/Release4/Development/GLUE2Compatibility.
[Not confirmed] Support for VOs (maybe query SEs by supported VO)
A re-prioritization exercise will then determine the next major developments.

@@ Line 4: / Line 4: @@
 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/>
 (related: [[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]])
-<!--
-===The object cardinality logic needs to be refactored===
-to fix known issues, particularly Domain, Production-Status and Service-Endpoint objects.
--->
-<!--
-===Data Scoping in the Central GOCDB===
-Expected approx end Nov. The following tasks need to be completed to introduce scoping to the central GOCDB instance. "DONE" means completed in our current development version of GOCDB and not necessarily put into production.
-* Enable database level tagging to allow scoping of data - <b>DONE</b>
-* Modify PI queries to be scope aware (e.g. get_downtime?scope=Regional) - <b>DONE</b>
-* Atomic database access - <b>IN PROGRESS</b>
-* Add scoping capability to the web portal - <b>IN PROGRESS</b>
-** This is being achieved through MVC implementation of inserting / editing objects
-*** Add / Edit Service Endpoint - <b>DONE</b>
-*** Add / Edit Site - <b>DONE</b>
-*** Add / Edit Downtime  - <b>DONE</b>
-*** Add / Edit User - <b>DONE</b>
-*** Add / Edit Role - <b>IN PROGRESS</b>
-* Remove old Non-MVC code - <b>IN PROGRESS</b>
-* Remove old XML Input code
-* Indicate what scope data has in the web portal
-** When viewing an individual object
-** When viewing a table of objects
-* Add scope specific web portal views
-** View Local Sites
-** View EGI Sites
-** Scope Specific Search
--->
-===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 Endpoints Per Service===