| commit | f24b56967cb1482e64c943b432d3fc7ea020c637 | [log] [tgz] |
|---|---|---|
| author | sangeeta.bellara <sangeeta.bellara@t-systems.com> | Sat Apr 29 19:18:30 2023 +0530 |
| committer | sangeeta.bellara <sangeeta.bellara@t-systems.com> | Sat Apr 29 19:18:30 2023 +0530 |
| tree | 75588869c7621032bf03a813eed25e60d855b466 | |
| parent | 7448e0aef213763803a670d265ff9d4f6f96027e [diff] |
[DCAEGEN2] Update PRH version for London release Issue-ID: DCAEGEN2-3376 Change-id: 9470749204 Signed-off-by: Sangeeta Bellara <sangeeta.bellara@t-systems.com> Change-Id: I2cf7c82e64a3fad33df498843be013f50c3158a4
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.