chef 0.9.8 → 0.9.10.rc.0

data/README.rdoc

@@ -47,7 +47,7 @@ Install these via your platform's preferred method; for example apt, yum, ports,
 * erubis
 * extlib
 * highline
-* json (1.4.2)
+* json (1.4.4 - 1.4.6)
 * mixlib-authentication
 * mixlib-cli
 * mixlib-config

data/distro/common/man/man8/knife.8

@@ -1,13 +1,13 @@
-.\" generated with Ronn/v0.6.0
-.\" http://github.com/rtomayko/ronn/
+.\" generated with Ronn/v0.7.3
+.\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "KNIFE" "8" "July 2010" "" ""
+.TH "KNIFE" "8" "September 2010" "" ""
 .
 .SH "NAME"
 \fBknife\fR \- Chef Server REST API utility
 .
 .SH "SYNOPSIS"
-\fBknife\fR\fIsub\-command\fR\fI(options)\fR
+\fBknife\fR \fIsub\-command\fR \fI(options)\fR
 .
 .SH "DESCRIPTION"
 This manual page documents knife, a command\-line utility used to interact with a Chef server directly through the RESTful API\. Knife uses sub\-commands to take various actions on different types of Chef objects\. Some sub\-commands take additional options\. General options follow sub\-commands and their options\. A configuration file can be created for common defaults\.
@@ -22,11 +22,11 @@ The Chef class \fBChef::Config\fR that configures the behavior of how knife runs
 .
 .TP
 \fB\-s\fR, \fB\-\-server\-url\fR URL
-Chef Server URL, corresponds to \fBChef::Config\fR\fBchef_server_url\fR\.
+Chef Server URL, corresponds to \fBChef::Config\fR \fBchef_server_url\fR\.
 .
 .TP
 \fB\-k\fR, \fB\-\-key\fR KEY
-API Client Key, corresponds to \fBChef::Config\fR\fBclient_key\fR\.
+API Client Key, corresponds to \fBChef::Config\fR \fBclient_key\fR\.
 .
 .TP
 \fB\-c\fR, \fB\-\-config\fR CONFIG
@@ -42,11 +42,11 @@ Which format to use for output
 .
 .TP
 \fB\-l\fR, \fB\-\-log_level\fR LEVEL
-Set the log level (debug, info, warn, error, fatal), corresponds to \fBChef::Config\fR\fBlog_level\fR\.
+Set the log level (debug, info, warn, error, fatal), corresponds to \fBChef::Config\fR \fBlog_level\fR\.
 .
 .TP
 \fB\-L\fR, \fB\-\-logfile\fR LOGLOCATION
-Set the log file location, defaults to STDOUT, corresponds to \fBChef::Config\fR\fBlog_location\fR\.
+Set the log file location, defaults to STDOUT, corresponds to \fBChef::Config\fR \fBlog_location\fR\.
 .
 .TP
 \fB\-n\fR, \fB\-\-no\-editor\fR
@@ -54,7 +54,7 @@ Do not open EDITOR, just accept the data as is
 .
 .TP
 \fB\-u\fR, \fB\-\-user\fR USER
-API Client Username, corresponds to \fBChef::Config\fR\fBnode_name\fR\.
+API Client Username, corresponds to \fBChef::Config\fR \fBnode_name\fR\.
 .
 .TP
 \fB\-p\fR, \fB\-\-print\-after\fR
@@ -99,7 +99,7 @@ Objects stored on the server support these, as described below\.
 The following are general sub\-commands that do not fit within the other object types utilized in the Chef Server API\.
 .
 .P
-\fBconfigure\fR\fI(options)\fR
+\fBconfigure\fR \fI(options)\fR
 .
 .TP
 \fB\-i\fR, \fB\-\-initial\fR
@@ -119,7 +119,7 @@ Create a configuration file for knife\. This will prompt for values to enter int
 Read the \fBknife\.rb\fR config file and generate a config file suitable for use in \fB/etc/chef/client\.rb\fR and copy the validation certificate into the specified \fIDIRECTORY\fR\.
 .
 .P
-\fBindex rebuild\fR\fI(options)\fR
+\fBindex rebuild\fR \fI(options)\fR
 .
 .TP
 \fB\-y\fR, \fB\-\-yes\fR
@@ -135,7 +135,7 @@ Rebuilds all the search indexes on the server\.
 List available recipes from the server\. Specify \fIPATTERN\fR as a regular expression to limit the results\.
 .
 .P
-\fBsearch INDEX QUERY\fR\fI(options)\fR
+\fBsearch INDEX QUERY\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-attribute ATTR\fR
@@ -165,7 +165,7 @@ The row to start returning results at
 Search indexes are a feature of the Chef Server and the search sub\-command allows querying any of the available indexes using SOLR query syntax\. The following data types are indexed for search: \fInode\fR, \fIrole\fR, \fIclient\fR, \fIdata bag\fR\.
 .
 .P
-\fBssh QUERY COMMAND\fR\fI(options)\fR
+\fBssh QUERY COMMAND\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-attribute ATTR\fR
@@ -190,8 +190,18 @@ The ssh username
 .P
 The \fIssh\fR sub\-command opens an ssh session to each of the nodes in the search results of the \fIQUERY\fR\. This sub\-command requires that the net\-ssh\-multi and highline Ruby libraries are installed\. On Debian systems, these are the libnet\-ssh\-multi\-ruby and libhighline\-ruby packages\. They can also be installed as RubyGems (net\-ssh\-multi and highline, respectively)\.
 .
+.P
+\fBstatus\fR \fI(options)\fR
+.
+.TP
+\fB\-r\fR, \fB\-\-run\-list RUN_LIST\fR
+Show the run list
+.
+.P
+The \fIstatus\fR sub\-command searches the Chef Server for all nodes and displays information about the last time the node checked into the server and executed a \fBnode\.save\fR\. The fields displayed are the relative checkin time, the node name, it\'s operating system platform and version, the fully\-qualified domain name and the default IP address\. If the \fB\-r\fR option is given, the node\'s run list will also be displayed\. Note that depending on the configuration of the nodes, the FQDN and IP displayed may not be publicly reachable\.
+.
 .SH "BOOTSTRAP SUB\-COMMANDS"
-\fBbootstrap FQDN\fR\fI(options)\fR
+\fBbootstrap FQDN\fR \fI(options)\fR
 .
 .TP
 \fB\-i\fR, \fB\-\-identity\-file IDENTITY_FILE\fR
@@ -312,13 +322,13 @@ Additional custom bootstrap templates can be created and stored in \fB\.chef/boo
 Clients are entities that communicate with the Chef Server API\.
 .
 .P
-\fBclient bulk delete REGEX\fR\fI(options)\fR
+\fBclient bulk delete REGEX\fR \fI(options)\fR
 .
 .P
 Delete clients on the Chef Server based on a regular expression\. The regular expression (\fIREGEX\fR) should be in quotes, not in //\'s\.
 .
 .P
-\fBclient create CLIENT\fR\fI(options)\fR
+\fBclient create CLIENT\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-admin\fR
@@ -335,19 +345,19 @@ Create a new client\. This generates an RSA keypair\. The private key will be di
 Admin clients should be created for users that will use \fIknife\fR to access the API as an administrator\. The private key will generally be copied to \fB~/\.chef/CLIENT\.pem\fR and referenced in the \fBknife\.rb\fR configuration file\.
 .
 .P
-\fBclient delete CLIENT\fR\fI(options)\fR
+\fBclient delete CLIENT\fR \fI(options)\fR
 .
 .P
 Deletes a registered client\.
 .
 .P
-\fBclient edit CLIENT\fR\fI(options)\fR
+\fBclient edit CLIENT\fR \fI(options)\fR
 .
 .P
 Edit a registered client\.
 .
 .P
-\fBclient list\fR\fI(options)\fR
+\fBclient list\fR \fI(options)\fR
 .
 .TP
 \fB\-w\fR, \fB\-\-with\-uri\fR
@@ -357,7 +367,7 @@ Show corresponding URIs
 List all registered clients\.
 .
 .P
-\fBclient reregister CLIENT\fR\fI(options)\fR
+\fBclient reregister CLIENT\fR \fI(options)\fR
 .
 .TP
 \fB\-f\fR, \fB\-\-file FILE\fR
@@ -367,7 +377,7 @@ 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 \fISTDOUT\fR or written to the named file\.
 .
 .P
-\fBclient show CLIENT\fR\fI(options)\fR
+\fBclient show CLIENT\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-attribute ATTR\fR
@@ -380,7 +390,7 @@ Show a client\.
 Cookbooks are the fundamental unit of distribution in Chef\. They encapsulate all recipes of resources and assets used to configure a particular aspect of the infrastructure\. The following sub\-commands can be used to manipulate the cookbooks stored on the Chef Server\.
 .
 .P
-\fBcookbook bulk delete REGEX\fR\fI(options)\fR
+\fBcookbook bulk delete REGEX\fR \fI(options)\fR
 .
 .TP
 \fB\-p\fR, \fB\-\-purge\fR
@@ -390,7 +400,7 @@ Purge files from backing store\. This will disable any cookbook that contains an
 Delete cookbooks on the Chef Server based on a regular expression\. The regular expression (\fIREGEX\fR) should be in quotes, not in //\'s\.
 .
 .P
-\fBcookbook create COOKBOOK\fR\fI(options)\fR
+\fBcookbook create COOKBOOK\fR \fI(options)\fR
 .
 .TP
 \fB\-o\fR, \fB\-\-cookbook\-path PATH\fR
@@ -466,16 +476,16 @@ The cookbook copyright, license and email settings can be filled in the \fBknife
 .
 .nf
 
-cookbook_copyright \"YOUR_COMPANY_NAME\"
-cookbook_license \"none\"
-cookbook_email \"YOUR_EMAIL\"
+cookbook_copyright "YOUR_COMPANY_NAME"
+cookbook_license "none"
+cookbook_email "YOUR_EMAIL"
 .
 .fi
 .
 .IP "" 0
 .
 .P
-\fBcookbook delete COOKBOOK [VERSION]\fR\fI(options)\fR
+\fBcookbook delete COOKBOOK [VERSION]\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-all\fR
@@ -489,7 +499,7 @@ Purge files from backing store\. This will disable any cookbook that contains an
 Delete the specified \fIVERSION\fR of the named \fICOOKBOOK\fR\. If no version is specified, and only one version exists on the server, that version will be deleted\. If multiple versions are available on the server, you will be prompted for a version to delete\.
 .
 .P
-\fBcookbook download COOKBOOK [VERSION]\fR\fI(options)\fR
+\fBcookbook download COOKBOOK [VERSION]\fR \fI(options)\fR
 .
 .TP
 \fB\-d\fR, \fB\-\-dir DOWNLOAD_DIRECTORY\fR
@@ -507,7 +517,7 @@ Download the latest version of the cookbook
 Download a cookbook from the Chef Server\. If no version is specified and only one version exists on the server, that version will be downloaded\. If no version is specified and multiple versions are available on the server, you will be prompted for a version to download\.
 .
 .P
-\fBcookbook list\fR\fI(options)\fR
+\fBcookbook list\fR \fI(options)\fR
 .
 .TP
 \fB\-w\fR, \fB\-\-with\-uri\fR
@@ -517,7 +527,7 @@ Show corresponding URIs
 List all the cookbooks\.
 .
 .P
-\fBcookbook metadata COOKBOOK\fR\fI(options)\fR
+\fBcookbook metadata COOKBOOK\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-all\fR
@@ -531,13 +541,13 @@ A colon\-separated path to look for cookbooks in
 Generate cookbook metadata for the named \fICOOKBOOK\fR\. The \fIPATH\fR used here specifies where the cookbooks directory is located and corresponds to the \fBcookbook_path\fR configuration option\.
 .
 .P
-\fBcookbook metadata from FILE\fR\fI(options)\fR
+\fBcookbook metadata from FILE\fR \fI(options)\fR
 .
 .P
 Load the cookbook metadata from a specified file\.
 .
 .P
-\fBcookbook show COOKBOOK [VERSION] [PART] [FILENAME]\fR\fI(options)\fR
+\fBcookbook show COOKBOOK [VERSION] [PART] [FILENAME]\fR \fI(options)\fR
 .
 .TP
 \fB\-f\fR, \fB\-\-fqdn FQDN\fR
@@ -581,7 +591,7 @@ Show a particular part of a \fICOOKBOOK\fR for the specified \fIVERSION\fR\. \fI
 .IP "" 0
 .
 .P
-\fBcookbook test [COOKBOOKS\.\.\.]\fR\fI(options)\fR
+\fBcookbook test [COOKBOOKS\.\.\.]\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-all\fR
@@ -595,7 +605,7 @@ A colon\-separated path to look for cookbooks in
 Test the specified cookbooks for syntax errors\. This uses the built\-in Ruby syntax checking option for files in the cookbook ending in \fB\.rb\fR, and the ERB syntax check for files ending in \fB\.erb\fR (templates)\.
 .
 .P
-\fBcookbook upload [COOKBOOKS\.\.\.]\fR\fI(options)\fR
+\fBcookbook upload [COOKBOOKS\.\.\.]\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-all\fR
@@ -612,7 +622,7 @@ Uploads the specified cookbooks to the Chef Server\. The actual upload executes
 The following sub\-commands are still in the context of cookbooks, but they make use of Opscode\'s Cookbook Community site, \fIhttp://cookbooks\.opscode\.com/\fR\. That site has an API, and these sub\-commands utilize that API, rather than the Chef Server API\.
 .
 .P
-\fBcookbook site download COOKBOOK [VERSION]\fR\fI(options)\fR
+\fBcookbook site download COOKBOOK [VERSION]\fR \fI(options)\fR
 .
 .TP
 \fB\-f\fR, \fB\-\-file FILE\fR
@@ -622,7 +632,7 @@ The filename to write to
 Downloads a specific cookbook from the Community site, optionally specifying a certain version\.
 .
 .P
-\fBcookbook site list\fR\fI(options)\fR
+\fBcookbook site list\fR \fI(options)\fR
 .
 .TP
 \fB\-w\fR, \fB\-\-with\-uri\fR
@@ -632,13 +642,13 @@ Show corresponding URIs
 Lists available cookbooks from the Community site\.
 .
 .P
-\fBcookbook site search QUERY\fR\fI(options)\fR
+\fBcookbook site search QUERY\fR \fI(options)\fR
 .
 .P
 Searches the Community site with the specified query\.
 .
 .P
-\fBcookbook site share COOKBOOK CATEGORY\fR\fI(options)\fR
+\fBcookbook site share COOKBOOK CATEGORY\fR \fI(options)\fR
 .
 .TP
 \fB\-k\fR, \fB\-\-key KEY\fR
@@ -662,13 +672,13 @@ Uploads the specified cookbook using the given category to the Opscode cookbooks
 Stops sharing the specified cookbook on the Opscode cookbooks site\.
 .
 .P
-\fBcookbook site show COOKBOOK [VERSION]\fR\fI(options)\fR
+\fBcookbook site show COOKBOOK [VERSION]\fR \fI(options)\fR
 .
 .P
 Shows information from the site about a particular cookbook\.
 .
 .P
-\fBcookbook site vendor COOKBOOK [VERSION]\fR\fI(options)\fR
+\fBcookbook site vendor COOKBOOK [VERSION]\fR \fI(options)\fR
 .
 .TP
 \fB\-d\fR, \fB\-\-dependencies\fR
@@ -681,31 +691,31 @@ Uses \fBgit\fR version control in conjunction with the cookbook site to download
 Data bags are stores of JSON blobs\. These blobs are called items\. They are free form JSON and indexed by the Chef Server\.
 .
 .P
-\fBdata bag create BAG [ITEM]\fR\fI(options)\fR
+\fBdata bag create BAG [ITEM]\fR \fI(options)\fR
 .
 .P
 Create a new data bag, or an item in a data bag\.
 .
 .P
-\fBdata bag delete BAG [ITEM]\fR\fI(options)\fR
+\fBdata bag delete BAG [ITEM]\fR \fI(options)\fR
 .
 .P
 Delete a data bag, or an item from a data bag\.
 .
 .P
-\fBdata bag edit BAG ITEM\fR\fI(options)\fR
+\fBdata bag edit BAG ITEM\fR \fI(options)\fR
 .
 .P
 Edit an item in a data bag\.
 .
 .P
-\fBdata bag from file BAG FILE\fR\fI(options)\fR
+\fBdata bag from file BAG FILE\fR \fI(options)\fR
 .
 .P
 Load a data bag item from a JSON file\. Looks in the directory \fBdata_bags/BAG/ITEM\.json\fR unless a relative path is specified\.
 .
 .P
-\fBdata bag list\fR\fI(options)\fR
+\fBdata bag list\fR \fI(options)\fR
 .
 .TP
 \fB\-w\fR, \fB\-\-with\-uri\fR
@@ -715,7 +725,7 @@ Show corresponding URIs
 List the available data bags\.
 .
 .P
-\fBdata bag show BAG [ITEM]\fR\fI(options)\fR
+\fBdata bag show BAG [ITEM]\fR \fI(options)\fR
 .
 .P
 Show a specific data bag or an item in a data bag\.
@@ -724,37 +734,37 @@ Show a specific data bag or an item in a data bag\.
 Nodes are the entities which are configured with Chef\. Typically these are servers or workstations\. Nodes are registered as a client, by default by the fully qualified domain name (fqdn)\. A single client may configure more than one node\.
 .
 .P
-\fBnode bulk delete REGEX\fR\fI(options)\fR
+\fBnode bulk delete REGEX\fR \fI(options)\fR
 .
 .P
 Delete nodes on the Chef Server based on a regular expression\. The regular expression (\fIREGEX\fR) should be in quotes, not in //\'s\.
 .
 .P
-\fBnode create NODE\fR\fI(options)\fR
+\fBnode create NODE\fR \fI(options)\fR
 .
 .P
 Create a new node\.
 .
 .P
-\fBnode delete NODE\fR\fI(options)\fR
+\fBnode delete NODE\fR \fI(options)\fR
 .
 .P
 Delete a single node\.
 .
 .P
-\fBnode edit NODE\fR\fI(options)\fR
+\fBnode edit NODE\fR \fI(options)\fR
 .
 .P
 Edit a node\.
 .
 .P
-\fBnode from file FILE\fR\fI(options)\fR
+\fBnode from file FILE\fR \fI(options)\fR
 .
 .P
 Create a node from a JSON file\.
 .
 .P
-\fBnode list\fR\fI(options)\fR
+\fBnode list\fR \fI(options)\fR
 .
 .TP
 \fB\-w\fR, \fB\-\-with\-uri\fR
@@ -764,7 +774,7 @@ Show corresponding URIs
 List all nodes\.
 .
 .P
-\fBnode run_list add [NODE] [ENTRY]\fR\fI(options)\fR
+\fBnode run_list add [NODE] [ENTRY]\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-after ITEM\fR
@@ -774,13 +784,13 @@ Place the ENTRY in the run list after ITEM
 Add a recipe or role to the node\'s \fBrun_list\fR\.
 .
 .P
-\fBnode run_list remove [NODE] [ENTRY]\fR\fI(options)\fR
+\fBnode run_list remove [NODE] [ENTRY]\fR \fI(options)\fR
 .
 .P
 Remove a recipe or role from the node\'s \fBrun_list\fR\.
 .
 .P
-\fBnode show NODE\fR\fI(options)\fR
+\fBnode show NODE\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-attribute [ATTR]\fR
@@ -800,13 +810,13 @@ Show a node\.
 List the recipes available on the server\. The results shown can be limited with the optional PATTERN, which is a regular expression\. PATTERN should be given in quotes, without slashes\.
 .
 .SH "ROLE SUB\-COMMANDS"
-\fBrole bulk delete REGEX\fR\fI(options)\fR
+\fBrole bulk delete REGEX\fR \fI(options)\fR
 .
 .P
 Delete roles on the Chef Server based on a regular expression\. The regular expression (\fIREGEX\fR) should be in quotes, not in //\'s\.
 .
 .P
-\fBrole create ROLE\fR\fI(options)\fR
+\fBrole create ROLE\fR \fI(options)\fR
 .
 .TP
 \fB\-d\fR, \fB\-\-description\fR
@@ -816,25 +826,25 @@ The role description
 Create a new role\.
 .
 .P
-\fBrole delete ROLE\fR\fI(options)\fR
+\fBrole delete ROLE\fR \fI(options)\fR
 .
 .P
 Delete a role\.
 .
 .P
-\fBrole edit ROLE\fR\fI(options)\fR
+\fBrole edit ROLE\fR \fI(options)\fR
 .
 .P
 Edit a role\.
 .
 .P
-\fBrole from file FILE\fR\fI(options)\fR
+\fBrole from file FILE\fR \fI(options)\fR
 .
 .P
 Create or update a role from a role Ruby DSL (\fB\.rb\fR) or JSON file\.
 .
 .P
-\fBrole list\fR\fI(options)\fR
+\fBrole list\fR \fI(options)\fR
 .
 .TP
 \fB\-w\fR, \fB\-\-with\-uri\fR
@@ -844,7 +854,7 @@ Show corresponding URIs
 List roles\.
 .
 .P
-\fBrole show ROLE\fR\fI(options)\fR
+\fBrole show ROLE\fR \fI(options)\fR
 .
 .TP
 \fB\-a\fR, \fB\-\-attribute ATTR\fR
@@ -866,7 +876,7 @@ In order to use knife with the various \fBCLOUD COMPUTING SUB\-COMMANDS\fR, cred
 Chef is commonly used with Amazon AWS EC2 nodes\. This sub\-command will generate instance metadata that can be used to automatically configure an EC2 instance with Chef\. This requires an AMI that has Chef preinstalled with a configuration file that can parse the metadata at run\-time\. At this time this is the only sub\-command for EC2, but more may be added later similar to \fBRACKSPACE\fR and \fBTERREMARK\fR below\.
 .
 .P
-\fBec2 instance data [RUN LIST\.\.\.]\fR\fI(options)\fR
+\fBec2 instance data [RUN LIST\.\.\.]\fR \fI(options)\fR
 .
 .TP
 \fB\-e\fR, \fB\-\-edit\fR
@@ -876,7 +886,7 @@ Edit the instance data
 The \fIRUN LIST\fR should be specified as a space separated list of roles or recipes that will be used by the instance to configure the server\.
 .
 .P
-\fBec2 server create [RUN LIST\.\.\.]\fR\fI(options)\fR
+\fBec2 server create [RUN LIST\.\.\.]\fR \fI(options)\fR
 .
 .TP
 \fB\-Z\fR, \fB\-\-availability\-zone ZONE\fR
@@ -938,7 +948,7 @@ Bootstrap a distro using a template, passed to \fBbootstrap\fR\.
 Creates a new Amazon AWS EC2 instance and bootstraps it by calling the \fBbootstrap\fR sub\-command\. The \fB[RUN LIST\.\.\.]\fR items are passed to the bootstrap\'s \fBrun_list\fR config parameter/option\. See the \fBBOOTSTRAP SUB\-COMMANDS\fR section above for more information\.
 .
 .P
-\fBec2 server delete SERVER [SERVER]\fR\fI(options)\fR
+\fBec2 server delete SERVER [SERVER]\fR \fI(options)\fR
 .
 .TP
 \fB\-A\fR, \fB\-\-aws\-access\-key\-id KEY\fR
@@ -952,7 +962,7 @@ Your AWS API Secret Access Key
 Terminates a running Amazon AWS EC2 instance\.
 .
 .P
-\fBec2 server list [RUN LIST\.\.\.]\fR\fI(options)\fR
+\fBec2 server list [RUN LIST\.\.\.]\fR \fI(options)\fR
 .
 .TP
 \fB\-A\fR, \fB\-\-aws\-access\-key\-id KEY\fR
@@ -969,7 +979,7 @@ List running Amazon AWS EC2 instances\.
 In addition to EC2 nodes, Chef can be used on Rackspace Cloud nodes\. The following sub\-commands allow manipulating Rackspace Cloud nodes via the \fBfog\fR library\.
 .
 .P
-\fBrackspace server create [RUN LIST\.\.\.]\fR\fI(options)\fR
+\fBrackspace server create [RUN LIST\.\.\.]\fR \fI(options)\fR
 .
 .TP
 \fB\-K\fR, \fB\-\-rackspace\-api\-key KEY\fR
@@ -995,13 +1005,13 @@ The server name
 Creates a new Rackspace Cloud server\.
 .
 .P
-\fBrackspace server delete SERVER\fR\fI(options)\fR
+\fBrackspace server delete SERVER\fR \fI(options)\fR
 .
 .P
 Deletes a running Rackspace Cloud server\.
 .
 .P
-\fBrackspace server list\fR\fI(options)\fR
+\fBrackspace server list\fR \fI(options)\fR
 .
 .P
 Lists running Rackspace Cloud servers\.
@@ -1010,7 +1020,7 @@ Lists running Rackspace Cloud servers\.
 As above, Chef can also be used on Slicehost nodes\. The following sub\-commands allow manipulating Slicehost nodes via the \fBfog\fR library\.
 .
 .P
-\fBslicehost server create [RUN LIST\.\.\.]\fR\fI(options)\fR * \fB\-f\fR, \fB\-\-flavor FLAVOR\fR:
+\fBslicehost server create [RUN LIST\.\.\.]\fR \fI(options)\fR * \fB\-f\fR, \fB\-\-flavor FLAVOR\fR:
 .
 .IP "" 4
 .
@@ -1038,7 +1048,7 @@ Your slicehost API password
 Creates a new slicehost server\.
 .
 .P
-\fBslicehost server list\fR\fI(options)\fR
+\fBslicehost server list\fR \fI(options)\fR
 .
 .P
 Lists running Slicehost servers\.
@@ -1059,7 +1069,7 @@ Lists the available Slicehost server images to boot\.
 As above, Chef can also be used on Terremark vCloud nodes\. The following sub\-commands allow manipulating Terremark vCloud nodes via the \fBfog\fR library\.
 .
 .P
-\fBterremark server create NAME [RUN LIST\.\.\.]\fR\fI(options)\fR
+\fBterremark server create NAME [RUN LIST\.\.\.]\fR \fI(options)\fR
 .
 .TP
 \fB\-K PASSWORD\fR, \fB\-\-terremark\-password\fR
@@ -1077,13 +1087,13 @@ Your terremark username
 Creates a new Terremark vCloud server\.
 .
 .P
-\fBterremark server delete SERVER\fR\fI(options)\fR
+\fBterremark server delete SERVER\fR \fI(options)\fR
 .
 .P
 Deletes a running Terremark vCloud server\.
 .
 .P
-\fBterremark server list\fR\fI(options)\fR
+\fBterremark server list\fR \fI(options)\fR
 .
 .TP
 \fB\-K PASSWORD\fR, \fB\-\-terremark\-password\fR
@@ -1175,25 +1185,25 @@ Specifies the name of the client used to validate new clients\. This is requeste
 Specifies the private key file to use for generating ec2 instance data for validating new clients\. This is implied from the \fBvalidation_client_name\fR\.
 .
 .P
-\fBcookbook_copyright\fR\fBcookbook_email\fR\fBcookbook_license\fR
+\fBcookbook_copyright\fR \fBcookbook_email\fR \fBcookbook_license\fR
 .
 .P
-Used by \fBknife cookbook create\fR sub\-command to specify the copyright holder, maintainer email and license (respectively) for new cookbooks\. The copyright holder is listed as the maintainer in the cookbook\'s metadata and as the Copyright in the comments of the default recipe\. The maintainer email is used in the cookbook metadata\. The license determines what preamble to put in the comment of the default recipe, and is listed as the license in the cookbook metadata\. Currently supported licenses are \"apachev2\" and \"none\"\. Any other values will result in an empty license in the metadata (needs to be filled in by the author), and no comment preamble in the default recipe\.
+Used by \fBknife cookbook create\fR sub\-command to specify the copyright holder, maintainer email and license (respectively) for new cookbooks\. The copyright holder is listed as the maintainer in the cookbook\'s metadata and as the Copyright in the comments of the default recipe\. The maintainer email is used in the cookbook metadata\. The license determines what preamble to put in the comment of the default recipe, and is listed as the license in the cookbook metadata\. Currently supported licenses are "apachev2" and "none"\. Any other values will result in an empty license in the metadata (needs to be filled in by the author), and no comment preamble in the default recipe\.
 .
 .P
-\fBknife[:aws_access_key_id]\fR\fBknife[:aws_secret_access_key]\fR
+\fBknife[:aws_access_key_id]\fR \fBknife[:aws_secret_access_key]\fR
 .
 .P
 Specifies the Amazon AWS EC2 credentials to use when running the ec2 sub\-commands\.
 .
 .P
-\fBknife[:rackspace_api_username]\fR\fBknife[:rackspace_api_key]\fR
+\fBknife[:rackspace_api_username]\fR \fBknife[:rackspace_api_key]\fR
 .
 .P
 Specifies the Rackspace Cloud credentials to use when running the rackspace sub\-commands\.
 .
 .P
-\fBknife[:terremark_username]\fR\fBknife[:terremark_password]\fR\fBknife[:terremark_service]\fR
+\fBknife[:terremark_username]\fR \fBknife[:terremark_password]\fR \fBknife[:terremark_service]\fR
 .
 .P
 Specifies the Terremark vCloud credentials to use when running the terremark sub\-commands\.