Ruby conf2010 OpenPaaS

The Buildingof the

OpenPaaSDerek Collison

Friday, November 12, 2010

Safe Harbor StatementForward-Looking Statements

This presentation contains forward-looking statements including, among other things, statements regarding the development and functionality of VMware products and services and the timing of their availability. These forward-looking statements are subject to the safe harbor provisions created by the Private Securities Litigation Reform Act of 1995. Actual results could differ materially from those projected in the forward-looking statements as a result of certain risk factors, including but not limited to: (i) adverse changes in general economic or market conditions; (ii) delays or reductions in information technology spending; (iii) competitive factors, including but not limited to pricing pressures, industry consolidation, entry of new competitors into the virtualization market, and new product and marketing initiatives by our competitors; (iv) our customers’ ability to develop, and to transition to, new products and computing strategies such as cloud computing; (v) the uncertainty of customer acceptance of emerging technology; (vi) rapid technological and market changes in virtualization software and platforms for cloud and desktop computing; (vii) changes to product development timelines; (viii) our ability to protect our proprietary technology; (ix) our ability to attract and retain highly qualified employees; and (x) the successful integration of acquired companies and assets into VMware. These forward looking statements are based on current expectations and are subject to uncertainties and changes in condition, significance, value and effect as well as other risks detailed in documents filed with the Securities and Exchange Commission, including our most recent reports on Form 10-K and Form 10-Q and current reports on Form 8-K that we may file from time to time, which could cause actual results to vary from expectations. VMware assumes no obligation to, and does not currently intend to, update any such forward-looking statements after the date of this release.


What is the OpenPaas?



• Application Platform as a Service

• Application delivery platform

• Favor choice and openness

• A what?



• Application is the unit of currency

• That is what you care about

• Everything else is decided for you

• And you shouldn’t care


What makes it Open?


What makes it Open?

• Multi-framework

• Sinatra, Rails, Spring, Node.js, Scala, Python, etc.

• Multi-cloud

• Terremark, vCloud, VMforce, vSphere, AWS?

• Multi-service

• MySQL, Postgres, Redis, RabbitMQ, Memcache, MongoDB, etc..


More Information

• http://blogs.vmware.com/console/2010/04/vmforce-and-vmwares-open-paas-strategy.html

• http://blogs.vmware.com/console/2010/05/google-and-vmwares-open-paas-strategy.html


http://blogs.vmware.com/console/2010/04/vmforce-and-vmwares-open-paas-strategy.html




http://blogs.vmware.com/console/2010/05/google-and-vmwares-open-paas-strategy.html




But I want control!!


But I want control!!

• I want access to the web server!

• I need access to my app server!

• I need to control all configurations..

• I want my app placed here, not there!


Relax!

"They got rid of the horizontal and the vertical settings years

ago."


But Seriously....

• We understand, we get it..

• You’ll have utility VMs

• Layer 4 IP Connectivity

• Apps will bind to them

• They will bind to provisioned services

• More to come..


Why do we care?


Why do we care?

• Cloud is about opex, not capex

• PaaS reduces opex

• Major portion of $$ spent is on application deployment and management

• Simplify and save $$

• Storage & Compute are trending -> $0


Why do we care?

• Speed

• Agility

• How long do you wait to deploy your app?

• What if that was seconds? For any app?

• What if the cloud really was your “other” computer?


What’s Important?


What’s Important?

• SLA, Services, multiple Service Providers

• Predictable Performance

• Choice and Openness

• The Lightbulb!


Lightbulb?


Lightbulb!


Lightbulb!

• Opex vs Capex

• Incandescent vs CFL..

• Framework X vs Framework Y


Lightbulb!

• What if you could light your room for half the cost?

• How much does that app cost me to run in the cloud again?

• What choices do I have to cut costs?


What is VMforce?


What is VMforce?

• VMware + SalesForce.com

• OpenPaaS instantiation at SalesForce.com

• Spring and Roo Frameworks

• SalesForce.com’s Data and Services

• Hosted in SalesForce.com datacenters


How does one build one of these things??


• Inner and Outer shells on top of IaaS

• Outer shell is creation, orchestration, and management of the infrastructure.

• Stemcell VMs, raw resources, and change management.

• Inner shell runs the core system components

• Routers, CloudControllers, ExecutionAgents, HealthManager and Services.

How does one build one of these things??


Basic Premises


Basic Premises

• Should be self healing

• Should be horizontally scalable at all levels

• Should utilize distributed state

• NO single point of failure!

• Above all, should be simple and dumb

• Dumber as you get closer to the core


Basic Premises

• Messaging as a foundation

• Addressing

• Component discovery

• Command and Control

• JSON

• HTTP or file systems for data transport

• File system is an optimization


App Basics


App Basics

• Execution is start and stop, that’s it!

• Be cloud-ready!

• Shared state, depend on nothing local

• No assumptions about resources

• X File.read(‘/home/derek/stuff ’)

• X EM.start_server(‘localhost’, 80, h)


App Basics

• Send us everything.. I mean everything

• Can’t create “start” button until you do!

• Bundler is good.. so to speak

• ‘bundle package’ is better!

• How does that not suck though?

• Other frameworks? node.js/npm??


Tools


Tools

• Ruby

• EventMachine

• Messaging

• HTTP

• JSON

• Rack/Sinatra/Thin/em-http-request


Tools

• Ruby

• EventMachine

• Messaging

• HTTP

• JSON

• Rack/Sinatra/Thin/em-http-request


Wait, Ruby?? Really?

• Ruby is a great language, well designed..

• Distributed systems architecture has little to do with language choice..

• If someone says so, walk the other way!

• Of course we all want faster Ruby!

• 1.9.2, RBX, JRuby, MagLev


Patterns


Patterns

• Event-Driven

• Non-Blocking

• Asynchronous

• N-wise Scalable

• No assumptions

• No Dependency on Central State


Components


Components

• Dynamically discoverable

• subscribe(‘you there?’)

• Launch in any order

• publish(‘hello!’)

• Never store central state

• Health status and state available via HTTP


Components

Routers

Droplets/Apps

CloudControllers

ServicesHealth


YES!

Is it Real?


Monitoring?


Monitoring?

• Simple

• Publish ‘Who’s there?’

• Everyone responds with HTTP endpoint

• Pull results

• Ask again!



• VMC - Command Line Interface

• STS - Spring version of Eclipse

Interfaces



Questions?


Thanks!


Technology

Ruby conf2010 OpenPaaS