Connectivity tests for OVS agent failures/restarts
Adding two tests:
* A test that for native ovs-ofctl interface verifies that stopping the
ovs-neutron-agent does not disrupt network traffic. Stopping the agent
means also stopping the OVS bridge controller, hence OVS can decide to
take over management of OpenFlow rules, clear them up, and this way
cause network traffic disruption.
* A test that creates two ports in a single network, then starts
pinging one from the other while restarting OVS agents. The test verifies
that no packet is lost during OVS agent restarts.
Reviewed: https:/ /review. openstack. org/462998 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=81bb6aa348c 05b9cff39ce2acd a2bd77e01167c7
Committed: https:/
Submitter: Jenkins
Branch: stable/ocata
commit 81bb6aa348c05b9 cff39ce2acda2bd 77e01167c7
Author: Hynek Mlnarik <email address hidden>
Date: Wed Aug 10 10:07:42 2016 +0200
Connectivity tests for OVS agent failures/restarts
Adding two tests:
* A test that for native ovs-ofctl interface verifies that stopping the neutron- agent does not disrupt network traffic. Stopping the agent
ovs-
means also stopping the OVS bridge controller, hence OVS can decide to
take over management of OpenFlow rules, clear them up, and this way
cause network traffic disruption.
* A test that creates two ports in a single network, then starts
pinging one from the other while restarting OVS agents. The test verifies
that no packet is lost during OVS agent restarts.
Change-Id: I2cd1195fc0622c 8c8d614f00e9dd6 884ad388d69 8916e074f5cb767 5871964448)
Related-Bug: 1514056
Related-Bug: 1607787
(cherry picked from commit 27aee4a9c53ad9e