Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Milwaukee DevOps MeetupDecember 5, 2012
“We are at our most productive when we share our thinking.One night of crazy brain-storming over a few beers is morelikely...
Who am I?Solution Engineer and EvangelistMy agenda   Bootstrap Meetups   Learn more   Share experiences with people from d...
“Rules of Engagement”3 Rules of DevOps Meetup
“Rules of Engagement”1 st   Rule:Talk about DevOpsMeetup
“Rules of Engagement”Collaboration      & Community
“Rules of Engagement”2 nd   Rule:TALK aboutDevOps Meetup
“Rules of Engagement”3 rd   Rule:No Assholes
“Rules of Engagement”Collaborate and debate     NO disrespect
“Rules of Engagement”DevOps = Community
Logistics• Topic coverage? topic focus? • Lightning talks, 4-5, 5-10m each • Unmeeting – Larger group • Presentations – In...
“Infrastructure As Code” 101
Infrastructure is Complex
Items of Manipulation                                          (resources)• Nodes         • Routes• Networking    • Users•...
See NodeApplication
See NodesApplicationApplication Database
See Nodes GrowApplicationApp Databases
See Nodes GrowApp ServersApp Databases
See Nodes GrowApp LB         App ServersApp Databases
See Nodes GrowApp LBs                App ServersApp Databases
See Nodes GrowApp LBs               App ServersApp DB CacheApp DBs
Infrastructures have topology        App LBs                      App Servers       App DB Cache       App DBs
Yours is a snowflake   Round Robin   DNS                 App Servers  App DB CacheFloating IP?   App DBs
Complexity increases quickly           App LBs                 Cache                     App ServersNoSQL            DB Ca...
It increases globally...      EURUSA                         AUS
Traditional Thinking Won’t Make the Grade …               Before discussing the future,               Let’s review the pas...
Unprecedented Growth AND Complexity …                                         Scale x Complexity > Skills                 ...
Inflection Point Inspires …    Mainframe                                           Client/Server                          ...
How can this be abstracted AND represented?                 EURUSA                                    AUS
Maturity of “Infrastructure As Code”1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2...
“In God we Trust, all others bring DATA!!!”     VS             http://radar.oreilly.com/2007/10/operations-is-a-competitiv...
“Infrastructure As Code” Mantra“Infrastructure As Code” …         The business, not just a tool     Enable the reconstruct...
“Infrastructure As Code”• A configuration management system (DSL)• A library for configuration management• A community, co...
Some Samplespackage { "apache2":      ensure => latest}service { "apache2":    ensure => running,    require => Package["a...
Some Samplespackage "apache2" do package_name node[:apache][:package] action :installendtemplate "/etc/www/configures-apac...
The players                    Dev                              &   OpsMetaphor Attribution – Andrew Shafer, now of Racksp...
Meet Dev                                                   • Little bit weird                                             ...
Meet Ops                                                   • Pulls levers & turns knobs                                   ...
Traditional ProcessDev’s job is to add newfeatures.Ops’ job is to keep the sitestable and fast
Agility - Design vs Manufacturing   Load          Load                     Load Balancer  Balancer      Balancer App Serve...
Agility - Design vs Manufacturing                             Goal = Increase Velocity          Load                      ...
Step 1 – SCM and DevelopersApplication      Software  Devs          Configuration                Management               ...
Step 2 – Introducing the Build Stage                                      Build    Changes in                             ...
Step 3 – “Infrastructure As Code” and the CD Process                                             Latest Codebase and      ...
Thank You!       Stathy Touloumis    stathy@opscode.comTwitter | IRC | github: stathyinc
Topic Brainstorming• 7:45 – 8:00 – Volunteers and Topics • Frequency of meeting – 5 of every month?                       ...
Upcoming SlideShare
Loading in …5
×

Stathy DevOps in MSP / MKE on IAC

1,815 views

Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Stathy DevOps in MSP / MKE on IAC

  1. 1. Milwaukee DevOps MeetupDecember 5, 2012
  2. 2. “We are at our most productive when we share our thinking.One night of crazy brain-storming over a few beers is morelikely 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/
  3. 3. Who am I?Solution Engineer and EvangelistMy agenda Bootstrap Meetups Learn more Share experiences with people from diverse backgroundsIntroductions … ~ 1m round the room brief intro, don’t be too shy 
  4. 4. “Rules of Engagement”3 Rules of DevOps Meetup
  5. 5. “Rules of Engagement”1 st Rule:Talk about DevOpsMeetup
  6. 6. “Rules of Engagement”Collaboration & Community
  7. 7. “Rules of Engagement”2 nd Rule:TALK aboutDevOps Meetup
  8. 8. “Rules of Engagement”3 rd Rule:No Assholes
  9. 9. “Rules of Engagement”Collaborate and debate NO disrespect
  10. 10. “Rules of Engagement”DevOps = Community
  11. 11. 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?
  12. 12. “Infrastructure As Code” 101
  13. 13. Infrastructure is Complex
  14. 14. Items of Manipulation (resources)• Nodes • Routes• Networking • Users• Files • Groups• Directories • Packages• Symlinks • Services• Mounts • Filesystems
  15. 15. See NodeApplication
  16. 16. See NodesApplicationApplication Database
  17. 17. See Nodes GrowApplicationApp Databases
  18. 18. See Nodes GrowApp ServersApp Databases
  19. 19. See Nodes GrowApp LB App ServersApp Databases
  20. 20. See Nodes GrowApp LBs App ServersApp Databases
  21. 21. See Nodes GrowApp LBs App ServersApp DB CacheApp DBs
  22. 22. Infrastructures have topology App LBs App Servers App DB Cache App DBs
  23. 23. Yours is a snowflake Round Robin DNS App Servers App DB CacheFloating IP? App DBs
  24. 24. Complexity increases quickly App LBs Cache App ServersNoSQL DB Cache DB slaves DBs
  25. 25. It increases globally... EURUSA AUS
  26. 26. 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.
  27. 27. Unprecedented Growth AND Complexity … Scale x Complexity > Skills Inflection point forces disruption. 1980 1990 2000 2010+ Mainframe Client/Server Datacenter Cloud1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 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
  28. 28. Inflection Point Inspires … Mainframe Client/Server Datacenter CloudyTraditional, dataTraditional, doma model driven in model driven “Infrastructure As applications. Code” Millions 120 100 80 60 40 20 - 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 Physcial Hardware Virtual Nodes
  29. 29. How can this be abstracted AND represented? EURUSA AUS
  30. 30. Maturity of “Infrastructure As Code”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
  31. 31. “In God we Trust, all others bring DATA!!!” VS http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html
  32. 32. “Infrastructure As Code” Mantra“Infrastructure As Code” … The business, not just a tool Enable the reconstruction of the business from nothing but a configuration repository, an application data backup, and bare resources. As rapidly and elegantly as possible.
  33. 33. “Infrastructure As Code”• 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/
  34. 34. Some Samplespackage { "apache2": ensure => latest}service { "apache2": ensure => running, require => Package["apache2"], subscribe => File[httpdconf],}
  35. 35. Some Samplespackage "apache2" do package_name node[:apache][:package] action :installendtemplate "/etc/www/configures-apache.conf" do notifies :restart, "service[apache2]”endservice “apache2”
  36. 36. The players Dev & OpsMetaphor Attribution – Andrew Shafer, now of Rackspace
  37. 37. 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
  38. 38. Meet Ops • Pulls levers & turns knobs • Easily excited • Yells a lot in emergencies Why you be hatin ?!?Metaphor Attribution – Andrew Shafer, now of Rackspace
  39. 39. Traditional ProcessDev’s job is to add newfeatures.Ops’ job is to keep the sitestable and fast
  40. 40. Agility - Design vs Manufacturing Load Load Load Balancer Balancer Balancer App Server App Server App Server App Server Database Database DatabaseDev (shared) QA Dev - QA - UAT - Prod How ?
  41. 41. Agility - Design vs Manufacturing Goal = Increase Velocity Load Load Load Balancer Balancer Balancer App App App App App App Server Server Server Server Server Server Database Database Database Dev QA ProdWhat ?
  42. 42. Step 1 – SCM and DevelopersApplication Software Devs Configuration Management (SCM)Infrastructur e Devs
  43. 43. Step 2 – Introducing the Build Stage Build Changes in SCM triggers builds and Payload N testsApplication Software Devs Configuration Management (SCM) Payload 3 Payload 2 Payload 1Infrastructur e Devs
  44. 44. Step 3 – “Infrastructure As Code” and the CD Process Latest Codebase and Build Create Data (#) Upload Policies Build Update DEV DEV Autodeploy to IACApplication Devs localhost Promote Infrastructure Devs Payload Request Portal QA N 1, 2, … N Software Autodeploy Promote Configuration N PROD Management (SCM) Payload 3 ….. ….. Payload 2 2 …. Payload Builds 1 1
  45. 45. Thank You! Stathy Touloumis stathy@opscode.comTwitter | IRC | github: stathyinc
  46. 46. Topic Brainstorming• 7:45 – 8:00 – Volunteers and Topics • Frequency of meeting – 5 of every month? th • Solidify next few topics to cover • Pick topic(s) and speaker(s) for the next meeting

×