| commit | 072e2d5c4c71f7f7179e38863c249e5813c9e3a1 | [log] [tgz] |
|---|---|---|
| author | rameshiyer27 <ramesh.murugan.iyer@est.tech> | Tue Nov 19 16:12:27 2024 +0000 |
| committer | rameshiyer27 <ramesh.murugan.iyer@est.tech> | Tue Nov 26 22:35:20 2024 +0000 |
| tree | db2ac2cd70e0f4ddb506d392b5b18a8538e17b06 | |
| parent | 7b584c689c52be2238d22aad20b57745bf03367c [diff] |
[POLICY] Update docker images to latest versions The image versions in policy values.yaml files have been updated *** This commit is generated by a PF release script *** Issue-ID: POLICY-5166 Change-Id: I1e81d5bbee812f584cd8ee769f95f9534a5cef9d Signed-off-by: rameshiyer27 <ramesh.murugan.iyer@est.tech>
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.