| commit | 5df5a5c46119496deef08c50da8f3a473c10b07e | [log] [tgz] |
|---|---|---|
| author | Timoney, Dan (dt5972) <dtimoney@att.com> | Fri Oct 28 11:50:38 2022 -0400 |
| committer | Timoney, Dan (dt5972) <dtimoney@att.com> | Fri Oct 28 11:50:38 2022 -0400 |
| tree | fab1159f9a657a2b684de84369073700a0100e10 | |
| parent | 26411370f979ba4e2d1fc1b9f4bd8e3f23f0fee1 [diff] |
[SDNC] Version bump for SDNC Kohn RC Version bump for SDNC Kohn RC milestone. Also, change callhome port from 6666 to 4334 to comply with RFC standard, implemented in ODL Sulfur release Issue-ID: SDNC-1744 Signed-off-by: Timoney, Dan (dt5972) <dtimoney@att.com> Change-Id: I1e5576d0b51d140a8899e8e48d27f4ab071c44e3
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.