deploy: exit with error code if booting the machines fails
Explain workaround for "malformed version number string" after upgrading
to Vagrant 1.5.x
Explain how to find the instance ID after launching an EC2 instance
Better explain how to scp/ssh into the newly launched instance
Use x86_64 RPM link installing PuppetLabs yum repo
Use puppetlabs-release-6-10.noarch.rpm
Terminate EC2 instance at the end of the custom AMI creation process
Fix AMI creation for latest Amazon Linux 2014.03 (Puppet woes)
Better name for custom AMI
Enforce Vagrant 1.5.4+
Use ami-fb8e9292 (Amazon Linux 2014.03.1) as base image

This AMI is PV EBS-Backed 64-bit, US East N. Virginia.
Explain how to delete custom AMIs
Explain problems of latest Amazon Linux AMIs with latest Puppet versions
Update CHANGELOG with WIRBELSTURM-6
Enforce Puppet version 3.3.1 in deployed machines

This prevents the following issue during puppet apply runs, which seems
to be related to Puppet 3.5.x:

    Failed to generate additional resources using 'eval_generate:
    uninitialized constant Puppet::FileSystem