| commit | 3422fe96531c951a3209ac3c2c6a3e8308559812 | [log] [tgz] |
|---|---|---|
| author | efiacor <fiachra.corcoran@est.tech> | Tue Jul 12 13:19:53 2022 +0100 |
| committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Tue Nov 22 14:11:42 2022 +0000 |
| tree | 9bbe9bafa53fa5e7928015f80a83091302ead06b | |
| parent | 3502e73a2762fc50f9ba3ae5d65a3efe5f05bead [diff] |
[SDC] Add strimzi kafka setup on sdc-be Add SDC KafkaTopics and KafkaUser Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: I78542539567d2e3b67376b154ad069df3d1dad55 Issue-ID: DMAAP-1744
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.