| commit | 3072a8980d4b54fa6deac38bc6d06e6359a04a9e | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Jan 07 17:41:42 2022 +0000 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Jan 07 17:45:33 2022 +0000 |
| tree | 1825568954b8ebd6bd64be63e9170a0d6c0d9cd1 | |
| parent | 0d2cf1aee02c84d5ff262b4ac1d414fdadf5432b [diff] |
[AAI] Add serviceAccount override to local cassandra config If localCluster is enabled, the serviceAccount name must match with the DB name Issue-ID: OOM-2905 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Ia6860d995dc7f19890855bcf3a8e3e768966a43a
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.