Devops journey chefpopup-2016.04.26-v2
Download as PPTX, PDF0 likes304 views
This document introduces Jon Aykroyd, an automation engineer with over 10 years of experience in Linux systems administration and automation. It provides an overview of Jon's background and role in helping organizations transition to DevOps practices. The document also shares a case study of how introducing Chef automation tools helped a clothing retailer reduce time-to-deployment from 2 weeks to just 2 hours. It closes with some details about Jon's initial work helping his own organization transition to Chef from various other tools and scripts.
![5 Stages of DevOps Transition
What’s
DevOps?
We need that
buzzword!
Our DevOps is
different!
Maybe our
DevOps isn’t
so different…
DevOps at
velocity
• Collection of
unorganized
scripts
• Sometimes in
revision control
• Lots of manual
processes
• LONG TTD
• Many silos
within an
organization
• Initial
implementation
of DevOps tool
• Lots of different
groups inventing
same wheel
• Hopefully some
source control…
• What’s testing?
• What’s a style
guide?
• Creation of
DevOps group
and / or titles
• Many different
groups writing
cookbooks
• Cookbooks
trying to be “all
encompassing”
• Groups
embracing the
importance of
source control
• Beginning to see
automated local
testing
• Emergence of
[manual]
formalized
testing
• Dissolution of
DevOps group
• Different groups
starting to
specialize
• Disparate groups
starting to work
together
• Review process
• Fully embracing
localized testing
• Beginning to see
automated
integration
testing.
• Emergence of
“gated” CI/CD
• Company-wide
acceptance of
DevOps:
Accounting to
Engineering
• Truly embracing
CI/CD
• Fully automated
testing, top to
bottom
• Unified coding
style](https://image.slidesharecdn.com/devopsjourney-chefpopup-2016-160429170946/85/Devops-journey-chefpopup-2016-04-26-v2-6-320.jpg)
![Case Study: Clothing Retailer
After Chef
ď‚— 30-40 VM Requests / week
ď‚— TTD: 2 hours from approval
ď‚— Most of the manual steps had been partially / wholly
automated with Chef anyway…
ď‚— Just tied it all together
ď‚— Process became:
ď‚— Deploy VM in vSphere
ď‚— knife bootstrap nodename --environment prod
--run-list “recipe[our_base]”
ď‚— Hand off to customer (i.e.: requestor)](https://image.slidesharecdn.com/devopsjourney-chefpopup-2016-160429170946/85/Devops-journey-chefpopup-2016-04-26-v2-8-320.jpg)
Devops journey chefpopup-2016.04.26-v2
- 1. Jon Aykroyd Cloud Platform Automation Email: jon.aykroyd@charter.com @gmail.com Twitter: @qubitrenegade
- 2. Introduction  Who Am I?  Automation Engineer –  Focus on Linux  10+ Years Linux SA Experience  10+ Years “Automation” Experience  Why Am I here?  2nd journey down this path  Big proponent of DevOps philosophies  Danielle and Jeremy asked me nicely (these guys do great work and they don’t get thanked nearly enough)
- 3. Who are you? ď‚— Manual Processes? ď‚— Buzzwords? ď‚— Source Control? ď‚— Automated Processes? ď‚— Formal Automation Tools?
- 6. 5 Stages of DevOps Transition What’s DevOps? We need that buzzword! Our DevOps is different! Maybe our DevOps isn’t so different… DevOps at velocity • Collection of unorganized scripts • Sometimes in revision control • Lots of manual processes • LONG TTD • Many silos within an organization • Initial implementation of DevOps tool • Lots of different groups inventing same wheel • Hopefully some source control… • What’s testing? • What’s a style guide? • Creation of DevOps group and / or titles • Many different groups writing cookbooks • Cookbooks trying to be “all encompassing” • Groups embracing the importance of source control • Beginning to see automated local testing • Emergence of [manual] formalized testing • Dissolution of DevOps group • Different groups starting to specialize • Disparate groups starting to work together • Review process • Fully embracing localized testing • Beginning to see automated integration testing. • Emergence of “gated” CI/CD • Company-wide acceptance of DevOps: Accounting to Engineering • Truly embracing CI/CD • Fully automated testing, top to bottom • Unified coding style
- 7. Case Study: Clothing Retailer Before Chef ď‚— 30-40 VM Requests / week ď‚— TTD: 2 weeks from approval ď‚— Able to deliver ~30 VMs/week (problem?) ď‚— Process largely manual, from setting NTP, DNS, to joining domain. 30 steps total after deploying VM in vSphere
- 8. Case Study: Clothing Retailer After Chef  30-40 VM Requests / week  TTD: 2 hours from approval  Most of the manual steps had been partially / wholly automated with Chef anyway…  Just tied it all together  Process became:  Deploy VM in vSphere  knife bootstrap nodename --environment prod --run-list “recipe[our_base]”  Hand off to customer (i.e.: requestor)
- 9. Our Start ď‚— Each team using something different (Puppet, Ansible, Salt) ď‚— Chef came on site for four days ď‚— 2d training ď‚— 2d writing cookbooks for our environment ď‚— Took internal deployment application ď‚— 100% BASH, works well but fragile ď‚— Wrote cookbooks to replace BASH framework ď‚— Initial BASH tool took over a month to develop (and still not 100% bug free) ď‚— Able to replicate 80% of functionality in Chef in the 2d
- 10. Questions?
- 11. ď‚— O RLY book generator: http://dev.to/rly
Editor's Notes
- #4: Ask if anyone has “piles of scripts” Ask if anyone is using source control Ask if anyone is using “Formal” DevOps tools: Chef, Puppet, etc.
- #5: Books commonly found around the office…
- #6: Any of these on your shelf?
- #7: Different groups starting to specialize Disparate groups starting to work together No more “This is MY cookbook”
- #9: TTD: 2hrs is actual hands on keyboards, sometimes techs working on other tickets Not 100% automated, but Base cookbook wrapped up all other cookbooks. Can be modified at run time with environment variables, e.g. different DNS servers for Prod, Test, or Dev