Information Technology Reference
In-Depth Information
to use the IP address 192.168.33.37. Make sure this address does not conflict with the IP ad-
dress of your Chef Server. It should be 192.168.33.36.
Note that we also changed the suite name to be
node
, as this sandbox environment will be
running our node, and have the other sandbox environment running our Chef Server. Having
different names will disambiguate the two environments.
Example A-6. chefdk/chef-repo/cookbooks/node/.kitchen.yml
---
driver
:
name
:
vagrant
provisioner
:
name
:
shell
platforms
:
-
name
:
centos65
driver
:
box
:
learningchef
/
centos65
box_url
:
learningchef
/
centos65
network
:
- [
"private_network"
, {
ip
:
"192.168.33.37"
}
]
suites
:
-
name
:
node
run_list
:
attributes
:
Spin up the node environment with
kitchen create
:
$
kitchen create node-centos65
Bootstrap the Node with Knife
Figure A-6
presents an overview of the current setup we've configured so far. We've con-
figured a Chef Server (or used Hosted Enterprise Chef), and we configured a
knife.rb
with
the appropriate keys, so that we can communicate with the Chef server from our host, the ad-
ministrator's workstation. We've established that this communication channel works by veri-
fying that
knife client list
produces the expected output.
