Information Technology Reference
In-Depth Information
ectory matching the suite name in the .kitchen.yml . To halt both virtual machines, run the fol-
lowing commands:
$ cd ~/chef-repo/cookbooks/enterprise-chef/.kitchen/kitchen-vagrant/
$ default-centos65 vagrant halt
==> default: Attempting graceful shutdown of VM...
$ cd ~/chef-repo/cookbooks/node/.kitchen/kitchen-vagrant/node-centos65
$ vagrant halt
==> default: Attempting graceful shutdown of VM...
When you want to restart them, run vagrant reload against both Vagrantfiles:
$ cd ~/chef-repo/cookbooks/enterprise-chef/.kitchen/kitchen-vagrant/
$ default-centos65 vagrant reload
==> default: Checking if box 'learningchef/centos65' is up to date...
...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
...
$ cd ~/chef-repo/cookbooks/node/.kitchen/kitchen-vagrant/node-centos65
$ vagrant reload
==> default: Checking if box 'learningchef/centos65' is up to date...
...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
...
$ cd ~/chef-repo
Bootstrap Chef Server with Chef Solo
Before we conclude this chapter, it is worth mentioning that you can use Chef Solo outside
of Test Kitchen to automate the deployment of Chef Server in production. We expect to see
most Chef Solo-based software migrate to Chef Local/Chef Zero, as we covered in Chef Cli-
ent Modes . However, Chef Solo is still singularly useful for bootstrapping Chef Server itself,
as some scripts get confused about which server to communicate with when you try to set up
Chef Server using Chef Local/Chef Zero, because Chef Zero launches a second in-memory
Chef Server.
Search WWH ::




Custom Search