| commit | 8624d2224da24c9a181af7b089b548a6e59c2582 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri May 13 17:16:41 2022 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Jun 03 13:11:55 2022 +0200 |
| tree | 78757e81d11b24a68629dadb0499026f9f5c6909 | |
| parent | c1aa68b0c1183d90e6ada524d7e16dabf51bf890 [diff] |
[AAI] Service mesh compatibility improvement Add waiting times for the jobs for the Sidecar to start up Cleanup old ClusterIP, which is not used anymore and corrected failing configuration for the modelloader. Added annotation for Sparky-be probe settings. Issue-ID: OOM-2820 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: I996c9bad4fcfea5aaba7f8eeb4b12b1282be0375
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.