Information Technology Reference
In-Depth Information
---
driver
:
name
:
vagrant
provisioner
:
name
:
shell
platforms
:
-
name
:
centos65
driver
:
box
:
learningchef
/
centos65
box_url
:
learningchef
/
centos65
network
:
- [
"private_network"
, {
ip
:
"192.168.33.35"
}
]
synced_folders
:
- [
"../../../chef-repo"
,
"/chef-repo"
]
suites
:
-
name
:
node
attributes
:
Spin up the node environment with
kitchen create
:
$
kitchen create
Bootstrap the Node with Knife
Figure 9-12
is an overview of the setup we've configured so far in this chapter. We've con-
figured a Chef server (or used Hosted Enterprise Chef), and we configured a
knife.rb
with the
appropriate keys so we can communicate with the Chef server from our host, the administrat-
or's workstation. We've established that this communication channel works by verifying that
knife client list
produces the expected output.
Now let's set up our node like we would in production by “bootstrapping” the node with
knife bootstrap
. ((((“Test Kitchen”,"in production environments”)))We won't be able to
use Test Kitchen in production!) When we run
knife bootstrap
on the our host, it will in-
stall Chef Client on the node and register it to be managed by Chef Server.
Nodes must have valid fully qualified domain names set up in your local domain name ser-
vice (DNS) as well. Let's add an entry to our local host database for the node just like we did
for Chef Server.
