1. EGI OMB 24/11/2017 George Ryall David Meredith
GOCDB 5.7 Release
EGI OMB 24/11/2017
George Ryall
David Meredith

2. GOCDB 5.7
Release process started (
Plan to deploy December 7th (assuming testing is satisfactory
Test server: gocdb-test.esc.rl.ac.uk
Release notes:

3. Three main changes Write API
assists WLCG to reduce dependence on BDII)
Add/update/delete custom properties defined on Sites/Services/Endpoints using a REST API.
Documentation:
Following the release of 5.7, the write API will be running ‘AT_RISK’ for a few weeks while we closely monitor the extra loading. Should this load impact on the operation of the rest of GOCDB, we will shut down the write API in order to address the issue.

4. Three main changes New attributes on service endpoints
Enables ARGO to remove dependency on BDII)
New boolean ‘monitored’ flag, exposed through read API
New field for adding contact details for the SE
The SE is NOT currently rendered in the output of the 'get_service' method, as this method has a Level 1 protection level which is considered a public method containing no critical information and no personal /details ( If s are needed, we can either:
Elevate the protection level of the get_service method to Level 2 (which means a certificate would be needed to query the method)
Relax EGI/GOCDB protection level rules so that Level 1 can include site/service s but no personal s, note however there would still be a risk that personal s would still be added.

5. Three main changes Optional cursor based paging on Read API
This release applies optional CURSOR-based paging to the majority of the API methods and includes XML output changes !
It replaces the current OFFSET-based paging that is available on the ‘get_downtime*’ methods due to possible data inconsistency issues when offset-paging over real-time data,
Most of the API methods now support optional 'next_cursor' and 'prev_cursor' URL params.
For backward compatibility, pagination is disabled by default and will only be enabled when passing one of the new cursor query params
Paged XML results introduce the <meta> element which contain links to the current/self, next, previous and first page of results.
More details in the release notes