| commit | d7136f1f9d6cc352897892ee4b0ef0470e58087d | [log] [tgz] |
|---|---|---|
| author | sushant53 <sushant.jadhav@t-systems.com> | Wed Feb 07 19:06:36 2024 +0530 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Feb 28 13:36:52 2024 +0000 |
| tree | 2d5cd533b27bf14a776b4843419a8b7784f029f2 | |
| parent | ee7e3ada3228e4c80b622aa588d48ac34789cedd [diff] |
[DCAEGEN2] Update helm chart for dcae-prh Update helm chart for prh changes to remove DMaaP dependency Issue-ID: DCAEGEN2-3402 Change-Id: I36ae6a6821a2462a147d0e80f7de5b7b34afda9a Signed-off-by: sushant53 <sushant.jadhav@t-systems.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.