Manage Nodes with Chef Client - Learning Chef - page 125

$ *kitchen destroy default-centos65*
-----> Starting Kitchen (v1.2.2.dev)
-----> Destroying <default-centos65>...
==> default: Forcing shutdown of VM...
==> default: Destroying VM and associated drives...
Vagrant instance <default-centos65> destroyed.
Finished destroying <default-centos65> (0m2.98s).
-----> Kitchen is finished. (0m3.24s)
Summary
In this chapter, we introduced the concept of a node. Because Chef can manage things other
than personal computers, such as network switches and embedded storage systems, Chef
uses the more generic term node to refer to the entities managed by Chef instead of server or
host .
Any entity managed by Chef must have Chef Client installed. We showed you how to use
Test Kitchen to install Chef Client on a node while writing Chef code. In Bootstrap the Node
with Knife , we'll show you how the knife bootstrap command is used to install Chef Cli-
ent on production nodes, as Test Kitchen isn't intended for production use.
You learned how to use the chef-client tool to perform a Chef run . This is how Chef man-
ages a node. chef-client reads recipes during a Chef run . Recipes indicate a desired con-
figuration through resources , and Chef determines the optimal sequence of steps in order to
put the node into the desired state. Chef is able to reason intelligently about the node config-
uration, because it collects detailed information about the state of a node in an associated
node attribute based on the information collected by ohai . We also showed you how you
can access the information in your Chef recipes.
In the next chapter, we'll show you how to organize multiple recipe files into a cookbook.
We'll also show you how you can run chef-client on a node using Test Kitchen on your
host instead of hopping back and forth between the host and the guest.