| commit | 1e184219318a6a386a16a6ae3ac3771205b81724 | [log] [tgz] |
|---|---|---|
| author | Jack Lucas <jflos@sonoris.net> | Tue Mar 08 13:35:24 2022 -0500 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Tue Mar 15 13:40:32 2022 +0000 |
| tree | bc2d98f7ee029f6acea6da0a971413c20f1e7143 | |
| parent | 4830e66d51450883839a7198ea0108376449b66e [diff] |
[DCAEGEN2] Fix check for log directory path Fix bug in dcaegen2-services-common deployment template that caused a nil pointer error when values.yaml for a dcaegen2 microservice did not have a log.path entry. Issue-ID: DCAEGEN2-3093 Signed-off-by: Jack Lucas <jflos@sonoris.net> Change-Id: I3874fd4c4327b487f3a9bf7d95e747d86a320998
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.