diff options
| author |   Piotr Jaszczyk <piotr.jaszczyk@nokia.com> | 2018-10-01 07:54:26 +0200 |
|---|---|---|
| committer | Piotr Jaszczyk <piotr.jaszczyk@nokia.com> | 2018-10-01 08:16:05 +0200 |
| commit | fd44b433ac9825be6cc654e8a566f9d0bfc70166 (patch) | |
| tree | f720c9d891bc43ee1abbb4662a72d1b942f31d47 /README.md | |
| parent | 069dcc194fd049e1c52e60d03ce2a9c0553289a7 (diff) | |
HV-VES Domain update
Change domain name. In this project this yields following changes:
* Comment change in VesEvent proto
* Updated measurements proto (kept as documentation only, ie. not used
in the collector)
* Update name in test scenarios for unit and component scope
Change-Id: I719077b5fcb642c067d25b7aa174a2e629404689
Issue-ID: DCAEGEN2-847
Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -24,7 +24,7 @@ For more details on the rationale, please read a [high-level feature description * It uses a PROTO representation of the VES Common Header * The PROTO files tend to use most encoding effective types defined by GPB to cover Common Header fields. * It makes routing decisions based mostly on the content of the "Domain" parameter - * It allows to embed Payload of different types (by default hvMeas domain is included) + * It allows to embed Payload of different types (by default PERF3GPP domain is included) * VES-HV publishes events on DMaaP-Kafka bus, using native Kafka Interfaces * Analytics applications impacts * An analytics application operating on high-volume data needs to be prepared to read directly from Kafka @@ -35,7 +35,7 @@ For more details on the rationale, please read a [high-level feature description VES-HV was designed to allow for extendability - by adding new domain-specific PROTO files. -The PROTO file, which contains the VES CommonHeader, comes with a binary-type Payload parameter, where domain-specific data shall be placed. Domain-specific data are encoded as well with GPB, and they do require a domain-specific PROTO file to decode the data. This domain-specific PROTO needs to be shared with analytics applications - VES-HV is not analyzing domain-specific data. In order to support the RT-PM use-case, VES-HV includes a "hvMeas" domain PROTO file, as within this domain, the high volume data is expected to be reported to VES-HV collector. +The PROTO file, which contains the VES CommonHeader, comes with a binary-type Payload parameter, where domain-specific data shall be placed. Domain-specific data are encoded as well with GPB, and they do require a domain-specific PROTO file to decode the data. This domain-specific PROTO needs to be shared with analytics applications - VES-HV is not analyzing domain-specific data. In order to support the RT-PM use-case, VES-HV includes a "PERF3GPP" domain PROTO file, as within this domain, the high volume data is expected to be reported to VES-HV collector. Still, there are no limitations to define additional domains, based on existing VES domains (like Fault, Heartbeat) or completely new domains. New domains can be added "when needed". In case of new domains, it is necessary to extend the Common Header PROTO "Domain" enumeration with new values covering this new domain(s). |