| commit | 9a51e07a2164c9be42d9d329559f4d2081b8f3fc | [log] [tgz] |
|---|---|---|
| author | mpriyank <priyank.maheshwari@est.tech> | Thu Sep 22 10:25:37 2022 +0100 |
| committer | mpriyank <priyank.maheshwari@est.tech> | Fri Oct 14 15:01:17 2022 +0100 |
| tree | 82d48a450893a3dead06407c7af700ad3979c2ab | |
| parent | 736bf37d0369fd88154f228efa4d94dd37156486 [diff] |
[CPS] OOM updates for CPS Repos - CPS-Core : Added NCMP tag in properties and updated container image from 3.0.1 to 3.1.4 - Fixed env variable missing in cps-core - Added missing kafka topics(ncmp-events and ncmp-async-m2m) - NCMP-DMI-PLUGIN: update container image from 1.1.0 to 1.2.1 - CPS-TEMPORAL: update container image from 1.1.0 to 1.2.0 Issue-ID: CPS-1290 Issue-ID: CPS-1343 Change-Id: Id5b4b6cfac9ddabe2421300e37f10185cee71ed3 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.