Merge pull request #194 from anodelman/make-gem

create beaker 1.9.0 gem
(maint) vagrant hypervisor support broken by bad call to hack_etc_hosts

- nertz
Merge pull request #195 from anodelman/vagrant-etc-hosts

(maint) vagrant hypervisor support broken by bad call to hack_etc_hosts
Merge pull request #196 from anodelman/make-gem

create beaker 1.9.1 gem
(QENG-407) update google compute to differentiate between template and platform

- assume that the google compute image name will be in host[:image],
  otherwise default to host[:platform]
- fixes up the differentiations between google naming rules and our
  internal platform naming rules
(QENG-409) Beaker does not write out JUnit XML when...

...certain internal exceptions occur
- on ruby 1.8 Timeouts are raised as Interrupt (parented by SignalException)
  instead of out of RuntimeError (which is parented by StandardError) and are
  thus not being caught appropraitely.
- added spec test coverage for correct error reporting
firewall + ssh fixes for google compute

- firewall allows ports 8080/8081
- retry on failure to authenticate errors (happens when google compute
  boxes haven't successfully spun up yet)
Add future parser as option when applying a manifest

This option can enable the use of the future parser when applying a manifest.
I'm not 100% sure though what it will do on older puppet versions that don't support that option.
(QENG-433) make validation steps in beaker optional

- turn on/off with -(-no)-validate
- defaults to 'true'
Error early if provision option is set to false but Vagrantfile not found

User needs to enable provision
Merge pull request #201 from maestrodev/provision-anyway

If provision option is set to false but Vagrantfile not found, then provision anyway
(maint) create host.hostname procedure

- convenience method for accessing the hostname of the given host
Merge pull request #197 from anodelman/google-cloud

(QENG-407) update google compute to differentiate between template and platform
Merge pull request #205 from anodelman/vmname-confusion

(maint) create host.hostname procedure
Add test and yardoc
Merge pull request #202 from anodelman/exit-with-xml

(QENG-409) Beaker does not write out JUnit XML when...
Merge pull request #209 from anodelman/optional-validation

(QENG-433) make validation steps in beaker optional
PDB-554 Implement a new EC2 backend and add jenkins_build_url to tags

This patch implements a replacement for the blimpy backend. It replaces the
use of blimpy to launch EC2 nodes with the Amazon AWS::EC2 library.

This was introduced to provide more control over handling error states, without
the granular control of a lower level library we are relying on blimpy to have
error handling (which it largely does not).

My theory was that we could either improve blimpy to do more, or just replace
it with a better driver that allows us to maintain our provisioning code on
its own without worrying about an upstream project. Since we don't use blimpy
for anything else, and we don't want the delay of having an upstream project
release our changes replacement seemed like a better option.

The driver is initiated with the hypervisor: ec2 setting in the users template
files and is built to match the blimpy behaviour in the way it configures
security groups and key pairs. To a reasonable extent users using blimpy right
now should be able to switch over with very little change.

As an aside, I've also added the ability to pass through the BUILD_URL from
a jenkins job as a tag in EC2 (and I've added this code to GCE as well). This
allows a better traceback from VM's to a particular job so we can identify
zombied jobs better.

Signed-off-by: Ken Barber <ken@bob.sh>
PDB-554 Add image checking and root device setup

Signed-off-by: Ken Barber <ken@bob.sh>
PDB-554 Set ENV variable jenkins_build_url to ensure test matches

Signed-off-by: Ken Barber <ken@bob.sh>