| commit | b02ca62bfca08104683f0ff0781fc759158952b9 | [log] [tgz] |
|---|---|---|
| author | Jack Lucas <jflos@sonoris.net> | Sun Dec 03 19:13:31 2023 -0500 |
| committer | Jack Lucas <jflos@sonoris.net> | Thu Feb 15 10:39:59 2024 -0500 |
| tree | 2141fb3f684aac2987a49c5dacf8ef9964d2b5f5 | |
| parent | ad8e7c7a9b5da7c348d9c1c6a3eda61f49301150 [diff] |
[DCAEGEN2] Update snmptrap-collector image Update snmptrap-collector to 2.0.8. Fix outdated configuration library. Add "protocol" to common.containerPorts. Update dcae-snmptrap-collector chart version to 13.0.1. Update dcaegen2-services chart version to 13.0.2. Issue-ID: DCAEGEN2-3409 Issue-ID: OOM-3251 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: If0ca26e07fdbbebafb442dc0ead3a14d4ea0d4a6
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.