© CaaSt Consortium. All rights reserved. The research leading to these results has received funding from the European Union's Seventh Framework Programme ([F7/ ) under grant agreement n° CaaSt Overview

4CaaSt: addressing PaaS Cloud in all dimensions 2 4CaaSt will address challenges in Utility-like provisioning of “Platforms as a Service” ( PaaS ) enabling advanced application hosting 4CaaSt will carry out RTD in components enabling 4CaaSt-compliant PaaS Clouds to become true business ecosystems 4CaaSt will address RTD in built- in native Cloud libraries providing the best programming framework

Dimension 1: Cloud Hosting 3 Virtualization of processing and networking end-to-end Higher level of abstraction through advanced service life-cycle management based on blueprint RT scaling and adaptation based on convergent QoS management Support of service platform technologies as immigrants on the cloud 4CaaSt will address challenges in Utility-like provisioning of “Platforms as a Service” ( PaaS ) enabling advanced application hosting

Dimension 2: Business Ecosystem 4 How can I make money ? Marketplace functions — Multiple Business Terms and Conditions — Support to automated selection of app/services based on business criteria — Rating & Charging on multi-vendor composition — Payment/Settlement functions, considering Marketplace federation — Marketplace analytics How can I best promote my app ? Mashup as a Service — Be able to combine with apps/services from other app providers and the Cloud Provider — Let end users develop their own apps (DIY) 4CaaSt will carry out RTD in components enabling 4CaaSt-compliant PaaS Clouds to become true business ecosystems

Dimension 3: Programming Framework 5 Rich set of APIs accessible “as a Service” from apps hosted in the Cloud: — Network Enablers as a Service — Context(*) as a Service — Publish/Subscribe EAI as a Service — DataStore as a Service (*) Context in its widest meaning: Access Device+Network Description, User’s preferences, User’s Social Network, … Focus on standardization Context EAI Network Enablers Data … 4CaaSt will address RTD in built- in native Cloud libraries providing the best programming framework

4CaaSt will bring an unique value proposition to application providers 6 How to minimize CAPEX and ensure OPEX do not grow faster than actual demand of my customers How to better position my application and make money How to develop application faster and based on advanced features that would be hard for me to implement on my own

mashable comps SaaS apps/components catalogue Application Provider perspective: deployment 7 4CaaSt Platform services App backend 3. Application provider designed apps PaaS Self-Service Portal 1. For a given application, an Application Provider can: 1.Deploy the application’s backend on the 4CaaSt Platform 2.Choose a revenue model (pay per use, share, ads) and bundling conditions 3.Register suites of gadgets linked to its front-end (if mashup- oriented) as mashable components in the SaaS catalogue 4.Register some mashups (or an URI to the application’s web portal) as designed applications in the SaaS catalogue The Cloud acts as a “clearing house”, dealing with settlement and payment with app providers SaaS ecosystem/delivery framework Application Blueprint SaaS Marketplace infrastructure 1.

4CaaSt Platform services App backend SaaS ecosystem/delivery framework End-user perspective: self-servicing 8 SaaS Desktop End users End users (SMEs, individuals): 1.Search for designed apps in the SaaS catalogue, relying on statistics, recommendations from other users, demo videos, etc. 2.Purchase applications they wish to use. Special offerings, promotional campaigns, etc would apply. Some applications might be available for free (indirect revenues) 3.Add purchased applications to their SaaS desktop. mashable comps SaaS apps/components catalogue designed apps SaaS Marketplace infrastructure

PaaS: Application Hosting A 4CaaST-compliant Cloud will support one or a set of Platforms on which application hosting is offered “as a Service” to Application Providers It will allow migration across platforms Platform A Web serverPython VM Object Table 4CaaST-compliant Cloud 1 Platform A Web serverPython VM Object Table 4CaaST-compliant Cloud 2 Platform B Web server servlet engine RDBMS Platform C J2EE container RDBMSBPEL engine Platform technologies 1. choose

PaaS: Application Blueprints Application provider registers the BluePrint associated to the applications it hosts on a 4CaaSt-compliant Cloud An Application Blueprint specifies, in a declarative manner, the various aspects linked to the application that any 4CaaST-compliant Cloud needs to know as to properly manage the lifecycle of the application, setup the runtime environment hosting the application, etc. Platform A Web server Python VM Object Table 4CaaST-compliant Cloud 2 2. register A1C2 A1C3 A1C1 Application Blueprint SLA(cost rules Target KPIs third-party app/services used … Exported services

Advanced hosting capabilities Processing the Application BluePrint, 4CaaSt determines the best architecture for the runtime environment and deploy it using APIs provided by the underlying IaaS and NaaS layers 11 Platform A Web server Python VM Object Table Runtime Execution Container Load Balancer Python VM A1C2AnC1 Virtual Machine Runtime Platform Runtime Execution Container Web Server A1C1 Virtual Machine … … HTTP Load balancer Web Servers farmApp Servers farm A1C3 DBRepository Service MMS/SMS system MMS/SMS Service API 3. resolve A1C2 A1C3 A1C1 Application Blueprint SLAs Target KPIs third-party app/services used … Exported services

Scalable Platform VM Platform Scalability Service Provider ‘s view of the Platform Application 1 Servlet DB Virtual Tomcat 4.0 Virtual Postgres 8.1 LoadBalancer Tomcat Instance Tomcat Instance … Postgres Instance Application 2 PHP DB Virtual Posgrest 8.1 Virtual Apache 2.0 VM LoadBalancer Apache Instance Apache Instance …

General Architecture eMarketPlace Service Lifecycle Manager Service Lifecycle Manager Resource Manager Monitoring Administration PaaS Interface Self-service Portal NaaS Storage Cloud Interface Storage Cloud Interface IaaS Interface IaaS Interface XaaS RECManager Enablers Resource Provisioning Service Layer Resource Layer Provisioning Layer …

Conclusions 4CaaSt addreses a holistic view of what Cloud means – Not just hosting but marketplace and generic services support PaaS hosting complements the IaaS hosting offering: target customers may be different – SMEs and individual programmes that are Application Providers – Large companies that have defined an internal standard platform for their Operation and Business Support Systems – IaaS still makes sense for those companies (large or SMEs) and programmers that want to keep control and fine tune the architecture of the execution infrastructure The Open Source nature of many of the software developments in 4CaaSt may help to implement a collaboration with third parties not involved in the initial consortia

© CaaSt Consortium. All rights reserved. The research leading to these results has received funding from the European Union's Seventh Framework Programme ([F7/ ) under grant agreement n°