| commit | fd450c4959d9cb4d4ae18218aa8b4e597139ce56 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Dec 10 08:36:45 2021 +0000 |
| committer | Sylvain Desbureaux <sylvain.desbureaux@orange.com> | Wed Jan 12 07:53:19 2022 +0000 |
| tree | b2441bb12066f58ea1cf927a6aad88335e6b842d | |
| parent | 0d2cf1aee02c84d5ff262b4ac1d414fdadf5432b [diff] |
[SDC] Add missing dependency to cassandra chart In case of "localCluster: true" the cassandra chart will be added in sdc-cs subchart. Renamed global section to sdc-cassandra. Additionally serviceAccount is added to cassandra definition in sdc-cs (see OOM-2905) Issue-ID: OOM-2899 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Id943db249a3abd9dbc67e333a05f6c2abd84a810
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.