| commit | 2cef564fe7af8a43cb3e9bba77fff91a02fae372 | [log] [tgz] |
|---|---|---|
| author | Michal Jagiello <michal.jagiello@t-mobile.pl> | Mon Jun 27 10:08:41 2022 +0000 |
| committer | Michal Jagiello <michal.jagiello@t-mobile.pl> | Mon Jul 04 17:30:37 2022 +0000 |
| tree | c9e9bba80c2aa9352a501adf2c77d78ea894d936 | |
| parent | fa9bd70bd3e2b4e5ca8f070e9a5f6125fc7fc283 [diff] |
[CDS] Add cps-data resourceSourceMapping in application.properties That is needed to send requests to CPS during resource assignement Issue-ID: CCSDK-3699 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: I17502aa394709d0e1b4b8a30448df8c6cb4bcfe2
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.