| commit | 72caf09f07b4530e1bb34be348c4b845c9d0bfde | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Dec 14 13:37:39 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Dec 14 19:13:16 2023 +0100 |
| tree | 98536c5c2282db60baec7f09d35d716438849f27 | |
| parent | 8cb16a6b59d8501808d62bb558f76f161b53d3e9 [diff] |
[MARIADB] Fix db/user creation in operator Fix the resource names for db/user in mariadb template for the mariadb-operator and corrected the resource notation to work with ArgoCD Added missing "user" entry for mariadb-galera in NBI and Etsicatalog values.yaml and missing dbName in SDNC Issue-ID: OOM-3255 Issue-ID: OOM-3257 Change-Id: Ib11c20ce99bdd7f29415611d2c0795466415eea6 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.