| commit | 128e9d2214c5a41a0ca4a9dac4248c55b38c59d0 | [log] [tgz] |
|---|---|---|
| author | Maciej Wereski <m.wereski@partner.samsung.com> | Mon Jan 10 11:03:27 2022 +0100 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Wed Jan 19 07:09:35 2022 +0000 |
| tree | 5fe05a9b9835d9749be1e2134d7aac9e826a1134 | |
| parent | 0d2cf1aee02c84d5ff262b4ac1d414fdadf5432b [diff] |
[DMAAP] Fix log volume name in some components Issue-ID: OOM-1 Reported-By: Jack Lucas <jflos@sonoris.net> Signed-off-by: Maciej Wereski <m.wereski@partner.samsung.com> Change-Id: Ieefbb96d8bcc1b4e9a7066acf6a877336a57117c
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.