| commit | 6a5cefa02eaf50e5c782f4b484c3114d93b5427a | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Apr 29 09:22:02 2022 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Apr 29 10:40:25 2022 +0200 |
| tree | 0cbc7d38b2554371bc38ca8d0d1de3a7518b15d8 | |
| parent | 618cfffd44e5a9d187e6a89586b00fb0737f81a7 [diff] |
[AAF] Make AAF ServiceMesh compatible Allthough AAF is not needed for SM it might be required on exceptional cases. In this case the sidecar needs to be disabled for aaf-service and aaf-locate. Additionally the order of chart creation need to be fixed and the job of aaf-sms requires a sidecar killing. Issue-ID: OOM-2820 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I77a2b3da4c826cf294c791bee0d1159233934253
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.