php|arch Cloud Summit

php|architect Live! The Cloud Summit - 11/30/2011 "What's this "cloud" stuff I keep hearing about and how do I use it?"

What is this “cloud” stuff I keep hearing about and how do I

use it?Kirsten Jones and Jeremy Johnstone

Developer Advocates @ LinkedIn

Wednesday, November 30, 2011


What is "cloud" anyway?



Agenda

• About Us

• Cloud Overview

• IaaS Comparison

• PaaS Getting Started



Our Backgrounds

• Jeremy

• Used Linux for over 17 years

• Experience scaling to billions of PV/m

• Kirsten

• Passionate about data and mashups

• Self proclaimed scripting princess



Types of Cloud providers

• Attack of the aaS:

• IaaS

• PaaS

• SaaS



IaaS vs PaaS

• Level of experience required

• Flexibility

• Customizability

• Ease of setup / deployment

• Risk



Types of IaaS providers

• Computing

• Storage

• HPC

• Telecom

• more...



IaaSComparison of three top compute providers

Amazon, Rackspace, and Linode



Amazon EC2

• Six geographically diverse facilities

• Moderately easy to use multiple zones

• Linux and Windows support

• Hourly billing



EC2 continued

• HPC support

• Automatic scaling

• Elastic IP

• Most storage included



Rackspace Cloud Servers

• Three geographically diverse facilities

• Relatively difficult to use multiple DCs

• Linux and Windows support

• Hourly billing

• Fully managed options available



Linode cloud servers

• Six geographically diverse facilities

• Relatively easy to use multiple DCs

• Linux distros only

• Monthly billing

• Closest to experience of a dedicated server



Common Functionality

• Burstable resource usage

• 99% or better SLA

• Load balancing

• APIs

• DNS

• Storage / CDN *



Use Cases• Conventional multi-machine web

hosting

• Short term / bursty usage

• High performance computing

• Persistent Storage

• Redundancy

• Managed Support



PaaSGetting Started with

Google App Engine, Heroku and Joyent

http://www.princesspolymath.com/princess_polymath/?page_id=506





Platform as a Service

• Build code and deploy to the cloud

• Provides the application framework

• More infrastructure: more lock-in

• Choosing: Programming language, pricing scheme

• All have free versions to test on



Quick Compare

• Google App Engine - Easy to administer, nice tools, high lock-in

• Heroku - Many languages, scalability, add-ons

• Joyent - Focused on node.js, shell access, more configurability



Google App Engine

• Native support for Python and Java

• Other languages supported in JVM

• Easy to deploy django applications

• Integrate with SimpleDB, Google OAuth

• Strong vendor lock-in



Getting Started with Google App Engine

• Walkthrough at http://code.google.com/appengine/docs/python/gettingstarted/

• Download the SDK: http://code.google.com/appengine/downloads.html

• Command line functionality or App Engine Launcher (Win/OSX)


http://code.google.com/appengine/docs/python/gettingstarted/




http://code.google.com/appengine/downloads.html

http://code.google.com/appengine/downloads.html


Creating Hello World

• helloworld/helloworld.pyprint 'Content-Type: text/plain'print ''print 'Hello, world!'

• helloworld/app.yamlapplication: helloworldversion: 1runtime: pythonapi_version: 1handlers:- url: /.*script: helloworld.py



Run the application• google_appengine/dev_appserver.py

helloworld/

• By default it will run at :8080 on your local server

• Automatically restarts when you change files

• Real applications use webapp framework



Deploy to the Cloud

• The dashboard can be reached at https://appengine.google.com/

• To deploy, you need to create an application ID on the dashboard, then edit app.yaml application: setting to match.

• appcfg.py update helloworld/

• http://application-id.appspot.com


https://appengine.google.com

https://appengine.google.com

http://application-id.appspot.com





Heroku

• Started with Ruby on Rails, now supports node.js, python, scala, clojure

• Plugins to quickly add functionality - logging, couchdb, redis

• Easy to control scaling of web and worker components of your application independently



Getting Started with Heroku

• http://devcenter.heroku.com/articles/node-js

• Get a Heroku user account: https://api.heroku.com/signup

• Set up your local workstation

• Node.js, NPM and Git

• Login to heroku


http://devcenter.heroku.com/articles/node-js


https://api.heroku.com/signup

https://api.heroku.com/signup



• server.jsvar http = require('http');var server = http.createServer(function (req, res) { res.writeHead(200, { "Content-Type": "text/plain" }) res.end("Hello world\n");});var port = process.env.PORT||process.env.port||8001;server.listen(port, function() console.log("Listening on " + port);});


http://web.js

http://web.js


NPM Configuration

• package.json{ "name": "my-app", "version": "1.0.0", "scripts": { "start": "node server.js"}



Procfile

• Procfileweb: node server.js

• Run foreman$ foreman start14:39:04 web.1 | started with pid 2438414:39:04 web.1 | Listening on 5000

• Test with a browser on localhost


http://web.js

http://web.js

http://web.1

http://web.1

http://web.1

http://web.1


Deploy to the Cloud

• Create local Git repo$ git init$ git add .$ git commit -m "init"

• Create heroku stack and deploy$ heroku create --stack cedar$ git push heroku master...-----> Launching... done, v2http://sharp-rain-871.herokuapp.com deployed to Heroku

• Scale web processes$ heroku ps:scale web=1


http://sharp-rain-871.herokuapp.com

http://sharp-rain-871.herokuapp.com


Joyent

• http://wiki.joyent.com/display/node/Getting+Started+with+a+Node.js+SmartMachine

• Sign up for no.de: http://no.de/

• Set up your SSH key

• “Order a machine”


http://wiki.joyent.com/display/node/Getting+Started+with+a+Node.js+SmartMachine






http://no.de

http://no.de



• Same node.js files as heroku exampleserver.jspackage.json

• Add config.json file (optional)web: node server.js


http://web.js

http://web.js


Deploy to the Cloud

• Update ~/.ssh/configHost synedranodetest.no.de Port 57791 User node ForwardAgent yes

• Create local Git repo$ git init$ git add .$ git commit -m "initial commit"

• Push to joyent$ git remote add joyent synedranodetest.no.de:repo$ git push joyent master



Resources
















The end... =)

Questions?


php|arch Cloud Summit

Technology