| commit | cde4a784a593555c17146635dcc25013872cabc5 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Wed Feb 28 16:08:06 2024 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Mar 07 08:33:07 2024 +0100 |
| tree | ebe7bdf5f2bf48bfb023ad8b1a97c4aed6b3e310 | |
| parent | 4753743f0743a6b22f69e718c3cdb4ba8843cea6 [diff] |
[MONGODB] Update to latest bitnami mongodb chart Import the latest bitnami mongodb chart and update the client charts, which use it: - NBI - DCAEGEN2/TCAEGEN2 (include Chart.yaml fix) - MULTICLOUD/K8S THe new version supports the initial creation of DBs and user Issue-ID: OOM-3277 Change-Id: I75a475aadb8b84a313527b75f4c69e85624af8ba 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.