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

Description

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

100% Done
Type
Key
Summary
Priority
Story Points
Assignee
Status

Activity

Show:

Former user April 20, 2020 at 11:48 AM

two years without update, let's see in the future if we want to continue or not

Former user December 30, 2018 at 10:39 AM

Good morning . The current fixVersion is set to "Beijing Release". Can you please review the status of this ticket and update it accordingly? thank you

Former user November 28, 2017 at 9:48 PM

2403

Won't Do

Details

Assignee

Reporter

Labels

Fix versions

Priority

Epic Name

Epic Status

Done

Created October 4, 2017 at 3:03 PM
Updated December 13, 2022 at 10:55 AM
Resolved April 20, 2020 at 11:48 AM

Flag notifications