| commit | 867602f80edce6d9cc47bb26f78a3a2787d8322f | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Tue Oct 24 10:49:10 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Tue Oct 24 10:51:19 2023 +0200 |
| tree | 9dee15373c5a71001386d0fb1889d40e10816074 | |
| parent | 2ff7f1c46d3e9a6b05e830ac4bc8f56c230b22aa [diff] |
[SO][UUI] Adjust resource settings Update the resource limits for UUI-Server and SO Admin Cockpit to start properly in "small" flavour Issue-ID: OOM-3241 Change-Id: I5f926e32c07d8135946436ebf72bdbb1bbc94e24 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.