| commit | 709ea3f8ba1fc234548d13f818c7ec67e50a9ea8 | [log] [tgz] |
|---|---|---|
| author | mpriyank <priyank.maheshwari@est.tech> | Fri Jan 13 10:05:46 2023 +0000 |
| committer | mpriyank <priyank.maheshwari@est.tech> | Fri Jan 13 11:37:45 2023 +0000 |
| tree | c1d776b019e66a1802a7da8789efc66259a7160d | |
| parent | f6bda71b5f76434b09004c5adfc8dab8cf17c1c2 [diff] |
[CPS] Add new Topic for CPS-NCMP AVC Events - Adding new topic dmi-cm-events - added user and topic parameters - changed one of the unreachable link for honolulu ( not relevant for CPS but had to do inorder to make the build pass ) Issue-ID: CPS-1385 Signed-off-by: JosephKeenan <joseph.keenan@est.tech> Change-Id: I0037ae727f9f06c3b28a9331c7eb9fd7037f501d 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.