| commit | 0e73b02702b6735d7fda50c51f6c282fd40a1de2 | [log] [tgz] |
|---|---|---|
| author | Vijay Venkatesh Kumar <vv770d@att.com> | Tue Sep 13 12:37:13 2022 -0400 |
| committer | Vijay Venkatesh Kumar <vv770d@att.com> | Mon Sep 26 15:33:16 2022 -0400 |
| tree | 30a1dd1be881cc1e0f5db1b67993213e8ca378e2 | |
| parent | ba86c11f138127067d533dbfa9c6729386e438f7 [diff] |
[DCAE] Version updates for Kohn RESTConf: 1.3.4 TCAGEn2: 1.3.4 SNMPTrap: 2.0.7 SON-Handler: 2.1.10 MOD/Distributor: 1.1.1 Issue-ID: DCAEGEN2-2976 Issue-ID: DCAEGEN2-3210 Issue-ID: DCAEGEN2-3166 Issue-ID: DCAEGEN2-3213 Issue-ID: DCAEGEN2-3234 Issue-ID: DCAEGEN2-3158 Change-Id: Ia0cc18bba14036284eb8de2a62220e9bab25d59b Signed-off-by: Vijay Venkatesh Kumar <vv770d@att.com>
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.