150 likes | 259 Views
4CaaSt Overview. 4CaaSt: addressing PaaS Cloud in all dimensions. 4CaaSt will address challenges in Utility-like provisioning of “Platforms as a Service” ( PaaS ) enabling advanced application hosting.
E N D
4CaaSt: addressing PaaS Cloud in all dimensions 4CaaStwill address challenges inUtility-likeprovisioningof “Platforms as a Service” (PaaS) enabling advanced application hosting 4CaaStwill carry out RTD in components enabling 4CaaSt-compliant PaaS Clouds to become true business ecosystems 4CaaStwill address RTD in built-in native Cloud libraries providing the best programming framework
Dimension 1: Cloud Hosting 4CaaStwill address challenges inUtility-likeprovisioningof “Platforms as a Service” (PaaS) enabling advanced application hosting • 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
Dimension 2: Business Ecosystem 4CaaStwill carry out RTD in components enabling 4CaaSt-compliant PaaS Clouds to become true business ecosystems • 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)
Dimension 3: Programming Framework 4CaaStwill address RTD in built-in native Cloud libraries providing the best programming framework Context Data Network Enablers … EAI • Rich set of APIs accessible “as a Service” from apps hosted in the Cloud: • Network Enablersas 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
4CaaSt will bring an unique value proposition to application providers How to minimize CAPEX and ensure OPEX do not grow faster than actual demand of my customers How to develop application faster and based on advanced features that would be hard for me to implement on my own How to better position my application and make money
Application Blueprint Application Provider perspective: deployment • For a given application, an Application Provider can: • Deploy the application’s backend on the 4CaaSt Platform • Choose a revenue model (pay per use, share, ads) and bundling conditions • Register suites of gadgets linked to its front-end (if mashup-oriented) as mashable components in the SaaS catalogue • 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 SaaSecosystem/delivery framework 4CaaSt Platform SaaS apps/components catalogue designed apps mashable comps App backend services 3. 4. 2. 1. 1. SaaS Marketplace infrastructure PaaSSelf-Service Portal Application provider 7
End-user perspective: self-servicing SaaSecosystem/delivery framework 4CaaSt Platform • End users (SMEs, individuals): • Search for designed apps in the SaaS catalogue, relying on statistics, recommendations from other users, demo videos, etc. • Purchase applications they wish to use. Special offerings, promotional campaigns, etc would apply. Some applications might be available for free (indirect revenues) • Add purchased applications to their SaaS desktop. SaaS apps/components catalogue designed apps mashable comps App backend 1. 3. services 2. SaaS Marketplace infrastructure End users SaaSDesktop 8
PaaS: ApplicationHosting • A 4CaaST-compliant Cloud will support one or a set of Platforms on which application hosting is offered “as a Service” to Application Providers • Itwillallowmigrationacrossplatforms Platform technologies 1. choose Web server Python VM Object Table Platform A Web server servlet engine RDBMS Platform B Web server Python VM Object Table J2EE container BPEL engine RDBMS Platform A Platform C 4CaaST-compliant Cloud 1 4CaaST-compliant Cloud 2
PaaS: Application Blueprints Application Blueprint • SLA(cost rules • Target KPIs • third-party app/services used • … A1C1 A1C2 2. register A1C3 Exported services • 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. Web server Python VM ObjectTable Platform A 4CaaST-compliant Cloud 2
Advanced hosting capabilities Application Blueprint • 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 • SLAs • Target KPIs • third-party app/services used • … A1C1 A1C2 A1C3 Exported services MMS/SMS system Web Servers farm App Servers farm HTTP Load balancer Load Balancer MMS/SMS Service API 3. resolve Runtime Execution Container Runtime Platform Runtime Platform Runtime Execution Container Runtime Execution Container Runtime ExecutionContainer A1C1 … A1C2 AnC1 A1C3 Web Server Python VM DBRepository Service OS OS Web server Python VM Object Table Virtual Machine Virtual Machine Platform A
PlatformScalability Application 1 Application 2 Servlet PHP DB DB ServiceProvider ‘s view of thePlatform Virtual Tomcat 4.0 Virtual Posgrest 8.1 Virtual Postgres 8.1 Virtual Apache 2.0 ScalablePlatform LoadBalancer LoadBalancer VM VM VM VM VM Postgres Instance Apache Instance Tomcat Instance Apache Instance Tomcat Instance … …
General Architecture Self-service Portal PaaS Interface Service Lifecycle Manager eMarketPlace ServiceLayer Monitoring Administration Resource Manager ResourceLayer ResourceProvisioning Provisioning Layer RECManager Enablers Storage Cloud Interface IaaS Interface XaaS NaaS …
Conclusions • 4CaaSt addreses a holisticview of what Cloud means • Notjusthostingbutmarketplace and genericservicessupport • PaaShostingcomplementstheIaaShostingoffering: target customersmaybedifferent • SMEsand individual programmesthat are ApplicationProviders • LargecompaniesthathavedefinedaninternalstandardplatformfortheirOperation and Business SupportSystems • IaaSstillmakessenseforthosecompanies (largeorSMEs) and programmersthatwanttokeep control and fine tune thearchitecture of theexecutioninfrastructure • The Open Sourcenature of many of the software developments in 4CaaSt mayhelptoimplement a collaborationwiththirdpartiesnotinvolved in theinitialconsortia