Updating Chef-compatible images#
If your image uses Chef recipes, after you upgrade to HCL™ Launch version 6.2.1 or later, you must manually update the Chef hook on the images in your cloud.
-
Extract the os-chef-config-hook.tgz file.
This file is provided in the heat engine installation media and is in the following location: /installation_files_location/ibm-ucd-patterns-install/engine-install/resources.
-
Create a copy of the
hook-chef
file, which is in the following directory: extracted_files/os-chef-config-hook/heat-templates/hot/software-config/elements/heat-config-chef/install.d. -
Rename the
hook-chef.py
file that you copied aschef
. -
On an image that you configured for Chef, in the /var/lib/heat-config/hooks folder, replace the
chef
file with the copy that you renamed. -
Change the permission of the new
chef
file to 0777. -
Shut down the image with the following command:
shutdown -h now
-
Create an image and upload it to your cloud.
For more information, see Creating Chef-compatible images.
After you update the Chef hook, you can provision environments from blueprints that contain Chef recipes. You can also modify blueprints that contain Chef recipes to obtain the Chef validator key value without the use of a hosted file that contains the value. See Modifying blueprints to access the Chef validator key in version 6.2.1 and later.