| commit | 9f2a0a07f134c9f5346ae241bb24748068e4f6bd | [log] [tgz] |
|---|---|---|
| author | efiacor <fiachra.corcoran@est.tech> | Mon Feb 20 17:05:30 2023 +0000 |
| committer | efiacor <fiachra.corcoran@est.tech> | Tue Feb 21 17:21:26 2023 +0000 |
| tree | dc9049f38d9d0d63e4880281a91ad83c782fe1ba | |
| parent | 23f5499dad42a1147b4edbd6d7b6480895d985bc [diff] |
[CPS] Change cps-core/temporal to use strimzi templates CPS core and temporal will now use the custom strimzi kafka tmplates Signed-off-by: efiacor <fiachra.corcoran@est.tech> Change-Id: I3a25e036e3bc2315c335424f624ebf6d538994e2 Issue-ID: CPS-1503
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.