| commit | 718fb74a15842d2bf178d3ad44a5d73d2986433b | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Mar 09 09:44:02 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Thu Mar 09 11:58:44 2023 +0100 |
| tree | b775109201584f4673532c6bc561c0f90b9a1862 | |
| parent | b8e544195b55094cfa58f43690fde71c3fba062e [diff] |
[MULTICLOUD] Cleanup charts and add Ingress configs Remove AAF/TLS configurations and enable NodePort/Ingress configuration for MC services Issue-ID: OOM-3117 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I9e3c7dfa3b15202a6e0f4cad7a3cdf616198e644
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.