|
Clients do work for one or many Nodes
A Chef Client does work on behalf of a Node. A single Chef Client can run recipes for multiple Nodes.
Clients do all the work
Clients are where all the action happens - the Chef Server and Chef Indexer are largely services that exist only to provide the Client with information.
You can run the client periodically
If you want, you can run the Chef Client as a persistent daemon. To do this, make your startup script for the chef client execute something like:
The -i option provides an Interval - it's how often the Chef client will attempt to wake up and Converge this Node. The -s option is the Splay - a random piece of time added to the interval, which helps avoid the thundering herd problem.
|
 | Chef-Client Cookbook
The Opscode chef-client cookbook is available for use on systems that should have a `chef-client` daemon running, such as when Knife bootstrap was used to install Chef on a new system.
It includes the interval set at 1800 seconds and the splay set at 20 seconds, as configurable defaults, and additional configurable detail information as detailed on this page. |
|
|
