| commit | 062e7c2a2f0e666ba87d4a0337e5774cf841b3f9 | [log] [tgz] |
|---|---|---|
| author | rajesh.kumar <rk00747546@techmahindra.com> | Tue Oct 17 15:29:20 2023 +0530 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Mon Feb 19 11:11:21 2024 +0100 |
| tree | 0b186a33f7b090df790010a59db643ea65ccebd7 | |
| parent | 2ee6ad456a91061d64b859ba20108c7e3c556de3 [diff] |
[POSTGRES][COMMON] Add support for postgres operator Add template for the postgres operator instance setup and modifications to use the postgres instance via Operator TBD: Update of documentation and fix for clients (DMaaP, CPS) Issue-ID: OOM-3247 Change-Id: I56c34400dc73c71b936a51260efd231017adaeae Signed-off-by: rajesh.kumar <rk00747546@techmahindra.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.