| commit | b402a59cd21c5df6e01efdbdc5cb8d21eef40c0e | [log] [tgz] |
|---|---|---|
| author | Sirisha_Manchikanti <sirisha.manchikanti@est.tech> | Fri Sep 09 12:01:20 2022 +0100 |
| committer | Sirisha_Manchikanti <sirisha.manchikanti@est.tech> | Wed Sep 21 11:52:25 2022 +0100 |
| tree | 5877db5ec213f8bdb21b20f3c7d82a1eb962592a | |
| parent | ba86c11f138127067d533dbfa9c6729386e438f7 [diff] |
[POLICY] Update strimzi config in policy helm charts Added strimzi kafka user and topics for policy apex-pdp in relevant helm charts. Updated kafka configuration for policy component helm charts. Corrected policy-group configuration in PAP Issue-ID: POLICY-4134 Signed-off-by: Sirisha_Manchikanti <sirisha.manchikanti@est.tech> Change-Id: I0f38f4919898c04e4f4dadc820a7627eee6e022a
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.