| commit | c6144829d2c4ee22cbdb4591ed34557b83999bc2 | [log] [tgz] |
|---|---|---|
| author | Dan Timoney <dtimoney@att.com> | Thu Apr 27 10:17:20 2023 -0400 |
| committer | Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> | Thu Jun 22 13:25:29 2023 +0000 |
| tree | b09f71f527b16f3c7faec3b7520ceda278d5e7f3 | |
| parent | 743dca9a2e5e4944474c6e2dff65109cfdef571a [diff] |
[SDNC] Bump SDNC and CCSDK versions for London release Bump versions of SDNC and CCSDK docker images for London release, bump sdnc version to 2.5.2 to resolve gating issues bump sdnc version to 2.5.3 to add missing Bierman API karaf feature bump sdnc version to 2.5.5 to resolve HTTP PATCH issue ueb-listener to use sdc-distr-client 2.0.0 (kafka native) Use Strimzi KafkaUser template Issue-ID: CCSDK-3876 Issue-ID: CCSDK-1789 Issue-ID: CCSDK-3908 Signed-off-by: Dan Timoney <dtimoney@att.com> Change-Id: I053058f09bad1f5d1578979134eed43eee1d76eb
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.