VNFRQTS - Changes to fix doc warnings

[vnfrqts/requirements.git] / docs / Chapter7.rst

diff --git a/docs/Chapter7.rst b/docs/Chapter7.rst
index efe5d89..9eb9d35 100644 (file)
--- a/docs/Chapter7.rst
+++ b/docs/Chapter7.rst
@@ -3,8 +3,8 @@
 .. Copyright 2017 AT&T Intellectual Property.  All rights reserved.
 
 
-**ONAP Management Requirements**
-=====================================
+ONAP Management Requirements
+============================
 
 The ONAP platform is the part of the larger Network Function
 Virtualization/Software Defined Network (NFV/SDN) ecosystem that
@@ -152,7 +152,8 @@ Configuration Management via Chef
 * R-18525 The xNF provider **MUST** provide a JSON file for each
   supported action for the xNF.  The JSON file must contain key value
   pairs with all relevant values populated with sample data that illustrates
-  its usage. The fields and their description are defined in Tables A1 and A2 in the Appendix.
+  its usage. The fields and their description are defined in Tables A1
+  and A2 in the Appendix.
 
  Note: Chef support in ONAP is not currently available and planned for 4Q 2017.
 
@@ -164,7 +165,8 @@ Configuration Management via Ansible
 * R-16777 The xNF provider **MUST** provide a JSON file for each
   supported action for the xNF.  The JSON file must contain key value
   pairs with all relevant values populated with sample data that illustrates
-  its usage. The fields and their description are defined in Table B1 in the Appendix.
+  its usage. The fields and their description are defined in Table B1
+  in the Appendix.
 
 * R-46567 The xNF Package **MUST** include configuration scripts
   for boot sequence and configuration.
@@ -313,7 +315,7 @@ Licensing Requirements
   onboarding the xNF into the ONAP environment and automating processes
   for putting the licenses into use and managing the full lifecycle of
   the licenses. The details of this license model are described in
-  Tables C1 to C8 in the Appendix. Note: License metadata support in 
+  Tables C1 to C8 in the Appendix. Note: License metadata support in
   ONAP is not currently available and planned for 1Q 2018.
 
 Configuration Management
@@ -486,17 +488,17 @@ must be supported.
 * R-56218 The VNF **MUST** support ONAP Controller’s Migrate command that
   moves container (VM) from a live Physical Server / Compute Node to
   another live Physical Server / Compute Node.
-  
+
 NOTE: Container migrations MUST be transparent to the VNF and no more
 intrusive than a stop, followed by some down time for the migration to
 be performed from one Compute Node / Physical Server to another, followed
-by a start of the same VM with same configuration on the new Compute 
+by a start of the same VM with same configuration on the new Compute
 Node / Physical Server.
-  
+
 * R-38001 The VNF MUST support ONAP Controller’s **Rebuild** command.
 * R-76901 VNF MUST support a container rebuild mechanism based on existing
   image (e.g. Glance image in Openstack environment) or a snapshot.
-  
+
 HealthCheck and Failure Related Commands
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -644,8 +646,6 @@ NETCONF Server Requirements
   [RFC6243].
 * R-59610 The xNF **MUST** implement the data model discovery and
   download as defined in [RFC6022].
-* R-87662 The xNF **SHOULD** implement the NETCONF Event Notifications
-  [RFC5277].
 * R-93443 The xNF **MUST** define all data models in YANG [RFC6020],
   and the mapping to NETCONF shall follow the rules defined in this RFC.
 * R-26115 The xNF **MUST** follow the data model upgrade rules defined
@@ -694,8 +694,6 @@ NETCONF Server Requirements
   the supplied YANG code and associated NETCONF servers.
 * R-60656 The xNF **MUST** support sub tree filtering.
 * R-80898 The xNF **MUST** support heartbeat via a <get> with null filter.
-* R-06617 The xNF **MUST** support get-schema (ietf-netconf-monitoring)
-  to pull YANG model over session.
 * R-25238 The xNF PACKAGE **MUST** validated YANG code using the open
   source pyang [1]_ program using the following commands:
 
@@ -719,8 +717,6 @@ conform, and those where applicable, that suppliers need to use.
 * R-28545 The xNF **MUST** conform its YANG model to RFC 6060,
   “YANG - A Data Modeling Language for the Network Configuration
   Protocol (NETCONF)”
-* R-29967 The xNF **MUST** conform its YANG model to RFC 6022,
-  “YANG module for NETCONF monitoring”.
 * R-22700 The xNF **MUST** conform its YANG model to RFC 6470,
   “NETCONF Base Notifications”.
 * R-10353 The xNF **MUST** conform its YANG model to RFC 6244,
@@ -740,7 +736,8 @@ conform, and those where applicable, that suppliers need to use.
 * R-87564 The xNF **SHOULD** conform its YANG model to RFC 7317,
   “A YANG Data Model for System Management”.
 * R-24269 The xNF **SHOULD** conform its YANG model to RFC 7407,
-  “A YANG Data Model for SNMP Configuration”.
+  “A YANG Data Model for SNMP Configuration”, if Netconf used to
+  configure SNMP engine.
 
 The NETCONF server interface shall fully conform to the following
 NETCONF RFCs.
@@ -1867,9 +1864,6 @@ Security
    This option is not currently supported in ONAP and it is currently
    under consideration.
 
-.. [6]
-   https://wiki.opnfv.org/display/PROJ/VNF+Event+Stream
-
 .. |image0| image:: Data_Model_For_Event_Records.png
       :width: 7in
       :height: 8in