| commit | e5f9156814f2571b0f4b79a4ba5789b743d837db | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Mon Jul 10 14:31:00 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Tue Jul 11 16:27:40 2023 +0200 |
| tree | 483c7ce6565103c380eb4a58c531b917962f4731 | |
| parent | 6e00a8b5804469a9be1ad7d59f612341ce9bf0ce [diff] |
[CASSANDRA] Enable new cassandra version using operator Deployment of shared cassandra (4.0.1) using k8ssandra-operator AAI config update to use new cassandra SDC config update to use new cassandra correct link in the oom_infra_optional_addons.rst Issue-ID: OOM-3226 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de> Change-Id: Ieeec9ad5c22a0674a477741d0515ae4515c6f3b8
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.