| commit | 3502e73a2762fc50f9ba3ae5d65a3efe5f05bead | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Nov 14 13:37:48 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Tue Nov 22 07:39:36 2022 +0000 |
| tree | 43b55657ee5d318f331d61141bee3c60c2e278d6 | |
| parent | 693e816b299d2c2c77be62510808256836bf926a [diff] |
[DCAE] Revert TLS disabling for external DCAE MSs For Kohn we still base on AAF CM to provide TLS on the external DCAE services: - dcae-ves-collector - dcae-hv-ves-collector - dcae-datafile-collector - dcae-pm-mapper connection to dmaap-dr-node For London this will be changed to use Ingress TLS Issue-ID: OOM-2775 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I1deb6492483c6ae2db7b5437319dc722d78727c0
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.