These are frequently asked questions or tips that don't have a better home just yet.
If you're using ChefDK, check for it
chef gem list | grep $DRIVER you need to make sure the driver exists,
if it does:
~$ gem install kitchen-openstack # for instance ~$ vi cookbooks/demo/.kitchen.yml # wherever your .kitchen.yml is for your cookbook
.kitchen.yml as appropriate and run
kitchen list to verify that everything
is working as expected. There is a strong chance that the flavors, or
image names are different per driver, so when migrating between drivers be prepared
to change these at the very least.
Certain drivers, like
kitchen-dokken recommend setting
KITCHEN_LOCAL_YAML environment variable to ensure these configs are used when there are multiple in a directory.
Due to the nature of how the ChefDK is built, it is not possible to update a gem that is part of the package. To get the latest versions of component software, builds from the current channel can be consumed.
transport section in
.kitchen.yml, for instance:
transport: username: ubuntu
So there are a few things that already exist that sort of cover this in the kitchen world:
For the system level proxies and the polipo/squid locally you don't need to do much but you'll still need to edit the conf files for yum/apt as appropriate. If vagrant-cachier it will be used by
kitchen-vagrant as default. This behaviour is documented here.