| commit | c8845ef1b7c3d78e756240d3f8c95470ece7529d | [log] [tgz] |
|---|---|---|
| author | Rommel Pawar <rommel.pawar@bell.ca> | Thu Sep 22 14:04:14 2022 -0700 |
| committer | Lukasz Rajewski <lukasz.rajewski@t-mobile.pl> | Tue Sep 27 18:11:32 2022 +0000 |
| tree | 55940fd40e6fa71d7a1c22a841cd4c1c85596824 | |
| parent | 740cb1c679b52e3d4597c1211ff9b0a02bde84d4 [diff] |
[AAI] OOM AAI resources healthcheck based on Cassandra DB Healthcheck Use echo endpoint for aai-resources liveness and readiness probes Updated aai resources docker image Issue-ID: AAI-3528 Signed-off-by: Rommel Pawar <rommel.pawar@bell.ca> Change-Id: I2ceb489142063189d39ec271d3ea82e00e781b75
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.