Information Technology Reference
In-Depth Information
Nope, doesn't seem to be installed. How do we install
chef-client
on the node? Although
we could follow the instructions again for
Installing Chef Client on Linux
from
Chapter 2
by
running the following, don't do this:
curl -Lk https://www.getchef.com/chef/install.sh | sudo bash
There is an easier way. Type in the
exit
command on your node to get back to your host
prompt:
[vagrant@default-centos65 ~]$
exit
logout
Connection to 127.0.0.1 closed.
Double-check to make sure that the prompt being displayed is actually your host prompt (no
vagrant@default-centos65
). Run the command
kitchen setup default-centos65
to
install
chef-client
:
$
kitchen setup default-centos65
-----> Starting Kitchen (v1.2.2.dev)
-----> Converging <default-centos65>...
Preparing files for transfer
Berksfile, Cheffile, cookbooks/, or metadata.rb not found so Chef will
run with effectively no cookbooks. Is this intended?
Removing non-cookbook files before transfer
-----> Installing Chef Omnibus (true)
downloading https://www.getchef.com/chef/install.sh
to file /tmp/install.sh
trying wget...
trying curl...
...
-----> Setting up <default-centos65>...
Finished setting up <default-centos65%gt; (0m0.00s).
-----> Kitchen is finished. (0m19.93s)
If you inspect the output, the
kitchen setup
command installed the
chef-client
for you.
The
kitchen setup
command is used to run a
provisioner
. Provisioner is a generic term for
any kind of configuration management software, as Test Kitchen can be used with other con-
figuration management tools besides Chef. By default, Test Kitchen is configured to use the
ChefSolo provisioner, which installs Chef Client without configuring the tools to use a Chef
