|
|
| Line 1: |
Line 1: |
| {{Template:Op menubar}} | | {{Template:Op menubar}} |
| {{Template:GOCDB_menubar}} | | {{Template:GOCDB_menubar}} |
| {{TOC_top}}
| |
| [[Category:GOCDB]]
| |
|
| |
|
| ==Current Developments==
| | This page has moved to [[GOCDB/Roadmap]] |
| * See EGI RT tracker: https://rt.egi.eu/rt/Dashboards/5541/GOCDB-Requirements
| |
| <!--* 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]]-->
| |
| | |
| ===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)
| |
| | |
| <!--
| |
| ===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 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...
| |
| | |
| | |
| ===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
| |
| <strike>
| |
| * [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
| |
| **[[GOCDB/Release4/Regionalisation|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.
| |
| </strike>
| |
| <!--** [[GOCDB/Release4/Development/VSites#VO_Feed_for_ATP]]-->
| |
| | |
| | |
| | |
| ===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 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
| |
| | |
| <!--
| |
| {|{{egi-table}}
| |
| ! development item !! Estimated release !! Estimated date
| |
| |-
| |
| | Provide a production quality package for GOCDB regional module || 4.0d7 || Oct 2010
| |
| |-
| |
| | Improvement of GOCDB failover system and backend replication || 4.0.1 || May 2011
| |
| |-
| |
| | New service endpoint URL associations for new service types (see above) || ? || April/June 2011
| |
| |-
| |
| | Re-develop GUI Logic (see above) || ? || Sept 2011 (EGI-Y2)
| |
| |-
| |
| | Update/refactor role model for finer grained permissions (see above) || ? || EGI-Y2
| |
| |-
| |
| | Data scoping by tagging GOCDB entities (see above) || ? || EGI-Y2
| |
| |-
| |
| | Regionalisation [[GOCDB/Release4/Regionalisation]] || ? || EGI-Y2/3
| |
| |-
| |
| | Work on GOCDB and Operations Portal common front end || ? || EGI-Y2
| |
| |-
| |
| | GOCDB interface to the dynamic information system (BDII/GluE) || ? || EGI-Y3
| |
| |}
| |
| -->
| |
| | |
| <!--
| |
| | Consolidation and polishing of the web admin interface for GOCDB regional module || 4.0.2 || Mar 2011
| |
| |-
| |
| | Provide a SOAP interface to GOCDB in parallel to GOCDBPI || 4.0.2 || Mar 2011
| |
| |-
| |
| | Provide a MySQL version of the GOCDB regional module || 4.1 || May 2011
| |
| |-
| |
| | GOCDB interface to MyEGEE framework or equivalent || ? || EGI-Y2
| |
| |-
| |
| -->
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.