Difference between revisions of "GOCDB/Roadmap"

From EGIWiki
Jump to: navigation, search
(Created page with "{{Template:Op menubar}} {{Template:GOCDB_menubar}} {{TOC_top}} Category:GOCDB ==Current Developments== * See EGI RT tracker: https://rt.egi.eu/rt/Dashboards/5541/GOCDB-Requi...")
 
(Current Roadmap)
 
(6 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
[[Category:GOCDB]]
 
[[Category:GOCDB]]
  
==Current Developments==
+
==Current Roadmap==
* See EGI RT tracker: https://rt.egi.eu/rt/Dashboards/5541/GOCDB-Requirements
+
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-->
 +
* See EGI RT tracker (queue is GOC-DB): https://rt.egi.eu/rt/Search/Results.html?Query=Queue%20%3D%20%27GOC-DB%27)
 +
 
 
<!--* Also priortised in following doc: https://documents.egi.eu/secure/ShowDocument?docid=1997-->
 
<!--* Also priortised in following doc: https://documents.egi.eu/secure/ShowDocument?docid=1997-->
 
<!--* Feedback received on the new system is given at: [[GOCDB/Release4/Feedback]]-->
 
<!--* Feedback received on the new system is given at: [[GOCDB/Release4/Feedback]]-->
  
 +
<!--
 
===Support different AAI schemes===
 
===Support different AAI schemes===
* Add support for Federated Identity Management (FIM) to allow authentication other than x509
+
* 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).  
 
* 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).  
  
===Audit Trail===
+
===Change Logging===
* History log, i.e. who did what and when such as updating data, approving roles (July 2015 - June  2016, EUDAT M4-M15)
+
* Record who did what and when, record object diffs pre/post change (July 2015 - June  2016, EUDAT M4-M15)
 
 
<!--
 
===Extensiblity mechanism (Key-Value pair property bags - expected Dec13/Jan14)===
 
* RT: https://rt.egi.eu/rt/Ticket/Display.html?id=3764
 
* [[GOCDB/Release4/Development/ExtensibilityMechanism]] <br/>
 
* Simiar to the GLUE2 extensibility mechanim, the core GOCDB entities (NGIs, Sites, Services, ServiceGroups, Endpoints) will be extended so that they can define an optional set of custom key-value pairs with PI query support.
 
-->
 
  
 +
===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 Service Registry Requirements===
* Investigate if GOCDB could be extended for use as public-facing service registry for science-applications, and assess feasibility and benefit. This would probably need to cover: un-authenticated users, service SLAs, pay-for-use details, service access/usage policies, service-capabilities, other extra info...  
+
* 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...  
  
  
Line 46: Line 47:
 
** 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>
 
</strike>
<!--** [[GOCDB/Release4/Development/VSites#VO_Feed_for_ATP]]-->
 
 
  
  
 
===Enhance Data Model===
 
===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.
+
* 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===
 
===Provide Service and ServiceEndpoint PIDs===
Line 61: Line 60:
 
===Enhance UI===
 
===Enhance UI===
 
* Introduce a more capable MVC framework to improve the UI and user experience
 
* Introduce a more capable MVC framework to improve the UI and user experience
 
+
-->
===Investigate Abstraction of Business Rules===
 
* Investigate if the GOCDB business rules could be abstracted using 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
 
  
 
<!--  
 
<!--  

Latest revision as of 10:06, 6 March 2017

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