| commit | 004ebce85d8214df87689db574efd7f16c87524d | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Fri Jul 05 15:26:43 2024 +0200 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Fri Jul 12 10:36:14 2024 +0200 |
| tree | bf97ff69628459455ebe53dbbb02dd37818b74b5 | |
| parent | dc8c05476d316a16627d5b0934b69c3a9ecc38b7 [diff] |
[AAI] Use 1.14.4 images - deploy 1.14.4 images - increase AAI chart version to 14.0.1 - change sidecar killer job to use wget instead of curl Issue-ID: AAI-3926 Change-Id: I405b52169006800b63fc76568482b4347c99c0b4 Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@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.