| commit | 6910bbe1e3f2e44e5e100b8fec34a6da8b8eb231 | [log] [tgz] |
|---|---|---|
| author | efiacor <fiachra.corcoran@est.tech> | Fri Mar 03 14:53:16 2023 +0000 |
| committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Fri Mar 10 12:25:42 2023 +0000 |
| tree | d0146b7ed4d448cec81f8356ba9c83110977dda2 | |
| parent | 9ff7ee73b1f5dd0adb1ae9d3b5ae6b324e12dad5 [diff] |
[POLICY-PPNT] Move policy-clamp-ppnt use case to use strimzi kafka Move acm to use strimzi common templates Enabled kafka by default for acm ppnts Update relevant config params Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: Ia23970e59f4ddaa83a07d224293b0155e28d0ab2 Issue-ID: DMAAP-1857
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.