commit | 4ee97a9f28fcb17b272e4e94931f9528afe797a7 | [log] [tgz] |
---|---|---|
author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Apr 29 13:01:14 2022 +0200 |
committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Mon May 09 09:01:04 2022 +0000 |
tree | f4c7903f84cad6c87e4e1a6105c739d187c29a83 | |
parent | 271560c6bc1e5ed027a7cc11683e6688c3bc56bf [diff] |
[CDS] Service mesh compatibility Patch on CDS charts dedicated to remove https and cert-related calls from all files. This ensure compatibility with patched AAI (IID: OOM-2670) and lays ground for service mesh use. Replaces https://gerrit.onap.org/r/c/oom/+/126099 Correction for CDS-Strimzi support in application properties Issue-ID: OOM-2824 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I522fe60ca748b7e5f731045dac8ca11b13ae2811
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.