Platform as a Service (PaaS)Introduction and Options

Suresh Paulraj

So-Cal-DevOps-User-Group

2 of 21

SoCal-DevOps-User-GroupCloud Platform Evolution

The Cloud Platform Evolution

Traditional IaaS

Virtualization Platform

Operating System

Data

base

Web

Serv

er

Messagin

g

Application Code

Physical Servers

Data

base

Web

Serv

er

Messagin

g

IAAS

PAAS

IAAS

PaaS

Application Code Application Code

3 of 21

SoCal-DevOps-User-GroupTraditional IT, IaaS and PaaS

Traditional IT

Storage

Servers

Networking

O/S

Middleware

Virtualization

Data

Applications

Runtime

You M

anage

O/S

IaaS

Storage

Servers

Networking

Middleware

Virtualization

Data

Applications

Runtime

You M

anage

IaaS

O/S

PaaS

Storage

Servers

Networking

Middleware

Virtualization

Data

Applications

Runtime

PaaS+

Choice ofIaaS

Business Value, Agility & Cost Savings

You

Manage

The Power of PaaS (On Premise & Off Premise)

4 of 21

SoCal-DevOps-User-Group

Developer profile and demands

2000 2014

Developers are demanding rapid provisioning of platform and not environments

Software Engineer

•Coder

•Wants configuration

control when they need it

•Configures platform

services and resources

•Usually codes,

Configures platform and

deploys code

•Not pressed for

automation

Developer

•Coder

•Wants to program, not

manage infrastructure

•Avoids platform and

virtual resource

configuration

•Usually codes locally,

and deploys own stack to

cloud

•Demands automation

Rapid Developer

•Coder

•Wants high productivity,

not resource details

•Shuns platform and

virtual resource

configuration

•Develops in the Platform

as a Service

•Develops against the

Platform as a Service

Why PaaS ?

2007

5 of 21

SoCal-DevOps-User-GroupWhy PaaS – What Drives PaaS

Eliminates Platform installation and configuration

Eliminate Maintenance significantly

Out-of-Box integrations (Database, Middleware, CDN, etc)

Easy to scale – No Wait time (Elasticity)

Cost (Hardware, Software, Support and Maintenance)

Business Agility and Time to Market

6 of 21

SoCal-DevOps-User-GroupMajor PaaS Products in the market

-AWS - Elastic Bean Stack-Microsoft - Azure PaaS-RedHat - OpenShift-Pivotal Cloud Foundry – EMC, VMWare

7 of 21

SoCal-DevOps-User-GroupAWS – Elastic Bean Stalk (EBS)

-It help to quickly deploy and manage application in AWS Cloud-Simply upload application EBS automatically handles deployment details capacity provisioning, load balancing, auto scaling and

application health monitoring

-Select Platform-Select Application to upload-Run

8 of 21

SoCal-DevOps-User-GroupAWS – Elastic Bean Stalk (EBS)

Environment Tier – Web Environment Tier – Worker

9 of 21

SoCal-DevOps-User-GroupAWS – Elastic Bean Stalk (EBS) – Container Type

A container type defines the infrastructure topology and software framework to be used for that environment. For example, an AWS Elastic Beanstalk environment with an Apache Tomcat container uses the Amazon Linux operating system, Apache web server, and Apache Tomcat software.

• Docker• Docker - Preconfigured • Java • Windows and .NET • Node.js • PHP • Python • Ruby

10 of 21

SoCal-DevOps-User-GroupAWS – Elastic Bean Stalk (EBS) – Launch Information

Application Info

Application name : newapp

Description : my new app

New Environment

Tier : Web Server

Instance profile : aws-elasticbeanstalk-ec2-role

Environment Type

Container type : 64bit Amazon Linux 2014.09 v1.2.0 running Python 2.7

Environment type : Load balancing, auto scaling

Application Version

Application source : Sample application

Deployment settings : Deploy to 30% of the fleet at a time

Environment Info

Environment name : newapp-env

Environment URL : http://newapp-env-psk.elasticbeanstalk.com

Configuration Details

Instance type : t1.micro

Key pair

Email address

Root volume type

(default)

Root volume size

(default)

Root volume IOPS

(default)

Application health check URLEnvironment Tags

11 of 21

SoCal-DevOps-User-GroupMicrosoft – Azure

12 of 21

SoCal-DevOps-User-GroupHow OpenShift Works

13 of 21

SoCal-DevOps-User-GroupRedHat PaaS - OpenShift Enterprise

14 of 21

SoCal-DevOps-User-GroupOpenShift Product Architecture

*OpenShift 3 is built around a core of application containers powered by Docker, with orchestration and management provided by Kubernetes, on a foundation of

Atomic and Enterprise Linux. Origin Milestone 5 (M5) is the upstream community project that brings it all together along with extensions, to accelerate application

development and deployment.

-Broker handles the creation and management of user applications, the user authentication service, and

manages communication with the appropriate nodes

-Nodes run the user applications in contained environments called gears

-Messaging Service (ActiveMQ) helps the broker to query and control nodes

-Client tools or the Management Console communicates through the REST API that is hosted by the

broker

-MCollective queries a set of nodes and communicates securely with individual nodes

-Cartridges are package of framework and services

15 of 21

SoCal-DevOps-User-GroupOpenShift - Automation and Self Service for Developers

16 of 21

SoCal-DevOps-User-GroupEMC PaaS - Pivotal Cloud Foundry

Operations Manager Director for VMWare vSphere – underlying IaaS Platform

Pivotal Elastic Runtime – Contains Platform components

MySQL (MariaDB) for Pivotal CF – an out of the box build pack

17 of 21

SoCal-DevOps-User-GroupPivotal Cloud Foundry Product Architecture

Router routes incoming traffic to the appropriate components usually the CloudController

Authentication through OAuth2 server (the UAA) and Login Server that provides identity management

Cloud Controller is responsible for managing the lifecycle of applications

HM9000 - Monitor applications to determine their state

Droplet Execution Agent (DEA) manages application instances, tracks started instances, and broadcasts state messages.

Blob Store holds application code, buildpacks and droplets

Service Broker is responsible for providing service instance for example database which is already provisioned and bound

to the application

NATS a message bus is a lightweight pub-sub distributed messaging system for internal communication between

components

18 of 21

SoCal-DevOps-User-GroupPivotal CF Application Staging workflow

How Applications Are Staged

19 of 21

SoCal-DevOps-User-GroupPivotal CF - Automation and Self Service for Developers

Spring Cloud

20 of 21

SoCal-DevOps-User-GroupWhat’s next in cloud computing technology?

-Hybrid Cloud approach-Cloud Management-Application Container (Docker, Rocket) – Container

specification-Cloud aware application – 12factor.net

21 of 21

SoCal-DevOps-User-GroupQ & A

Thank you !

Suresh PaulrajORGANIZER SOCALDEVOPUSERGROUP

SURESH.PAULRAJ@GMAIL.COM

Join SoCal-DevOps-User-Group !!!http://www.meetup.com/SoCal-DevOps-User-Group/

Contact Info

The User Group in Southern California is dedicated to DevOps, System Administrators, Operation Professionals, Configuration Management professionals and Devlopers, Software/Infrastructure Automation professionals, Entrepreneurs, Students and anyone interested in this group . It is free for users to register and participate. Welcome contribution from participants.