neutron

History

Assaf Muller 1a1ccb8c94 Uniquely identify tunnel interfaces for fullstack tests OVS agent tunnel interfaces are named via: '%s-%s' % (tunnel_type, destination_ip) This means that the tunnel interface name is not unique if two OVS agents on the same machine try to form a tunnel with a third agent. This happens during full stack tests that start multiple copies of the OVS agent on the test machine. Thus, for full stack tests, to make sure that the tunnel interface names created by ovs agents are globally unique, they will have the following format : '%s-%s-%s' % (tunnel_type, hash of source IP, hash of dest IP) Since this patch centralizes the formation of the tunnel interface name in a dedicated method that is monkey patched by the full stack framework, a unit test has been added for this method. Co-Authored-By: Mathieu Rohon <mathieu.rohon@gmail.com> Closes-Bug: #1467633 Change-Id: I991af6a5f982746cc297f0248454f803dfbb2daf		2016-01-28 15:12:40 -05:00
..
resources	Uniquely identify tunnel interfaces for fullstack tests	2016-01-28 15:12:40 -05:00
README	Moved fullstack test doc content to TESTING.rst	2015-12-03 17:02:54 -05:00
__init__.py	Add full-stack tests framework	2015-03-26 20:21:40 +02:00
base.py	Merge "fullstack: use migration scripts to create db schema"	2015-08-21 03:48:33 +00:00
test_connectivity.py	Uniquely identify tunnel interfaces for fullstack tests	2016-01-28 15:12:40 -05:00
test_l3_agent.py	Add l2pop support to full stack tests	2015-09-10 14:31:35 +00:00
test_qos.py	Don't register agents for QoS l2pop fullstack test	2015-10-05 10:46:11 -04:00

README

Please see neutron/TESTING.rst.