summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorsteven stark <ss820f@att.com>2018-02-06 14:28:23 -0800
committersteven stark <ss820f@att.com>2018-02-06 14:28:23 -0800
commit521f92c433ba7b397250d1fb27db6cc1989e54e3 (patch)
tree1186e001883c8988c677d7691225f892698ad4a9
parentc391a5cfd4af29ded7311bcea9f1a9f6ab950b3e (diff)
VNFRQTS - update ref to seed doc
Update reference to seed document "VNF Guidelines for Network Cloud and ONAP" to proper ONAP reference modified Chapter7 Change-Id: I8e0cc1f08d14e977372a981f32f7f8a346a23fc9 Issue-ID: VNFRQTS-172 Signed-off-by: steven stark <ss820f@att.com>
-rw-r--r--docs/Chapter7.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Chapter7.rst b/docs/Chapter7.rst
index d0aed53..cf01bd1 100644
--- a/docs/Chapter7.rst
+++ b/docs/Chapter7.rst
@@ -79,7 +79,7 @@ and GS NFV IFA011 V0.3.0 (2015-10) - Network Functions Virtualization
- A unique identification string for the specific VNF, a description of the problem that caused the error, and steps or procedures to perform Root Cause Analysis and resolve the issue.
- All events, severity level (e.g., informational, warning, error) and descriptions including causes/fixes if applicable for the event.
- - All events (fault, measurement for VNF Scaling, Syslogs, State Change and Mobile Flow), that need to be collected at each VM, VNFC (defined in *VNF Guidelines for Network Cloud and ONAP*) and for the overall VNF.
+ - All events (fault, measurement for VNF Scaling, Syslogs, State Change and Mobile Flow), that need to be collected at each VM, VNFC (defined in `VNF Guidelines <http://onap.readthedocs.io/en/latest/submodules/vnfrqts/guidelines.git/docs/vnf_guidelines/vnf_guidelines.html#a-glossary>`__ ) and for the overall VNF.
* R-27711 The VNF provider **MUST** provide an XML file that contains a list of VNF error codes, descriptions of the error, and possible causes/corrective action.
* R-01478 The VNF Package **MUST** include documentation describing all parameters that are available to monitor the VNF after instantiation (includes all counters, OIDs, PM data, KPIs, etc.) that must be collected for reporting purposes. The documentation must include a list of: