VNF Requirements PM Meta Data

Issue-ID: VNFRQTS-523

Change-Id: I83af91039a1a0893aef6f57b1fff35510a624c59
Signed-off-by: marge.hillis <marge.hillis@nokia.com>

1 files changed, 15 insertions, 1 deletions

diff --git a/docs/Chapter7/VNF-On-boarding-and-package-management.rst b/docs/Chapter7/VNF-On-boarding-and-package-management.rst
index 26ba9d5..e725d17 100755
--- a/docs/Chapter7/VNF-On-boarding-and-package-management.rst
+++ b/docs/Chapter7/VNF-On-boarding-and-package-management.rst
@@ -1,4 +1,4 @@
-.. Modifications Copyright © 2017-2018 AT&T Intellectual Property.
+.. Modifications Copyright © 2017-2018 AT&T Intellectual Property.
 
 .. Licensed under the Creative Commons License, Attribution 4.0 Intl.
    (the "License"); you may not use this documentation except in compliance
@@ -151,6 +151,20 @@ Resource Description
    supported by that NF at onboarding time and the Meta Data must follow
    the VES Event Listener and VES Event Registration Specifications.
 
+.. req::
+   :id: R-816745
+   :target: VNF or PNF PROVIDER
+   :keyword: MUST
+   :introduced: dublin
+   :impacts: DCAE,Documentation,Integration,SDC
+   :validation_mode: static
+
+   The VNF or PNF PROVIDER *MUST* provide the Service Provider with
+   PM Meta Data (PM Dictionary) to support the analysis of PM events delivered
+   to DCAE. The PM Dictionary is to be provided as a separate YAML artifact at
+   onboarding and must follow the VES Event Listener Specification and VES
+   Event Registration Specification which contain the format and content
+   required.
 
 Resource Configuration
 ^^^^^^^^^^^^^^^^^^^^^^^