GOCDB/Roadmap

Main

EGI.eu operations services

Support

Documentation

Tools

Activities

Performance

Technology

Catch-all Services

Resource Allocation

Security

GOC DB menu:

Home •

Documentation Index •

Current Roadmap

Current roadmap: https://wiki.egi.eu/wiki/EGI-Engage:TASK_JRA1.4_Operations_Tools#GOCDB

• Other core developments are currently being prioritised as part EGI Engage project within WP3, a summary of some of the main areas are given below.
• See EGI RT tracker: https://rt.egi.eu/rt/Dashboards/5541/GOCDB-Requirements

Support different AAI schemes

• Add support for Federated Identity Management (FIM) to allow authentication other than x509.
• Depends on outcome of EGI Engage AAI working group.
• Extend the authentication system for different open-access modes allowing un-authenticated users to browse the public-facing services/resources in read-only mode (hiding selected/sensitive data).

Change Logging

• Record who did what and when, record object diffs pre/post change (July 2015 - June 2016, EUDAT M4-M15)

Customise Roles per Project

• Abstract the GOCDB Roles/RoleTypes so they can be customised per project for improved multi-tenant project hosting. Potentially use a Business Rules Management Engines (BRMS), and assess feasibility and benefit: currently GOCDB enforces a number of EGI specific business rules and access policies. These could be abstracted into a separate module (or external system) to allow other resources in different projects/scopes to apply different rule-sets and policies for their resources.

Investigate Service Registry Requirements

• Investigate how GOCDB can support a front/public-facing service registry for science-applications. This would probably need to cover: un-authenticated users, service SLAs, pay-for-use details, service access/usage policies, service-capabilities, other extra info...

Render GOCDB data in GLUE2 Format

• GOCDB/Release4/Development/GLUE2Compatibility.

Insert-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 (http://www.ogf.org/documents/GFD.209.pdf).
• RT: https://rt.egi.eu/rt/Ticket/Display.html?id=4935

• [Not confirmed] Support for VOs (maybe query SEs by supported VO)
• [Not confirmed] Regionalisation
  • RT: https://rt.egi.eu/rt/Ticket/Display.html?id=2788
  • GOCDB4 Regionalisation Status and Plans - More details on regionalisation and progress of Standalone deployments within NGIs.
  • GOCDB/Release4/Regionalisation/Transfer_Mechanism
  • GOCDB/Release4/Regionalisation/Data_Transfer_Format
  • GOCDB/Release4/Regionalisation/PI_Updates
• [Not confirmed] VO Feed for ATP GOCDB/Release4/Development/VSites/VOFeedXML
  • Use the Service Groups (VSites) to build a VO feed for ATP.

Enhance Data Model

• Extend the data model to more effectively support clouds, virtual infrastructures new resource types, marketplace e.g. by supporting more attributes from the GLUE2 standard and the currently evolving GLUE2.1 cloud extensions.

Provide Service and ServiceEndpoint PIDs

• e.g. leverage the EPIC PID service (www.pidconsortium.eu) to assign PIDs to Services and Endpoints
• Creates a longtime stable and unique service-id, assigned when a new SE is created.
• ID could be resolvable such as the EPIC/Handle PIDs are.
• Provide at least one new specific PID field which can be entered by site (service-endpoint) managers.

Enhance UI

• Introduce a more capable MVC framework to improve the UI and user experience