| commit | 891eeb77f57dcb28db018fab84ece4b46758a162 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Thu Oct 12 13:10:53 2023 +0200 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Wed Oct 18 14:56:44 2023 +0200 |
| tree | 7d44ecec00ff21264fa0fad88196b9d3ccf33b35 | |
| parent | 11a7c5036e8d5b7e4c9bf3c2d0c06dc0ebef9ba8 [diff] |
[CASSANDRA] Add Reaper and Stargate label checked by SDC/AAI Schema creations of Reaper and AAI/SDC can conflict with each other. Therefor the reaper init script should finish before AAI and SDC schema init scripts are started Update jvm options for cassandra instance Issue-ID: OOM-3246 Change-Id: I16cea161fc8b75e15c76c4cbe4851739782dfb06 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.