rally/rally-jobs/plugins
Boris Pavlovic e2d52daf12 Refactoring of scenario plugin base
* Moved rally.task.scenarios.base -> rally.task.scenario

  - Shorter imports and simpler structure of tree
  - Unified with other plugin bases

* Add rally.task.atomic module

  - We will use atomic actions in both scenarios and context
    this is first step of unification

  - Module has only links to method and atomic action context
    with new names. So we will change all plugins but won't
    touch atomic actions at this patch (to reduce amount of
    LOC in this patch)

  - Next step is to move and unify atomic action code for
    scenarios and contexts

* Rename rally.task.scenario.scenario to rally.task.scenario.configure

  scenario.scenario is unclear and not aligned with other plugin
  types where configure() method is used for the same purpose

* Add shortcut rally.plugins.openstack.scenario.configure

  so there is no need to import rally.plugins.openstack.scenario
  and rally.task.scenario modules

* Fix all unit tests & docs

Change-Id: I388bd1c1af951670c6a1d043cfeb2a6753a085b0
2015-08-14 08:27:20 -07:00
..
test_relative_import Fix rally plugins relative imports 2015-04-22 11:59:40 +03:00
__init__.py Fix rally plugins relative imports 2015-04-22 11:59:40 +03:00
fake_plugin.py Refactoring of scenario plugin base 2015-08-14 08:27:20 -07:00
README.rst Rename rally-scenarios to rally-jobs & add readme 2014-11-24 16:13:47 +04:00

Rally plugins

All *.py modules from this directory will be auto-loaded by Rally and all plugins will be discoverable. There is no need of any extra configuration and there is no difference between writing them here and in rally code base.

Note that it is better to push all interesting and useful benchmarks to Rally code base, this simplifies administration for Operators.