| commit | db8167bbf6923c8f316ebadd6cec1dd4891428a1 | [log] [tgz] |
|---|---|---|
| author | vladimir turok <vladimir.turok@t-systems.com> | Wed Sep 20 11:09:21 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Oct 18 11:55:13 2023 +0000 |
| tree | 5f5e393573f0270973f0af3599e06dcffb58f958 | |
| parent | 7a24e5fedfafeab43c80403759507960abb3c2b0 [diff] |
[OOM] Fixing k8s cpu limits Adding specific cpu limits for all oom components Issue-ID: OOM-3241 Change-Id: I0bbd973d91d11dbb0ffa5848f7c1ed5ebb5f54ba 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.