| commit | 2f3773631ae41e6c66f2a0222810621044cbbb16 | [log] [tgz] |
|---|---|---|
| author | a.sreekumar <ajith.sreekumar@bell.ca> | Wed Feb 09 12:40:57 2022 +0000 |
| committer | Prakhar Pandey <prakhar.pandey@bell.ca> | Tue Mar 22 13:54:41 2022 -0400 |
| tree | f24dc90e3dee4b0f21862b7d42d6c7ea98c9a24a | |
| parent | f91c26bb28e7ee59ccc941647190c18257f23a01 [diff] |
[POLICY] OOM Jakarta changes for PAP,API & PDPs This review contains the below changes: 1) PAP config changes for spring boot migration 2) savePdpStatistics flag is disabled by default 3) DMaaP connectivity added to PAP consolidated healthcheck 4) Improve PAP & API readiness probe from TCP to HTTP GET based healthcheck api 5) API config changes for springboot migration 6) Update the docker image versions for Jakarta. Change-Id: I8dfc821b1245cd4ef6bdedad7802deb4ac3297e3 Issue-ID: POLICY-3750 Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
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.