run_tests.sh should exit non-zero when tests fail

If any test fail set set a global flag to a non-zero value.  Exit
with that value.
pylint should only fail test on fatal error

pylint will exit non-zero on any type of issue it uncovers, such
as a code convention issue.  We only want to fail the tests if
pylint discovers fatal issues.

There are currently only a few errors and dozens of warnings.  If
we can get those cleaned up then we can cause the test to fail
when new errors (or warnings) are introduced.
Merge pull request #367 from nsavin/master

added several dependencies for nova/Grizzly
Modify smithy to facilitate multi-distribution support

* support for OEL 6.3+ added to smithy
* smithy no longer bootstraps as a side-effect of being run: it asks the user to
  set '--bootstrap' if necessary.
* bootstrap steps and (rpm, pip) package dependencies moved to configuration files
  under tools/bootstrap/$distribution
* common bootstrap code refactored
* rpm installs are now idempotent.
* smithy checksum now based on bootstrap config files
* --force also supported as a command-line flag

TODO:
* pypi installs should probably also be made idempotent
* CentOS support
Merge pull request #368 from dmercer/multi-distro-smithy

Modify smithy to facilitate multi-distribution support
Merge pull request #369 from jaybuff/run-tests-exit-code

run_tests.sh should exit non-zero when tests fail 
Update smithy
No longer need these files
Merge pull request #370 from harlowja/master

Remove files replaced by bootstrap files.
Add in comment about the dynamic late import.
Only bother destroying if a domain object was found.
Small cleanups.