1. www.cloud4soa.eu FIA Workshop March, 17, 2014 A multi-PaaS application management system Panagiotis Gouvas (SingularLogic) euprojects@singularlogic.eu

2. Context and Motivation  Young and fragmented market: The actual PaaS market is, quite young, chaotic and highly fragmented, dominated by a few providers which use and promote their incompatible standards and formats  Vendor Lock-in and Adoptions barriers Cloud solutions lock customers in a single platform preventing the portability of data and software; Interoperability and portability are a few of the main challenges to adoption of Cloud Computing 2  Platform as a Service: Novel paradigm that enables Software Developers to create (develop or integrate), deploy, execute, and manage business applications, using a service provided by third party (SaaS fashion).

3. PaaS Portability/Interoperability PaaS Interoperability as the Ability for different cloud to talk to each other at three different levels (Software, PaaS, IaaS) PaaS Portability as the capability to operate software on different platforms without the need for changes Lock-in when there is significant cost to switch cloud vendors PaaS Interoperability at PaaS Level C# PaaS Interoperability at Software Level PaaS Interoperability at IaaS Level PaaS Interoperability as the ability of applications and data to be managed and migrated between Cloud PaaS offerings that are using the same technological background but different concepts and Application Programming Interfaces (APIs).

4. 4 Integrated and open-source multi-PaaS applications management system Adapters provide APIs and drivers essential for connecting to cloud PaaS providers Cloud4SOA system Cloud4SOA ecosystem Manage - Monitor Developer A A A A Migrate Search - Deploy Multiplatform Matchmaking ManagementMonitoringMigration What is Cloud4SOA about? Simplifies the access and lifecycle management for Cloud-based application developers Through innovative graphical user and command line interfaces (integrated in Eclipse IDE)

5. Harmonized Application Monitoring Application SLA Management layer Application Management Harmonized Application Monitoring Application SLA Management layer Application Management Toolbox that provides intelligent Service Publication, Discovery and Matchmaking, Recommendation and Migration. Formal representation of information by means of the Cloud4SOA ontology. Acts as an intermediary between the Cloud4SOA platform and the various PaaS offerings allowing the applications to be independent from specific PaaS offering implementations. Intelligent Interface to support the user understand the data presented by the interface and efficiently interact with the data presented.

6. Cloud4SOA ontology  Specification: 5 layers  Conceptualization: both top-down and bottom-up approach  Implementation OWL formalism  Evaluation 6

7. Matchmaking algorithm 7

9. Harmonization Layer

10. Santa Clara, USA, 3-5 April 2013 CAMP Member Meeting  Oracle, Rackspace, Red Hat, Google, CloudSoft, Huawei Technologies and Software AG among participants Standardization

11.  CAMP goal: “CAMP aims to provide an API (Application Programming Interface) for a set of commands for controlling PaaS workloads along with specifications on how to package a workload also addressed as Deployment Unit ”  Cloud4SOA goal: “Cloud4SOA is providing an open semantic interoperable framework for Platform as a Service (PaaS) developers and providers, capitalizing on Service Oriented Architecture (SOA), lightweight semantics and user-centric design and development principles” 11 Goals of CAMP vs Cloud4SOA

12. Collaboration with CAMP Cloud4SOA has already created 'Adapters' for 6 PaaS providers: AWS Beanstalk, Cloudbees, Heroku, CloudControl, CloudFoundry & OpenShift  Experience in existing diversities A common API is already formulated that covers the needs of these 6  Act as Validation for a possible RI

13. Lessons Learnt (1/2) Interoperability is inversely proportial to market adoption (to the insentive of adoption) Interoperability Adoption -Fixed Vocabularies -Strongly Typed Models -RI capabilities are given -Strict Assertion Policies -Baby Vocabularies PaaS-defined expressivity -RI varies -Loose Assertion (no-CAMP conformance) What is here?

14. Lessons Learnt (2/2) Almost everything was ideal until we touched the issue of non-archive based devlopment – Injection of source code : inevitable (Openshift,CloudControl …) – Who takes the responsibility? If SLA enforcement comes into play the challenge is even bigger – No concrete monitoring abstraction can be formulated (boundaries between PaaS / IaaS)

15. introducing Cloud Pier Visit: http://www.opencloudpier.orghttp://www.opencloudpier.org Github: https://github.com/cloudpierhttps://github.com/cloudpier

16. Any Questions? Panagiotis Gouvas euprojects@singularlogic.eu FIA Workshop March 17, 2014