| commit | 49a40b21008be7220eb26b3f5784e756359e82c0 | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Tue Nov 14 10:35:03 2023 +0100 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Tue Nov 14 10:35:03 2023 +0100 |
| tree | 785ed387ec7985150e40ecfb494c09f769529ae4 | |
| parent | 546e7acd3e3bdcfbbf31c28fcf81703dc994f384 [diff] |
[AAI] Log to stdout in aai pods - do not log to *.log files in aai pods [0] [0] this is more in line with the idea of statelessness in pods and will allow to persist logs centrally in ELK Issue-ID: AAI-3683 Change-Id: Id7c3faeb24a896f5189336d1fae8473dd9533d83 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.