(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
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)
(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
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>
PDB-554 Decompose #provision and break out amiports into its own class

Signed-off-by: Ken Barber <ken@bob.sh>
PDB-554 Use hack_etc_hosts instead and make a wait_for_ssh method

The wait_for_ssh method works around a race during provisioning whereby a
machine can come up and be ready for SSH connections, but you will get an
authenthentication error if you try to quickly.

Signed-off-by: Ken Barber <ken@bob.sh>
PDB-554 Correct handling of /etc/hosts creation and ensure hostnames are set

Signed-off-by: Ken Barber <ken@bob.sh>
PDB-554 Use ec2's dynamic names

This obviates the need for /etc/hosts modification by using the EC2 public
names only.

Signed-off-by: Ken Barber <ken@bob.sh>
PDB-554 Provide a bare minimum /etc/hosts for Ubuntu 10.04 compatibility

Signed-off-by: Ken Barber <ken@bob.sh>
PDB-554 Execute configure_hosts() after wait_for_ssh()

Signed-off-by: Ken Barber <ken@bob.sh>
PDB-554 Remove wait_for_ssh now the underlying layers handles it

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