Infrastructure In The Cloud Era

1,051 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,051
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Infrastructure In The Cloud Era

  1. 1. Infrastructure in the Cloud Era Adam Jacob - Co-founder & CTO, Opscode Ezra Zygmuntowicz - Co-Founder & Mad Scientist Engine Yard Opscode Wednesday, April 8, 2009
  2. 2. Please Join our Ad-Hoc Cloud If you have a Mac with Developer Tools installed... curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  3. 3. What are you guys talking about? • Bootstrapping • Configuration • Command and Control curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  4. 4. Many Different Tools curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  5. 5. Bootstrapping curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  6. 6. Bootstrapping Approaches Good Bad Time Known Costs, No High Waste (Hoarding) Variation. Red Tape Corp Approvals Anything you want, as long Expensive ($/Time) 6-8w as IT pre-approved it. Long lead time Lower Waste Agile Corp Known Costs. Less Red Tape Total Hardware Control. Still slow 2-4w Approvals Trivial Approvals. Expensive ($/Time) Shorter lead time Variable Costs. Highly Adaptable. Variable Costs. Cloud Minimal lead time. Trivial approvals. No control over hardware. Must re-train. 5-10m No humans needed. curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  7. 7. Why Time Matters Total Bootstrapping Time in Weeks Corp Approvals Agile Approvals Cloud 8 6 4 2 0 Best Time 0 Worst Time curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  8. 8. Tools for Bootstrapping PXE Boot FAI System Imager Kickstart Cobbler curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  9. 9. Bootstrapping Demo Engine Yard Solo Now would be a totally sweet time to pull out your Mac and run... curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  10. 10. Configuration curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  11. 11. java logrotate bind postgresql rubygems redmine iptables mongrel rails Manage perlbal memcached munin resolver nginx php logwatch ports ebuilds maradns erlang apt-proxy nagios openssh Complexity nscd sudo apache keepalived mysql trac dpkgs ntp openldap rpms ipvsadm jira rsync subversion couchdb curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  12. 12. Configuration Approaches Good Bad Slow. You can do anything. Error Prone (Bus Error!) Manual Results in an intimate knowledge of the details. Non-repeatable. Difficult knowledge transfer. Rarely idempotent. More repeatable. Hard to collaborate. Ad-Hoc Knowledge is dispersed. Built your way, with your model. Brittle. No API. Repeatable. Infrastructure as Idempotent. Agile. Have to learn how to use it. Hard things remain hard. Code Sharable. Self documenting. Not magic. (Yet!) curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  13. 13. Tools for Configuration Chef, Puppet, Cfengine, Bcfg2 Shell Scripts, Perl, Python, Ruby, etc. Operating System tools Your favorite text editor curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  14. 14. Infrastructure as Code Manage configuration as idempotent Resources. Put them together in Recipes. Track it like source code. Configure your servers. You can learn more about Chef at http://wiki.opscode.com/display/chef/Home curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  15. 15. You need an API You can learn more about Chef at http://wiki.opscode.com/display/chef/Home curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  16. 16. Command and Control You are running out of time to join the Ad-Hoc Cloud Party! curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  17. 17. Command and Control Good Bad Super flexible. Error Prone. Can do almost anything. Slow. Meatcloud* Always easy to find someone to blame. Expensive to Scale. Not repeatable. Free will. Free will. One-off by neccessity. More repeatable. Tooling sprawl. Ad-Hoc Easier to scale. Less error prone (hopefully!) Hard to share solutions. Much higher learning curve. One system to learn. Scales well. Not everything maps cleanly. Framework Paint by numbers. Repeatable. Trades depth of knowledge for ease of use. Two-Way. *Meatcloud appears in this presentation courtesy of Andrew Shafer - http://is.gd/Ega Last Chance! - curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  18. 18. Tools for Command and Control Nanite, Capistrano, Control Tier Shell Scripts, Perl, Python, Ruby, etc. You Your co-workers Last Chance! - curl -O https://cloud.engineyard.com/w2e.sh && sh w2e.sh Wednesday, April 8, 2009
  19. 19. Command and Control Demo You can learn more about Nanite at http://github.com/ezmobius/nanite/tree/master Wednesday, April 8, 2009
  20. 20. What else can you do? • Application Deployment • Starting and stopping services • Maintenance • You name it. Wednesday, April 8, 2009
  21. 21. In Practice Wednesday, April 8, 2009
  22. 22. Typical Peak Load 1. Bring on capacity as traffic ramps up 2. Take down capacity as it ramps down 3. 10-15 Minutes on either side, fully unattended Graphs in this portion of the presentation taken from Theo Schlossnagle http://omniti.com/seeds/dissecting-todays-internet-traffic-spikes Wednesday, April 8, 2009
  23. 23. Atypical Load No way However, around you are Capacity still better Planning off! 1. Hope you know it is coming. 2. Increase capacity in advance. 3. Take down capacity as it ramps down. Graphs in this portion of the presentation taken from Theo Schlossnagle http://omniti.com/seeds/dissecting-todays-internet-traffic-spikes Wednesday, April 8, 2009
  24. 24. 1. Signal Command and Control 2. Analyze Responses 3. Rinse and Repeat 4. Profit Wednesday, April 8, 2009
  25. 25. 1. Your infrastructure is disposable. 2. Make sure you can turn each layer off. 3. New efficiencies often lead to new hard problems. Wednesday, April 8, 2009
  26. 26. Q &A Brought to you by... Opscode You can learn more about Chef at http://wiki.opscode.com/display/chef/Home You can learn more about Nanite at http://github.com/ezmobius/nanite/tree/master Wednesday, April 8, 2009

×