checked code logic for UC2-vim001 recovery time measurement 45/59245/1
authorGerard Damm <gerard.damm@wipro.com>
Fri, 22 Jun 2018 02:10:11 +0000 (21:10 -0500)
committerGerard Damm <gerard.damm@wipro.com>
Thu, 28 Jun 2018 20:43:37 +0000 (20:43 +0000)
commit9dab43792c0e7801acce8dbdfbd8012d21464251
tree4a81992ba6ad6a2acea9bb56da3a6bfd616bc05c
parent0f43563624832c5908e6fc00eb0a4bbc6cc82c33
checked code logic for UC2-vim001 recovery time measurement

JIRA: AUTO-38

Leveraging new OpenStack SDK release 0.14, tested existing code for
UC2/vif-001 (simulated VM failure), to verify that generic code for
recovery time measurement works.

Entered test code in placeholders for this test case: challenge start
(suspend a VM), challenge stop (resume, although this was done
outside (from Horizon), to simulate an ONAP-controlled recovery),
test code (periodic status check, stop when VM is active again).
Time was measured correctly, output files (.csv) were created
successfully.

This will allow to close Jira ticket 38.

Next steps will be to interface with ONAP, to obtain VNF info
(especially the ID of the corresponding OpenStack VMs), and perform
the same measurement, which this time will be an actual recovery
time, provided DCAE data collection, Policy and CLAMP have the
proper configuration.

Change-Id: I7320f7570c119d2b59d1ed6ca787ba975ad04a44
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
(cherry picked from commit dffc2bee5650b10831f3792b162b6ea73a4624ae)
lib/auto/testcase/resiliency/AutoResilItfCloud.py
lib/auto/testcase/resiliency/AutoResilMgTestDef.py
lib/auto/testcase/resiliency/clouds.yaml