Every day Rally step by step closer to the point where Rally is going to be
generic framework and it would be possible to split Rally & Rally OpenStack Plugins
One of the blockers for doing this is certification & samples directories and
their contents. Current apporach creates a lot of confusion:
- Rally Users are running samples against production
- Rally samples are actually not that usefull, because creating from them
tasks takes a lot of time
- Rally Users don't know what certification task is and how to use it
- Samples are hard to ship/find in packaged way (when rally is installed)
- Samples are going to be impossible to ship after the split
- We have to keep hunderds of yaml/json files in actual state
in our repo (extra work for developers)
Proposed approach is to:
- Create mechansim CLI command that generates samples using plugin names
- Rename certification -> tasks
- Put in tasks directory pre created and tested tasks for different use cases:
key performance metrics, functional testing, load testing of key functionality,
ha Testing
- Remove samples as they are not needed anymore
Change-Id: I4c45224c3af637d17dab0edea038c69a2bae8b1a
bd067082c5