From 80801137ba1fc23baddce99242ae67e1c71068fb Mon Sep 17 00:00:00 2001 From: "Lovett, Trevor (tl2972)" Date: Fri, 21 Sep 2018 09:03:24 -0500 Subject: VNFRQTS - Fixing typos in Monitoring Change-Id: Ie5d332a8d04961aeacd5d9ec326141d33eaf02ed Issue-ID: VNFRQTS-446 Signed-off-by: Lovett, Trevor (tl2972) --- docs/Chapter7/Monitoring-And-Management.rst | 33 +++++++++++++++-------------- 1 file changed, 17 insertions(+), 16 deletions(-) (limited to 'docs/Chapter7/Monitoring-And-Management.rst') diff --git a/docs/Chapter7/Monitoring-And-Management.rst b/docs/Chapter7/Monitoring-And-Management.rst index f4b5fb2..f3043a7 100755 --- a/docs/Chapter7/Monitoring-And-Management.rst +++ b/docs/Chapter7/Monitoring-And-Management.rst @@ -132,7 +132,7 @@ sender and other identifying characteristics related to the domain and event. :keyword: MUST The VNF **MUST** produce VES events that include the following mandatory - fields in the common event header + fields in the common event header. * ``domain`` - the event domain enumeration * ``eventId`` - the event key unique to the event source @@ -454,7 +454,7 @@ xNF Telemetry using Google Protocol Buffers The xNF **MAY** leverage the Google Protocol Buffers (GPB) delivery model depicted in Figure 3 to support real-time performance management (PM) data. In this model the VES events are streamed as binary-encoded GBPs over via - TCP sockets + TCP sockets. |image2| @@ -570,14 +570,15 @@ Google Protocol Buffers (GPB) :validation_mode: in_service The xNF, when leveraging Google Protocol Buffers for events, **MUST** - serialize the events using native Google Protocol Buffers (GPB) where: - - * keys are represented as integers pointing to the system resources for - the xNF being monitored - * values correspond to integers or strings that identify the operational - state of the VNF resource, such a statistics counters and the state of - an xNF resource. - * required Google Protocol Buffers (GPB) metadata is provided in the + serialize the events using native Google Protocol Buffers (GPB) according + to the following guidelines: + + * The keys are represented as integers pointing to the system resources + for the xNF being monitored + * The values correspond to integers or strings that identify the + operational state of the VNF resource, such a statistics counters and + the state of an xNF resource. + * The required Google Protocol Buffers (GPB) metadata is provided in the form of .proto files. .. req:: @@ -587,15 +588,15 @@ Google Protocol Buffers (GPB) :introduced: casablanca :validation_mode: static - The xNF providers **MUST** provide to the Service Provider the additional - following artifacts to support the delivery of high-volume xNF telemetry to - DCAE via GPB over TLS/TCP: + The xNF providers **MUST** provide the Service Provider the following + artifacts to support the delivery of high-volume xNF telemetry to + DCAE via GPB over TLS/TCP: - * a valid VES Event .proto definition file, to be used validate and + * A valid VES Event .proto definition file, to be used validate and decode an event - * a valid high volume measurement .proto definition file, to be used for + * A valid high volume measurement .proto definition file, to be used for processing high volume events - * a supporting PM content metadata file to be used by analytics + * A supporting PM content metadata file to be used by analytics applications to process high volume measurement events Reporting Frequency -- cgit 1.2.3-korg