summaryrefslogtreecommitdiffstats
path: root/docs/development/opnfvsecguide
diff options
context:
space:
mode:
authorGerard Damm <gerard.damm@wipro.com>2018-06-28 20:49:18 +0000
committerGerrit Code Review <gerrit@opnfv.org>2018-06-28 20:49:18 +0000
commitdb95ec7006d71139833fcdb62188c818499d7507 (patch)
tree1adce85503c9fd23d92d480643a61ea28e333dc1 /docs/development/opnfvsecguide
parentccaa66ca744d0612d24072e70e15de76634d1bdd (diff)
Update git submodules
* Update docs/submodules/auto from branch 'stable/fraser' - Merge "checked code logic for UC2-vim001 recovery time measurement" into stable/fraser - 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)
Diffstat (limited to 'docs/development/opnfvsecguide')
0 files changed, 0 insertions, 0 deletions