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 @ egi.eu.

Difference between revisions of "GOCDB/Release4/Development"

From EGIWiki
Jump to navigation Jump to search
Line 36: Line 36:
**[[GOCDB/Release4/Regionalisation/Data_Transfer_Format]]
**[[GOCDB/Release4/Regionalisation/Data_Transfer_Format]]
**[[GOCDB/Release4/Regionalisation/PI_Updates]]
**[[GOCDB/Release4/Regionalisation/PI_Updates]]
</strike>
* [Not confirmed] VO Feed for ATP [[GOCDB/Release4/Development/VSites/VOFeedXML]]
* [Not confirmed] VO Feed for ATP [[GOCDB/Release4/Development/VSites/VOFeedXML]]
** Use the Service Groups (VSites) to build a VO feed for ATP.  
** Use the Service Groups (VSites) to build a VO feed for ATP.  
</strike>
<!--** [[GOCDB/Release4/Development/VSites#VO_Feed_for_ATP]]-->
<!--** [[GOCDB/Release4/Development/VSites#VO_Feed_for_ATP]]-->



Revision as of 09:45, 4 September 2014

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security


GOC DB menu: Home Documentation Index


Current Developments

The developments we are currently working on are listed below.


Multiple Endpoints Per Service

Render GOCDB data in GLUE2 Format

Insert-downtime PI method

Support different AAI schemes

  • Add support for Federated Identity Management (FIM) to allow authentication other than x509
  • Extend the authentication system to simplify user-access: a modular architecture will be adopted to allow easy extension and integration with different AAI systems, especially for Federated Identity Management (FIM). This would also include an open-access mode allowing un-authenticated users to browse the public-facing services/resources in read-only mode (hiding selected/sensitive data).

Audit Trail

  • History log, i.e. who did what and when such as updating data, approving roles (July 2015 - June 2016, EUDAT M4-M15)

Enhance Data Model

  • Extend the data model to more effectively support clouds, virtual infrastructures new resource types, 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

Investigate Service Registry Requirements

  • Investigate requirements for GOCDB as a public-facing service registry for science-applications, e.g. would need to cater for; un-authenticated users, service SLAs, pay-for-use details, service access/usage policies, service-capabilities, other extra info...