Download to read offline
![Some Samples
package { "apache2":
ensure => latest
}
service { "apache2":
ensure => running,
require => Package["apache2"],
subscribe => File[httpdconf],
}](https://image.slidesharecdn.com/devopskcmeetup5202013-130523212431-phpapp01/75/Devops-kc-meetup_5_20_2013-35-2048.jpg)
![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”](https://image.slidesharecdn.com/devopskcmeetup5202013-130523212431-phpapp01/75/Devops-kc-meetup_5_20_2013-36-2048.jpg)
Uploaded byAaron Blythe
Devops kc meetup_5_20_2013
This document contains the agenda for the Kansas City DevOps Meetup on December 5, 2012. The agenda includes presentations on Google Fiberspace and DevOps logistics by Aaron from Cerner and Stathy from OpsCode. It also discusses deciding on topics and volunteers for future meetups, with suggestions like infrastructure as code, continuous deployment, and experience sharing.
![[Rakuten TechConf2014] [C-2] Big Data for eBooks and eReaders](https://cdn.slidesharecdn.com/ss_thumbnails/c2koborit20141025-141105040826-conversion-gate01-thumbnail.jpg?width=640&height=640&fit=bounds)
Devops kc meetup_5_20_2013
- 1. December 5, 2012 KansasCity 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 atour 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? AreaDirector 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” 3Rules of DevOps Meetup
- 6. “Rules of Engagement” 1stRule: Talk about DevOps Meetup
- 7.
- 8. “Rules of Engagement” 2ndRule: TALK about DevOps Meetup
- 9. “Rules of Engagement” 3rdRule: No Assholes
- 10. “Rules of Engagement” Collaborateand 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.
- 15.
- 16. • Nodes • Networking •Files • Directories • Symlinks • Mounts • Routes • Users • Groups • Packages • Services • Filesystems Items of Manipulation (resources)
- 17.
- 18.
- 19.
- 20. App Servers App Databases SeeNodes Grow
- 21. App LB App Servers AppDatabases See Nodes Grow
- 22. App LBs App Servers AppDatabases See Nodes Grow
- 23. App LBs App Servers AppDB Cache App DBs See Nodes Grow
- 24. App LBs App Servers AppDB Cache App DBs Infrastructures have topology
- 25. Round Robin DNS App Servers AppDB Cache App DBs Floating IP? Yours is a snowflake
- 26. App LBs App Servers NoSQL DBslaves Cache DB Cache DBs Complexity increases quickly
- 27.
- 28. Traditional Thinking Won’tMake the Grade … Before discussing the future, Let’s review the past. More importantly why “traditional” enterprise technologies will not cut it.
- 29. 1990 1991 19921993 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 thisbe abstracted AND represented?
- 32. 1990 1991 19921993 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 weTrust, all others bring DATA!!!” http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html VS
- 34. • A configurationmanagement 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 • Littlebit weird • Sits closer to the boss • Thinks too hard Don’t hate the player … Metaphor Attribution – Andrew Shafer, now of Rackspace
- 39. Meet Ops • Pullslevers & 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 jobis 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
Editor's Notes
- #3 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
- #4 Pre-empt introductions with a simple yet powerful statement.Spirit of community and collaboration.
- #5 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
- #10 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
- #11 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.
- #13 DevOps is bigger than Dev and OpsSpans other tech groups, dba’s, QASpans business side tooGet out of the “us” vs “them” mentality
- #14 Things to decide after prezoTopic Coverage possibilitiesMeeting frequency[Come up with several topics]
- #15 DevOps is bigger than Dev and OpsSpans other tech groups, dba’s, QASpans business side tooGet out of the “us” vs “them” mentality
- #30 Automation nothing new but the complexity we just talked about has really proliferated with enabling platforms such as virtualization and cloud.
- #31 Infrastructure As Code is nothing newIt’s been growing in popularity, was always a consideration with cutting edge Bay Area tech firms.The inflection point has given it escape velocity.
- #33 CFEngine – Mark BurgessPuppet – Luke KaniesOpscode – Adam Jacob
- #34 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
- #38 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
- #41 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…