2. “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/
3. Who am I?
Solution Engineer and Evangelist
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
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.
31. “In God we Trust, all others bring DATA!!!”
VS
http://radar.oreilly.com/2007/10/operations-is-a-competitive-ad.html
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. “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/
35. 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”
36. The players
Dev & Ops
Metaphor Attribution – Andrew Shafer, now of Rackspace
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. 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. Agility - Design vs Manufacturing
Load Load Load Balancer
Balancer Balancer
App Server App Server App Server App Server
Database Database
Database
Dev (shared) QA
Dev - QA - UAT - Prod
How ?
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 Prod
What ?
42. Step 1 – SCM and Developers
Application Software
Devs Configuration
Management
(SCM)
Infrastructur
e Devs
43. Step 2 – Introducing the Build Stage
Build Changes in
SCM triggers
builds and
Payload
N
tests
Application Software
Devs Configuration
Management
(SCM) Payload
3
Payload
2
Payload
1
Infrastructur
e Devs
44. Step 3 – “Infrastructure As Code” and the CD Process
Latest Codebase and
Build
Create Data (#)
Upload Policies
Build Update DEV DEV
Autodeploy to IAC
Application 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
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
Notes de l'éditeur
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
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
Automation nothing new but the complexity we just talked about has really proliferated with enabling platforms such as virtualization and cloud.
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.
CFEngine – Mark BurgessPuppet – Luke KaniesOpscode – Adam Jacob
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
SALES-> “Infrastructure As Code” Opscode position“Infrastructure As Code” … core conceptSource code – Agile, leveragedev best-practices for managing infrastructure change.Configuration Repository – Source Code Repository, common methods used in software development for tracking the degrees of state change in a developing system.Data Backup – Separation of data from execution. Think of code/execution as the house and the data as the furniture and accessories that give it personality/distinction.Bare Resources – Primitives, an understanding of the core building blocks to easily support new platforms and make it intuitive to do so.
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…
Anyone know this book? Anyone catch Derek Hammer's talk before lunch?Jez Humble and David Farley's Continuous Delivery. Let's talk about that.
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.
