DevOps - Successful Patterns
-
Upload
creationlineinc -
Category
Technology
-
view
116 -
download
0
Transcript of DevOps - Successful Patterns
![Page 1: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/1.jpg)
DevOps – Successful Patterns
Alex VinyarEnterprise Architect; CHEF Software
![Page 3: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/3.jpg)
What do I do?
• Mostly on-site engagements
• Enterprise Assessment & Design• Infrastructure & Workflow Assessment• Hands-on Training• Implementations
![Page 4: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/4.jpg)
Companies I’ve worked with
• Alaska Air Group• Bloomberg• Bridgewater• CenturyLink• Chef• Cycle30• Delta Dental Insurance• Expeditors International• Fred Hutchinson Cancer Research Center• GE Capital
• General Electric• HP Support• IBM• Microsoft - Office 365• Microsoft - Security• Ooyala• Rakuten• Samtec• Walgreens• Yahoo
![Page 5: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/5.jpg)
Lessons I’ve learned about “starting to DevOps”
![Page 6: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/6.jpg)
Best if there is an Executive sponsor.
• Will help give you budget• Will help give you freedom• Will help give you protection• Will help give you visibility.
• DevOps is about bringing teams together
![Page 7: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/7.jpg)
Pick a small but meaningful first project
• Resist business “recommending” a specific project - usually bad idea• Pick a small project• Don’t be afraid to change if it’s a wrong project.• Greenfield is great but almost never.
• Pick something that you can succeed in!
![Page 8: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/8.jpg)
Control the blast radius
• …but not the size of the explosion
![Page 9: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/9.jpg)
Have a Champion!
• Find a champion inside your company• or build a champion• Excitement has to come from more than one person
• Often it’s someone who is very grumpy (and too honest)
![Page 10: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/10.jpg)
Metrics, Metrics, Metrics, Metrics
• Helps prove your case• Helps demonstrate value• Celebrate successes• “exploit compelling events”
• 2’200 server + 1 person + chef = 15 minutes • 60’000 servers + 156 people + lots of typing = 9 days
“6 months ago we only wished we had problems we do today” - Justin Arbuckle
![Page 11: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/11.jpg)
Take care of your people!
• When you ask people to do the impossible, you can’t treat them like everyone else.• Stack rating superstars does not work
• Good people will leave once they see “the light”• Good people will leave if you make them bored
![Page 12: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/12.jpg)
DevOps takes time
• Typical org takes around 2 years• 6-10 months to establish SME
![Page 13: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/13.jpg)
You will NOT be automated out of the job
• Nobody wants to perform the same task over and over ….and over• Automation gives you freedom to innovate• or to go home early
• Computers get together at night and laugh when a human manually does what a computer can do automatically
![Page 14: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/14.jpg)
Demo! Demo! Demo
• Build an internal community.• Demo Successes• Demo Failures• Invite EVERYONE!• Let EVERYONE demo!• Demo every week, even if you’re the only one in the room!
• Demo IS part of your job
![Page 15: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/15.jpg)
Technical Demo suggestions
• 5 minutes max.• Business people have little patience for technical mumbo jumbo
• Practice at least once before.• Video of your code running is OK• Time box debuging during demo - 30 seconds max!• Remember that no one can see your mouse, use mouse locator to point.
![Page 17: DevOps - Successful Patterns](https://reader036.fdocuments.in/reader036/viewer/2022081515/58ede6c61a28ab0e4a8b46a1/html5/thumbnails/17.jpg)