Fixes the issue with Fog and AWS not returning a "groupName" for rules
Attempt to work around a bug in Amazon's API response for describing security groups.
Revert "Attempt to work around a bug in Amazon's API response for describing security groups."

This reverts commit 8755ac2c008d814b285af8743f400c3e12b38261.
Merge pull request #449 from FernandoEscher/master

Work around a bug in Amazon's API response for describing security groups.
Some code clean up.
A bit more clean up.
Validate the SSH key configuration.

This is a common source of error for newcomers and veterans lalike. It's especially annoying because Capistrano hides the true source of error. So, if we can catch common error cases before Capistrano fails silently it'll be better for all.
ruby-head is failing due to nokogiri not working on it.
While Process::Status can be compared to Fixnum, it looks a bit weird so this switches to comparing the exit status.
Be more graceful in failing to install core packages.

This may seem counterintuitive, since if a package is core and fails to install, that's usually bad. The problem is, since this list is hard-coded in, our users have no way of modifying it short of forking the gem. The real problem here is Ubuntu has a history of renaming packages that we need as core.  So, we have to include all possible names in our core list, but not all are guaranteed to install on the supported LTS releases.  We only need one of the alternatives to install properly, so in that scenario it is appropriate to ignore the failures.
Preparing the 2.10.1 release.
Removed a duplicated char.
Upgraded from ruby-build 20140225 to 20140702 to get newer definitions.
Upgraded default Ruby from 2.0.0-p451 to 2.0.0-p481 to get latest security fixes.
Use different download URLs for graphite because GitHub has an SSL bug preventing downloads on Ubuntu 12.04.
Clean up after the graphite installation.
Upgrade from graphite 0.9.10 to 0.9.12.
Preparing the 2.10.2 release.