JeanQuilbeufHuawei / draft-collected-data-manifest

1 stars 1 forks source link

Clarifications on generation of Data Collection Manifest #29

Closed idomingu closed 2 years ago

idomingu commented 2 years ago

Hello,

While reviewing the Data Collection Manifest (Section 4) I started to have doubts regarding who generates this manifest.

I recall that it was previously discussed whether the data collection manifest can be retrieved directly from devices or that it is collector who generates the data manifest based on external information (e.g., from a controller). This is also remarked in the draft as shown in the following fragment:

https://github.com/JeanQuilbeufHuawei/draft-collected-data-manifest/blob/0212a49beed0a0ef0c9046980c7da107269fa18f/draft-claise-opsawg-collected-data-manifest-03.txt#L875-L879

This brings me to YANG-Push/openconfig-telemetry and configured/persistent subscriptions (aka dial-out). If we assume that the collector can retrieve the data collection manifest from the device, why don't we just collect data from YANG-Push/openconfig-telemetry? What does the data collection manifest provide that the aforementioned modules do not?

I'm sorry but right now I'm very confused with the current approach. I think a diagram with the interactions between device, collector, controller (if needed), and database, would help a lot to clarify the role of the collector.

Many thanks!, Nacho.