2 Commits (739dc16fe75253d392bd4112bc638c1648e0ccf9)

Author	SHA1	Message	Date
John Schwarz	7aa3b2eace	Add EnvironmentDescription, pass it down ... * The EnvironmentDescription class describes an entire fullstack environment (as opposed to the currently implemented host-only descriptions). This will allow future patches to signify that a test should set up an environment that supports tunneling, l2pop, QoS and more. * Now, most fullstack fixtures (config and process ones, at least), expect both the EnvironmentDescription for the current test and the HostDescription for the 'host' the config/process is on. This allows for easier and most robust future changes, as now adding a new parameter to one of the description objects doesn't mean adding that argument to a number of other objects which are using it. * Changed HostDescription's default argument of l3_agent to False, since adding new configurations and defualting them to True forces the author to go through ALL the tests and explicitly turn them on/off. However, defaulting new configurations to False only requires explicitly turning them on, which we ought to do anyway. Change-Id: Ib2f12016ba4371bfda76c82e11d0794acc759955	8 years ago
Assaf Muller	53fe9ddd6c	Add a fullstack fake VM, basic connectivity test ... * Full stack tests' fake VMs are represented via a namespace, MAC, IP address and default gateway. They're plugged to an OVS bridge via an OVS internal port. As opposed to the current fake machine class used in functional testing, this new fake machine also creates a Neutron port via the API and sets the IP and MAC according to it. It also sets additional attributes on the OVS port to allow the OVS agent to do its magic. * The functional fake machine and the full stack fake machine should continue to share commonalities. * The fullstack fake machine currently takes the IP address from the port and statically assigns it to the namespace device. Later when I'll add support for the DHCP agent in full stack testing this assignment will look for the dhcp attribute of the subnet and either assign the IP address via 'ip' or call a dhcp client. * Added a basic L2 connectivity test between two such machines on the same Neutron network. * OVSPortFixture now uses OVSInterfaceDriver to plug the port instead of replicate a lot of the code. I had to make a small change to _setup_arp_spoof_for_port since all OVS ports are now created with their external-ids set. Change-Id: Ib985b7e742f58f1a6eb6fc598df3cbac31046951	8 years ago