| commit | 23b51ea99e9a6410de0d913b4a3a6140f4e5ef03 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Jul 08 09:09:00 2022 +0200 |
| committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Fri Jul 08 12:02:49 2022 +0000 |
| tree | 6636f699fb6d694d1bd62b12bcfc3edb60867cd7 | |
| parent | d32b273cbd16058d4d22448766c06c68e38e90af [diff] |
[COMMON][MARIABD] Fix MariaDB ServiceMesh compatibility Update the pod annotations to exclude the cluster communication ports from the SM sidecars. Fix mysql protocol setup fodddr istio and update mariadb-init job to support istio sidecar communication. This is separated from a patch for CDS SM compatibility Issue-ID: OOM-2820 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I9e839e019c948614fea7d4b3b5930270f7e7a7c6
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.