Difference between revisions of "GOCDB/Roadmap"

From EGIWiki
Jump to: navigation, search
(Current Roadmap)
(Current Roadmap)
 
(2 intermediate revisions by the same user not shown)
Line 7: Line 7:
 
Current roadmap: https://wiki.egi.eu/wiki/EGI-Engage:TASK_JRA1.4_Operations_Tools#GOCDB  
 
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.  
 
* 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: 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.  
Line 21: Line 24:
 
===Customise Roles per Project===
 
===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.
 
* 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.
 
 
<!--
 
===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.
 
-->
 
 
  
 
===Investigate Service Registry Requirements===
 
===Investigate Service Registry Requirements===
Line 53: 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]]-->
 
 
  
  
Line 68: 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
 
+
-->
  
 
<!--  
 
<!--  

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