-
Epic
-
Resolution: Won't Do
-
Medium
-
None
-
None
-
Platform Resiliency/Geo-diversity
-
Done
As an ONAP operator, I want to have a highly available and resilient platform so that I maintain optimal production uptime and stability.
Acceptance Criteria
- Resiliency on failure:
- ONAP components failures (hardware, software, environment) don't affect the ability for ONAP platform to perform the work;
- Strategies such as High-Availability, Recoverability and Auto-Healing are properly applied at the component level to make sure platform uptime and performance is maintained
- Recoverability:
- ONAP components can be fully recovered from failure, including configuration and state
- Backup and restore mechanisms enabled and tested for each platform component
- Components can be backed up and restored independently from each other
- High-Availability:
- ONAP components can be deployed in a highly available manner; High-availability parameters configurable by the operator
- High-availability/clustering mechanisms may vary per component
- Geo-redundancy support for all ONAP platform containers; Geo-redundancy parameters configurable by the operator
- blocks
-
DMAAP-905 [DMAAP] DMaaP support for multi-site applications
- Closed
- relates to
-
LOG-380 Platform Maturity: Performance, Stability, Resiliency, Scalability
- Closed
-
LOG-707 Logging El-Alto (moved from) Dublin Scope
- Closed
-
OOM-607 Kubernetes Federation support - for multi site deployment
- Closed
(1 mentioned in)