| commit | bf4b2e5b9344764967319ae7ab378ee23adb6dc3 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Jan 22 16:21:27 2024 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Jan 22 16:26:07 2024 +0100 |
| tree | 5d66c863bbfdf9dad18436a384d5b332e6e84000 | |
| parent | 2ee6ad456a91061d64b859ba20108c7e3c556de3 [diff] |
[CDS] Support the external creation of the CDS DB Add the global.mariadbGalera section to allow the selection for a locally created DB or external DB Disable the mariadb-galera dependency, if no local DB is used. Issue-ID: OOM-3266 Change-Id: Ia0ec94e552681eede519010951cbf1c92da863c3 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.