| commit | 4bc879a3dd204729b98b64cea9fc49a17d9c7fa5 | [log] [tgz] |
|---|---|---|
| author | Michal Jagiello <michal.jagiello@t-mobile.pl> | Wed Apr 20 12:58:42 2022 +0000 |
| committer | Lukasz Rajewski <lukasz.rajewski@orange.com> | Thu Apr 21 05:51:04 2022 +0000 |
| tree | ee68d2edb4c2617c1fd9ec34057ad99dac23072b | |
| parent | c8964e507dfc9b32a0f29f2a67ce74b1f8a260b9 [diff] |
[MARIADB] Back to istanbul version of mariaDB image We have stability issues with MariaDB (which didn't occur on istanbul). Issue-ID: OOM-2963 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: I23b31db06dd87a45a47c8b2741b36e6387e5d1ec
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.