This summary provides an overview of key topics from the Chef conference document: 1. The document discusses the evolution of software delivery from a non-core capability to more businesses claiming to be in the software business. Cloud, automation, DevOps allow for faster delivery while maintaining quality, safety and security. 2. Chef Delivery was announced, which provides an opinionated pipeline solution for continuous integration, deployment, configuration management and visibility. It standardizes stages and phases in the pipeline. 3. Top talks included Adam Jacobs' keynote discussing experiences transforming businesses with DevOps and how DevOps is uniquely defined, as well as a talk on DevOps "kung fu" principles and applications being unique to individuals.

1. Mike Villis @mvillis

2. http://bit.ly/eggs365

3. A conference about Chef
building great software!!

4. Evolution of Software
• Software was a non-core capability.
• Surface area of IT is expanding an in impressive
rate
• More and more businesses are claiming to be in
the software business

5. Delivery at Speed
• Cloud, Automation, DevOps
• Do it right - you get Speed & Quality, Safety and
Security
• Dual Speed IT (digital first versus traditional IT)

6. Key Chef Announcements
• Chef Delivery!!
• Audit Mode (include ServerSpec in your Chef
Recipes)
• Test Kitchen (windows support now merged to
master)

7. Top 3 Presos

8. Adam Jacobs - Keynote

9. Adam Jacobs - Keynote
• Some felt as if they had some ownership of what
DevOps meant and how it felt
• DevOps best defined by the experiences of all
these people trying to transform their businesses
• Unique to any person who tries to do “DevOps”

10. Kung Fu

11. DevOps KungFu
• Principles - universally held beliefs
• Forms - shared between many styles, emphasis
varies from style to style
• Application - unique to the individual

12. Is it OK for DevOps to be in
your title?

13. Should we just make all Ops
Devs and all Devs Ops?

15. http://bit.ly/devopskungfu
https://github.com/chef/devops-
kungfu

17. Governance at Velocity

18. Changing Role of Auditors

19. Sample Tests

20. Chef Delivery
• Opinionated Pipeline Solution
• Includes GIT, CI, Deployments, Config Mgmt,
Visibility, Audit

21. THE STAGES ARE FIXED
EACH STAGE HAS A FIXED SET OF PHASES

22. COMMON PIPELINE

23. BUILD COOKBOOK
!"" recipes
!"" default.rb
!"" lint.rb
!"" syntax.rb
!"" unit.rb
!"" quality.rb
!"" security.rb
!"" publish.rb
!"" provision.rb
!"" deploy.rb
!"" smoke.rb
$"" functional.rb

24. PHASE EXEC
log "Running unit"
repo = node['delivery_builder']['repo']
delivery_builder_exec “run my junit tests" do
command "mvn test"
cwd repo
end

25. MANY ACCEPTANCE PIPELINES
ONE DELIVERY PIPELINE

26. COMMON PIPELINE
One Pipeline
Delivery Pipeline - Shared
union rehearsal delivered
Acceptance Pipelines - Private
review approve deliverChange
Cookbook [A]
review approve deliverChange
Cookbook [B]
review approve deliverChange
Application [A]
review approve deliverChange
Application [B]
Infrastructure & Applications

27. APPLICATION WORKFLOW
review approve deliverChange
Application
Node Node Node
Node Node Node
Node Node Node
Deploy
1 2 3
2 2 3
3 3 3

28. COOKBOOK WORKFLOW
Supermarket
Chef Server
review approve deliverChange
Cookbook
Node Node Node
Node Node Node
Node Node Node
Publish
Publish
Update

29. CONFIG.JSON
{
"version": "1",
"build_cookbook": "./.delivery/build_cookbook",
"build_nodes": {
"default": [“name:*buildnode-*”],
"unit": [“name:*-unittest*”],
"lint": [“name:*-linttest*”],
"build": [“name:*-builder*”]
}
}

31. Chef Delivery Open Source
• Delivery Truck - https://github.com/opscode-
cookbooks/delivery-truck
• Delivery CLI - https://github.com/chef/delivery-cli

33. Chef Office

34. All the talks from ChefCon
2015
• http://bit.ly/chef-talks

35. Mike Villis @mvillis