1. December 5, 2012
Kansas City DevOps Meetup

2. Agenda
• 5:30 – 6:15 – Meet, greet, and eat
• 6:15 – 6:45 – Google Fiberspace Presentation
• 6:45 – 7:00 – Agenda and Introductions
• 7:00 – 7:30 – Meetup group logistics
• 7:30 – 7:45 – Presentation – Aaron (Cerner) and Stathy
(OpsCode)
• 7:45 – 8:00 – Volunteers and next meeting decisions
• 8:00 Q&A and Wrap-up

3. “We are at our most productive when we share our thinking.
One night of crazy brain-storming over a few beers is more
likely to produce more exciting results than 20 years’
solitary study in the lab.”
–Professor Howard Trevor Jacobs, Descartes Prize Winner
Read more at redmonk.com - http://goo.gl/FEJyI
http://redmonk.com/jgovernor/2004/12/15/the-pub-is-the-place-for-creativity-and-innovation/

4. Who am I?
Area Director
My agenda
Bootstrap Meetups
Learn more
Share experiences with people from diverse backgrounds
Introductions …
~ 1m round the room brief intro, don’t be too shy 

5. “Rules of Engagement”
3 Rules of DevOps Meetup

6. “Rules of Engagement”
1st Rule:
Talk about DevOps
Meetup

7. “Rules of Engagement”
Collaboration
&
Community

8. “Rules of Engagement”
2nd Rule:
TALK about
DevOps Meetup

9. “Rules of Engagement”
3rd Rule:
No Assholes

10. “Rules of Engagement”
Collaborate and debate
NO disrespect

12. “Rules of Engagement”
DevOps = Community

13. Logistics
• Topic coverage? topic focus?
• Lightning talks, 4-5, 5-10m each
• Unmeeting – Larger group
• Presentations – Intro & Advanced
• Demo & Tutorial
• Case studies and experience sharing.
• Monthly? Bi-monthly? Quarterly?

14. “Infrastructure As Code” 101

15. Infrastructure is Complex

16. • Nodes
• Networking
• Files
• Directories
• Symlinks
• Mounts
• Routes
• Users
• Groups
• Packages
• Services
• Filesystems
Items of Manipulation
(resources)

17. Application
See Node

18. Application
Application Database
See Nodes

19. Application
App Databases
See Nodes Grow

20. App Servers
App Databases
See Nodes Grow

21. App LB
App Servers
App Databases
See Nodes Grow

22. App LBs
App Servers
App Databases
See Nodes Grow

23. App LBs
App Servers
App DB Cache
App DBs
See Nodes Grow

24. App LBs
App Servers
App DB Cache
App DBs
Infrastructures have topology

25. Round Robin
DNS
App Servers
App DB Cache
App DBs
Floating IP?
Yours is a snowflake

26. App LBs
App Servers
NoSQL
DB slaves
Cache
DB Cache
DBs
Complexity increases quickly

27. USA
EUR
AUS
It increases globally...

28. Traditional Thinking Won’t Make the Grade …
Before discussing the future,
Let’s review the past.
More importantly why
“traditional” enterprise
technologies will not cut it.

29. 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 20151980 1981 1982 1983 1984 1985 1986 1987 1988 1989
Unprecedented Growth AND Complexity …
1980
Mainframe
1990
Client/Server
2000
Datacenter
2010+
Cloud
Scale x Complexity > Skills
Inflection point forces
disruption.

30. Inflection Point Inspires …
Mainframe Client/Server Datacenter
Cloudy
-
20
40
60
80
100
120
1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015
Millions
Physcial Hardware Virtual Nodes
Traditional, data
model driven
applications.
Traditional, doma
in model driven
applications.
“Infrastructure As
Code”
“Infrastructure As
Code”

31. USA
EUR
AUS
How can this be abstracted AND represented?

32. 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015
Maturity of “Infrastructure As Code”

33. “In God we Trust, all others bring DATA!!!”
http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html
VS

34. • A configuration management system (DSL)
• A library for configuration management
• A community, contributing to library and expertise
• A systems integration platform (API)
http://www.flickr.com/photos/asten/2159525309/sizes/l/
“Infrastructure As Code”

35. Some Samples
package { "apache2":
ensure => latest
}
service { "apache2":
ensure => running,
require => Package["apache2"],
subscribe => File[httpdconf],
}

36. Some Samples
package "apache2" do
package_name node[:apache][:package]
action :install
end
template "/etc/www/configures-apache.conf" do
notifies :restart, "service[apache2]”
end
service “apache2”

37. The players
Metaphor Attribution – Andrew Shafer, now of Rackspace
Dev Ops&

38. Meet Dev
• Little bit weird
• Sits closer to the boss
• Thinks too hard
Don’t hate the
player …
Metaphor Attribution – Andrew Shafer, now of Rackspace

39. Meet Ops
• Pulls levers & turns knobs
• Easily excited
• Yells a lot in emergencies
Why you be hatin
? ! ?
Metaphor Attribution – Andrew Shafer, now of Rackspace

40. Traditional Process
Dev’s job is to add new
features.
Ops’ job is to keep the site
stable and fast

41. Load
Balancer
App Server
Database
Dev (shared)
Dev - QA - UAT - Prod
Load Balancer
App Server App Server
Database
Load
Balancer
App Server
Database
QA
Agility - Design vs Manufacturing
How ?

42. Dev ProdQA
Goal = Increase Velocity
Agility - Design vs Manufacturing
Load
Balancer
App
Server
App
Server
Database
Load
Balancer
App
Server
App
Server
Database
Load
Balancer
App
Server
App
Server
Database
What ?

43. “Infrastructure As Code” + Continuous Deployment
Value of Continuous Deployment?
• Visibility and Accountability
• Reduce Risk
• Increase Productivity
• Innovate Faster
• Business Agility

44. Thank You!
Stathy Touloumis
stathy@opscode.com
Twitter | IRC | github: stathyinc

45. Thank You!
Aaron Blythe
aaron.blythe@gmail.com
Twitter: ablythe
Github: aaronblythe

46. Topic Brainstorming
• 7:45 – 8:00 – Volunteers and Topics
• Frequency of meeting – 5th of every month?
• Solidify next few topics to cover
• Pick topic(s) and speaker(s) for the next meeting