-
Type: Epic
-
Status: Resolved (View Workflow)
-
Priority: High
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: VOLTHA v1.0.0, VOLTHA v1.1.1
-
Component/s: Deprecated - VOLTHA
-
Labels:None
-
Epic Name:VOLTHA High Availability
-
Story Points:0
A means to recover from individual component/container failures as well as complete server failures is required for voltha to be suitable for use in a telecommunication carrier environment.
Acceptance Criteria
Validate VOLTHA components are recoverable from faults
List of components
1.
2.
3.
- blocks
-
VOL-21 Volha suite container provisioning during installation
- Resolved
-
VOL-6 Installation without external network access
- Resolved
-
VOL-49 Collection of configuration information for installation
- Resolved
- is blocked by
-
VOL-238 Architecture spike to assess openflow agent behavior with HA
- Resolved
- relates to
-
VOL-72 A mechanism to save voltha's state at any time is required
- Resolved
-
VOL-8 VOLTHA Backup and Restore
- Resolved
-
VOL-112 A mechanism to save the state of other voltha suite components is required
- Resolved
-
VOL-84 A mechanism to Backup immutable cluster configuration is required for backups (Review for K8s)
- Resolved