| commit | 1eeb37b34517aecb0fdcef2e486188768b5ee513 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Tue Apr 09 13:58:38 2024 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Tue Apr 09 17:11:06 2024 +0200 |
| tree | 57ed2741974e759d0fdf3273a64203c2cbb37cac | |
| parent | 5230ed9ba9769c93487ad66d0d1f68eec5134a90 [diff] |
[CASSANDRA] Add some fixes for K8ssandra Operator Some ports need to be excluded from cassandra to support JMX and Metrics interfaces. Also some memory settings need to be adjusted. Issue-ID: OOM-3275 Change-Id: I7530b69d65c7c612bcf54eba64d5a4dd5a20f753 Signed-off-by: Andreas Geissler <andreas-geissler@telekom.de>
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.