VNFRQTS - Add VNF package meta-data in VNFRQTS-580

Change-Id: Ibd08ef66622f6c94cc6b002c8f45379afcd69f54
Issue-ID: VNFRQTS-580
Signed-off-by: Hagop Bozawglanian <hagop.bozawglanian@att.com>

diff --git a/docs/Chapter5/Tosca.rst b/docs/Chapter5/Tosca.rst
index ec664d2..d3b2efc 100644 (file)
--- a/docs/Chapter5/Tosca.rst
+++ b/docs/Chapter5/Tosca.rst
@@ -242,7 +242,7 @@ VNF Package Contents
 
 .. req::
     :id: R-57019
-    :target: PNF CSAR PACKAGE  
+    :target: PNF CSAR PACKAGE
     :keyword: MUST
     :introduced: dublin
 
@@ -258,6 +258,25 @@ VNF Package Contents
 
       - pnfd_archive_version
 
+.. req::
+    :id: R-795126
+    :target: VNF CSAR PACKAGE
+    :keyword: MUST
+    :introduced: dublin
+
+    The VNF TOSCA CSAR package Manifest file **MUST** start with the VNF
+    package metadata in the form of a name-value pairs. Each pair shall appear
+    on a different line. The name is specified as following:
+
+      - vnf_provider_id
+
+      - vnf_product_name
+
+      - vnf_release_date_time
+
+      - vnf_package_version
+
+
 VNF or PNF Package Authenticity
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~