commit | bc4d85d2c5352aa827846a39afd9ed34c356fae0 | [log] [tgz] |
---|---|---|
author | egernug <gerard.nugent@est.tech> | Thu Mar 16 14:23:55 2023 +0000 |
committer | egernug <gerard.nugent@est.tech> | Mon Mar 20 15:54:13 2023 +0000 |
tree | 49b4971ab07145f4dcb882c8713f263d3c15e099 | |
parent | 0879dfcaad420fcc7a6adc77b2b9c72b9522e3cb [diff] |
[SO] Set override property for CNFM in BPMN Infra CNFM needs to be referenced in BPMN Infra Issue-ID: SO-4077 Signed-off-by: egernug <gerard.nugent@est.tech> Change-Id: I2975abd7769eff70663064e71c90a9f0e7e3f67b
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.