diff options
| author |   chenjiankun <chenjiankun1@huawei.com> | 2017-02-25 00:48:07 +0000 |
|---|---|---|
| committer | chenjiankun <chenjiankun1@huawei.com> | 2017-03-08 08:42:32 +0000 |
| commit | af3478e95314b5147c7837831dc8113d552ba067 (patch) | |
| tree | e9411bebe78eca2f0d204d8a49464e7f620a0ff1 /yardstick/dispatcher/base.py | |
| parent | 501175fbb095a771f5f1b9fb80dcf729192214d2 (diff) | |
Bugfix: yardstick will create stacks with the same name when run using API in parallel
JIRA: YARDSTICK-575
Currently yardstick will create stacks with the same name when run using
API in parallel.
The reason is there is a global variable in context base and the core
will always deploy the first context in Context.list. When run in
parallel, it will run in the one process. So yardstick will deploy
stacks with the same name.
The solution is do not use Context.list in yardstick core. And using a
local variable instead.
BTW, if we use API to call yardstick core, we can not config the output
way. So I parse yardstick.conf when task start. And I think we can
include scenario_cfg, context_cfg, yardstick_cfg in one config object
later so that we can get all config in one object.
Change-Id: I1ada4ef486bd252e78c3a2e49c6a39b3f8f16a7c
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
Diffstat (limited to 'yardstick/dispatcher/base.py')
| -rw-r--r-- | yardstick/dispatcher/base.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/yardstick/dispatcher/base.py b/yardstick/dispatcher/base.py index 09ce8d1e8..a1c858297 100644 --- a/yardstick/dispatcher/base.py +++ b/yardstick/dispatcher/base.py @@ -38,10 +38,10 @@ class Base(object): raise RuntimeError("No such dispatcher_type %s" % dispatcher_type) @staticmethod - def get(config): + def get(conf, config): """Returns instance of a dispatcher for dispatcher type. """ - return Base.get_cls(config["type"])(config) + return Base.get_cls(conf["type"])(conf, config) @abc.abstractmethod def record_result_data(self, data): |