| commit | b1a0103760fdee36c958210c73a1d774658238dc | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Tue Dec 05 13:51:26 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Tue Dec 05 13:54:24 2023 +0100 |
| tree | 84113c3cd2849a1ba55dd69be78d02e2359951d5 | |
| parent | 2ad6c16c56c038178c8001a242e8c3243e21e9ba [diff] |
[MARIADB] Fix StorageClassName for Galera Add missing entry for customized StorageClass for the MariaDB-Operator based DB instances Issue-ID: OOM-3236 Change-Id: I6c65c1553fc01181aa7dbc5fedb3237c110fc172 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.