| commit | 5e6114080035729f4da49f05ddfe279b54ef544f | [log] [tgz] |
|---|---|---|
| author | saul.gill <saul.gill@est.tech> | Thu Mar 02 11:49:23 2023 +0000 |
| committer | saul.gill <saul.gill@est.tech> | Fri Mar 03 16:55:24 2023 +0000 |
| tree | 00c1b34a57f73af71206275bf7f2bfc195f27410 | |
| parent | d0aaa45535dbb91e6fe5cb609420c2645e4f5d71 [diff] |
[POLICY] Update docker images to latest versions The image versions in policy values.yaml files have been updated Chart config update to match new images *** This commit is generated by a PF release script *** Issue-ID: POLICY-4570 Signed-off-by: saul.gill <saul.gill@est.tech> Change-Id: I347f3601c4a0d3c09cf5eaec6e8ed51878c1a02d Signed-off-by: saul.gill <saul.gill@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.