| commit | 8cb16a6b59d8501808d62bb558f76f161b53d3e9 | [log] [tgz] |
|---|---|---|
| author | mpriyank <priyank.maheshwari@est.tech> | Fri Nov 03 12:16:54 2023 +0000 |
| committer | Priyank Maheshwari <priyank.maheshwari@est.tech> | Wed Dec 13 11:15:54 2023 +0000 |
| tree | 69e1776c24212d6e136d25eaebabe48e330d4844 | |
| parent | b384dc127c99a1aeccd31e170a580b750374b54b [diff] |
[CPS] Config updates for cps-core and DMI - Actuator health check endpoints and ports updated from /manage to /actuator and port to service port - Config changes relating to spring boot upgrade - Updating the latest cps image for montreal that has security.permit-uri under root - Added hazelcast capability to run on kubernetes mode Issue-ID: CPS-1945 Issue-ID: CPS-1977 Change-Id: I28cc1c576d036cda1d61893a7f897698a056f0a8 Signed-off-by: mpriyank <priyank.maheshwari@est.tech>
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.