chef-client(8) [debian man page]

CHEF-CLIENT(8)							    Chef Manual 						    CHEF-CLIENT(8)

NAME

       chef-client - Runs a client node connecting to a chef-server.

SYNOPSIS

       chef-client (options)

       -S, --server CHEFSERVERURL
	      The chef server URL

       -c, --config CONFIG
	      The configuration file to use

       -d, --daemonize
	      Daemonize the process

       -g, --group GROUP
	      Group to set privilege to

       -i, --interval SECONDS
	      Run chef-client periodically, in seconds

       -j, --json-attributes JSON_ATTRIBS
	      Load attributes from a JSON file or URL

       -E, --environment ENVIRONMENT
	      Set the Chef Environment on the node

       -l, --log_level LEVEL
	      Set the log level (debug, info, warn, error, fatal)

       -L, --logfile LOGLOCATION
	      Set the log file location, defaults to STDOUT - recommended for daemonizing

       -V, --verbose
	      Ensures logging goes to STDOUT as well as to other configured log location(s).

       -N, --node-name NODE_NAME
	      The node name for this client

       -o, --override-runlist
	      Replace current run list with specified items

       -K, --validation_key KEY_FILE
	      Set the validation key file location, used for registering new clients

       -k, --client_key KEY_FILE
	      Set the client key file location

       -s, --splay SECONDS
	      The splay time for running at intervals, in seconds

       -u, --user USER
	      User to set privilege to

       -P, --pid PIDFILE
	      Set the PID file location, defaults to /tmp/chef-client.pid

       --once Cancel any interval or splay options, run chef once and exit

       -v, --version
	      Show chef version

       -h, --help
	      Show this message

DESCRIPTION

       The  Chef  Client  is where almost all of the work in Chef is done. It communicates with the Chef Server via REST, authenticates via Signed
       Header Authentication, and compiles and executes Cookbooks.

       A Chef Client does work on behalf of a Node. A single Chef Client can run recipes for multiple Nodes.

       Clients are where all the action happens - the Chef Server and Chef Expander are largely services that exist only  to  provide  the  Client
       with information.

SEE ALSO

       Full documentation for Chef and chef-client is located on the Chef wiki, http://wiki.opscode.com/display/chef/Home.

AUTHOR

       Chef  was  written  by  Adam Jacob adam@ospcode.com of Opscode (http://www.opscode.com), with contributions from the community. This manual
       page was written by Joshua Timberman joshua@opscode.com with help2man. Permission is granted to copy, distribute and / or modify this docu-
       ment under the terms of the Apache 2.0 License.

       On Debian systems, the complete text of the Apache 2.0 License can be found in /usr/share/common-licenses/Apache-2.0.

Chef 10.12.0							     June 2012							    CHEF-CLIENT(8)

KNIFE-CLIENT(1) 						    Chef Manual 						   KNIFE-CLIENT(1)

NAME

       knife-client - Manage Chef API Clients

SYNOPSIS

       knife client sub-command (options)

SUB-COMMANDS
       Client subcommands follow a basic create, read, update, delete (CRUD) pattern. The Following subcommands are available:

BULK DELETE

       knife client bulk delete regex (options)

       Delete  clients	where the client name matches the regular expression regex on the Chef Server. The regular expression should be given as a
       quoted string, and not surrounded by forward slashes.

CREATE

       knife client create client name (options)

       -a, --admin
	      Create the client as an admin

       -f, --file FILE
	      Write the key to a file

       Create a new client. This generates an RSA keypair. The private key will be displayed on STDOUT or written to the named	file.  The  public
       half will be stored on the Server. For chef-client systems, the private key should be copied to the system as /etc/chef/client.pem.

       Admin  clients  should  be  created  for users that will use knife to access the API as an administrator. The private key will generally be
       copied to ~/.chef/client\_name.pem and referenced in the knife.rb configuration file.

DELETE

       knife client delete client name (options)

       Deletes a registered client.

EDIT

       client edit client name (options)

       Edit a registered client.

LIST

       client list (options)

       -w, --with-uri
	      Show corresponding URIs

       List all registered clients.

REREGISTER

       client reregister client name (options)

       -f, --file FILE
	      Write the key to a file

       Regenerate the RSA keypair for a client. The public half will be stored on the server and the private key displayed on STDOUT or written to
       the  named  file.  This	operation will invalidate the previous keypair used by the client, preventing it from authenticating with the Chef
       Server. Use care when reregistering the validator client.

SHOW

       client show client name (options)

       -a, --attribute ATTR
	      Show only one attribute

       Show a client. Output format is determined by the --format option.

DESCRIPTION

       Clients are identities used for communication with the Chef Server API, roughly equivalent to user accounts on the Chef Server, except that
       clients only communicate with the Chef Server API and are authenticated via request signatures.

       In the typical case, there will be one client object on the server for each node, and the corresponding client and node will have identical
       names.

       In the Chef authorization model, there is one special client, the "validator", which is authorized to create new non-administrative clients
       but has minimal privileges otherwise. This identity is used as a sort of "guest account" to create a client identity when initially setting
       up a host for management with Chef.

SEE ALSO

       knife-node(1)

AUTHOR

       Chef was written by Adam Jacob adam@opscode.com with many contributions from the community.

DOCUMENTATION

       This manual page was written by Joshua Timberman joshua@opscode.com. Permission is granted to copy, distribute and / or modify  this  docu-
       ment under the terms of the Apache 2.0 License.

CHEF

       Knife is distributed with Chef. http://wiki.opscode.com/display/chef/Home

Chef 10.12.0							     June 2012							   KNIFE-CLIENT(1)