| commit | b60b3b7a6539d64e062a9ba57af9d968be28b6d3 | [log] [tgz] |
|---|---|---|
| author | Maciej Wereski <m.wereski@partner.samsung.com> | Fri Nov 04 13:00:38 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Tue Nov 08 09:54:45 2022 +0000 |
| tree | 7e64ef17ec4635d1f50dcfbb7e275d2632e64c8c | |
| parent | 365bdbc7853b4ca522899629c4ec653a06e5931a [diff] |
[RESOURCES] Tune sm-onap overrides for service mesh Make sure unneeded components are disabled. Issue-ID: OOM-2431 Signed-off-by: Maciej Wereski <m.wereski@partner.samsung.com> Change-Id: Ic57d4ba8bd8cefcb355ee85e6f8d14f05706bcb3
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.