Chef Cookbook - Third Edition

Chef Cookbook - Third Edition

By : Matthias Marschall

Buy this Book

Chef Cookbook - Third Edition

By: Matthias Marschall

Buy this Book

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.

Chef Cookbook - Third Edition

Credits

About the Author

About the Reviewer

www.PacktPub.com

Customer Feedback

Preface

Free Chapter

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

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

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

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

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

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

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

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

Index

Customer Reviews

5 star

4 star

3 star

2 star

1 star

Managing NTP

Your nodes should always have synchronized clocks, if for no other reason than that the Chef server requires clients' clocks to be synchronized with it. This is required because the authentication of clients is based on a time window in order to prevent man-in-the-middle attacks.

NTP is there to synchronize your nodes' clocks with its upstream peers. It usually uses a set of trusted upstream peers so that it gets a reliable timing signal.

It's a good idea to put the installation of NTP into a role which you assign to every node. Bugs caused by clocks which are out of sync are not nice to track down. It is better to avoid them in the first place by using NTP on every node.

Getting ready

Create a Berksfile in your Chef repository including the ntp cookbook:

mma@laptop:~/chef-repo $ subl Berksfile
cookbook 'ntp', '~> 3.2.0'

Install the ntp cookbook:

mma@laptop:~/chef-repo $ berks install
Resolving cookbook dependencies...
Using ntp (3.2.0)

Upload the ntp cookbook to the Chef server...

Chef Cookbook - Third Edition

By : Matthias Marschall

Chef Cookbook - Third Edition

By: Matthias Marschall

Overview of this book

Related Content you might be interested in

Current Title:

Chef Cookbook - Third Edition

Infrastructure as Code (IAC) Cookbook

DevOps Bootcamp

Puppet 5 Cookbook

Managing NTP

Getting ready