diff options
author | 2018-08-29 16:02:42 +0100 | |
---|---|---|
committer | 2018-08-29 16:02:42 +0100 | |
commit | a04f16e618d2a34b90ca8c736861a915a6f341e7 (patch) | |
tree | cf3989144e333b046ca4bac7265077be360808d7 /docs/Chapter7 | |
parent | ec2f263e009b1463dc6df01b8e45ae94b2609829 (diff) |
Remove R-51910, add R-10623
Change R-51910 to paragraph text
Change Google protocol buffer text to requirement
Updated needs.json
Issue-ID: VNFRQTS-207
Change-Id: Id73872f3be1c59d36251fc9270caa7cea3bd183a
Signed-off-by: joquiltyL <john.quilty@ericsson.com>
Diffstat (limited to 'docs/Chapter7')
-rwxr-xr-x | docs/Chapter7/Monitoring-And-Management.rst | 72 |
1 files changed, 35 insertions, 37 deletions
diff --git a/docs/Chapter7/Monitoring-And-Management.rst b/docs/Chapter7/Monitoring-And-Management.rst index 32a486d..c40eea2 100755 --- a/docs/Chapter7/Monitoring-And-Management.rst +++ b/docs/Chapter7/Monitoring-And-Management.rst @@ -357,14 +357,9 @@ VNF telemetry via standardized interface ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -.. req:: - :id: R-51910 - :target: XNF - :keyword: MUST - - The xNF **MUST** provide all telemetry (e.g., fault event - records, syslog records, performance records etc.) to ONAP using the - model, format and mechanisms described in this section. +All VNF telemetry data (e.g. fault event records, syslog records, +performance records, etc.) need to be delivered to ONAP using the +standardized models and interfaces described in this section. Encoding and Serialization ~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -416,36 +411,39 @@ Buffers (GPB). KV-GPB/GPB ~~~~~~~~~~~~~~~~~~ -Telemetry data delivered using Google Protocol Buffers v3 (proto3) -can be serialized in one of the following methods: - -* Key-value Google Protocol Buffers (KV-GPB) is also known as - self-describing GPB: - - * keys are strings that correspond to the path of the system - resources for the VNF 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 a VNF resource. - -* VNF providers must supply valid KV-GPB definition file(s) to allow - for the decoding of all KV-GPB encoded telemetry messages. - -* Native Google Protocol Buffers (GPB) is also known as compact GPB: - - * keys are represented as integers pointing to the system resources for - the VNF 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 a VNF resource. - -* Google Protocol Buffers (GPB) requires metadata in the form of .proto - files. VNF providers must supply the necessary GPB .proto files such that - GPB telemetry messages can be encoded and decoded. - -* In the future, we may consider support for other types of - encoding & serialization methods based on industry demand. +.. req:: + :id: R-10623 + :target: XNF + :keyword: MUST + :introduced: casablanca + Telemetry data delivered using Google Protocol Buffers v3 (proto3) + **MUST** be serialized in one of the following methods: + + * Key-value Google Protocol Buffers (KV-GPB) is also known as + self-describing GPB: + + * keys are strings that correspond to the path of the system + resources for the VNF 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 a VNF resource. + * VNF providers must supply valid KV-GPB definition file(s) to allow + for the decoding of all KV-GPB encoded telemetry messages. + + * Native Google Protocol Buffers (GPB) is also known as compact GPB: + + * keys are represented as integers pointing to the system resources for + the VNF 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 a VNF resource. + * Google Protocol Buffers (GPB) requires metadata in the form of .proto + files. VNF providers must supply the necessary GPB .proto files such that + GPB telemetry messages can be encoded and decoded. + +In the future, we may consider support for other types of +encoding & serialization methods based on industry demand. Reporting Frequency ~~~~~~~~~~~~~~~~~~~~~ |