Add name into dummy engine schema and make it required

In the super class EngineFactory, the engine name is got from deployment.
So each deploy engine should have the name.
The patch is to add name to DummyEngine and make it required.

Change-Id: Ic5da73b2f4cffe1cad0fe104203b267b2501af6e
Remove debug print from fileutils

Change-Id: I2ebc3818d90847c3bfa931c1de6b7c29eda9839b
Closes-Bug: #1272221
Add option to use deployment on creation

Call use deployment when a deployment is created so that the newly
created deployment is default for future operations.

Change-Id: I3d223336d221f4794b3912fea8a381a0c4934aa5
Add FuelClient

Client for access to Fuel API.

blueprint fuel-engine

Change-Id: If1572357b58e66cff84a5d2256f7b4d3bff2f0e4
Merge "Create rally deployment from OS_* environment variables"
Merge "Add option to use deployment on creation"
Merge "Add FuelClient"
Merge "Add name into dummy engine schema and make it required"
Validators adder for benchmarks preconditions

Implements decorator for adding validators to method.
Validators are called in benchmark runner.
Validation method should return instance of
rally.benchmark.validation.ValidationResult class.

Blueprint validate-benchmark-preconditions

Change-Id: I68c8f5cc5d8758026bbe7ef211aa914b313ebb81
Add deployment check subcommand

* Check keystone endpoints and print user-friendly messages so the
user can easily troubleshoot issues,
* List all available services of your deployed OpenStack,
* Refactoring of benchmark.engine.bind in order to avoid redundancy.

Implements blueprint deployment-check-subcommand

Change-Id: Iecfc2e4c093f567b56c3990c598326942c50e34a
Move cleanup utility functions to benchmark.utils

This is an initial effort to cleanup ScenarioRunner before it is
refactored to sparate scenario types.

Change-Id: Icd2002b3a8919bcbb162e5a75e17f00891b04199
Trello: https://trello.com/c/JN6xUY79