Alert.png 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 @


From EGIWiki
Jump to navigation Jump to search

<< 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.
(related: [GOCDB development items is available in the EGI RT ticket tracker])

The GOCDB role/permissions model will be updated

in order to cater for a finer grained permissions currently emerging as a new EGI requirement. More information available here: 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 '' 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)


Support Multiple GRIS Endpoints


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:



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

Development Roadmap