9. For Developers...
• Do it yourself.
• The infrastructure is the application
(and vice versa).
10. For Developers...
• Do it yourself.
• The infrastructure is the application
(and vice versa).
• You are not a Systems Administrator.
11. For Developers...
• Do it yourself.
• The infrastructure is the application
(and vice versa).
• You are not a Systems Administrator.
• You need tools.
12. Sysadmins..
http://covers.oreilly.com/images/9780596007836/lrg.jpg
Lean into it appears courtesy of Cliff Moon, of Dynomite fame: http://twitter.com/moonpolysoft
13. Sysadmins..
• Say “Yes”.
http://covers.oreilly.com/images/9780596007836/lrg.jpg
Lean into it appears courtesy of Cliff Moon, of Dynomite fame: http://twitter.com/moonpolysoft
14. Sysadmins..
• Say “Yes”.
• You never liked rack
and stack that much
anyway.
http://covers.oreilly.com/images/9780596007836/lrg.jpg
Lean into it appears courtesy of Cliff Moon, of Dynomite fame: http://twitter.com/moonpolysoft
15. Sysadmins..
• Say “Yes”.
• You never liked rack
and stack that much
anyway.
• You have never
been more critical.
http://covers.oreilly.com/images/9780596007836/lrg.jpg
Lean into it appears courtesy of Cliff Moon, of Dynomite fame: http://twitter.com/moonpolysoft
16. Sysadmins..
• Say “Yes”.
• You never liked rack
and stack that much
anyway.
• You have never
been more critical.
• Lean into it.
http://covers.oreilly.com/images/9780596007836/lrg.jpg
Lean into it appears courtesy of Cliff Moon, of Dynomite fame: http://twitter.com/moonpolysoft
19. Executives...
• Not a magic unicorn
• Benefits come from efficiency, not raw Capex
20. Executives...
• Not a magic unicorn
• Benefits come from efficiency, not raw Capex
• Has real cultural implications at every level
21. Executives...
• Not a magic unicorn
• Benefits come from efficiency, not raw Capex
• Has real cultural implications at every level
• You are the biggest asset to success
55. Private Public
nt t o SaaS
a
w d s,
o u lo u
y c
If l k
PaaS
rs t.PaaS
t a ne f i
i ck o
IaaS p IaaS
Managed
Virtualization
hosting
Slide courtesy Alistair Croll - alistair@rednod.com
56. Infrastructure as a Service
(IaaS)
Amazon EC2, Rackspace Cloud, Terremark,
Gogrid, Joyent (and nearly every private
cloud built on Zenserver or VMWare.)
Slide courtesy Alistair Croll - alistair@rednod.com
59. Always on
premise
Private
Compliance-
enforced
Need to track and
audit
Legislative
Data near local
computation
Slide courtesy Alistair Croll - alistair@rednod.com
60. Always on Can be done
premise anywhere
Private
Compliance- Testing
enforced
Training
Need to track and
Prototyping
audit
Batch processing
Legislative
Seasonal load
Data near local
computation
Slide courtesy Alistair Croll - alistair@rednod.com
61. Always on Can be done Always in
premise anywhere cloud
Private
Partner access
Compliance- Testing
enforced Proximity to cloud
Training services (storage,
Need to track and
Prototyping CDN, etc.)
audit
Batch processing Massively grid/
Legislative
Seasonal load parallel (genomic,
Data near local modelling)
computation
Slide courtesy Alistair Croll - alistair@rednod.com
62. Always on Can be done Always in
premise anywhere cloud
Load/pricing engine
Private
Partner access
Compliance- Testing
enforced Proximity to cloud
Training services (storage,
Need to track and
Prototyping CDN, etc.)
audit
Batch processing Massively grid/
Legislative
Seasonal load parallel (genomic,
Data near local modelling)
computation
Slide courtesy Alistair Croll - alistair@rednod.com
63. Always on Can be done Always in
premise anywhere cloud
Load/pricing engine
Private
Partner access
Compliance- Testing
enforced Proximity to cloud
Training services (storage,
Policy engine
Need to track and
Prototyping CDN, etc.)
audit
Batch processing Massively grid/
Legislative
Seasonal load parallel (genomic,
Data near local modelling)
computation
Slide courtesy Alistair Croll - alistair@rednod.com
64. Virtual machine
(infrastructure cloud)
Always on Can be done Always in
premise anywhere cloud
Load/pricing engine
Private
Partner access
Compliance- Testing
enforced Proximity to cloud
Training services (storage,
Policy engine
Need to track and
Prototyping CDN, etc.)
audit
Batch processing Massively grid/
Legislative
Seasonal load parallel (genomic,
Data near local modelling)
computation
Slide courtesy Alistair Croll - alistair@rednod.com
65. Compute task
(service cloud)
Always on Can be done Always in
premise anywhere cloud
Load/pricing engine
Private
Partner access
Compliance- Testing
enforced Proximity to cloud
Training services (storage,
Policy engine
Need to track and
Prototyping CDN, etc.)
audit
Batch processing Massively grid/
Legislative
Seasonal load parallel (genomic,
Data near local modelling)
computation
Slide courtesy Alistair Croll - alistair@rednod.com
68. 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.
70. 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 Idempotent.
Agile.
Have to learn how to use it.
Hard things remain hard.
as Code Sharable.
Self documenting.
Not magic. (Yet!)
72. 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
82. 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
83. 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
84. Capacity Planning is
king.
http://www.flickr.com/photos/allspaw/2095439645/sizes/l/