Imporve monitor_process pass criteria 55/35655/1
authorJingLu5 <lvjing5@huawei.com>
Thu, 25 May 2017 08:48:15 +0000 (08:48 +0000)
committerJing Lu <lvjing5@huawei.com>
Thu, 1 Jun 2017 12:36:38 +0000 (12:36 +0000)
commit9a372b8adf618981e4fbfb8d0cb3a48674c65d92
tree1f1bfe82e1854d576e109727afc88c9ab57ffd1c
parentad3ff4cbaf92808801c9157d25416da6cff82666
Imporve monitor_process pass criteria

JIRA: YARDSTICK-660

The monitor func()'s criteria in the monitor_process.py now is whether at least
one process of the specific controller node service is recovered. But in reality
is more resonable to use whether processes have been recoverd to it's original
amount. This patch is aiming at improving the isssue

Change-Id: I950ce2a89555801b96092735b0d670e892049927
Signed-off-by: JingLu5 <lvjing5@huawei.com>
(cherry picked from commit 37921fcd232cd2fbba9f45ef9fa5d8c912f54af6)
13 files changed:
tests/unit/benchmark/scenarios/availability/test_attacker_process.py
tests/unit/benchmark/scenarios/availability/test_basemonitor.py
tests/unit/benchmark/scenarios/availability/test_monitor_command.py
tests/unit/benchmark/scenarios/availability/test_monitor_general.py
tests/unit/benchmark/scenarios/availability/test_monitor_multi.py
tests/unit/benchmark/scenarios/availability/test_monitor_process.py
yardstick/benchmark/scenarios/availability/attacker/attacker_process.py
yardstick/benchmark/scenarios/availability/attacker/baseattacker.py
yardstick/benchmark/scenarios/availability/director.py
yardstick/benchmark/scenarios/availability/monitor/basemonitor.py
yardstick/benchmark/scenarios/availability/monitor/monitor_multi.py
yardstick/benchmark/scenarios/availability/monitor/monitor_process.py
yardstick/benchmark/scenarios/availability/serviceha.py