| commit | 46067c739335b6b456e507be170075dfb62b3086 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Nov 14 19:58:53 2022 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Nov 23 07:53:21 2022 +0000 |
| tree | a9de7b4d4c93dfedeecebdda1caaaada100d4148 | |
| parent | 3502e73a2762fc50f9ba3ae5d65a3efe5f05bead [diff] |
[AAI] Make AAI Sparky BE ServiceMesh ready SparkyBE settings need corrections, as the internal nonTSL port is different from the TLS port. Additionally the AAI port needed to be changed Issue-ID: OOM-2491 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Id675ec3719eaaf1f6d6c2b1468cbd168c852e4d3
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.