Cloud Foundry the Open PaaS - OpenTour Austin Keynote

Cloud Foundry
The Open Platform as a Service

Patrick Chanezon
Senior Director
Developer Relations
chanezonp@vmware.com
http://twitter.com/chanezon Cloud Foundry OpenTour, Austin, April 2012
Thursday, April 5, 12

P@ in a nutshell

• French, based in San Francisco
• Senior Director, Developer Relations,VMware
• Software Plumber, API guy, mix of Enterprise and
Consumer
• 18 years writing software, backend guy with a
taste for javascript
• 2 y Accenture (Notes guru), 3 y Netscape/AOL
(Servers, Portals), 5 y Sun (ecommerce, blogs,
Portals, feeds, open source)
• 6 years at Google, API guy (ﬁrst hired, helped start the
team)
• Adwords, Checkout, Social, HTML5, Cloud


Dreams Of my childhood

3


Accelerando / Singularity, in a Galaxy far far away

§ Even if we automate ourselves out of a job every 10 years
§ ...I don’t think the singularity is near!

4


Moore's Law is for Hardware Only

§ Does not apply to software
§ Productivity gains not keeping up with hardware and bandwidth
§ Writing software is hard, painful, and still very much a craft

5


Moore's Law’s free lunch is over

§ Herb Sutter, Welcome to the Jungle
http://herbsutter.com/welcome-to-the-jungle/

6


Future

“The future is already here
— it's just not very evenly
distributed”
William Gibson

7


Haiku - Skylark

“Trampling on clouds,
inhaling the mist,
the skylark soars”
—SHIKI

8


Haiku - Frog

“Crouching,
studying the clouds—
a frog”
CHIYO-JO

9


Architecture Changes: 60’s Mainframe


Architecture Changes: 80’s Client-Server


Architecture Changes: 90’s Web


Architecture Changes: 2010’s Cloud, HTML5, Mobile


Back to Client Server: Groovy Baby!

14


What is Cloud Computing?

Cloud According to my daughter Eliette

15


Cloud Stack - Classic Pyramid

Software
As A Service

Platform As A Service

Infrastructure As A Service

16


Cloud Stack - By Number

Software
As A Service


Infrastructure
As A Service

17


Cloud Stack - By Value

Software
As A Service


Infrastructure
As A Service

18


Cloud Stack - Neutral

Software
As A Service


Infrastructure As A Service

19


Cloud Stack - History

§ What does cloud mean, 4 main angles
• Software 1994 Netscape
• Infrastructure 2002 Amazon AWS
• Platform 2008 Google
• Development now!

§ Industrialization of hardware and
software infrastructure
like electricity beginning of 20th century

§ But software development itself is moving towards craftmanship

20


Cloud started at Consumer websites solving their needs
• Google, Amazon, Yahoo, Facebook, Twitter
• Large Data Sets
• Storage Capacity growing faster than Moore’s Law
• Fast Networks
• Horizontal -> Vertical scalability
• Open Source Software
• Virtualization
• Cloud is a productization of these infrastructures
• Public Clouds Services: Google, Amazon
• Open Source Software: Hadoop, Eucalyptus, Ubuntu, Cloud Foundry


Infrastructure

22


IaaS/Virtualization getting mainstream

§ AWS, Joyent, Rackspace,...
§ Open Source projects: OpenStack, DeltaCloud, Eucalyptus
§ Automation: Chef, Juju
§ Standardization? DMTF
§ Inside the Firewall, Virtualization: VMware, Microsoft, Xen, KVM
§ 50% of workloads are virtualized
§ Easy to provision, manage instance...BUT
§ Still need to manage backups, software stacks, monitor, upgrades

23


With Infrastructure, you still need to build your own platform

§ Need to build a distributed platform on top of you infrastructure
§ Story of the AWS meltdown from last summer
• http://blog.reddit.com/2011/03/why-reddit-was-down-for-6-of-last-24.html
• http://www.readwriteweb.com/cloud/2010/12/chaos-monkey-how-netflix-
uses.php
• http://news.ycombinator.com/item?id=2477296
• http://stu.mp/2011/04/the-cloud-is-not-a-silver-bullet.html
§ Twilio, Smugmug, SimpleGeo survived it because they built their
own distributed platform on top of IaaS
§ Enterprise customers want to consider Infrastructure like CDNs
• Multi Cloud usage
• Based on Open Source de facto standards, or full standards whenever that
happens

24


Platforms

25


Platforms

§ Raise the Unit of currency to be application & services instead of
infrastructure
§ Google App Engine, Cloud Foundry, Joyent, Heroku, Stax
(Cloudbees), Amazon elastic beanstalk, Microsoft Azure, AppFog
§ Single or a few languages, services
§ Start of Multi language Polyglot platforms
§ Enabler for Agile Developers -> Create Business value faster
§ Lack of standards: risk, vendor lock-in
§ Enterprise needs:
• Control, customizability
• Private/Hybrid Cloud
• Avoid lock-in

26


Agile Development Processes


Agility as a survival skill

§ Consumer software is becoming like fashion
• Phone apps, social apps, short lifetime, fast lifecycles
• Ab testing
§ Clay shirky situational apps
§ Kent Beck, Usenix 2011 Talk, “Software G-Forces”
change in software process when frequency grows
§ Cloud Platforms enables an Agile culture, driver for innovation
• Scalability is built in the platforms
• Can iterate faster
• Focus on design
§ Cloud Platforms lets developers focus on driving business value

28


Main Risk: Lock-In

Welcome to the hotel california
Such a lovely place
Such a lovely face
Plenty of room at the hotel california
Any time of year, you can ﬁnd it here

Last thing I remember, I was
Running for the door
I had to ﬁnd the passage back
To the place I was before
’relax,’ said the night man,
We are programmed to receive.
You can checkout any time you like,
But you can never leave!

29


Cloud Foundry: The Open PaaS

• Open Source: Apache 2 Licensed
• multi language/frameworks
• multi services
• multi cloud

Ap

ce
pli
vFabric

rfa
Postgres Private
ca

nte
Data
Services tio Clouds

rI
n

e
Se
Public

vid
vFabric
RabbitMQTM rvi
Cloud

ro
Msg Services
ce

dP
Micro

ou
Other
Cloud
Cl
Services

30


Open Source

31


Open Source Advantage

§ http://code.google.com/p/googleappengine/issues/detail?id=13

• https://github.com/cloudfoundry/vcap/pull/25

32


Multi Cloud

33


CloudFoundry.COM

Cloud Foundry

Runtimes & Frameworks

Services

vCenter / vSphere

Infrastructure

34


Cloud Foundry.ORG

Cloud Foundry

The Source Code to Compile & Build Cloud Foundry

vCenter / vSphere

Download Setup Setup Scripts Deploy
Code Environment Behind
Firewall

35


Micro Cloud Foundry

Micro

36


What is a Micro Cloud?

Or

Entire Cloud Running inside of a single VM

37


Micro Cloud Foundry… (BETA)
A pre-built Micro (Single VM) version of Cloud Foundry…

You need a Cloud Foundry.com Account to use Micro Cloud Foundry

Signup @ http://cloudfoundry.com/micro

38


Micro Cloud Foundry… (BETA)
A pre-built Micro (Single VM) version of Cloud Foundry…

Micro

You need a Cloud Foundry.com Account to use Micro Cloud Foundry

Signup @ http://cloudfoundry.com/micro

38


What is in Micro Cloud Foundry?

.COM

Dynamic Updating DNS

App Instances Services

Open source Platform as a Service project

10.04

39


Other Cloud Foundry powered PaaS

Private PaaS
Added Python and Perl

Public PaaS
Added PHP

Tier3 and Uhuru recently added .NET support

40


Development
LifeCycle

41


Traditional App Deploy and Request/Response

Web

Request/Allocate
Web Build/Setup
Install/Configure
App

Deploy/Test
App
Scale?
Upgrade?
DB
DB
Update?


How Apps are Deployed on Cloud Foundry

Web
Web
App

“vmc push MyApp” DB

App
Web

Scale? “vmc instances MyApp 5”
DB Upgrade? “vmc map MyApp MyApp2”
Update? “vmc update MyApp”


How Apps are Accessed on Cloud Foundry

Request Web Interface
Load
Balancing
Response
and
Routing

Web

App

App Instance

DB
“vmc push MyApp”
Service


How Apps are Scaled on Cloud Foundry

Request
Load
Load
Load
Balancer(s)
Balancing Response
Balancer(s)
and
Routing

App Instances

Web Web Web

App App App

DB
“vmc instances MyApp 3”
Service


How Apps are Updated on Cloud Foundry

Previous Instance Updated New
Version Stopped Code Version
Web Web Web Web

App App App App

DB DB

Service Service

“vmc update MyApp”


Services

47


Current Services Available on Cloud Foundry

48


Service Creation and Binding

VCAP_SERVICES:
{"redis-2.2":[{"name":"redis_sample","label":"redis-2.2","plan":"free",
"tags":["redis","redis-2.2","key-value","nosql"],
"credentials":
{"hostname":"172.30.48.40",
"host":"172.30.48.40",
"port":5023,
"password":"8e9a901f-987d-4544-9a9e-ab0c143b5142",
"name":"de82c4bb-bd08-46c0-a850-af6534f71ca3"}
}],
"mongodb-1.8":[{"name":"mongodb-e7d29","label":"mongodb-1.8","plan":"free","tags”:
………………….

49



App Instance

50



App Instance Redis Service

50



App Instance Redis Service

MongoDB
Service

50


How it works

51


Logical View

Browser
VMC client STS plugin
(user app access)

Routers

CloudControllers App App

HealthManager
Services DEA Pool

Messaging

52


Architecture

53


Register today

http://cloudfoundry.com/signup
Use Promo Code CFOpenTour2012
To avoid approval queue waiting time

54


Cloud for Developers: the true path is PaaS!

55


sample app
polyglot in action
by Mark Lucovsky

56 developer perspective v2.0


stac2: load generation system
- jQuery, jQuery UI json-p stac2 - 2 x 128mb
- haml templates frontend - ruby 1.8.7, sinatra
- 100% JS based UI
smtp http json

email - 16 x 128mb*
api server - node.JS, 0.6.8
reports

rpush redis api

redis

blpop redis api blpop
- 96 x 128mb - 16 x 128mb*
- ruby 1.8.7, sinatra vmc worker http worker - node.JS, 0.6.8
* - api server and http worker
share the same node.JS
process/instance


deployment instructions

$ cd ~/stac2
$ vmc push



how is this possible?
$
cd
~/stac2;
cat
manifest.yml
applications:

./nabh:

instances:
16

mem:
128M

runtime:
node06

url:
${name}.${target-‐base}

services:

nab-‐redis:

type:
:redis
./nabv:

instances:
96

mem:
128M

runtime:
ruby18

url:

services:

nab-‐redis:

type:
:redis
./stac2:

instances:
2

mem:
128M

runtime:
ruby18

url:



design tidbits
• producer/consumer pattern using rpush/blpop
• node.JS: multi-server and high performance async i/o
• caldecott – aka vmc tunnel for debugging
• redis sorted sets for stats collection
• redis expiring keys for rate calculation



producer/consumer
• core design pattern
• found at the heart of many complex apps
classic mode:
- thread pools
- semaphore/mutex, completion ports, etc.
- scalability limited to visibility of the work queue

producer work work queue work consumer

cloud foundry mode:
- instance pools
- redis rpush/blpop, rabbit queues, etc.
- full horizontal scalability, cloud scale



producer/consumer: code
//
producer
function
commit_item(queue,
item)
{

//
push
the
work
item
onto
the
proper
queue

redis.rpush(queue,
item,
function(err,
data)
{

//
optionally
trim
the
queue,
throwing
away

//
data
as
needed
to
ensure
the
queue
does

//
not
grow
unbounded

if
(!err
&&
data
>
queueTrim)
{

redis.ltrim(queue,
0,
queueTrim-‐1);

}

});
}
//
consumer
function
worker()
{

//
blocking
wait
for
workitems

blpop_redis.blpop(queue,
0,
function(err,
data)
{

//
data[0]
==
queue,
data[1]
==
item

if
(!err)
{

doWork(data[1]);

}

process.nextTick(worker);

});


node.JS multi-server: http API server
//
the
api
server
handles
two
key
load
generation
apis
//
/http
–
for
http
load,
/vmc
for
Cloud
Foundry
API
load
var
routes
=
{“/http”:
httpCmd,
“/vmc”:
vmcCmd}

//
http
api
server
booted
by
app.js,
passing
redis
client
//
and
Cloud
Foundry
instance

function
boot(redis_client,
cfinstance)
{

var
redis
=
redis_client;

function
onRequest(request,
response)
{

var
u
=
url.parse(request.url);

var
path
=
u.pathname;

if
(routes[path]
&&
typeof
routes[path]
==
‘function’)
{

routes[path](request,
response);

}
else
{

response.writeHead(404,
{‘Content-‐Type’:
‘text/plain’});

response.write(‘404
Not
Found’);

response.end();

}

}

server
=
http.createServer(onRequest).listen(cfinstance[‘port’]);
}



node.JS multi-server: blpop server
var
blpop_redis
=
null;
var
status_redis
=
null;
var
cfinstance
=
null;

//
blpop
server
handles
work
requests
for
http
traffic
//
that
are
placed
on
the
queue
by
the
http
API
server
//
another
blpop
server
sits
in
the
ruby/sinatra
VMC
server
function
boot(r1,
r2,
cfi)
{

//
multiple
redis
clients
due
to
concurrency
constraints

blpop_redis
=
r1;

status_redis
=
r2;

cfinstance
=
cfi;

worker();
}

//
this
is
the
blpop
server
loop
function
worker()
{

blpop_redis.blpop(queue,
0,
function(err,
data)
{

if
(!err)
{

doWork(data[1]);

}

process.nextTick(worker);

});
}


caldecott: aka vmc tunnel
#
create
a
caldecott
tunnel
to
the
redis
server
$
vmc
tunnel
nab-‐redis
redis-‐cli
Binding
Service
[nab-‐redis]:
OK
…
Launching
'redis-‐cli
-‐h
localhost
-‐p
10000
-‐a
...’

#
enumerate
the
keys
used
by
stac2
redis>
keys
vmc::staging::*
1)
“vmc::staging::actions::time_50”
2)
“vmc::staging::active_workers”
…

#
enumerate
actions
that
took
less
that
50ms
redis>
zrange
vmc::staging::actions::time_50
0
-‐1
withscores
1)
“delete_app”
2)
“1”
3)
“login”
4)
“58676”
5)
“info”
6)
“80390”

#
see
how
many
work
items
we
dumped
due
to
concurrency
constraint
redis>
get
vmc::staging::wastegate
“7829”


redis sorted sets for stats collection
#
log
action
into
a
sorted
set,
net
result
is
set
contains
#
actions
and
the
number
of
times
the
action
was
executed
#
count
total
action
count,
and
also
per
elapsed
time
bucket
def
logAction(action,
elapsedTimeBucket)

#
actionKey
is
the
set
for
all
counts

#
etKey
is
the
set
for
a
particular
time
bucket
e.g.,
_1s,
_50ms

actionKey
=
“vmc::#{@cloud}::actions::action_set”

etKey
=
“vmc::#{@cloud}::actions::times#{elapsedTimeBucket}”

@redis.zincrby
actionKey,
1,
action

@redis.zincrby
etKey,
1,
action
end

#
enumerate
actions
and
their
associated
count
redis>
zrange
vmc::staging::actions::action_set
0
-‐1
withscores
1)
“login”
2)
“212092”
3)
“info”
4)
“212093”

#
enumerate
actions
that
took
between
400ms
and
1s
redis>
zrange
vmc::staging::actions::time_400_1s
0
-‐1
withscores
1)
“create-‐app”
2)
“14”
3)
“bind-‐service”
4)
“75”


redis incrby and expire for rate calcs
#
to
calculate
rates
(e.g.,
4,000
requests
per
second)
#
we
use
plain
old
redis.incrby.
the
trick
is
that
the

#
key
contains
the
current
1sec
timestamp
as
it’s
suffix
value
#
all
activity
that
happens
within
this
1s
period
accumulates
#
in
that
key.
by
setting
an
expire
on
the
key,
the
key
is

#
automatically
deleted
10s
after
last
write
def
logActionRate(cloud)

tv
=
Time.now.tv_sec

one_s_key
=
"vmc::#{cloud}::rate_1s::#{tv}"

#
increment
the
bucket
and
set
expires,
key

#
will
eventually
expires
Ns
after
the
last
write

@redis.incrby
one_s_key,
1

@redis.expire
one_s_key,
10
end

#
return
current
rate
by
looking
at
the
bucket
for
the
previous

#
one
second
period.
by
looking
further
back
and
averaging,
we

#
can
smooth
the
rate
calc
def
actionRate(cloud)

tv
=
Time.now.tv_sec
-‐
1

one_s_key
=
"vmc::#{cloud}::rate_1s::#{tv}"

@redis.get
one_s_key
end


stac2 demo -or- screencast



Lessons for
Developers

70


Predictions

§ Software is becoming like fashion, design rules
§ Welcome to Babel, use the best tool for the job, embrace multiple
language & heterogeneity
§ Our jobs will change, build yourself out of your current job
§ Sysadmin jobs will morph, there will be less of them
§ Many opportunities open when you embrace change

71


Things to Forget

§ First normal form
§ Waterfall model
§ Single server deployment
§ Single language skill
§ Build everything from scratch
§ Build custom infrastructure

72


Things to Learn

• Agile, API Design
• UI Design, Javacript, HTML5, CSS3
• A/B Testing
• Open Source, Open Standards
• Architecture, Distributed Computing (CAP theorem, 8 fallacies)
• Cloud Platforms and APIs
• Multiple types of languages (imperative, object, functional, logic)
• Ability to encapsulate domain knowledge in a DSL
• Build on the shoulders of giants: reuse, rest APIs
• Pick your battles, choose what you need to build yourself to add value
• Learn to live in a box (embrace platform limitations) to think outside the box
• Use an App Store for distribution

73


Be your own bitch

“Don’t be a Google Bitch,
don’t be a Facebook Bitch,
and Don’t be a Twitter
Bitch. Be your own Bitch.”
Fred Wilson
http://techcrunch.com/2011/05/23/fred-wilson-be-your-own-bitch/

74


Such stuff as dreams are made on

§ Like a kid on a candy store: there's never been a better time to be a
software developer!
§ Welcome to the Cloud: embrace change and reinvent yourselves
§ “The future is already there, not evenly distributed” Gibson
§ We Developers, invent the future today

75


Cloud Foundry Resources

Primary Site : cloudfoundry.com
Open Source Site : cloudfoundry.org

Twitter : @cloudfoundry , hash tag #cfoundry
Blog : blog.cloudfoundry.com
FB : facebook.com/cloudfoundry

Support : support.cloudfoundry.com
• Documentation
• Knowledge Base
• Q & A / Forums
We’re hiring: www.cloudfoundry.com/jobs

76


Questions

77

?

Thank You!
t @CloudFoundry

t @chanezon

Website : www.cloudfoundry.com
Blog : blog.cloudfoundry.com
Forum : support.cloudfoundry.com


Books / Articles

§ Nick Carr, The Big Switch
§ Eric Raymond, The Art of Unix Programming
§ Weinberg, Psychology of Computer Programming
§ Wes python book
§ Mark html5 book
§ Kent Beck XP
§ Hunt, Thomas, The Pragmatic Programmer
§ Ade Oshineye, Apprenticeship Patterns
§ Matt Cutt's Ignite Talk IO 2011, Trying different things
§ Josh Bloch talk about api design
§ Larry and Sergey, Anatomy of a Search Engine
§ Rob Pike, The Practice of Programming

79


Papers / Talks

§ Simon Wardley, Oscon 09 “Cloud - Why IT Matters”
§ Tim O’Reilly article on internet os
§ Peter Deutsch’s 8 Fallacies of Distributed Computing
§ Brewer’s CAP Theorem
§ Gregor Hohpe’s Starbucks Does Not Use Two-Phase Commit
§ Stuff I tag http://www.delicious.com/chanezon/
§ More specifically http://www.delicious.com/chanezon/cloudfoundry
§ My previous Talks http://www.slideshare.net/chanezon
§ My list of favorite books
http://www.chanezon.com/pat/soft_books.html

80


Acknowledgement

§ Drawings from my daughters Eliette
§ Slides from Dave McCrory, Derek Collison, Duke Leto
§ Haiku from Addiss, Stephen; Yamamoto, Fumiko; Yamamoto,
Fumiko Y.; Yamamoto, Akira Y. (2011-06-22). Haiku: An Anthology of
Japanese Poems (Shambhala Library)
§ Painting Hiroshige, Sengai

81


Cloud Foundry the Open PaaS - OpenTour Austin Keynote

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Cloud Foundry the Open PaaS - OpenTour Austin Keynote

Ähnlich wie Cloud Foundry the Open PaaS - OpenTour Austin Keynote (20)

Mehr von Patrick Chanezon

Mehr von Patrick Chanezon (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Cloud Foundry the Open PaaS - OpenTour Austin Keynote