| commit | b66260d1edc2e2a7decf349e0735279f9e87bb06 | [log] [tgz] |
|---|---|---|
| author | efiacor <fiachra.corcoran@est.tech> | Mon Sep 26 10:28:43 2022 +0100 |
| committer | efiacor <fiachra.corcoran@est.tech> | Thu Sep 29 16:19:51 2022 +0100 |
| tree | c3e0c2afc3d50da7ce3c96348d56a2021d7298b7 | |
| parent | 6fc48a9d8a0f186e1fb9c5b94d52927d3714425d [diff] |
[DMAAP] Update Kohn versions Bump image version for kohn release Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: I34e6714797e88c0cf6131022696b537aa36ff505 Issue-ID: DMAAP-1769
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.