As a user of SDNC, I want improvements to resiliency of the geo-redudent (multi-site) deployment delivered in Beijing, which only supported manual fail-over.  I want support of auto-detection of health issues with the site and automatic corrective action of site-switching to take place.

I want to achieve level 3, as defined in the ONAP Carrier Grade requirements - resiliency

  https://wiki.onap.org/pages/viewpage.action?pageId=15998867

In particular, I want

1.  Automatic fail-over, enabling SDN-C clients to access an alternative (≥ 1) geographically separated SDN-C site(s) to assure normal operation in case of unavailability of the primary SDN-C site.
2. The fail over between SDN-C sites to be performed automatically within no more than 10 seconds – TBD from the primary SDN-C failure.
3. Geo redundancy solution to maintain a set of policies for a number of available correction actions to use in different failure conditions to minimize downtime. E.g. if the site is operational but ODL cluster fails to operate, to restart ODL or part of it instead of initiating fail over to the secondary site.
4. To operate after the fail-over, the previously secondary site as a primary site, while the recently primary site becomes standby secondary.
5. Support fail-over mechanism with no impact on the SDN-C ONAP client e.g. MSO.
6. Be able to initiate fail-over manually
7. Monitor Geo-redundant mechanism status to get info regarding the sites availability and log regarding the Geo redundancy mechanism events