Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Chef Cookbook
  • Toc
  • feedback
Chef Cookbook

Chef Cookbook

By : Marschall
close
Chef Cookbook

Chef Cookbook

By: Marschall

Overview of this book

Chef is a configuration management tool that lets you automate your more cumbersome IT infrastructure processes and control a large network of computers (and virtual machines) from one master server. This book will help you solve everyday problems with your IT infrastructure with Chef. It will start with recipes that show you how to effectively manage your infrastructure and solve problems with users, applications, and automation. You will then come across a new testing framework, InSpec, to test any node in your infrastructure. Further on, you will learn to customize plugins and write cross-platform cookbooks depending on the platform. You will also install packages from a third-party repository and learn how to manage users and applications. Toward the end, you will build high-availability services and explore what Habitat is and how you can implement it.
Table of Contents (9 chapters)
close
close
Preface
Preface
What this book covers
What you need for this book
Who this book is for
Sections
Conventions
Reader feedback
Customer support
Free Chapter
1
1. Chef Infrastructure
chevron up
1. Chef Infrastructure
Introduction
Using version control
Installing the Chef Development Kit on your workstation
Using the hosted Chef platform
Managing virtual machines with Vagrant
Creating and using cookbooks
Inspecting files on your Chef server with knife
How to do it…
How it works…
There's more…
See also
Defining cookbook dependencies
Managing cookbook dependencies with Berkshelf
Using custom knife plugins
Deleting a node from the Chef server
Developing recipes with local mode
Using roles
Using environments
Freezing cookbooks
Running the Chef client as a daemon
2
2. Evaluating and Troubleshooting Cookbooks and Chef Runs
2. Evaluating and Troubleshooting Cookbooks and Chef Runs
Introduction
Testing your Chef cookbooks with cookstyle and Rubocop
Flagging problems in your Chef cookbooks with Foodcritic
Test-driven development for cookbooks using ChefSpec
Compliance testing with InSpec
Integration-testing your Chef cookbooks with Test Kitchen
Showing affected nodes before uploading cookbooks
Overriding a node's run list to execute a single recipe
Using chef-shell
Using why-run mode to find out what a recipe might do
Debugging Chef client runs
Inspecting the results of your last Chef run
Using Reporting to keep track of all your Chef client runs
Raising and logging exceptions in recipes
Diff-ing cookbooks with knife
Using community exception and report handlers
3
3. Chef Language and Style
3. Chef Language and Style
Introduction
Using community Chef style
Using attributes to dynamically configure recipes
Using templates
Mixing plain Ruby with Chef DSL
Installing Ruby gems and using them in recipes
Using libraries
Creating your own custom resource
Extending community cookbooks by using application wrapper cookbooks
Creating custom Ohai plugins
Creating custom knife plugins
4
4. Writing Better Cookbooks
4. Writing Better Cookbooks
Introduction
Setting environment variables
Passing arguments to shell commands
Overriding attributes
Using search to find nodes
Using data bags
Using search to find data bag items
Using encrypted data bag items
Accessing data bag values from external scripts
Getting information about the environment
Writing cross-platform cookbooks
Making recipes idempotent by using conditional execution
5
5. Working with Files and Packages
5. Working with Files and Packages
Introduction
Creating configuration files using templates
Using pure Ruby in templates for conditionals and iterations
Installing packages from a third-party repository
Installing software from source
Running a command when a file is updated
Distributing directory trees
Cleaning up old files
Distributing different files based on the target platform
6
6. Users and Applications
6. Users and Applications
Introduction
Creating users from data bags
Securing the Secure Shell daemon
Enabling passwordless sudo
Managing NTP
Installing nginx from source
Creating nginx virtual hosts
Creating MySQL databases and users
Managing Ruby on Rails applications
Managing Varnish
Managing your local workstation with Chef Pantry
7
7. Servers and Cloud Infrastructure
7. Servers and Cloud Infrastructure
Introduction
Creating cookbooks from a running system with Blueprint
Running the same command on many machines at once
Setting up SNMP for external monitoring services
Deploying a Nagios monitoring server
Using HAProxy to load-balance multiple web servers
Using custom bootstrap scripts
Managing firewalls with iptables
Managing fail2ban to ban malicious IP addresses
Managing Amazon EC2 instances
Managing applications with Habitat
8
Index
Index

Freezing cookbooks

Uploading broken cookbooks that override your working ones is a major pain and can result in widespread outages throughout your infrastructure. If you have a cookbook version, you tested successfully with Test Kitchen, it's a good idea to freeze this version so that no one can overwrite the same version with broken code. When used together with version constraints that are specified in your environment manifests, freezing cookbooks can keep your production servers safe from accidental changes.

Note

Berkshelf takes care of freezing cookbooks automatically.

Getting ready

Make sure you have at least one cookbook (I'll use the ntp cookbook) registered with your Chef server.

How to do it…

Let's see what happens if we freeze a cookbook.

  1. Upload a cookbook and freeze it:
    mma@laptop:~/chef-repo $ knife cookbook upload ntp --freeze
Uploading ntp            [3.2.0]
Uploaded 1 cookbook.
  2. Try to upload the same cookbook version again:
    mma@laptop:~/chef-repo $ knife cookbook upload ntp
Uploading ntp            [3.2.0]
ERROR: Version 3.2.0 of cookbook ntp is frozen. Use --force to override.
WARNING: Not updating version constraints for ntp in the environment as the cookbook is frozen.
ERROR: Failed to upload 1 cookbook.
  3. Change the cookbook version:
    mma@laptop:~/chef-repo $ subl cookbooks/ntp/metadata.rb
…
version           "3.2.1"
  4. Upload the cookbook again:
    mma@laptop:~/chef-repo $ knife cookbook upload ntp
Uploading ntp            [3.2.1]
Uploaded 1 cookbook.

How it works…

By using the --freeze option when uploading a cookbook, you tell the Chef server that it should not accept any changes to the same version of the cookbook anymore. This is important if you're using environments and want to make sure that your production environment cannot be broken by uploading a corrupted cookbook.

By changing the version number of your cookbook, you can upload the new version. Then you can make, for example, your staging environment use that new cookbook version.

There's more…

To support a more elaborate workflow, you can use the knife-spork knife plugin, which comes pre-installed with the Chef DK. It helps multiple developers work on the same Chef server and repository without treading on each other's toes. You can find more information about it at https://docs.chef.io/plugin_knife_spork.html.

See also

End of Section 20
Next Section
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete