| commit | 3afce3d632a64c5f29056e069c296782795553a5 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Wed Feb 15 19:21:32 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Feb 15 19:46:58 2023 +0100 |
| tree | 398dcc0441e46738c743b2efad6eafa5d923c587 | |
| parent | 22f3b16043de9d28461a523202018ef82fcb892d [diff] |
[DCAE] DFC Config-Binding-Service setup fixed The DFC stops running, if the CBS config is not complete. This leads to errors in the 5GBulkPM test. The CBS port has to be set to 0000 and the DMaaP certAuth must be disabled Issue-ID: OOM-3100 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Ibf33666b4cec5b0444f0aec59c106be43aa3cedd
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.