IF you want to configure your Management Workstation as a Chef-Client, this page will explain how to do so. |
Node vs. Client vs. User vs. WorkstationFirst, to help avoid any confusion, lets go over terminology. The system where you are doing development and maintaining a cookbook repository we can call a workstation or your management workstation. It is where you run knife commands. A server you want to manage with chef we call a node, and the only command you will run on it should be "sudo chef-client". A client allows you to access the server API. In general, clients map 1:1 to the list of nodes (every node is a client, and every client represents 1 node.) However, it is possible for a single client to manage multiple nodes - this is most often done for programmatic access to the nodes via the API. A user is an individual: credentialed entities used by humans to connect to the Hosted Platform to manage the organization. The user is the credentialed entity that manages the organization:
The organization is comprised of nodes
Which run the chef-client software
|
|
Having Chef Manage the Configuration of your Management WorkstationTo have the Chef Server (or Hosted Chef, as the case may be) manage the configuration of your workstation, you need to configure the client. These directions assume you have already installed knife by following the Installation Guides. You'll now have a client-config directory in your local repository: To configure your workstation as a chef client, you just need to copy this directory to /etc/chef:
|
|
|

