| commit | 531941ee2a217fdbf192f506f3ae2afef613f44b | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Jun 15 16:44:51 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Jun 19 10:03:25 2023 +0000 |
| tree | dc987b29eee0e71beaacbdad2e8609387cc40e8f | |
| parent | 1df3539c188c062c1a4dde08e9a2baf83a155413 [diff] |
[UUI] Uui-intent-analysis resource settings fix The pod uses more memory, so the resource limits needed to be enhanced Issue-ID: OOM-3189 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I0096a1b08add252fbed642182b95e5e26a0f0d0c
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.