(QE-519) beaker should raise error if host does not have a platform set

- beaker tries to do crazy things when hosts aren't on supported
  platforms, let's check that option right at the start
documentation for supported HOST settings
enforcing platform format of OS-VERSION-ARCH

- added spec tests to ensure that we correctly sort out bad platform
  names
- will need to write an associated patch to update our node
  configuration files to meet the new standard
Merge pull request #83 from anodelman/make-gem

make 1.0.1 gem
move VagrantFiles into .vagrant_files directory of working directory
Merge pull request #80 from anodelman/hunner

move VagrantFiles into .vagrant_files directory of working directory
Merge pull request #72 from anodelman/check-platform-set

(QE-519) beaker should raise error if host does not have a platform set
Catch SystemCallError during blimpy provision for retry

Previously we were only catching Fog::Errors::Error exceptions, this patch
makes sure that system call failures are also caught, so things like connection
refused and no route to host which are generally transient, are caught and
retried properly.

Signed-off-by: Ken Barber <ken@bob.sh>
Merge pull request #84 from kbarber/maint/master/retry-blimpy-on-systemcall-errors

Catch SystemCallError during blimpy provision for retry
(QE-148) support upgrading packages
(QE-147) Add support to deploy package repositories
Only update apt repo if needed

Previously, the code would run apt-get update at every package
install. This memoizes when apt-get update has been run so we don't
need to run it as frequently
Merge pull request #39 from branan/master

RFC: QE-147 and QE-148
Merge pull request #87 from anodelman/make-gem

make 1.1.0 gem
Fix catch_failures option

If `:catch_failures => true` is supplied and no extra
`:acceptable_exit_codes` are supplied, a bug hindered the
`#apply_manifest_on` method from performing correctly.
Merge pull request #88 from hunner/fix_catch_failures

Fix catch_failures option
Add `:expect_failures` option

When performing positive tests of applying manifests, the
`#apply_manifest` method may be called with `:catch_failures => true`.

This commit also adds an argument of `:expect_failures` to allow
`#apply_manifest` to perform negative tests.
Merge pull request #89 from hunner/expect_failures

Add `:expect_failures` option
(QE-598) apply_manifest_on fails if acceptable_exit_codes is not set

- was using 0 instead of [0] as the default acceptable exit code
Add specs for this bug