Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-346

Platform Resiliency (Recoverability, High-Availability, Geo-Diversity)


    • Type: Epic
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: Dublin Release
    • Labels:
    • Epic Name:
      Platform Resiliency/Geo-diversity
    • Epic Status:
      To Do


      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


          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.



              • Assignee:
                melliott Mike Elliott
                david.sauvageau David Sauvageau
              • Votes:
                0 Vote for this issue
                6 Start watching this issue


                • Created: