PaaS on OpenStack:Give App Teams What They Want While Accelerating IT Agility

SUSECon SPR1445

Chris HadadWSO2 Technology Evangelist

Frank RegoSUSE Business Development

2

Cloud Computing Hype Cycle: Get Ready

3

PaaS Defined

• Build applications for the cloud that are portable, elastically scalable, and automated governance.

• Develop applications on a uniform platform, using common middleware and database back-end

• Reduce CAPEX (through reduced software licensing fees) and OPEX (through higher integration).

4

Technology Trends Shaping PaaS

• Rise in cloud based DevOps and Application Lifecycle Management (ALM) adaptation

• Rise in demand for hybrid cloud configurations

• Big data analysis and complex event processing in the cloud

• Greater emphasis on required change management and cost benefits when enterprise organizations select aPaaS instead of Cloud-enabled Application Platform (CEAP)

5

Why Adopt PaaS?

• Faster Time to Market

• Portfolio Efficiency

• Enhanced Productivity

6

PaaS Can Crush DevOp Challenges

• Long time and significant effort required to create application project environment(s)

• Complex integration required to extend core application capabilities and bridge consumers

• Difficult to enforce governance best practices and policies

• Time consuming, manual process to obtain project status, dependencies, and change impact

7

Goal Category Metric Market Category Assists

   PaaS

FrameworkPaaS

Framework + Middleware

PaaSFramework +

DevOps + ALM

   

     

Time to MarketTime and effort to create new application environment Yes Yes Yes

Time to Market Time to redeploy application Yes Yes Yes

Time to MarketTime to promote application into a new lifecycle phase No No Yes

Portfolio Efficiency

Ability to dynamically right-size infrastructure and elastic scalability Yes Yes Yes

Portfolio Efficiency

Ability to re-use existing platform services and business services from resource pool instead of re-building solution stack

No No Yes

ProductivityTime and effort required integrating business process, event processor – creating a complex app.

No Yes Yes

ProductivityTime and effort required to apply policy across tenant(s) Yes Yes Yes

ProductivityCost to operate application per user or transaction measured against the value provided by the application or transaction.

Partial Yes Yes

Comparing PaaS Distributions

8

WSO2 PaaS Offering(s) – Key Differentiators• A complete set of Cloud-Native middleware services enabling

complex project delivery

• Enterprise-ready foundation

• Scale, performance, SLA, integration

• Re-shapes team collaboration and reduces wait states

• Incorporates DevOps processes

• Fosters Application Lifecycle Management and Governance best practices

• Business driven PaaS

• CxO Dashboards

• Showback / Chargeback

• Service catalogue and subscription management

9

OpenStack

10

Partner OpportunityCloud Architecture Transformation

WSO2 Carbon

middleware images

Application Containers &

Services

WSO2 Stratos PaaS Controller

WSO2 Stratos Foundation Services

11

WSO2 Private PaaS Key differentiators: Inherently multi-tenant, polyglot runtime, enterprise-class services

12

WSO2 Cloud Native Advantage

• Automated governance

• DevOps tooling

• Multi-tenant platform

• On-demand self service

• Elastic scalability

• Service-aware load balancing

• Cartridge extensibility

13

Cloud-Native Log Service

14

http://wso2.com/whitepapers/cloud-native-advantage-multi-tenant-shared-container-paas

Cloud-Native Tenancy

15

Cloud-Native Load BalancingTenant-Aware and Service-Aware

16

Cloud-Native Application Delivery

17

DevOp Principles

• Iterative

• Incremental

• Continuous

• Automated

• Self-service

• Collaborative

• Holistic

18

DevOps Processes

• Self-service configuration

• Automated provisioning

• Continuous build

• Continuous integration

• Continuous delivery

• Automated release management

• Incremental testing

19

DevOps Tooling

• Self service project and policy configuration– Via project configuration portals

– Security, service levels, frameworks, usage, topology

• Automated platform provisioning– Via service tier templates

– Framework and policy enforcement points (PEPs)

• Process automation– Continuous build, test, and deployment

– Code promotion and synchronization across environments and servers

• Dependency analysis and impact analysis

20

Defining Governance

• Ensuring people do the right thing

• Make doing the right thing the easy path– via automation

• Spans precepts, policies, people, and process

• Governance applies to many domains– Design and development

– Operational processes and run-time environment

– Organizational resources

• Effective governance requires a big picture view of portfolio and dependencies

21

Unified, Full Life Cycle DevOps

22

WSO2 App Factory

23

To Establish Responsive Iterations,Increase DevOps Automation

24

https://appfactorypreview.wso2.com

WSO2 App Factory

25

Why Choose DevOps PaaS

• For Developers– Simplifies project setup and provisioning– Fits into their existing IDE (i.e. Eclipse, IDEA, Rational)– Works with leading development tooling (i.e. SVN, Git, Junit, Selenium,

Maven, Jenkins, Bamboo, and JIRA)

• For Operators– Instant provisioning– Automated governance

• For DevOps managers– Manage project lifecycle with well defined checkpoints and phases– Ensures projects follow governance model and best practices– Provides consistent frameworks and architecture

• For the CIO and Executive IT management– Development dashboards deliver at a glance view of projects’ status, lifecycle,

activity, and health

26

Measuring PaaS Outcomes

• Foundation

– Time and effort to create new application environment

– Time to redeploy application

– Time to promote application into a new lifecycle phase

• Optimize

– Dynamically right-size infrastructure scale

– Re-use existing platform services and business services from resource pool instead of re-building solution stack

• Transformation

– Time and effort required integrating business process, event processor – creating a complex application

– Time and effort required to apply policy across tenant(s)

– Cost to operate application per user or transaction

27

Paas On OpenStack Use Cases

• DevOps Automation and Governance– Deployment

– Deploying assets to Cloud

– Lifecycle promotion

– Promoting cloud applications across development, test and production clouds

– Policy decisions and enforcement

28

PaaS on OpenStack Use Cases

• DevOps Tooling and On-demand self-service– Use Cases

– Rapidly provision application environment

– Rapidly provision application tenant

– Allocate, provision, monitor, manage, and administer resources across multiple tenants, nodes, and locations

– Develop complex, composite integrated applications

– Key Metrics

– Time to create new application environment

– Time to redeploy application

29

PaaS on OpenStack Use Cases

• Automated Governance– Use Cases

– Create users and configure rights

– Deploy on preferred topology that meets deterministic performance requirements (e.g., replication, utilization, latency, bandwidth, and coherency)

– Create service throttling and security governance (XACML) policies

– Key Metrics

– Time and effort required integrating business process, event processor – creating a complex application

– Time and effort required to apply policy across tenant(s)

30

Why WSO2 PaaS? Gain the Advantage

31

WSO2 Complete Platform Advantage

• Complete

• Composable

• Cohesive

32

Complete, Composable PlatformApplication, Integration, Analytics, Identity, Data

33

Middleware, Cloud, and DevOps

34

WSO2 Enterprise-Ready Advantage

• Scale and Performance

• Enterprise governance

• Identity and Entitlement Management

• Re-shape Architecture

35

PaaS Evaluation Framework – Production Ready

• PaaS Maturity– Suitability for enterprise and mission critical use

– Service level agreement (SLA) quality

– Quality of Service warranted by the service provider

– Service level management capabilities

– Resource monitoring and management

– Resource quota and performance management

– Traffic orchestration

36

Selected Customer Scenarios

Using WSO2 ESB as API Gateway, 3.5bn transactions on one day Christmas 2012, 2.2bn average/day

WSO2 API Manager in production, managing all internal and external APIs

OEM of Governance Registry, shipping as part of their products

ESB, Rules, Identity, BAM

Governance Registry

WSO2 ESB and Data Services as the backbone for their iPhone App

Managing 3m identities using OpenId with WSO2 Identity Server

Using WSO2 Governance Registry to govern a complete end-to-end SOA

Using WSO2 ESB, Business Process Server, Data Services and others to run a complete SOA

37

WSO2 API-centric Advantage

• Managed APIs

• Enterprise Integration Patterns (EIP)

• Application services governance

• Hybrid integration infrastructure

38

WSO2 Cloud-Native Advantage

• Automated governance

• DevOps tooling

• Multi-tenant platform

• On-demand self service

• Elastic scalability

• Service-aware load balancing

• Cartridge extensibility

39

WSO2 DevOps Advantage

• Complete lifecycle automation

• Collaboration oriented

• Project workspaces and dashboards

• Continuous delivery

40

PaaS Evaluation Framework

• DevOps Activities and Phases– Automated provisioning, self-service configuration, continuous

integration, continuous delivery, automated release management, incremental testing

– PaaS integration with on-premise software development life-cycle tooling

– Automated governance including:

– Service catalogue and service tiers

– Demand and capacity management

– Lifecycle management

– Infrastructure authority integration

41

WSO2 Open Source Advantage

• Rapid innovation

• Affordability

• Visibility

• Flexibility

42

http://wso2.com/landing/gartner-compares-vendors-of-comprehensive-application-infrastructure-suites/Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose

WSO2: The only Open Source visionary in all 3 application infrastructure categories

4322

SLES

WSO2

Application

WSO2

SUSE Cloud

WSO2

SUSE Cloud

WSO2

SUSE Cloud

WSO2

SUSE Cloud

. . . . .

. .

Dev platform:• Tools• Languages• Libraries• Runtime

Same as above with:• Self service• Scaling• Metering• Multi-tenancy

WSO2 delivers the only 100% open source complete middleware platform from

on-premise to the cloud for developing large-scale, elastic and

cloud-ready enterprise

applications.

Enterprise Middleware

PaaS

44

• Complete – Recognized by Gartner as the only open source vendor with a complete middleware platform.

• Adaptable – Customizable to match your unique architectural needs

• Leading edge –Solutions for big data, event processing, social enterprise and ecosystems, and cloud.

• Deploys anywhere – Same code runs as standalone servers, or as a private or public PaaS

• Enterprise-ready – Commercial support acclaimed by Fortune 1000/Global 2000 customers worldwide.

• SUSE-ready – Reference architecture based on SUSE Linux Enterprise and certified/supported on SUSE Linux Enterprise Server and SUSE Cloud

Magic Quadrant for On-Premises Application Integration Suites

45

Validated, enterprise-ready open source Middleware and PaaS solution for

enterprise and private cloud deployments

+ =

WSO2 certified on SUSE Cloud and SLES

Reference architecture for WSO2 Stratos on SUSE Cloud

Joint sales engagements

SUSE membership in Apache Stratos

Unpublished Work of SUSE. All Rights Reserved.This work is an unpublished work and contains confidential, proprietary, and trade secret information of SUSE. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.