| commit | 9eb2c11d39161671070085b21f73847b61ea8e5f | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Nov 21 14:13:23 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Nov 28 14:34:32 2022 +0100 |
| tree | 6fe047a945b43678ad86f372553bd69b9b476d10 | |
| parent | 693e816b299d2c2c77be62510808256836bf926a [diff] |
[DOC] ServiceMesh documentation Add instructions for SM Installation (addon guide), ONAP configuration (customize_override) and access guide Issue-ID: OOM-3006 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I31acad2c8c84ed3382e1c43897333f9ff565ff6d
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.
