| commit | 9b91aef5f2150c21b55fbeead8c3005576214f4f | [log] [tgz] |
|---|---|---|
| author | puthuparambil.aditya <aditya.puthuparambil@bell.ca> | Tue Feb 01 09:30:03 2022 +0000 |
| committer | aditya puthuparambil <aditya.puthuparambil@bell.ca> | Tue Feb 01 10:17:34 2022 +0000 |
| tree | 54d494fa7d3a7d91519c805f7c88ff8dd92a677a | |
| parent | 0eec968ce240c0f029de5c3d3f8b3e8037ee74ce [diff] |
[CPS] Database port made configurable port configured in values.yaml and used in application_helm.yaml Issue-ID: CPS-867 Signed-off-by: puthuparambil.aditya <aditya.puthuparambil@bell.ca> Change-Id: I73c77c0b95c64e51a3b5107b3e0802c9eb4cabe9
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.