| commit | 65e8f785c1ab86a761970161bb1e754a0e03c895 | [log] [tgz] |
|---|---|---|
| author | dasarathi528024 <ds00528024@techmahindra.com> | Wed May 03 09:51:20 2023 +0000 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri May 26 08:48:39 2023 +0200 |
| tree | d37c350e0a8318f7fc1eac47dab657a0ba9e07d7 | |
| parent | 7448e0aef213763803a670d265ff9d4f6f96027e [diff] |
[COMMON] Adding Common Template for cassa-operator - K8ssandraCluster resources template file added - Modification of the cassandra chart to add the option to install cassandra using the k8ssandra-operator - AAI and SDC values changed to support the new cassandra settings - Fix for SDC cql version in jobs - for London make k8ssandra-operator optional (default: false) Issue-ID: OOM-3168 Signed-off-by: Dasarathi, Swain (ds00528024) <ds00528024@techmahindra.com> Change-Id: Idfe232460c9c1f584536e60ea042345d7dca3164
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.