| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|
| Forced failover from standby site in healthy system | Verify that the site operator is able to force the standby site to become active from the standby site when both sites are in a healthy state from any site | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Forced failover from active site in healthy system | Verify that the site operator is able to force the standby site to become active from the active site when both sites are in a healthy state from any site | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Forced failover from standby site in healthy system | Verify that the site operator is able to force the standby site to become active from the standby site when both sites are in a healthy state from any site | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Forced failover from active site in healthy system | Verify that the site operator is able to force the standby site to become active from the active site when both sites are in a healthy state from any site | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Site failover invoked by total ODL outage | Verify that the sdnc.failover script can successfully be used to make a standby site active when the ODLs in the active site are no longer available. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Site recovery after total ODL outage | Verify that a documented process can be followed to recover an SDN-C site that failed due to a total loss of ODL instances. The procedure should restore the site so that it is available to become the active site. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Site failover invoked by simple failure | Verify that the enhancements in sdnc.failover do not affect the ability to failover in non-catastrophic conditions. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Site failover invoked by total ODL outage | Verify that the sdnc.failover script can successfully be used to make a standby site active when the ODLs in the active site are no longer available. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Force failover from standby site without network segmentation |
| PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Forced failover from standby site during network segmentation | Verify that the site operator is able to force the standby site to become active from the standby site when the network connection to the remote site has failed. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| DMaaP message for PROM-initiated failover | Verify that the SDN-C site delivers a DMaaP-based message when a successful automatic site switch from one site to the other has taken place. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| DMaaP message for healthy to unhealthy transition on active site | Verify that the SDN-C site delivers a DMaaP-based message when the active site transitions from healthy to unhealthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| DMaaP message for healthy to unhealthy transition on standby site | Verify that the SDN-C site delivers a DMaaP-based message when the standby site transitions from healthy to unhealthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| DMaaP message for unhealthy to healthy transition on standby site | Verify that the SDN-C site delivers a DMaaP-based message when the standby site transitions from unhealthy to healthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| DMaaP message for operator-initiated failover | Verify that the SDN-C site delivers a DMaaP-based message when a successful operator-initiated switch from one site to the other has taken place. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| DMaaP message for unsuccessful PROM-initiated failover | Verify that the SDN-C site delivers a DMaaP-based message when an automatic site switch fails to be completed successfully. The message should be very clear that the failover did not complete successfully. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| DMaap Initial state message | Verify that the SDN-C site delivers an initial DMaaP-based message about the health check | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| DMaap subsequent health state message | Verify that the SDN-C site delivers an subsequent DMaaP-based message about the health check | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| DMaaP messaging documentation review | Verify that the ONAP wiki documentation correctly describes the DMaaP messaging feature for SDN-C Geo. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-281 |
|---|
|
|
|
| Auto-switch on unhealthy report | Verify that PROM is able to publish the local site's health to MUSIC and the remote site's PROM initiates site failover in the case where the site is found to be unhealthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Auto-switch on PROM failure | Verify that the remote site's PROM initiates a site failover when the local site's PROM is unable to publish health updates. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| Single failover activity | Verify that delays in carrying out a site failover do not prevent PROM from running its enableSdncActive.sh script or from initiating multiple failover activities. The failover process should be called asynchronously. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| PROM starts in passive mode on standby site | Verify that PROM starting in passive mode on standby site | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| No component outages | Verify that when all components in the site are available, the site is reported as being healthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-282 |
|---|
|
|
|
| Single ODL outage | Verify that a single ODL outage does not result in the site being unhealthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-282 |
|---|
|
|
|
| Double ODL outage | Verify that a double ODL outage results in the site being unhealthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-282 |
|---|
|
|
|
| Triple ODL outage | Verify that a triple ODL outage results in the site being unhealthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-282 |
|---|
|
|
|
| Single Admin Portal outage | Verify that an outage of the Admin Portal results in the site being unhealthy. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-282 |
|---|
|
|
|
| Exit code on successful execution of healthy | Verify that when sdnc.monitor runs successfully and detects the site is healthy, the exit code returned is "0". | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-282 |
|---|
|
|
|
| Exit code on successful execution of unhealthy | Verify that when sdnc.monitor runs successfully and detects the site is unhealthy, the exit code returned is "0". | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-282 |
|---|
|
|
|
| sdnc.dnsswitch updates CoreDNS settings for Site A | Verify that the sdnc.dnsswitch script modifies the CoreDNS configuration so that the SDN-C domain points to the local site. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| sdnc.dnsswitch updates CoreDNS settings for Site B | Verify that the sdnc.dnsswitch script modifies the CoreDNS configuration so that the SDN-C domain points to the local site. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| sdnc.dnsswitch run when site is already target | Verify that the dns.dnsswitch script is capable of being run on the local site when the CoreDNS configuration is already pointing to the local site. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| sdnc.dnsswitch returns "0" exit code on success | Verify that the sdnc.dnsswitch script provides a "0" exit code when run successfully. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| sdnc.dnsswitch returns non-zero exit code on failure | Verify that the sdnc.dnsswitch script provides a non-zero exit code when run unsuccessfully. | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| sdnc.dnsswitch returns non-zero exit code on failure when core-dns is unavailable in config file | Verify that the sdnc.dnsswitch script provides a non-zero exit code when core-dns is unavailable in site.conf | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| sdnc.dnsswitch returns non-zero exit code on failure when app name is other than sdnc in config file | Verify that the sdnc.dnsswitch script provides a non-zero exit code when app name is other than sdnc in site.conf | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| sdnc.dnsswitch returns non-zero exit code on failure when core-dns host is invalid | Verify that the sdnc.dnsswitch script provides a non-zero exit code when core-dns host is invalid in site.conf | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|
| sdnc.dnsswitch returns non-zero exit code on failure when appname or siteip are missing | Verify that the sdnc.dnsswitch script provides a non-zero exit code when appname or siteip are missing from site.conf | PASS | |
| | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | SDNC-213 |
|---|
|
|
|