This gist will contain updates to the Chef Provisioning portion located in Chapter 9 of the 1st edition of “DevOps for VMWare Administrators"
The chapter has a warning on page 136 warning users due to the heavy development of Chef Provisioning that the instructions may no longer work. This gist is to capture the changes and allow the instructions to work.
-
Combined use of provisioning driver & machine recipes
-
No need for two files (like done in book)
-
Recipes become one stop artifacts for the cloud they are deployed in
- The chapter originally highlights the benefits of keep these two separate. Real world feedback suggests users like the provisioning driver to live with the machine recipe.
-
-
Examples still used ‘chef_metal_vsphere’ but the driver has been renamed to: ‘require 'chef/provisioning/vsphere_driver'.
-
Development between original publication to today changed:
-
The way drivers are organized and found to avoid namespace collisions
-
Product was renamed from ‘chef metal’ to ‘chef provisioning’ and these naming changes were made aggressively in the core product.
-
-
-
Resource name changed from ‘with_vsphere_provisioner’ to ‘with_vsphere_driver’
- Property name changed from ‘vsphere_host’ to ‘host’
-
Resource name changed from ‘with_provisioner_options’ to ‘with_machine_options’