Cloud expo 2015_rags

1© Copyright 2015 EMC Corporation. All rights reserved.
Architecting for Cloud with Cloud
Foundry
RAGHAVAN N. SRINIVAS @ragss

•  Rags (not to Riches) and work for EMC CODE
•  Middleware and Application programmer
•  Architect and Evangelist
•  Part time teaching at UML and writing at InfoQ
•  Philosophy: It’s better to have an unanswered question than a
unquestioned answer
Who am I?

•  Overview and Architecture
•  Applications, Service Brokers and Services
•  Health Management
•  Dockerized apps and Lattice
•  Demos
•  Resources and Summary
Agenda

Business Expectations Exceed IT
Capabilities
Cloud
IT Technology Eras
Mainframe Client-Server
The exponential
increase in
business
expectations is
unsustainable for
IT
MILLIONS OF
APPS BILLIONS
OF USERS
* Source: Gartner, 2013: “Hunting and Harvesting in a Digital World: The 2013 CIO Agenda”
$ $ $ $ $ $
ABILITY OF IT TO
DELIVER S/W
STEADY IT
BUDGETS*
BUSINESS
EXPECTATIONS

PaaS (On Premise & Off Premise)
Traditional IT
Storage
Servers
Networking
O/S
Middleware
Virtualization
Data
Applications
Runtime
YouManage
O/S
IaaS
Storage
Servers
Networking
Middleware
Virtualization
Data
Applications
Runtime
YouManage
IaaS
Business
Value,
Agility
&

Cost
Savings

PaaS
Storage
Servers
Networking
Middleware
Virtualization
Data
Applications
Runtime
O/S Cloud
Foundry
+
OpenStack
You
Manage

Provision
VM

Install
Applica;on
Run;me

Deploy
Applica;on

Configure
Load
Balancer

Configure
Service
Connec;vity

Configure
Firewall

cf
push

Configure
SSL
Termina;on

cf
bind-‐service

Application Development – IaaS vs PaaS
cf
scale

Removing Developer and Operator
Constrains
BUILD
APPLICATION
PUSH FIRST
RELEASE
MAINTAIN
APPLICATION
UPDATE
APPLICATIONS
RETIRE
APPLICATIONS
•  Auto-detect frameworks
•  Link to PaaS
•  Self-service deploy
•  Dynamic routing
•  CI/CD
•  Elastic scale
•  Integrated HA
•  Autoscaling and APM
•  Log aggregation
•  Policy and Auth
•  A/B versioning
•  Live upgrades
•  Self-service
removal

•  Microservices: a radical departure from traditional
monolithic applications
•  12 Factor Linux applications
•  In both cases, the enterprise is
forced to “think different.”
Microservices Architectures

•  Not monolithic J
•  Smaller units of a larger system – independent
deployability
•  Single Responsibility Principle
•  Runs in its own process – Unix pipes
•  Lightweight communication protocols
•  Polyglot persistence - multiple persistence
techniques (not just SQL)
What are MicroServices?

Gold
Silver
Cloud Foundry Foundation

Cloud Foundry Runtime Architecture
Ops
Manager
UI

Ops
Manager
Director

Operations Manager
Service
Service
Broker

Service
Nodes

Service
Broker

Service
Nodes

Service
App
Log
Aggregator

Login
Server

Dynamic
Router

Cloud
Controller

UAA

Health
Manager

DEA
Pool

Messaging
(NATS)

Apps

Metrics
Collec;on

Apps

HA
Proxy
LB

Elastic Runtime

BOSH DB
Blob
Store
Worker NATS
Health
Monitor
CPI
DirectorCLI
Inner
shell
Outer
shell
Agents
When you deploy Cloud Foundry the
following sequence of steps occur:
1.  Target a BOSH director using CLI
2.  Upload a Stemcell
3.  Get a Release from a repo
4.  Create a deployment manifest
5.  BOSH Deploy Cloud Foundry:
•  Prepare deployment
•  Compile packages
•  Create and bind VMs
•  Pull in job configurations
•  Create needed job
instances – this is where
things get pushed live

Message Bus
Behind the Scenes - BOSH
IaaS

DB
BOSH
Director
Blobs
Health
Monitor
Deploy
Worker VMs
Messaging
Target VMHealth Manager
Target VMCloud Controller
Target VM
PaaS
Ops
Deployment
•  Packages
•  Blobs
•  Source
•  Jobs
•  Manifest

Apps and Services

Stage an Application
Router

Blobstore DB
DEA
Detect Compile Upload
NoYes
System
Buildpacks
+ =
Cloud
Controller
App
Ops
Pivotal
CF

Elas;c
Run;me

Application Deployment Overview
App
Ops
①  Upload app
bits and
metadata
push app
Router

②  Create and bind services
③  Stage application
④  Deploy application
Cloud
Foundry

Elas;c
Run;me

Blobstore DB
Cloud
Controller
Service
Broker
Node(s)
DEA
DEA
DEA
DEA
+ app MD
+ =
Service
credentials

DEA

Apps

Service
Broker

Service
Nodes

Cloud
Controller

create
bind
Service Brokers generate
connection details and credentials
for managed services
CC encrypts and stores
credentials in CCDB
Credentials are exposed to bound
applications via
VCAP_SERVICES environment
variable
connect
Managed Services

Blobstore
BOSH
Health Monitor
DB
Deploy my
Services
IaaS
Worker VMsBOSH Director
NATS
Cassandra Node
Target VMCassandra Node
Target VMCassandra Node
Target VM
http://bosh.cloudfoundry.org/
Data Services

DB
Router
Data Services binding
Service
credentials
reserve resources
obtain connection data
CLI Cloud
Controller
Service
Broker
Data
Service
Runtime
create service (HTTP)
bind service (HTTP)
create service (HTTP)
bind service (HTTP)
http://docs.cloudfoundry.org/services/api.html

VCAP_SERVICES
environment variable is
visible only to members
of the org and space
containing the service
instance
VCAP_SERVICES=" {
"p-mysql": [
{
"name": "music-db",
"label": "p-mysql",
"tags": [ "mysql", "relational” ],
"plan": "100mb-dev",
"credentials": {
"hostname": "192.168.1.147",
"port": 3306,
"name": "cf_aceae021_7f27_48db_9844_d7c151f29195",
"username": "Tr12ZI4hPu4OPJPY",
"password": "fuTWBqpGeyvv0qge",
"uri": "mysql://Tr12ZI4hPu4OPJPY:fuTWBqpGeyvv0qge@192.168.1.147:3306/
cf_aceae021_7f27_48db_9844_d7c151f29195?reconnect=true”
}
}
]
} "
Managed Services

Health Management
Applications and Platform

Multiple Availability Zones for HA
requirements
•  Application and the Platform
itself are automatically balanced
across availability zones
–  Enhanced availability for
applications
–  Tolerate significant infrastructure
failures with continuous
availability

Application Instances and Availability
Zones
Router

DEA
DEA
DEA
DEA
DEA
DEA
Zone 1 Zone 2 Application
instances are
evenly distributed
over two availability
zones.
Losing an AZ keeps
instances running
and available.
App
Ops
CF
Elas;c

Run;me

Router

Failed Application Instances Replaced
Blobstore
Cloud
Controller
Health
Manager
Actual StateDesired State
Messaging
(NATS)
DEA DEA DEA
App
Ops
CF
Elas;c

Run;me

Message Bus
Monitoring Processes (Elastic Runtime
Example)
IaaS

Health
Monitor Health Manager
DEA
Cloud Controller
Responder
s:
pager
email
monitoring
…
PaaS
Ops

Opera;on
Manager

Message Bus
Monitoring VMs (Elastic Runtime Example)
IaaS

Health
Monitor Messaging
Cloud Controller
DEA
Responder
s:
pager
email
monitoring
resurrector
…
BOSH
Director
(CPI)
Actual StateDesired State
DEA
PaaS
Ops
Opera;on
Manager

Lattice

•  A lightweight container rewritten in Go
•  Ability to run Dockerized applications
Why La#ce?
App
Log
Aggregator

Dynamic
Router

DEA
Pool

Apps

Metrics
Collec;on

Apps

Elastic Runtime 1.0
Diego

Apps
Apps

Lattice

Resources and Summary

•  Cloud Native Architectures – a new paradigm
–  Scale and Speed is not just for Netflix/Twitter/Baidu/etc.
–  Microservices not Monoliths
–  12-factor app. and DevOps
–  Polyglot persistence/Multiple Data services
–  Containers
•  Containers come in multiple shapes, types and sizes
•  Choose a Platform that enables microservices,
containers, different services and enables DevOps
Summary

•  Sign up for the Cloud Foundry and BOSH
mailing lists.
•  Learn how to write 12-factor applications.
•  Try out Lattice.
•  Free workshop and roadshows. CFAD!
•  Try out Pivotal Web Services (http://run.pivotal.io)
Cloud Foundry

BOOK
Available to you
compliments of Pivotal!
Get the FREE e-book
at http://bit.ly/cloud-native-book!

https://ace.ng.bluemix.net/
http://www.hpcloud.com/products-services/
application-paas
http://www.anynines.com/
https://run.pivotal.io/
Resources

Cloud expo 2015_rags

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Cloud expo 2015_rags

Similar to Cloud expo 2015_rags (20)

Recently uploaded

Recently uploaded (20)

Cloud expo 2015_rags