Cloud Computing for Hackers

Presented on workshop at Universidad de Puerto Rico, Rio Piedras.

Transcript

1. Cloud Computing for Hackers
2. Thanks for showing up
3. We are going to move fast
4. I will stop for questions
5. Giovanni Collazo @gcollazo
8. Hacker
9. “jakel”
10. “To programmers, ‘hacker’ connotes mastery in the most literal sense: someone who can make a computer do what he wants—whether the computer wants to or not” - Paul Graham
11. “It can be either a compliment or an insult. It's called a hack when you do something in an ugly way. But when you do something so clever that you somehow beat the system, that's also called a hack.” - Paul Graham
17. If you are here you are a Hacker
18. So, what’s cloud computing?
19. a computer in the sky
20. a computer over network
21. a computer somewhere on the internet
22. elastic
23. providing service as a utility
24. the illusion of infinite supply
25. Why so much attention?
26. Paradigm shift
28. Everything talks to the network
29. All computers are over the network
30. Does it matter if the other side of the cable is in the same building?
31. For most apps it doesn’t matter
32. So, I don’t have to buy and maintain servers?
34. Why Hackers should care?
35. We can deploy a server in seconds
36. We can deploy hundreds in minutes
37. Pay for what you use
38. New kinds of apps are possible
39. New toy to play with
40. How many servers they have?
41. It’s been reported that AWS has somewhere around 500,000
42. That’s not enough
43. They are enough because the are virtualized
44. What’s this virtualization thing?
45. Hardware virtualization or platform virtualization refers to the creation of a virtual machine that acts like a real computer with an operating system - Wikipedia
46. One physical machine can run multiple virtual machines
47. They share the resources of the physical machine
48. XEN
49. XEN x86, x86_64, IA64, ARM
50. XEN Windows, Linux, Solaris, BSD
51. They look like “real” machines over the network
52. They are cheap to run
54. This is specially cool for scaling web apps
55. Modern web apps are designed to scale horizontally
56. That means that to support more traffic you just add more “cheap” machines
57. ...instead of using really big, powerful and “expensive” machines
58. What does the architecture of a web app looks like?
59. App Server HTTP Request HTTP Response DB
60. App Server HTTP Request HTTP Response DB Cache
61. App Server HTTP Request HTTP Response Cache DB Reads & Writes
62. App Server HTTP Request HTTP Response Cache DB Reads & Writes App Server Load Balancer
63. Load Balancer App Server App Server App Server App Server DB Read Slave DB Read Slave Cache Reads DB Master Writes Replication HTTP Request HTTP Response
64. Load Balancer App Server App Server App Server App Server Cache DB01 HTTP Request HTTP Response DB02 DB03 Shard01 Shard10 Shard11 Shard20 Shard21 Shard30 Reads & Writes Reads & Writes
65. what if AWS goes down?
66. AWS America East Rackspace OpenCloud DNS
67. 18 million visitors per month 3 million + users 410TB of data
68. 12 Employees
69. 30 million users 150 million photos
70. 3 engineers
71. Sold for $1 billion to Facebook
72. OK. Got it! How do I use the cloud?
73. There are many approaches to “the cloud” but we are going to talk about 2
74. The ones I think you’ll care about
76. you rent an instance
77. you manage your OS
78. upgrade packages
79. take care of security
80. ... and availability
81. it’s the closest to renting a physical server on a data center
82. maximum control
83. management over web console or api
85. They provide a container for your app
86. Easy deployment
87. git push heroku master
88. They take care of OS level issues
89. Super easy scaling
90. They enforce good app design
91. Less control over the environment
92. They run on top of AWS
93. What should I use?
94. Well, it depends
95. Understand the AWS model
96. Start with Heroku
97. Move to AWS when it’s absolutely necessary
99. Hands-on
101. Login to the AWS console
102. Create a Linux instance
103. Install Apache and PHP
104. Create a simple PHP script
105. Warning
106. Let’s do it
107. https://blimp.signin.aws.amazon.com/console
123. chmod 600 keyfile.pem
124. ssh -i keyname.pem ubuntu@hostname
125. sudo aptitude install apache2
126. sudo aptitude install php5 libapache2-mod-php5
127. cd /var/www/
128. sudo mv index.html index.php
129. sudo vim index.php
130. <?php echo 'AppServer: ' . gethostname(); ?>
131. Now what?
132. Live demo
133. Creating an image from a running instance
134. Launch an instance from an image
135. Creating an ELB
136. Me gusta
137. ProTips™
138. Free Tier
139. Micro instances are throttled down after a few minutes of heavy use
140. Using the biggest available instance size gets you a “full” machine
141. Chaos Monkey
142. Homework: Try to learn some Python
143. That’s it for today... Questions
144. Day 2
145. Cloud Computing for Hackers
147. Load Balancer Web Dyno Web Dyno Worker Dyno Cron Dyno HTTP Request HTTP Response
148. Load Balancer Web Dyno Web Dyno Worker Dyno Cron Dyno HTTP Request HTTP Response Ruby, Python, Scala, Java, Javascript, PHP
149. They do SysOps
150. You make web apps
151. Let’s try it
152. Setup a Python dev environment
153. Create a virtualenv for our first project
154. Create the simplest web app ever made
155. Deploy to Heroku
156. Make changes to the app
157. Deploy again
158. Start * tested on Mac OSX
159. mkdir ~/.virtualenvs
160. sudo easy_install pip
161. sudo pip install virtualenvwrapper
162. vim ~/.bash_profile
163. export WORKON_HOME=$HOME/.virtualenvs source /usr/local/bin/virtualenvwrapper.sh .bash_profile
164. source ~/.bash_profile
165. cd ~/Desktop mkdir myapp cd myapp
166. mkvirtualenv myapp
167. pip install flask pip freeze > requirements.txt
168. app.py import os from flask import Flask app = Flask(__name__) app.debug = True @app.route("/") def hello(): return 'Hello: {}'.format(os.uname()[1]) if __name__ == "__main__": port = int(os.environ.get('PORT', 5000)) app.run(host='0.0.0.0', port=port)
169. python app.py open http://localhost:5000
170. vim Procfile
171. web: python app.py Procfile
172. git init git add . git commit -m ‘Initial Commit’
173. Install the Heroku Toolbelt https://toolbelt.heroku.com
174. Sign up to Heroku https://api.heroku.com/signup
175. heroku login
176. heroku create
177. git push heroku master
178. heroku open
179. import os from flask import Flask app = Flask(__name__) app.debug = True @app.route("/") def hello(): return 'Bye: {}'.format(os.uname()[1]) if __name__ == "__main__": port = int(os.environ.get('PORT', 5000)) app.run(host='0.0.0.0', port=port) app.py
180. git commit -am ‘Small copy change’
181. git push heroku master
182. heroku open
183. Something more exiting, please * tested on Mac OSX
184. Let’s use Redis
185. brew install redis * Mac OSX only
186. pip install redis
187. pip freeze > requirements.txt
188. import os import redis redis_url = os.getenv('REDISTOGO_URL', 'redis://localhost:6379/0') redis = redis.from_url(redis_url) store.py
189. mkdir templates vim templates/index.html
190. <!doctype html> <html> <head> <meta charset="utf-8"> <title>The List</title> </head> <body> <ul> {% for item in the_list %} <li>{{ item }}</li> {% endfor%} </ul> </body> </html> index.html
191. import os import time from flask import Flask from flask import render_template from store import redis app = Flask(__name__) app.debug = True @app.route("/") def hello(): redis.rpush('thelist', 'Hello: {} - {}'.format(os.uname()[1], time.time())) the_list = redis.lrange('thelist', 0, -1) return render_template('index.html', the_list=the_list) if __name__ == "__main__": port = int(os.environ.get('PORT', 5000)) app.run(host='0.0.0.0', port=port) app.py
192. git add . git commit -am ‘Added redis’
193. heroku addons:add redistogo:nano
194. git push heroku master heroku open
195. How can I manage the app?
196. heroku ps
197. heroku logs
198. heroku config
199. ProTips™
200. heroku logs --tail
201. heroku run bash
202. heroku maintenance:on heroku maintenance:off
203. Prevent app from sleeping http://pingdom.com
204. Use foreman locally to run multiple app processes
205. web: python app.py redis: redis-server Procfile.local
206. foreman start -f Profile.local
207. Q&A
208. Giovanni Collazo @gcollazo