| commit | 2c1ba293ccef7dcaf09c46f5b0a8a36245238389 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Wed Jan 10 22:20:05 2024 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Jan 11 13:24:47 2024 +0100 |
| tree | 12c6ad43ce4c89c494ea5c4f198a2b9ddbdb8dd3 | |
| parent | c8ef023537910038ef05ce84337a35e429bfc931 [diff] |
[MARIADB][SO] Connect MariaDB Galera via master node To avoid "lock" situations all clients of the mariadb-galera cluster should use the "primary" service, which connects to the master node. This service is provided by the mariadb-operator. Additionally for SO the bugfix for "local" DB configuration is fixed. Additionally missing readiness checks added to so-cnfm-lcm and so-etsi-nfvo-ns-lcm to wait for the DB job to complete Issue-ID: OOM-3261 Issue-ID: OOM-2697 Change-Id: I3d44f8b6d84d112c0271bfccebc4fa533c4e6aff Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
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.