| commit | 1734ba109dc0a0aa50a64d7029f4cad30bcbb3c6 | [log] [tgz] |
|---|---|---|
| author | mpriyank <priyank.maheshwari@est.tech> | Tue May 14 16:24:29 2024 +0100 |
| committer | mpriyank <priyank.maheshwari@est.tech> | Fri May 17 09:41:40 2024 +0100 |
| tree | 588016692b735be3882c3582b31f8926896323e2 | |
| parent | 65656b526ecb6bcb8f6113ecaee2194d3235ac6c [diff] |
[CPS] New Delhi release changes - cps-and-ncmp image updated to use tag 3.4.9 version - ncmp-dmi-plugin image updated to use tag 1.5.0 version - fixed the labels in application-helm file as it was introduced as part of java17 upgrade in the app. Issue-ID: CPS-2222 , CPS-2225 Change-Id: I9bdda445f8e4a0a97cddb15edb9cdafd15c86e45 Signed-off-by: mpriyank <priyank.maheshwari@est.tech>
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.