1. Portrait of the developeur as

2. @chanezon
French
Polyglot
Server Side
San Francisco
Developer Relations

3. Patrick Chanezon
Senior Director
Developer Relations
chanezonp@vmware.com
@chanezon

4. Very freely inspired from
... and a few years as an
Enterprise consultant in France before
moving to California

19. 2010
- George became CIO

29. What happened while
George was playing
Golf

30. Dreams Of my childhood
30

31. 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!
31

32. 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
32

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

34. Architecture Changes: 60’s Mainframe

35. Architecture Changes: 80’s Client-Server

36. Architecture Changes: 90’s Web

37. Architecture Changes: 2010’s Cloud, HTML5, Mobile

38. Back to Client Server: Groovy Baby!
38

39. What is Cloud Computing?
Cloud According to my daughter Eliette
39

40. Cloud Stack - Classic Pyramid
Software
As A Service
Platform As A Service
Infrastructure As A Service
40

41. Cloud Stack - By Value
Software
As A Service
Platform As A Service
Infrastructure
As A Service
41

42. 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
42

43. 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
• Vertical -> Horizontal 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

44. Infrastructure
44

45. IaaS/Virtualization getting mainstream
§ AWS, Joyent, Rackspace,...
§ Open Source projects: OpenStack, DeltaCloud, Eucalyptus
§ Automation: Chef, Juju, Cloud Foundry BOSH
§ Standardization? DMTF
§ Inside the Firewall, Virtualization: VMware, Microsoft, Xen, KVM
§ 60% of workloads are virtualized in 2012
§ Easy to provision, manage instance...BUT
§ Still need to manage backups, software stacks, monitor, upgrades
45

46. 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
46

47. Platforms
47

48. Platforms
§ Raise the Unit of currency to be application & services instead of
infrastructure
§ Google App Engine, Cloud Foundry, Heroku, 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
48

49. Agile Development Processes

50. Agility as a survival skill
§ Consumer software is becoming like fashion
•Phone apps, social apps, short lifetime, fast lifecycles
•A/B testing
§ Enterprise
•Clay shirky situational apps
§ Kent Beck, Usenix 2011 Talk, “Software G-Forces: the effects of
acceleration”
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
50

51. 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 find it here
Last thing I remember, I was
Running for the door
I had to find 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!
51

52. Cloud Foundry: The Open PaaS
• Open Source: Apache 2 Licensed
• multi language/frameworks
• multi services
• multi cloud
Ap
ce
pli
vFabric
Private
rfa
Postgres
ca
e
tio Clouds
Int
Data Services
n
er
Se
vFabric Public
vid
RabbitMQTM rvi
Clouds
ro
Msg Services
ce
dP
Micro
ou
Other
Clouds
Cl
Services
52

53. CloudFoundry.COM – Multi-Tenant PaaS Operated by VMware
CloudFoundry.COM (beta)
Frameworks
Services
vCenter / vSphere
Infrastructure
53

54. Micro Cloud FoundryTM – Industry First Downloadable PaaS
Micro Cloud Foundry
Frameworks
Services
Your Laptop/PC
Single VM instance of
Cloud Foundry
that runs on a developer’s
MAC or PC
New release v116 last week
Tracks CloudFoundry.com
54

55. Open Source
55

56. CloudFoundry.ORG – Community Open Source Project
github.com/cloudfoundry
.NET x 2 § Memcached
PHP § SQL Server
JRuby § Neo4j
Python § CouchDB
Rails 2.x § VirtualBox
Clojure § Mono
Erlang § Rack
Haskell
56

57. CloudFoundry.ORG – Community Open Source Project
CloudFoundry.ORG
Community Frameworks Contributions
Community Services Contributions
Your Infrastructure
Download Setup Tool Chain & Deploy Behind
Code Environment Scripts Firewall
Cloud
Foundry
BOSH
Apache2
license
57

58. Cloud Foundry Open Source Workflow
cloudfoundry.com
production updated ~2x/week
github
github.com/cloudfoundry
on +2 and ✓ change pushed to github
Reviewers +1/-1 Gerrit Code Review +2/-2 Committers
reviews.cloudfoundry.org
test verification score ✓ ✗ git push triggers test execution
Jenkins CI
ci.cloudfoundry.org
58

59. Open Source Advantage: speed
§ http://code.google.com/p/googleappengine/issues/detail?id=13
• https://github.com/cloudfoundry/vcap/pull/25
59

60. Open Source Advantage: breadth
60

61. Ecosystem
61

62. Broad Industry Investment
62

63. Cloud Foundry - Making Multi-Cloud a Reality
Private Cloud Public Cloud
Management and
Distributions Operators
.COM
Bare metal
63

64. Cloud Foundry
Architecture

65. Architectural Goals
65

66. Architectural Goals
No single point of failure
65

67. Architectural Goals
No single point of failure
Distributed state
65

68. Architectural Goals
No single point of failure
Distributed state
Self healing
65

69. Architectural Goals
No single point of failure
Distributed state
Self healing
Horizontally scalable
65

70. Architectural Principles
66

71. Architectural Principles
Loose coupling
66

72. Architectural Principles
Loose coupling
Event-driven
66

73. Architectural Principles
Loose coupling
Event-driven
Asynchronous
66

74. Architectural Principles
Loose coupling
Event-driven
Asynchronous
Non-blocking
66

75. Architectural Principles
Loose coupling
Event-driven
Asynchronous
Non-blocking
Idempotent
66

76. Architectural Principles
Loose coupling
Event-driven
Asynchronous
Non-blocking
Idempotent
Eventually consistent
66

77. Architectural Principles
Loose coupling
Event-driven
Asynchronous
Non-blocking
Idempotent
Eventually consistent
Language-independent communication
66

78. Cloud Foundry Layers
67

79. Cloud Foundry Layers
Clients
67

80. Cloud Foundry Layers
Clients
Inner Shell
67

81. Cloud Foundry Layers
Clients
Inner Shell
Outer Shell
67

82. Cloud Foundry Layers
Clients
Inner Shell
Outer Shell
Infrastructure as a Service
67

83. Cloud Foundry Layers
Clients
Inner Shell
Outer Shell
Infrastructure as a Service
Hardware (CPU, Memory, Storage,
Network)
67

84. Cloud Foundry
Core
Components

85. Design Principles
Dynamically discoverable components
No inter-component dependencies
• Launch in any order
• Scale up and down independently
Monitor using HTTP end points
69

86. Cloud Foundry Logical View
Developers Users
vmc
Routers
CloudControllers App App
HealthManager
Execution Agents (DEA)
Services
Pool
Messaging

87. Cloud Foundry
BOSH
71

88. Production Grade Cloud Foundry Clusters
500 – 5,000 VMs cloudfoundry.com
40+ unique node types
75+ unique software packages
75+ unique environments
2x/week cf.com updates
24x7x365 non-stop operation
No-downtime deployments
Reliable, robust, repeatable
deployments, updates, capacity
adjustments
Small teams manage many
instances
production, staging, stress, qa, dev
Google style problem è Google style solution
72

89. Cloud Foundry BOSH
Cloud Foundry BOSH is an open source tool-chain for release
engineering, deployment, and lifecycle management of large scale
distributed services
• Prescriptive way of creating releases and managing systems and services
• It is not a collection of shell scripts, not a pile of Perl
Built to deploy and manage production-class, large scale clusters
• Production grade Cloud Foundry clusters: 500+ VMs, 40+ jobs, 75+ packages
• Multi-node, multi-tier, complex clusters: e.g., our Gerrit/Jenkins Cluster
Built for devops usage and scale by a crack team of veterans
• A project, not a product: command line interface, YAML, etc.
• Continuous improvement, iterative development, rough edges
github.com/cloudfoundry/bosh
73

90. BOSH: under the hood
BOSH User
“BOSH is deployed by BOSH”
bosh cli director healthmon
cloudfoundry.com
db redis nats
workers blobs active jobs
agent
IaaS CPI stemcell disk
74

91. IaaS neutral by design
vSphere: battle tested implementation, thousands of
deployments
CPI: code complete
vCloud Director: “work in progress”, 2H 2012 functional status: “work in progress”
Cloud Foundry BOSH
Cloud Provider Interface (CPI)
github.com/piston/openstack-bosh-cpi
contribute: github.com/cloudfoundry/bosh
75

92. Lessons for
Developers
76

93. 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
77

94. Things to forget
• First normal form
• Waterfall model
• Single server deployment
• Single language skill
• Build everything from scratch
• Build custom infrastructure
78

95. Things to learn
• Agile
• Take risks, fail often, fail fast and learn
• API Design: create the API first
• 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
79

96. Redemption

108. The (Happy) End

109. Register today
http://cloudfoundry.com/signup
Use Promo Code cfopentoursofia
To avoid approval queue waiting time
Download Micro Cloud Foundry locally
ftp://192.168.5.5/micro-v116-20121101.000204.zip
Events we do on Lanyrd
http://lanyrd.com/2012/cloud-foundry-open-tour-sofia/
93