EGI-InSPIRE EGI-InSPIRE RI Developing the concept of a service marketplace for EGI Diego Scardaci EGI.eu/INFN

Outline Session agenda Service Marketplace analysis in EGI-InSPIRE PY5 Service Marketplace analysis in EGI-Engage (TJRA1.2) User stories EGI Conference, Amsterdam, September 20142

Session Agenda EGI Conference, Amsterdam, September Session 1 –09:00-09:20 “Developing the concept of a service marketplace for EGI” – Diego Scardaci, EGI.eu/INFN –09:20-09:50 “Marketplace & service catalogue concepts, first design analysis” – Dean Flanders, SWITCH –09:50-10:30 Open Discussion What other functionalities are needed in the marketplace? What functionalities are needed in the service catalogue? How do they relate to each other? What is the relationship with the pay-for-use activity and business model? Session 2 –11:00-11:45 “Overview of existing tools/solutions for a Service catalogue and marketplace” – David Meredith, STFC –11:45-12:30 Open Discussion How to integrate a service catalogue and marketplace in the EGI infrastructure? Which open source tools can we re-use ? Can we re-use and extend current EGI tools?

EGI Conference, Amsterdam, September Service Marketplace analysis Main aim of this session is starting-up the service marketplace design activity in EGI-InSPIRE –Funded activity in EGI-InSPIRE PY5 (Sept – Dec) Targets: –Evaluation of the already existing tools/solutions to offer service registry and marketplace features in the EGI infrastructure –Evaluation of the EGI tools to understand if they already offer "service registry and marketplace" features (e.g. GOCDB -> registry, e-GRANT -> SLA management, AppDB -> UI) how they could/should be extended to offer "service registry and marketplace" features –Understand how a future EGI service registry and marketplace could be integrated with the current EGI tools and, more in general, the EGI infrastructure.

EGI Conference, Amsterdam, September Service Marketplace analysis Teams involved: –AppDB –GOCDB –e-GRANT –IRIS (from SWING) –EGI.eu Policy Team Strong link with the Pay-for-Use PoC Service Registry and Marketplace Working Group mailing list: Interested to participate into the Marketplace analysis? Please, write me!

EGI Conference, Amsterdam, September Service Marketplace in EGI-Engage The activity will continue in EGI-Engage under WP3 (JRA1) E-Infrastructure Commons –Task JRA1.2 – Service Registry and Marketplace (Lead: SWING, M1 – M30) (22.5 PM) Activity will be led by Dean Flanders (SWING) Partners involved –SWING (7 PM) –INFN (6.5 PM) –CYFRONET (3 PM) –GRNET/IASA (3 PM) –STFC (3 PM)

EGI Conference, Amsterdam, September From EGI-Engage proposal –Simplify the access to the infrastructure services through technological innovation and new services in the area of Service Registry and Marketplace… The Marketplace will allow customer to acquire services: –through a payment –for free, through a negotiation to establish a SLA and policies with the service providers The output of the Pay-for-Use PoC and of design analysis running in EGI-InSPIRE will be inputs for this task Target –development of a proof-of-concept of a Service Registry and a Marketplace for the EGI infrastructure Service Marketplace in EGI-Engage

EGI Conference, Amsterdam, September D3.2 - Design of the EGI Service Registry and Marketplace (R) (M12) –Main features offered by the Service Registry and Marketplace –Definition of the functions offered by the services (user stories) –Which external tools could be adopted to speed-up the deployment in the EGI infrastructure –Which EGI tools could be extended to include and offer Service Registry and Marketplace features –Interfaces to exchange information with analogue tools belonging to other e-infrastructures or research infrastructures: create a network of analogue tools spanning different infrastructures. It will allow to provide users with integrated view off all the infrastructures involved. EGI-Engage – JRA1.2 Timeline (1/2)

EGI Conference, Amsterdam, September D3.7 - First release of the EGI Service Registry and Marketplace prototype (DEM) (M18) –First release of the Service Registry and Marketplace proof-of-concept prototype deployed in the EGI infrastructure for testing D Second release of the EGI Service Registry and Marketplace prototype (DEM) (M26) –Second release of the Service Registry and Marketplace proof-of-concept prototype D Final report on EGI Service Registry and Marketplace (R) (M30) –EGI Service Registry and Marketplace activities during the whole project –Description of the final proof-of-concept prototype released, feedback collect by the users and guideline for the future developments will be reported EGI-Engage – JRA1.2 Timeline (2/2)

EGI Conference, Amsterdam, September Service Marketplace User Stories (1/4) The service provider publishes a service –The service provider (SP) registers a new service in the Service Catalogue –The SP can assign a SLA to the new service –The SP assigns a price to the new service (can be 0, for free) –The SP can define a policy to access the service –The new service is available in the service catalogue The customer discovers the existing services –The customer accesses the Service Catalogue and get the list of offered services –The customer can look for a service with specific characteristics/requirements (search engine) –The customer can read the details of a service: description, SLA, price, SPs list, etc.

EGI Conference, Amsterdam, September Service Marketplace User Stories (2/4) The customer directly selects and buys a service –The customer accesses the Service Catalogue and look for a service –The customer chooses the service to buy –The customer may negotiate the SLA through a broker or accept the pre-defined SLA associated to the service –The customer buys the service The customer selects a service through a broker –The customer lists the requirements that should be satisfied by the service he’s looking for –The broker identifies the best service according to the customer’s requirements –The broker offers the selected service to the customer –The customer evaluates the offered service, may negotiate the SLA through a broker or accept the pre-defined SLA –The customer buys the service

EGI Conference, Amsterdam, September Service Marketplace User Stories (3/4) The customer reviews and rates a service and/or a service provider –The customer selects a service from the list of bought services –The customer reviews and rates the service and/or the service provider The customer wants to check the status of his orders The customer consults the consumption/usage The customer manages the service (add/remove users, define quotas ?) A Service Provider manages the published services –A Service Provider registers into the service catalog –Hide previously published services / changes the conditions associated / highlight the services / announce a maintenance break

EGI Conference, Amsterdam, September Service Marketplace User Stories (4/4) A Service Provider checks the information associated to services –The SP controls the accounting information related to their services (usage, number of users, average consumption). They can control either by service published or total …

Questions ? EGI Conference, Amsterdam, September