Meetup chef intro business reasons for chef

Agenda

•  Reasons to “Chefalize” your business - Scott Russell – 20 minutes

•  Chef at Etsy - Jon Cowie - 40 minutes

•  Jenkins in the CI pipeline - Zac Stevens – 20 minutes

Reasons to “Chefalize” your business Chef Users London – Ninth September two thousand and fourteen

Scott Russell Devops Evangelist

Quick Trivia questions

• Who said this? And which year? • Q “ I'm not allowed to say how many planes joined the raid, but I counted them all out and I counted them all back. ”

• A http://en.wikipedia.org/wiki/Brian_Hanrahan, 1982 • Q In what year was WFW 3.11 released? • A http://en.wikipedia.org/wiki/Windows_3.1x, “released on August 11, 1993” • Q What is the longest recorded uptime for a Novell 3.12 server? • A http://arstechnica.com/information-technology/2013/03/epic-uptime-achievement-can-you-beat-16-years/ - 16 Years.

http://en.wikipedia.org/wiki/Chef_%28film%29

Addressable business Issues with Chef

•  Institutional Knowledge repository for IT •  Auditability ( compliance ) •  Repeatability & Deployment quality •  All changes in one place ( DRY ) •  Everything “breaks” or “works”, choose? •  Reduce random events & Variation •  Increase predictability •  Dynamic Scaling ( wide and deep ) •  Speed •  Feedback

Enterprise Current Practice

•  Applications delivered on CD/DVD/FTP •  50 page word install document •  15 page per patch word install document •  Hand written notes/email notes •  Requires developers on-site at initial install •  Human variability •  Upgrade fear and loathing – “it will break” •  Institutional knowledge loss ( key staff exit )

Welcome to the Coded Enterprise

•  Institutional Knowledge retained in a repository •  Code delivered to external VCS site •  Code compiled and deployed to test via Continuous integration •  Complete build on virgin VM's with supplier/Customer code, and Continuous

Integration/Continuous Deployment pipeline •  “One click” deploy gates to production, by business users ( Customers? ). Not

Ops/IT. •  Receive small incremental updates. No big-bang! •  Automated testing, reduced human testing

Coded Enterprise - “brave new world”

•  Auditable records of who, what, when, where and how •  Institutional Knowledge retained in central repository •  Limited console access ( End of the world? ) •  Version controlled deployments •  Tested deployment recipes. Tested Install iterations before a deployment recipe

is allowed to be used for a “live install” to development, test and subsequent production.

•  Decoupling of application deployment, and installation. Smooth process of deployment

•  Control the tool chain, cradle to grave

Continuous Delivery

Summary of business issues •  Institutional Knowledge retention •  Auditability ( compliance ) •  Customers conduct business ( not IT ) •  One change many replications •  Stability and Repeatability ( Feedback) •  Minimised Vendor lock-in •  Increased predictability •  Reduced time to market ( Speed) •  Dynamic Scalability – ( wide and deep )

Thank You – Questions?

Serving up Delight in London Posted on October 7, 2014 by Nathen Harvey The week of October 13-17 is full of amazing Chef events in London. Make plans to join us for as many of these events as you can. And if you would like an early preview, join us this week for the Chef Users London Meetup on Thursday, October 9. Chef Intermediate Topics https://www.getchef.com/blog/event/chef-intermeditate-topics-london/ Chef Community Summit https://www.getchef.com/summit-london/ Hack Day https://www.getchef.com/blog/event/hack-day-london-uk/ discount code CHEFWEEK Next Meetups at Chef Users London – 4th November and 4th December