| commit | 2d7874249e98871ed13231f3bed8486c1e65e3aa | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Tue Feb 14 17:27:42 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Feb 17 09:47:09 2023 +0100 |
| tree | b8c9af76a8121a299c7faa34e5c45bce4e60dad8 | |
| parent | 63ec99de7215eb043093dd0e8ec90d8c33aa6590 [diff] |
[DCAE][HVVES] Make HVVES collector SM compatible As we have problems to send binary data to the HVVES collector the support for service appProtocol attribute is required to fix the hvves service protocol to "tcp" and to disable the port for sidecar usage Issue-ID: OOM-3076 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Ied6ca4d4d8cd088c8ec0e0ee13068dfdbfb38461
The ONAP Operations Manager (OOM) is responsible for life-cycle management of the ONAP platform itself; components such as SO, SDNC, etc.
It is not responsible for the management of services, VNFs or infrastructure instantiated by ONAP or used by ONAP to host such services or VNFs.
OOM uses the open-source Kubernetes container management system as a means to manage the containers that compose ONAP where the containers are hosted either directly on bare-metal servers or on VMs hosted by a 3rd party management system.
OOM ensures that ONAP is easily deployable and maintainable throughout its life cycle while using hardware resources efficiently.
Full documentation is available in ONAP documentation in operations and administration guides.
Please see contributing file to learn on how to contribute
All issues should be filled in ONAP Jira.