DevOps Columbus Meetup Kickoff - Infrastructure as Code
•
1 like•1,322 views
Slides from the DevOps Columbus Meetup Kickoff meeting.
Recommended
Recommended
More Related Content
What's hot
What's hot (19)
Viewers also liked
Viewers also liked (20)
Similar to DevOps Columbus Meetup Kickoff - Infrastructure as Code
Similar to DevOps Columbus Meetup Kickoff - Infrastructure as Code (20)
More from Michael Ducy
More from Michael Ducy (20)
Recently uploaded
Recently uploaded (20)
DevOps Columbus Meetup Kickoff - Infrastructure as Code
- 1. July 11, 2013 DevOps Columbus Meetup
- 2. Agenda • 5:30 – 6:00 – Meet, greet, and eat • 6:00 – 6:15 – Welcome, introductions, and agenda • 6:15 – 6:45 – Infrastructure as Code • 6:45 – 7:00 – Meetup group logistics • 7:00 – 7:30 – "Picks, Tips, and Protips" and then 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? “Field Guy” 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. Who am I? • Linux Engineer • Operations • Performance and Capacity • Software Consulting • Cloud Architect • Opscode • Buckeye, Maroon • @mfdii, michael@opscode.com
- 6. “Rules of Engagement” 3 Rules of DevOps Meetup
- 7. 1st Rule: Talk about DevOps Meetup “Rules of Engagement”
- 9. 2nd Rule: TALK about DevOps Meetup “Rules of Engagement”
- 10. 3rd Rule: No Assholes “Rules of Engagement”
- 11. Collaborate and debate NO disrespect “Rules of Engagement”
- 12. “Rules of Engagement” DevOps = Community
- 15. DevOps = CAMS • Culture • Automation • Measurement • Sharing
- 16. DevOps is not: • A Job Description • A marketing term • A new product • A problem • A name for a team • Is not just “Development + Operations”
- 17. “Infrastructure As Code” 101
- 18. Infrastructure IT is Complex
- 19. Items of Manipulation (resources) • Nodes • Networking • Files • Directories • Symlinks • Mounts • Routes • Users • Groups • Packages • Services • Filesystems
- 22. Application App Databases See Nodes Grow
- 23. App Servers App Databases See Nodes Grow
- 24. App LB App Servers App Databases See Nodes Grow
- 25. App LBs App Servers App Databases See Nodes Grow
- 26. App LBs App Servers App DB Cache App DBs See Nodes Grow
- 27. App LBs App Servers App DB Cache App DBs See a Topology
- 28. Round Robin DNS App Servers App DB Cache App DBs Floating IP? Yours is a snowflake
- 29. App LBs App Servers NoSQL DB slaves Cache DB Cache DBs Grows in complexity
- 31. USA EUR AUS How can this be abstracted AND represented?
- 32. 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.
- 33. 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 Virtual Nodes Physical Hardware Coded Businesses = Unprecedented IT Complexity 1980 Mainframe 1990 Client/Server 2000 Datacenter 2010+ Cloud Scale x Complexity > Skills
- 34. 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 Virtual Nodes Physical Hardware Inflection Point Inspires … The coded business Mainframe Client/Server Datacenter Future 35 Inflection point forces disruption.
- 35. 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
- 36. “In God we trust, all others bring DATA!!!” –W. Edwards Deming http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html VS
- 37. Patterns of the Coded Business • Enables Continuous Change • Enforces Consistency • Provides a Common Coded Platform For Applications and Infrastructure • Leverages Scarce Talent Through Reuse • Transcends Organizational Boundaries The Result – IT enables Business Agility and becomes a strategic advantage rather than a cost center. Business Agility Development Velocity and Consistency Continuous Delivery Infrastructure Automation
- 38. • 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 “Infrastructure As Code”
- 39. package { "apache2": ensure => latest } service { "apache2": ensure => running, require => Package["apache2"], subscribe => File[httpdconf], } Puppet
- 40. 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” Chef
- 41. Metaphor Attribution – Andrew Shafer, now of Rackspace Dev Ops& The Players
- 42. • Little bit weird • Sits closer to the boss • Thinks too hard Don’t hate the player … Metaphor Attribution – Andrew Shafer, now of Rackspace Meet Dev
- 43. • Pulls levers & turns knobs • Easily excited • Yells a lot in emergencies Why you be hatin ? ! ? Metaphor Attribution – Andrew Shafer, now of Rackspace Meet Ops
- 44. Traditional Process Dev’s job is to add new features. Ops’ job is to keep the site stable and fast
- 45. 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 ?
- 46. 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 ?
- 47. Step 1 – SCM and Developers Application Devs Infrastructur e Devs Software Configuration Management (SCM)
- 48. Step 2 – Introducing the Build Stage Software Configuration Management (SCM) Build Payload N Payload 3 Payload 2 Payload 1 Changes in SCM triggers builds and tests Application Devs Infrastructur e Devs
- 49. 1 2 …. Step 3 – “Infrastructure As Code” and the CD Process Software Configuration Management (SCM) Build Payload N Payload 3 Payload 2 Payload 1 Create Data (#) Upload Policies Autodeploy to localhost Request Portal IAC Autodeploy Application Devs Infrastructure Devs QA DEV ….. PROD Promote Promote Latest Codebase and Build 1, 2, … N ….. N Builds Update DEV
- 50. Stathy Touloumis stathy@opscode.com Twitter | IRC | github: stathyinc Michael Ducy michael@opscode.com Twitter | IRC | github: mfdii
- 51. 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
Editor's Notes
- 5:30 – 6:15 – Meet, greet, and eat6:15 – 7:00 – Welcome, introductions, and agenda7:00 – 7:30 – Meetup group logisticsExpectations and general thoughtsPotential future topics we'd like to coverDetermine how often we'd like to meet7:30 – 7:45 – Infrastructure as Code, short prezo7:45 – 8:00 – "Picks" and then wrap-up.Solidify next few topics to coverPick topic(s) and speaker(s) for the next meeting8:00 Wrap-up
- Pre-empt introductions with a simple yet powerful statement.Spirit of community and collaboration.
- Main – Help bootstrap technology groups around Midwest region.Began tech career diving feet first into co-founding ISP, multiple downturns and upturns, multiple generations of Automation technology, 7 yrs Software Eng, 3 yrs leadingApply learning in different contexts – industries, maturity, organizations, cultures
- Main – Help bootstrap technology groups around Midwest region.Began tech career diving feet first into co-founding ISP, multiple downturns and upturns, multiple generations of Automation technology, 7 yrs Software Eng, 3 yrs leadingApply learning in different contexts – industries, maturity, organizations, cultures
- Context around “No Assholes”Have respect for others who may be less experienced, have less exposure or maybe just do not learn as fast.Have respect for those who may have limited time and/or realize some topics are not easily conveyed.Mutual Respect
- Mutual RespectIt’s not so much about just technology but the complete interaction of people, process and technology used.If you can’t get along with people, you are missing a big part of the equation.
- DevOps is bigger than Dev and OpsSpans other tech groups, dba’s, QASpans business side tooGet out of the “us” vs “them” mentality
- Things to decide after prezoTopic Coverage possibilitiesMeeting frequency[Come up with several topics]
- DevOps is bigger than Dev and OpsSpans other tech groups, dba’s, QASpans business side tooGet out of the “us” vs “them” mentality
- DevOps is bigger than Dev and OpsSpans other tech groups, dba’s, QASpans business side tooGet out of the “us” vs “them” mentality
- DevOps is bigger than Dev and OpsSpans other tech groups, dba’s, QASpans business side tooGet out of the “us” vs “them” mentality
- DevOps is bigger than Dev and OpsSpans other tech groups, dba’s, QASpans business side tooGet out of the “us” vs “them” mentality
- DevOps is bigger than Dev and OpsSpans other tech groups, dba’s, QASpans business side tooGet out of the “us” vs “them” mentality
- SALES>Traditional Enterprise Tech VS. “Infrastructure As Code”Give a hint to the fact that this is a config/automation problem specifically, not just a shift in computing architectureThe inflection, caused by scale and complexity pain, is what has accelerated the disruption in how IT is managed. This disruption is “Infrastructure As Code” (IT Service As Code).The next slide goes into more technical depth on why the old model doesn’t work. High Level :Dated technologies limits scalability and functionality (no SaaS). It’s why job scheduling (intro of automation) is not used for most current platforms and technology strategies.In addition, useability (directly impacts productivity) is immediately stale. Most enterprise products do a poor job of representing the data model in the first place let alone keep pace with how IT is managed. As new vendors and platforms come into play which require integration, the gap (breadth and depth) between supporting them becomes bigger.Mapping a data model (rigid, static) to the IT infrastructure limits ability to support new platforms/models. The proliferation of cloud exposes this further.Reached just a handful of large, enterprise customers which inevitably required custom implementations with large professional services bills.
- TECH-> “Infrastructure As Code” Opscode positionDon’t directly discount or object to other “Infrastructure As Code” platforms. Let the prezo do that subtly, this is a final stake into the legacy enterprise automation platforms. The next section will focus on why Opscode Chef and what makes it unique. Opscode Chef was designed based on previous competitor limitations and is better positioned to evolve with the current tech landscape.Source code – Agile, leveragedev best-practices for managing infrastructure change.Community – Easily support cutting edge tech *now* vs. 15 month releaseNext gen architecture – SaaS, opensource, scalable, API drivenUseability – Declarative programming, representative of domain, flexible yet lower learning curve than *heavy* enterprise app.
- SALES-> “Infrastructure As Code” Opscode positionObvious, several articles on Oreilly discussing studies and data from companies using “secret sauce” tech which is really “Infrastructure As Code” VS traditional methods including enterprise tech.http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html
- How does this apply to DevOps?So how many people recognize these characters? And I’m not just talking about Spock and Scotty, how many people recognize the traditional IT roles embedded in their behaviors.Metaphor Attribution – Andrew Shafer, now of Rackspace
- And furthermore, we think these two roles have always pinned dev and ops against each other. Developers are measured based on the output of new functionality they churn out. Create a bunch of features, send them over the wall to Q&A/release/ops who are left to deploy and scale that new functionality while keeping the site up. Ops meanwhile, is really only tasked with just that, with keeping everything running as a sole focus. What is the single most common way to make a running site go down, introduce change…
- And this is what it looks like. Application and Infrastructure developers and operators check in their code to version control.
- The commits (once approved) will get picked up by the continuous integration tool (like Jenkins), which will build the code, deploy to a test infrastructure and start testing.
- That cycle of build, deploy and test repeats until it fails or gets to production. Catching issues and smoketesting your changes well before they get to Production.