| commit | 4cb23fffcbfe3e88475a6bd3c3e0e91835c38e28 | [log] [tgz] |
|---|---|---|
| author | Sreeja Gattagouni <sg00744975@techmahindra.com> | Thu Apr 20 06:56:27 2023 +0000 |
| committer | Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> | Tue May 02 10:16:35 2023 +0000 |
| tree | ee22f7d31848eef8d42ff8ddb8c1e00038f95b9a | |
| parent | 7448e0aef213763803a670d265ff9d4f6f96027e [diff] |
[SO] Config Changes for SO to listen to a new DMaap Topic - PNF Addition use case-patch2 - To listen PNF DMaap topics added new Topic PNF_UPDATE Issue-ID: OOM-3092 Change-ID:I73f97f986a817d423f92f8d36809d0947b8a2506 Signed-off-by: Sreeja Gattagouni <sg00744975@techmahindra.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.