| commit | a8a47e06d84f696656479bf507e802a422effd5a | [log] [tgz] |
|---|---|---|
| author | Prakhar Pandey <prakhar.pandey@bell.ca> | Thu Apr 14 12:15:00 2022 -0400 |
| committer | Lukasz Rajewski <lukasz.rajewski@orange.com> | Fri Apr 22 07:08:06 2022 +0000 |
| tree | 7481b5fe44d444354cb771122e13bbf0e331d927 | |
| parent | 2205e0c6bbc9ed05b0fe4a1af88532d95652881f [diff] |
[POLICY] Increase hikari connection pool size for PAP & API We saw some bottlenecks during S3P testing of API component due to the default connection pool size of 10. Setting it to 20 based on the number of parallel threads used for performance tests. The change is required because prior to spring boot migration (Istanbul and earlier), the default connection size was 32 so it was never a problem for running load tests. Issue-ID: POLICY-4007 Change-Id: Iaaa573d5fce0298e3aff05a27c2e845840a6cb06 Signed-off-by: Prakhar Pandey <prakhar.pandey@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.