| commit | 0d1c0e84c753604ae2f9c29dde7da51ea1ed4e79 | [log] [tgz] |
|---|---|---|
| author | jhh <jorge.hernandez-herrero@att.com> | Fri Apr 08 14:36:15 2022 -0500 |
| committer | Jorge Hernandez <jorge.hernandez-herrero@att.com> | Tue Apr 19 13:16:54 2022 +0000 |
| tree | 446a7419f0a0bc1dff05cf0fba4fb4300819ac56 | |
| parent | cd3dccc6055a1c1b3bbe0c95e489a0a630bf4f4a [diff] |
[POLICY] Enhance liveness probes and metrics - added logback prometheus support for xacml and drools. - enabled enhanced healthchecks. - enabled enhanced liveness probes for drools pdp to detect stuck PDP application and restart it. - add prometheus servicemonitor for drools. - set latest docker image versions for drools-applications and xacml Issue-ID: POLICY-3386 Issue-ID: POLICY-4089 Signed-off-by: jhh <jorge.hernandez-herrero@att.com> Change-Id: I0ffd9bf93452f8a7a63deb33f2103f9b80476d07 Signed-off-by: jhh <jorge.hernandez-herrero@att.com>
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.