1. GOCDB Handover + Status Update Quite heavy GGUS ticketing traffic; responding to user issues has been quite timely, especially in first few weeks (expected after newly released v4 – slowing now). Many instances where user permissions not properly propagated between v3 + v4 (users with political roles do not have corresponding technical roles). Varied fire-fighting – usually requires manual interaction with the DB (PL/SQL). Decommissioned a number of ROCs and moved sites to newly created NGIs (e.g SW Europe, NW Europe). Lots of more simple bug fixes (largely RexEx refinements / validation).

2. Bug and Task lists have grown (normal after major release). 18 Known bugs https://savannah.cern.ch/bugs/?group=gocdbhttps://savannah.cern.ch/bugs/?group=gocdb 30 Savannah tasks / dev requests https://savannah.cern.ch/task/?group=gocdbhttps://savannah.cern.ch/task/?group=gocdb 15 RT tasks / dev requests Servers updated (yesterday) to support secure SSLReneogotiation (an important security vulnerability with the SSL protocol – MiM attacks). Web clients have to support (RFC 5746). Firefox, IE, Chrome, and Opera all support RFC 5746 (Safari not yet). DNS updated (goc.egi.e), Wiki moved. GOCDB Handover + Status Update Cont…

3. Next TODOs / Priorities Understand, then consolidate/prioritise growing list of development requests and tasks (have started merging Savannah and RT tickets this week). Reviewing the RT tickets today will help me here. Expand proposal for service endpoint URLs and GLUE2 service naming conventions and Virtual sites (present at next weeks f2f). Started adding a Unit and Integration test suite (vital to understand code, should be in place before I am confident to tackle more significant changes). Failover db in Germany (switched with DNS) to be established. Probably use Oracle streams if possible. Work through bug list and dev request lists. Other: Improve inline phpDoc, absorb Oracle PL/SQL programming language (used to define PROM API).

4. Notes when reviewing RT Requirements Tickets #931 – New roles in GOCDB and renaming of existing roles GM added Chief Operations Officer, but does not yet have permissions over all regions / NGIs (would have synchronization implications for regionalizing the infrastructure). Merge ‘Regional Staff’ + ‘Regional Front Line Supporter’ into ‘Regional Operations Staff’ Are there any repercussions on other tools ? #939 – Requirement for history of sites’ Certification Status Will require new timestamp's and audit/history table(s) to record these changes and corresponding PI methods (maybe GUI support too?). #940 – Site status transitions Need to enforce rules about which site status transitions are allowed (and by whom) in the site certification procedure, e.g. examples of disallowed transitions: Closed –> Any Suspended –> Certified (only allowable by Regional Manager) Candidate –> Certified Candidate –> Suspended

5. #941 – Enhance Browsing Functionality OK #943 – Mask Site from entire EGI community Require a way to restrict the visibility of sites at the EGI level (just install a regional GOCDB?). If we have to regionalize GOCDB, consider sync issues (e.g. ticket # 931). # 944 – New GOCDB Service Types / GLUE2 Ok – to discuss/present at f2f next week. # 945 - New Early Adopter downtime type Special downtime type for EAs ? Or A new EA group to identify those EA sites ? New flag to mark a site as an EA ? # 973 - Declare downtimes on VOs / list which VOs are supported by particular services GOCDB does not store VO info (yet). Prob need to retrieve EGI VOs from Ops Portal WS. # 979 – Extensions for decommissioned ROCs/NGIs Query / display info for decommissioned ROCs in PI/GUI.