| commit | ca06856557a33f8203d1c5550d436471784dc374 | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Thu Mar 28 08:41:55 2024 +0100 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Wed Apr 17 14:56:52 2024 +0200 |
| tree | 307d48230b421988a0f46dd10684f77cb26c5825 | |
| parent | 6d5a8690d675f65a8ec38b2c03f6fde2c2d2d9b8 [diff] |
[AAI] Add model-loader tracing config - mount application.properties file that is used by Spring [1] - add tracing config to that file - deploy model-loader version 1.13.5 [1] this is also a prerequisite for replacing the model-loader.properties file that is loaded by the service via some custom logic. Spring does this out of the box for application-*.properties files. Issue-ID: AAI-3812 Change-Id: I0a101fd246b8313f90cfc3ebca5a65dae769d3d6 Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de>
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.