| commit | 2c5cff362628393c5803ac9d68b5590c3ed21434 | [log] [tgz] |
|---|---|---|
| author | Jack Lucas <jflos@sonoris.net> | Fri Oct 13 10:53:42 2023 -0400 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Oct 23 19:05:30 2023 +0000 |
| tree | efe417a74413c958869ee35638a287c72e6f91ce | |
| parent | 2ff7f1c46d3e9a6b05e830ac4bc8f56c230b22aa [diff] |
[DCAEGEN2] Update base image for healthcheck Update healthcheck container to version 2.4.1 (Updates nodejs base image to 18.18.0) Issue-ID: DCAEGEN2-3400 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I27e78fdcab44a4c25acb92320f1aa9a40a0eeef7
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.