2.16.3.1.16. Yardstick Test Case Description TC087¶
SDN Controller resilience in non-HA configuration |
|
test case id |
OPNFV_YARDSTICK_TC087: SDN controller resilience in non-HA configuration |
test purpose |
This test validates that network data plane services are highly available in the event of an SDN Controller failure, even if the SDN controller is deployed in a non-HA configuration. Specifically, the test verifies that existing data plane connectivity is not impacted, i.e. all configured network services such as DHCP, ARP, L2, L3 Security Groups should continue to operate between the existing VMs while the SDN controller is offline or rebooting. The test also validates that new network service operations (creating a new VM in the existing L2/L3 network or in a new network, etc.) are operational after the SDN controller has recovered from a failure. |
test method |
This test case fails the SDN controller service running on the OpenStack controller node, then checks if already configured DHCP/ARP/L2/L3/SNAT connectivity is not impacted between VMs and the system is able to execute new virtual network operations once the SDN controller is restarted and has fully recovered |
attackers |
In this test case, an attacker called “kill-process” is needed. This attacker includes three parameters:
|
monitors |
This test case utilizes two monitors of type “ip-status” and one monitor of type “process” to track the following conditions:
Monitors of type “ip-status” use the “ping” utility to verify reachability of a given target IP. |
operations |
In this test case, the following operations are needed:
|
metrics |
In this test case, there are two metrics:
|
test tool |
Developed by the project. Please see folder: “yardstick/benchmark/scenarios/availability/ha_tools” |
references |
none |
configuration |
This test case needs two configuration files:
|
test sequence |
Description and expected result |
pre-action |
|
step 1 |
Result: The monitor info will be collected. |
step 2 |
Start attacker: SSH connect to the VIM node and kill the SDN controller process Result: the SDN controller service will be shutdown |
step 3 |
Verify the results of the IP connectivity monitors. Result: The outage_time metric reported by the monitors is zero. |
step 4 |
Restart the SDN controller. |
step 5 |
Create a new VM in the existing Neutron network |
step 6 |
|
step 7 |
Stop IP connectivity monitors after a period of time specified by “waiting_time” Result: The monitor info will be aggregated |
step 8 |
Verify the IP connectivity monitor results Result: IP connectivity monitor should not have any packet drop failures reported |
test verdict |
This test fails if the SLAs are not met or if there is a test case execution problem. The SLAs are define as follows for this test:
|