| commit | 312ab3700fea8579a9f072f095f3c6a1ef66f9d0 | [log] [tgz] |
|---|---|---|
| author | liamfallon <liam.fallon@est.tech> | Mon Dec 13 14:33:33 2021 +0000 |
| committer | liamfallon <liam.fallon@est.tech> | Tue Jan 11 11:09:44 2022 +0000 |
| tree | 3a273809a1c78637578d4148bba857e8d0c9b594 | |
| parent | 98b40be0f580491e015b0c1c33debfccb40a404f [diff] |
[POLICY] Update docker images to latest versions The image versions in policy values.yaml files have been updated and the CLAMP runtime configuration has been updated to use Spring style configuration *** This commit is generated by a PF release script *** Issue-ID: POLICY-3827 Signed-off-by: liamfallon <liam.fallon@est.tech> Change-Id: I220773eb7728d8f5cff36faad388970e1732f12c Signed-off-by: liamfallon <liam.fallon@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.