| commit | dfa23c83cc8630915824968ba7b043ef968e38b6 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri May 13 16:54:43 2022 +0200 |
| committer | Jack Lucas <jflos@sonoris.net> | Wed Sep 14 13:22:29 2022 +0000 |
| tree | e86e83dd0cbae293ce845ddb3d38bcb4ae40c448 | |
| parent | 8cd7e264e2a8d7f6686065f882b3b2f0663a6690 [diff] |
[MULTICLOUD] Service mesh compatibility Patch on MC charts dedicated to make http/https calls depending on configuration for TLS. Include an updated version of the framework-artifactbroker Issue-ID: OOM-3015 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I03deae9dcea703540fe6e3a81ddba20505f246f1
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.