| commit | d32b273cbd16058d4d22448766c06c68e38e90af | [log] [tgz] |
|---|---|---|
| author | MichaelMorris <michael.morris@est.tech> | Sat Jun 11 20:28:32 2022 +0100 |
| committer | Fiachra Corcoran <fiachra.corcoran@est.tech> | Wed Jul 06 16:01:50 2022 +0000 |
| tree | 9dd618c38c3e6162aa5a632559bf89163d7664cf | |
| parent | ab71c57205ef0c84050ea1b8f08e46213db470c2 [diff] |
[SDC] Update SDC docker versions to 1.11.4 Early release of Kohn functionality Signed-off-by: MichaelMorris <michael.morris@est.tech> Issue-ID: SDC-4040 Change-Id: If64f4d3db51bcfb274a4895a19d51a6474c31cfe
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.