This document provides an overview of DevOps concepts like DebOps and Chef. It discusses how Chef can be used to manage infrastructure as code through cookbooks, nodes, attributes, templates and other resources. Challenges with traditional infrastructure management like complexity and risk are addressed through DevOps approaches like Chef which enable stable, reliable and auditable infrastructure through self-healing automation and configuration as code. Key Chef concepts like the chef-client, nodes, attributes, templates, files, roles, environments, data bags, and Test Kitchen are defined to explain how infrastructure can be managed from code through the Chef platform.

1. WHO AM I
WHO ARE YOU?

2. WHO ARE YOU?
A Newbie to IT?
Developer?
Tester?
System Administrator?
“Business” People?

3. DebOps

4. Why DebOps?
Debit Ops from your Infrastructure to make NoOps Infrastructure.

5. Challenges
• Complex to Manage
• Extra long time required for a change
• Risky Rollbacks
• Anti Agnostic
• High Maintenance

6. Why DebOps Adoption ?
• Stable/Reliable operating environments
• Infrastructure is maintained as code
• Infrastructure Versioning
• Self Healing Capability
• Early detection and faster correction
• Less Time to Market
• Auditable
• Proactive

7. WHAT IS CHEF?

8. 30,000ft View?

10. • Chef Design

11. Chef can also Stand Alone
Code Test and Release locally with Chef Solo

12. Why Chef ?
• Infrastructure as a Code
• Self Healing Capability
• Idempotent
• Lightweight
• Resilient Infrastructure
• Auditable

13. Why Chef?
• Infra as a Code
• Version Controlled
• Idempotent
• TMTOWDI
• Push Me
• Pull Me

14. Let’s Hangout with Chef!

15. Chef-Client is always with you

16. Chef Node
Any Server/VM which is managed and controlled by Chef is a Chef
Node

17. What makes your server a Chef Node?
• Chef-Client installed
• Bootstrapped(Registered) with Chef Server
• Runlist Attached

18. Node Attributes
• Node specific properties are called as Node Attributes
• It can be provided in a form of Array, Hash, or as a single variable.
• Attributes can be passed from attribute file, roles, environment,
runlist
• Attributes works on priority basis.

20. Attributes Priority

21. Know Your Cookbook

22. Cookbook Contents
• Metadata.rb
• Recipes
• Attributes
• Files
• Templates
• Resources
• Providers

23. Can you Imagine Chef without Knife ?

24. KNIFE
C - Create
R - Read
U - Update
D - Delete
D - Download
S - Search

25. Chef Essentials

26. Chef Development Kit (DK)
• Chef Development Kit
• Why DK with Knife?
• We need few more tools to build a better Cookbook
• CRUDDS… Am I missing anything?
• Cookbook Dependency Management
• A warning tool, if recipe is not healthy – Foodcritic
• Gem bar
• Push Jobs

27. WYW|WYR

28. Attributes
• I am used to supply what is required by a cookbook
• Yes I have priorities
• You can stamp me from cookbook, roles, environments, Runlist

29. Template(Configuration as a Code)
• Program your Configuration files
• I can fetch your attributes from anywhere
• I understand your if else for…

30. Template

31. Files
• Use me to dump your as is files
• I am used to provide your pre baked resources

32. Data Bags
• I am a special attribute
• Node Independent
• Priority Independent
• Available for All
• I am available as a global/environment variables in your cookbook
• I am also capable to hold your secrets(Encrypted Data Bags)
• I like to reside at Chef Server so that I could serve every node

33. Chef Vault
• I am specially developed for managing your secret data.
• I am keyless
• Only trusted nodes can read me
• gem install chef-vault

35. Roles
• I am a runlist template which can be consumed by all nodes
• You can assign me to multiple nodes in same time
• Same as runlist, I have recipies and atrributes in me
• My attributes get high precedence than node and environment
attributes(same type)
• Roles can be assigned in Roles too
• I am JSON
• I miss versioning

36. Role view

37. Environments

38. Environments
• Every node is a part of environment
• By default every node is registered under _default environment
• _default is a environment which cannot be changed
• We can create our own environments
• A node can be a part of one environment at a time
• Environments allow you to assign roles, attributes, restricting
cookbook version
• I am JSON
• I miss versioning

39. Environment view

41. Test Kitchen
• Kitchen supports multiple platforms (i.e.: RHEL, Ubuntu, Windows,
etc.)
• It supports multiple frameworks (i.e.: Rspec, Serverspec, etc.)
• It encourages Test-Driven Development

44. Chef Supermarket
• 100% free
• Chef Supermarket hosts cookbooks which are built by community and
available for everyone.
• https://supermarket.chef.io/
• Private Supermarket

47. Let’s Cook
• Build a Cookbook
• Test On Kitchen
• Roll out in Environment

49. For any questions, reach out to me at
dilip.panwar@barclaycard.co.uk