| commit | 7a34dfca27abc3a13f89ed8d6b87e4aa7be9613f | [log] [tgz] |
|---|---|---|
| author | vladimir turok <vladimir.turok@t-systems.com> | Wed Jul 26 12:17:31 2023 +0200 |
| committer | vladimir turok <vladimir.turok@t-systems.com> | Wed Jul 26 12:19:12 2023 +0200 |
| tree | 81684f314b27ed8c6e487cafaf1c45cfc40b4651 | |
| parent | 8c55fdd1dc3f78e32d7214353f09dd67831de216 [diff] |
[OOM] Fixing k8s recouces Fixing resources limits for uui, cps and dcaegen2 Issue-ID: OOM-3199 Change-Id: Ibee9a5a5993d6401b5c4556a84a7e01a0a8b92a1 Signed-off-by: vladimir turok <vladimir.turok@t-systems.com>
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.