EGI Marketplace Prototype: Requirements and Roadmap

EGI marketplace prototype: requirements and implementation roadmap Dean Flanders Friedrich Miescher Institute / Swiss National Grid Association EGI Conference 2016 Amsterdam, April 6th2016 www.egi.eu EGI-Engage is co-funded by the Horizon 2020 Framework Programme of the European Union under grant number 654142

Primary Goal The goal of the marketplace and service registry activity is to design a simple entry point for researchers to discover and access resources and services from those interested in making them available, either as central portal or as custom views for organizations and communities. As mentioned in the Activity Summary: Marketplace and Service Registry 3/12/2025 2

Benefits of the EGI Marketplace Optimize Discover Accelerate Help optimize resource utilization by sharing of resources and tools to manage resources. To help researchers discover local, national, and international resources available to them. In allowing researchers to discover and access cutting edge resources they will be able to accelerate their research activities. 3/12/2025 3

Key Functional Requirements Easy discoverability of resources and services, with advanced filtering and information on capability and service levels. Resources and services with the ability for users to rate them. Ability for service providers of the EGI federation to register a resource or service and make it available to others. This could any be any type of academic or commercial service or resource relevant to research (data, software, instruments, services, etc.). Ability to define visibility and access to resources or services by user, research group, organization, project, and community. Only exposing resources and services to the right audience. Customizable views that can be defined for labs, communities, and organizations. Integration with federated identity management solutions to simplify access for users. Possibility for resource providers to define usage quotas and statistics. Users can access free and for fee resources and services. Resource providers can manage the lifecycle of services and resources via requests, authorisation, usage, accounting, and billing. As mentioned in the Activity Summary: Marketplace and Service Registry 3/12/2025 4

Long Term Vision of the Marketplace Research Group Resources Organization Resources Consortiums EGI Marketplace Commercial Vendor Resources NGI Resources Goal to have a one stop shop for resources . As defined in the deliverable D2.3 Concept of EGI Marketplace 3/12/2025 5

Steps to take to get there In the initial phase the EGI Marketplace will provide a list of EGI available services from the EGI Service Portfolio (i.e. those with OLAs with EGI and that can provide SLAs). The marketplace should then be extendable with the addition of services from other service providers in order that it can be used for them to provide a service catalog of their own, which can include services from the EGI Marketplace . Providers retain responsibility for their own services These then can be included into thematic or general purpose collections within the EGI Marketplace with UAs. Insert footer here 3/12/2025 6

EGI Role in the Marketplace Promotion of EGI service portfolio of compute, storage, data, security, operations, and training resources. Support the ability of communities to build collections of services which is essential to engagement to the long tail of science. Ability to add EGI quality statement to resource providers. In the long term this can offer opportunities for generation of persistent identifiers for data generated. 3/12/2025 7

Survey Results of Essential Features ESSENTIAL / IMPORTANT IMPORTANT NOT Rate the following functionalities: service description direct link to the service filter by... status of the service: up & running, down, etc.. visibility/access rules by user, group, organization, department, community, project categorization of EGI affiliation (e.g. integrated, endorsed, external) user rating visibility/access rules by VO 100% 100% 87% 87% 75% 56% 50% 44% 37% 31% 25% 0% 0% 13% 13% 25% 44% 50% 56% 63% 69% 75% prices negotiation phase visitors of this service have also viewed Survey results of users from from EGI.eu, Barcelona Supercomputing Center, SURFSara, EMBL- EBI, VENUS-C, France Grilles, DARIAH, STFC, MTA SZTAKI, Cyfronet, GRNET, CSC, the Lifescience Grid Community, Neugrid, iMarine, WeNMR 3/12/2025 8

High Level Architecture Directory Authentication (eduGAIN, social, enterprise, etc.) Group management (organizational, local, etc.) Attributes (billing information, ORCID, etc.) Etc. user organization community group directory Portal Search across all service types Different catalogs (AppDB, GOCDB, Helix Nebula, IRIS, etc.) Catalogs should deliver additional value to providers Can have multiple of the same type of catalog user profile Service Catalogs Search across all service types Different catalogs (AppDB, GOCDB, Helix Nebula, IRIS, etc.) Catalogs should deliver additional value to providers Can have multiple of the same type of catalog Resources from the catalog are administered via a resource provider. VM registry software etc. instruments cloud services API Modules Different plugins for catalogs (e-GRANT, etc.) Plugins should deliver additional value to service catalogs Not mandatory to the catalogs. Can have multiple of the same type of plugin proposals accounting / reporting billing persistent identifiers etc. Details in deliverable 3.2 of EGI-Enage Design of the EGI Service Registry and Marketplace . 3/12/2025 9

Directory Model audience description requirements trust Support for multiple affiliations and discover resources. users Anyone (academic, commercial, private, etc.) Track usage and billing information of resources used by their group. groups A group of people affiliated with one institution. A group of groups in an organization or across organizations. Can be used to provide access at levels of multiple groups in a department. departments Any legal entity (commercial, academic, NGO, association, etc.). A legal entity that can control users and groups, and handle billing. organizations A group of people affiliated with one or more organizations. projects Useful for providing access to data. Like an organization but with people and groups affiliated with one or more organizations. Useful for large collaborations across multiple institutions. communities Publish into a service catalog, authentication services, billing, etc. providers Can be a lab, core facility, commercial, etc. Details in deliverable 3.2 of EGI-Enage Design of the EGI Service Registry and Marketplace . 3/12/2025 10

Example Catalog of Resource Providers A broad collection of resource providers is essential in order to engage the long tails of science. 3/12/2025 11

Example Catalog of Resources/Services/Applications EGI services could appear along side of other resource providers to facilitate discovery. 3/12/2025 12

Existing Candidate Applications for the EGI Marketplace Various solutions were evaluated: AppDB GOCDB FIWARE Marketplace Generic Enabler Open IRIS PrestaShop WooCommerce The following have been shortlisted: AppDB Open IRIS Details in deliverable 3.2 of EGI-Enage Design of the EGI Service Registry and Marketplace . 3/12/2025 13

Feedback from Evaluators Solution Open IRIS AppDB FIWARE MP GE PrestaShop WooCommerce GOCDB Score Solution AppDB GOCDB Open IRIS FIWARE MP GE WooCommerce PrestaShop Score Solution AppDB GOCDB Open IRIS FIWARE MP GE WooCommerce PrestaShop Score 33 30 27 24 24 13 32 29 26 23 22 21 37 31 25 24 20 19 Adequacy of the solution against requirements Overall ranking of tools according to the envisaged costs in terms of licenses and support Is the solution supportable in terms of expertise within EGI Details in deliverable 3.2 of EGI-Enage Design of the EGI Service Registry and Marketplace . Insert footer here 3/12/2025 14

GOCDB, AppDB, and Open IRIS Match to Requirements Requirement Area Application Match GOCDB AppDB 20 20 40 Open IRIS Service Provider Directory Total 29 12 41 50 42 92 Based on original use cases from EGI and analyzed in deliverable 2.3 of EGI-Enage Concept of EGI Marketplace . Details in deliverable 3.2 of EGI-Enage Design of the EGI Service Registry and Marketplace . Insert footer here 3/12/2025 15

Roadmap Start Date (MM/YY) Completion Date (MM/YY) Dependencies From other tasks Task Number Status Task Name Evaluation of terms of use, legal requirements, costs of ownership, development and support Design and mockup of public facing marketplace. Development of public facing marketplace. Define technical integration of AppDB, GOCDB, and eGrant. Integration work for of AppDB, GOCDB, and eGrant Define EGI catalogues for demonstration purposes and populate service catalogue with EGI services. Test release of first version of public facing marketplace for EGI. First release of the EGI Service Registry and Prototype 03/2016 05/2016 Started None 1 03/2016 04/2016 Started None 2 3 04/2016 05/2016 Planned 2 4 03/2016 06/2016 Started 5 04/2016 07/2016 Planned 4 6 05/2016 06/2016 Planned 7 07/2016 07/2016 Planned 3, 5, 6 8 08/2016 08/2016 Planned 3, 5, 6 Insert footer here 3/12/2025 16

Summary A EGI Marketplace will be an entry point for researchers to discover services and resources. This will initially be limited to EGI services, but later extended to support other service providers, which can be combined into thematic or general collections. Further details need to be examined in terms of cost of ownership and operational model from the short listed options. Demonstrator to be released in August 2016. Insert footer here 3/12/2025 17

Thank you for your attention. Questions? www.egi.eu This work by Parties of the EGI-Engage Consortium is licensed under a Creative Commons Attribution 4.0 International License Creative Commons Attribution 4.0 International License.