diff options
author | Hagop Bozawglanian <hagop.bozawglanian@att.com> | 2019-05-28 20:06:20 +0000 |
---|---|---|
committer | Hagop Bozawglanian <hagop.bozawglanian@att.com> | 2019-05-28 22:15:43 +0000 |
commit | 6cef7fd987f90b02e3b472fe31a4393aa52a7df4 (patch) | |
tree | 3fe39e283ddb0d8e881116cca823799834718bce /docs/Chapter7 | |
parent | e9e154435369900f4a38ecfe3b94bfe468ae3a47 (diff) |
VNFRQTS - fixing links and formatting in VES
Issue-ID: VNFRQTS-644
Signed-off-by: Hagop Bozawglanian <hagop.bozawglanian@att.com>
Change-Id: I60a2619f5893db17cb8720f8aeb220e51c9c5981
Signed-off-by: Hagop Bozawglanian <hagop.bozawglanian@att.com>
Diffstat (limited to 'docs/Chapter7')
-rwxr-xr-x | docs/Chapter7/Monitoring-And-Management.rst | 6 | ||||
-rwxr-xr-x | docs/Chapter7/VNF-On-boarding-and-package-management.rst | 4 |
2 files changed, 5 insertions, 5 deletions
diff --git a/docs/Chapter7/Monitoring-And-Management.rst b/docs/Chapter7/Monitoring-And-Management.rst index da2a2bc..24ad489 100755 --- a/docs/Chapter7/Monitoring-And-Management.rst +++ b/docs/Chapter7/Monitoring-And-Management.rst @@ -319,7 +319,7 @@ Data Structure Specification of the Event Record :updated: dublin The VNF or PNF provider **MUST** provide a YAML file formatted in adherence with - the :doc:`VES Event Registration specification <../../../../vnfsdk/model.git/docs/files/VESEventRegistration_3_0>` + the :ref:`VES Event Registration specification <ves_event_registration_3_2>` that defines the following information for each event produced by the VNF: * ``eventName`` @@ -339,7 +339,7 @@ Data Structure Specification of the Event Record The VNF or PNF provider **MUST** indicate specific conditions that may arise, and recommend actions that may be taken at specific thresholds, or if specific conditions repeat within a specified time interval, using the semantics and - syntax described by the :doc:`VES Event Registration specification <../../../../vnfsdk/model.git/docs/files/VESEventRegistration_3_0>`. + syntax described by the :ref:`VES Event Registration specification <ves_event_registration_3_2>`. **NOTE:** The Service Provider may override VNF or PNF provider Event Registrations using the ONAP SDC Design Studio to finalizes Service @@ -361,7 +361,7 @@ These changes may modify any of the following: The events produced by the VNF or PNF **MUST** must be compliant with the common event format defined in the - :doc:`VES Event Listener<../../../../vnfsdk/model.git/docs/files/VESEventListener_7_0_1>` + :ref:`VES Event Listener<ves_event_listener_7_1>` specification. .. req:: diff --git a/docs/Chapter7/VNF-On-boarding-and-package-management.rst b/docs/Chapter7/VNF-On-boarding-and-package-management.rst index dc2800a..f170f30 100755 --- a/docs/Chapter7/VNF-On-boarding-and-package-management.rst +++ b/docs/Chapter7/VNF-On-boarding-and-package-management.rst @@ -132,7 +132,7 @@ Resource Description :updated: dublin :validation_mode: static - The VNF or PNF package **MUST** provide :doc:`VES Event Registration <../../../../vnfsdk/model.git/docs/files/VESEventRegistration_3_0>` + The VNF or PNF package **MUST** provide :ref:`VES Event Registration <ves_event_registration_3_2>` for all VES events provided by that VNF or PNF. .. req:: @@ -332,7 +332,7 @@ Resource Control Loop The VNF or PNF Package **MUST** include documentation which must include all events (fault, measurement for VNF or PNF Scaling, Syslogs, State Change - and Mobile Flow), that need to be collected at each VM, VNFC (defined in `VNF Guidelines <https://onap.readthedocs.io/en/latest/submodules/vnfrqts/guidelines.git/docs/vnf_guidelines/vnf_guidelines.html>`__ ) and for the overall VNF or PNF. + and Mobile Flow), that need to be collected at each VM, VNFC (defined in `VNF Guidelines <https://onap.readthedocs.io/en/latest/submodules/vnfrqts/guidelines.git/docs/vnf_guidelines.html>`__ ) and for the overall VNF or PNF. .. req:: |