diff options
author | Gerard Damm <gerard.damm@wipro.com> | 2018-04-13 14:39:15 -0500 |
---|---|---|
committer | Gerard Damm <gerard.damm@wipro.com> | 2018-04-26 02:12:51 +0000 |
commit | dffc864fe9f66d125ec937d63b3279363ab26cec (patch) | |
tree | 9de3bdb7e7e3cf4929d65a3002fd7de60421a4ab /docs/release/userguide/UC01-feature.userguide.rst | |
parent | 5c8112dd4434e726da1325b0a699b9839f2f3d6b (diff) |
User Guide April 13th update, for Fraser MS9
JIRA: AUTO-26
Updated user guide for each Use Case:
- UC1: minor typos
- UC2: new figures (test logic, cardinalities), additional text
- UC3: new figures (test cases mapped on architecture), updated
text, aligned with updated UC3 definition
Change-Id: I45faef95fde8eb362faffaa7469a0f2e1bcbf318
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
(cherry picked from commit 56002f18fbac67bcdd197e04689414b25c830ddc)
Diffstat (limited to 'docs/release/userguide/UC01-feature.userguide.rst')
-rw-r--r-- | docs/release/userguide/UC01-feature.userguide.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/release/userguide/UC01-feature.userguide.rst b/docs/release/userguide/UC01-feature.userguide.rst index 5cf38e1..ea02bad 100644 --- a/docs/release/userguide/UC01-feature.userguide.rst +++ b/docs/release/userguide/UC01-feature.userguide.rst @@ -34,7 +34,7 @@ Preconditions: Main Success Scenarios: -* lifecycle management - stop, stop, scale (dependent upon telemetry) +* lifecycle management - start, stop, scale (dependent upon telemetry) * recovering from faults (detect, determine appropriate response, act); i.e. exercise closed-loop policy engine in ONAP @@ -47,7 +47,7 @@ Details on the test cases corresponding to this use case: * Environment check - * Basic environment check: Create test script to check basic VIM (OpenStack), ONAP, and VNF are up and running + * Basic environment check: Create test script to check basic VIM (OpenStack), ONAP, and VNF(s) are up and running * VNF lifecycle management @@ -55,7 +55,7 @@ Details on the test cases corresponding to this use case: * Tacker Monitoring Driver (VNFMonitorPing): - * Write Tacker Monitor driver to handle monitor_call and based on return state value create custom events + * Write Tacker Monitor driver to handle monitor_call and, based on return state value, create custom events * If Ping to VNF fails, trigger below events * Event 1 : Collect failure logs from VNF |