Information Technology Reference
In-Depth Information
CONVERGENCE INTRODUCED
Chef can dynamically adjust how it brings a node into a desired state depending on the current
state of the node. For example, if the Chef run is aborted for any reason, Chef will merely pick up
where it left off the next time it runs. Key to this fault-tolerant approach is that the plan for the
steps Chef uses to configure a node are entirely data-driven, based on the results produced by
ohai
, which we covered in
Chapter 6
.
Another example of a
convergence-based
tool is the
make
command. It behaves in a similar fash-
ion. The
make
tool assesses the current state of the components used to produce an application,
and it only builds what hasn't been built before. You can run
make
as many times as you like, and
it will only perform the necessary build steps that haven't been successfully performed already.
TIP
Make sure you run the
kitchen converge
command
inside
the
motd
cookbook directory.
If you entered in the code correctly so far, the output of
kitchen converge
should resemble
the following:
$
kitchen converge default-centos65
-----> Starting Kitchen (v1.2.2.dev)
-----> Creating <default-centos65>...
Bringing machine 'default' up with 'virtualbox' provider...
...
-----> Converging <default-centos65>...
Preparing files for transfer
Resolving cookbook dependencies with Berkshelf 3.1.3...
Removing non-cookbook files before transfer
-----> Installing Chef Omnibus (true)
...
Starting Chef Client, version 11.14.2
[2014-08-14T13:22:37-07:00] INFO: *** Chef 11.14.2 ***
[2014-08-14T13:22:37-07:00] INFO: Chef-client pid: 2004
Creating a new client identity for default-centos65 using the validator
key.
[2014-08-14T13:22:40-07:00] INFO: Client key /tmp/kitchen/client.pem is
not present - registering
[2014-08-14T13:22:40-07:00] INFO: HTTP Request Returned 404 Not Found
