VNFRQTS -Updated Chapter 8 appendix D

removed blank requirement R-77737 from appendix D
changed requirement R-nnnnn to R-53433 in appendix D
added additional requirements R-81725 and R-38474 from chapter 4 to appendix D

Change-Id: I35a9ef2ff433879230f5f061c3ec3eaaccc7183b
Issue-ID: VNFRQTS-156
Signed-off-by: steven stark <ss820f@att.com>

diff --git a/docs/Chapter8.rst b/docs/Chapter8.rst
index e2a9bf1..d9b6ea1 100644 (file)
--- a/docs/Chapter8.rst
+++ b/docs/Chapter8.rst
@@ -910,7 +910,11 @@ R-62170: The VNF **MUST** over-ride any default values for configurable paramete
 
 R-41994: The VNF **MUST**, if not using the NCSP’s IDAM API, comply with "No Self-Signed Certificates" policy. Self-signed certificates must be used for encryption only, using specified and approved encryption protocols such as LS 1.1 or higher or equivalent security protocols such as IPSec, AES.
 
-R-nnnnn: The VNF MUST have a corresponding environment file for a Cinder Volume Module.
+R-38474: The VNF **MUST** have a corresponding environment file for a Base Module.
+
+R-81725: The VNF **MUST** have a corresponding environment file for an Incremental Module.
+
+R-53433: The VNF **MUST** have a corresponding environment file for a Cinder Volume Module.
 
 R-84160: The VNF **MUST** have security logging for VNFs and their OSs be active from initialization. Audit logging includes automatic routines to maintain activity records and cleanup programs to ensure the integrity of the audit/logging systems.
 
@@ -1020,8 +1024,6 @@ R-69565: The VNF Package **MUST** include documentation describing VNF Managemen
 
 R-92571: The VNF **MUST** provide operational instrumentation such as logging, so as to facilitate quick resolution of issues with the VNF to provide service continuity.
 
-R-77737: The VNF **MUST**
-
 R-29488: The VNF **MUST** implement the protocol operation: **get-config(source, filter)** - Retrieve a (filtered subset of a) configuration from the configuration datastore source.
 
 R-03070: The VNF **MUST**, by ONAP Policy, provide the ONAP addresses as data destinations for each VNF, and may be changed by Policy while the VNF is in operation. We expect the VNF to be capable of redirecting traffic to changed destinations with no loss of data, for example from one REST URL to another, or from one TCP host and port to another.