| commit | 0d893db1cd97d4bf90e861f8a381981aad36a2d3 | [log] [tgz] |
|---|---|---|
| author | Tomasz Wrobel <tomasz.wrobel@nokia.com> | Thu Feb 17 11:50:43 2022 +0100 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Tue Mar 15 13:47:00 2022 +0000 |
| tree | 8e244af243a1575bc6e55046ed35322bccc264ba | |
| parent | 6f7684bcc1e68267b8f9df68839308ac4c47b700 [diff] |
[DCAEGEN2] Top up DCAEGEN2 images Top up following DCAEGEN2 images: - DFC 1.7.1 - PM-Mapper 1.8.0 - PRH 1.8.0 - VES 1.11.0 Issue-ID: DCAEGEN2-3006 Signed-off-by: Tomasz Wrobel <tomasz.wrobel@nokia.com> Change-Id: Icf8c08c42a002d131207201af7df1e7ced5e120e
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.