commit | 7373ad2c2660cd42a997d3908e2f4fb8dac55fca | [log] [tgz] |
---|---|---|
author | efiacor <fiachra.corcoran@est.tech> | Wed Jan 04 10:56:27 2023 +0000 |
committer | efiacor <fiachra.corcoran@est.tech> | Wed Jan 04 10:56:34 2023 +0000 |
tree | 5e01c56da6b261d308e1fd7938e08d708981c4a6 | |
parent | e3529a28a1fa8b48b1a8d013be01cfdcb9bb905e [diff] |
[AAI-ML] Move aai-modelloader to use strimzi kafka user template Use common kafka template for the user Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: Id4f58800856c4d8caa45bb1bd4f8df30263fb91b Issue-ID: DMAAP-1852
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.