Hi
 I would like to start a discussion on the need to clarify some of the 
requirements for Monitoring and Management Requirements
This area is covered in chapter 7.4.5 in the VNF Provider part of the ONAP 
Documentation 
(http://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/Chapter7.html)

There are a few issues to be dealt with here.

Initially the whole chapter was one requirement
"R-51910 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." This is not a standalone requirement as 
it requires the whole chapter to provide context. What has happened in this is 
that almost all statements within the chapter that can be read as a requirement 
have been given a requirement tag themselves.
 Also this requirement is not testable as "all telemetry" is not defined, and 
the chapter doesn't cover needs of some types of telemetry. So this requirement 
needs to be re-worded or removed, and the remaining "sub-requirements" in the 
chapter need to be given Requirement Tags.

 Also the context of the chapter context is written on the assumption JSON 
(with/without AVRO) would be used for telemetry delivery. But at some stage a 
GPB was added as another telemetry delivery mechanism. It is now not clear 
whether VNF providers are required to provide JSON and GPB, or JSON or GPB. The 
scenarios for use of JSON and/or GPB need to be clarified.

 The chapter is written from the perspective of Event handling, as mentioned 
above it doesn't cover all telemetry types contrary to R-51910. For example the 
mechanism for the collection of information such as large counter files is not 
covered properly here.

Section 7.4.5.6. Addressing and Delivery Protocol also contains CM related 
requirements that belong to Chapter 7.3

Section 7.4.5.8. Security contains security requirements common to CM and 
Monitoring so probably should be in a new Chapter 7.5

Regards
    John

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to