As a user of SDNC, I want a Geo-redundant deployment that builds on the existing site-resilient solution that leverages Kubernetes cluster.

This proof of concept leverages Kubernetes Federation to ensure the two sites can talk to each other in a way that allows native features to be exported.  For this solution, it is ok if I need to manually detect an issue with a given site and need to perform a set of manual steps to switch the active/standby role of each site.

This will build on top of https://wiki.onap.org/display/DW/SDN-C+Clustering+on+Kubernetes

• All required configuration, even though Geo-redundancy shall be disabled by default
• Measurements of solution against KPI of interest.
• Configuration or procedure to ensure that requests get routed to the active site.

In Beijing, this will just be a proof of concept.

Exclusion

• Simple health reporting API or script
• Simple role switching API or script
• Automatic detection of site heath issue and switching of roles.