diff options
| -rwxr-xr-x | docs/Chapter7/VNF-On-boarding-and-package-management.rst | 16 | ||||
| -rw-r--r-- | docs/Chapter8/VES_Registration_3_2.rst | 2 |
2 files changed, 11 insertions, 7 deletions
diff --git a/docs/Chapter7/VNF-On-boarding-and-package-management.rst b/docs/Chapter7/VNF-On-boarding-and-package-management.rst index e3f01c6..2c57a1e 100755 --- a/docs/Chapter7/VNF-On-boarding-and-package-management.rst +++ b/docs/Chapter7/VNF-On-boarding-and-package-management.rst @@ -147,17 +147,19 @@ Resource Description .. req:: :id: R-025941 - :target: VNF PROVIDER + :target: VNF or PNF PROVIDER :keyword: MUST - :introduced: dublin + :updated: frankfurt :impacts: DCAE,Documentation,Integration,SDC :validation_mode: static - The VNF or PNF PROVIDER **MUST** provide FM Meta Data to support the - analysis of fault events delivered to DCAE. The Meta Data must be - included in the VES Registration YAML file with each fault event - supported by that NF at onboarding time and the Meta Data must follow - the VES Event Listener and VES Event Registration Specifications. + The VNF or PNF PROVIDER **MUST** provide :ref:`FM_meta_data` to support the + analysis of fault events delivered to DCAE. The metadata must be + included in the VES Registration YAML file for each fault event + supported by that VNF or PNF at onboarding time. The metadata must follow + the VES Event Listener Specifications for Fault domain and VES Event + Registration Specifications for YAML registration file format. + .. req:: :id: R-816745 diff --git a/docs/Chapter8/VES_Registration_3_2.rst b/docs/Chapter8/VES_Registration_3_2.rst index 09ad322..370a5ee 100644 --- a/docs/Chapter8/VES_Registration_3_2.rst +++ b/docs/Chapter8/VES_Registration_3_2.rst @@ -1551,6 +1551,8 @@ indent-style YAML formats vendorField2: A ... +.. _FM_meta_data: + FM Meta Data ~~~~~~~~~~~~~ |