Benchmark engine code refactoring
One of the core parts of Rally, the benchmark engine, has recently considerably grown and now requires some code refactoring. The main directions of refactoring here comprise:
* Better module organization: e.g. the ScenarioRunner class should be definitely moved into a separate module;
* Merging two 'utils' modules (cleanup_utils and utils) into one module;
* Avoiding code duplicate inside ScenarioRunner and utils methods;
* Fixing inconsistency in the output of the benchmark engine (ensure that the output JSON has always the same fields).
Blueprint information
- Status:
- Complete
- Approver:
- Boris Pavlovic
- Priority:
- Medium
- Drafter:
- Mikhail Dubov
- Direction:
- Needs approval
- Assignee:
- Mikhail Dubov
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Boris Pavlovic
- Completed by
- Boris Pavlovic
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Moving ScenarioRunner class to a separate module
Addressed by: https:/
Merge benchmark.utils and benchmark.
Addressed by: https:/
Refactor the way benchmark engine returns its results
Gerrit topic: https:/
Addressed by: https:/
Make resource status checking letter case independent
Addressed by: https:/
Log warnings instead of infos about cleanup fails
Addressed by: https:/
Fix and unify structure of modules in benchmark engine
Gerrit topic: https:/
Addressed by: https:/
[WIP] Refactor BenchmarkEngine
