Use latest chef-metal-* gems
Make us machine_batch aware
Vagrant modifications for new chef-metal interface
WIP: EC2 support
My vagrant install has vmware as the default provider which highlighted an issue when here that virtualbox is assumed to be the provider.  Adding this ENV var accounts for that expectation.
New knife options to tell chef-metal where the ssh keys are
Horrible stuff I had to do since hashie 3.0.0
Deal with changes in the ChefMetalFog::AWSCredentials class
To deal with recent fog_key_pair changes
To deal with namespace change from provisioner_output to metal.location
To deal with namespace change from provisioner_output to metal.location
Be smarter about regions, use the one from config.json rather than .aws/config
Fix bug where S3 is sometimes flakey, retry a couple of times
vgchange -a is more universally accepted than vgchange --activate
Comment-out the manual creation of the backend_vip - this should be handled by the custom scripts anyway
chef-metal 0.11 doesn't respect not_if/only_if in machine resource anymore
Correct the cloud_machine_created behavior when no instances are running
Automatically hunt for an open chef-zero TCP port
Here too:  automatically find the next available port
One more thing was needed to allow parallel ec-metal runs, a local lockfile