| commit | 21d48641d6344e9f00523ca15d49d44fcdb277b3 | [log] [tgz] |
|---|---|---|
| author | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Tue Jan 16 08:33:59 2024 +0100 |
| committer | Fiete Ostkamp <Fiete.Ostkamp@telekom.de> | Tue Jan 16 08:39:59 2024 +0100 |
| tree | 6cd24475a18dd8794cccf45231e2919df5dbc9d7 | |
| parent | 13c91a3f135f4cd622c0f3b4019e284cc88b0ebf [diff] |
[AAI] Add options for remote debugging and profiling - add debug.enabled value for enabling debugging [1] - add profiling.enabled value for enabling probiling [2] - only expose debug port (5005) if debug.enabled=true [1] appropriate jvm args will be added and the debug port will be exposed on the pod [2] appropriate jvm args will be added and the 9999 port used for profiling via jmx will be exposed Issue-ID: AAI-3730 Change-Id: I1d83a6ac1875ba63e710e86d4fcbfc8924810292 Signed-off-by: Fiete Ostkamp <Fiete.Ostkamp@telekom.de>
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.