| commit | b053025fe94b0f9a2bb5cd5ff270c47a7fb71247 | [log] [tgz] |
|---|---|---|
| author | Andreas Geissler <andreas-geissler@telekom.de> | Fri Nov 10 11:28:49 2023 +0100 |
| committer | Andreas Geissler <andreas-geissler@telekom.de> | Fri Nov 10 17:43:47 2023 +0100 |
| tree | b7124d829f92f4899ba03feefc1bbdfa08da1f0a | |
| parent | 09ed93b87cb27864b0f1211799af3aaea8b63db7 [diff] |
[CASSANDRA] Make stargate and reaper deployment optional As Reaper startup is failing in many cases the deployment it should be possible to disable it to stabilize the gating Change the delay handling in the deploy plugin. Issue-ID: OOM-3246 Change-Id: Ibf435d30551aacc213d7c9d38bce72198f4f4b3d 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.