11 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
Assaf Muller	0de917e09b	Enable fullstack multinode tests, add L3 HA test exemplar ... * Created a 'resources' subdir and moved all fixture files to it. * Split ML2ConfigFixture to the server-side ml2 configuration fixture, and the OVS agent configuration fixture. * Neutron process logs were using H:M:S format as their file name, but when starting multiple agents of the same type my machine was fast enough to do that in the same second so that different processes were outputting to the same log file. No good! Added ms to the log name format. I also changed the log time from UTC to local timezone. * Renamed and moved 'FullstackFixture' to neutron/tests/fullstack/ resources/environment.Environment * Added a 'Host' abstraction that groups agents that report with the same 'host' value. Hosts may be interconnected by the environment via shared bridges. * The 'Environment' class will accept global attributes (This will be later filled with stuff like tunneling, l2pop or other environment-level flags), and in this patch accepts a list of host attributes (Configuration that may differ between hosts like the l3 agent mode [legacy, dvr, dvr_snat]). * Made OVS agent and L3 agent fixtures expose their bridges so that I could interconnect them. * Added a super simple L3 HA test to show that this entire thing works. Change-Id: Ie64de9f35bd6ab7cbad494061613ecf5e0ccd806	8 years ago
Cedric Brandily	25baeccac9	Define fullstack router/network/subnet management fixture ... This change defines the generic fixture ClientFixture for managing neutron resources: * router create/cleanup * network create/cleanup * subnet create/cleanup * router interface add/cleanup And uses it in neutron.test.fullstack.test_l3_agent. Change-Id: I09fe40d65db60aeee1ff57a7e45c1978a5433517	8 years ago
Robert Collins	7344e3ab8e	Improve fixture usage. ... There were two broad issues with fixtures. Firstly, the 'SafeFixture' workaround for resource leaks in fixtures <1.3 is not needed if we depend on fixtures>=1.3.1. While testtools may raise a TypeError when trying to query a fixture that failed to setup, this is only ever a cascading failure - it will not cause tests to fail, cause leaks, or cause tests to incorrectly pass. That will be fixed in testtools soon to stop it happening (but as it cannot affect whether a test passes or fails or leaks happen there is no reason to wait for that). Leaks are seen with fixtures 1.3.0 still because eventlet raises a BaseException subclass rather than an Exception subclass, and fixtures 1.3.0 didn't handle that - 1.3.1 does. Secondly, some of the fixtures had race conditions where things were started and then cleanups scheduled. Where possible I've fixed those, but some of them require more significant work to fully address. Change-Id: I3290712f7274970defda19263f4955e3c78e5ed6 Depends-On: I8c01506894ec0a92b53bc0e4ad14767f2dd6a6b3 Closes-bug: #1453888	8 years ago
ChangBo Guo(gcb)	c3d65a0ed9	Switch to oslo_utils.uuidutils ... Get rid of oslo-incubator uuidutils Closes-Bug: #1467020 Depends-On: I2df519965883b05d5d58cdc4785c850b0685dc2c Depends-On: I9f8e98ad9517864a9ffdacf01c0a9a5aab554edb Depends-On: Ied0faac809a5b72b1cd466c8babc9ca5418692c3 Change-Id: Iebe491b981b4b7c02785412fadd27678bb5e47de	8 years ago
John Schwarz	2fcbbf3031	Move full-stack logs post-tests ... Currently, it's up to the developer who wants to run full-stack on his machine to make the directory in question (/opt/stack/logs). However, this also means that the files don't get compressed at the end of a gate run. Now, each full-stack test will have each own log directory in /tmp. Once the logs are there, post_test_hook.sh can run 'gzip' on all the log files before moving them to /opt/stack/logs on its own. Change-Id: I5c04d0af0b9858722ae0c4baf0ee478ffb078e02	8 years ago
John Schwarz	cc1efd0855	Support for concurrent full-stack tests ... This patch introduces the last step of complete test separation for full-stack tests - separate rabbitmq queues - in the form of rabbitmq virtual hosts. * This patch also renames EnvironmentFixture to FullstackFixture, for clarity. Change-Id: I24776e3970a73fdd3271023da7967f2c7261621b Closes-bug: #1452737	8 years ago
Carl Baldwin	8d4cbb3911	Append @randtoken to L3 agent namespaces in full stack tests ... Change-Id: Ib180a5836f653385ec2877c50fbca6f850eff351 Closes-Bug: #1446261	8 years ago
Carl Baldwin	d0d7030ce7	Utilities for building/parsing netns names to facilitate testing ... Creating these utilities allows functional tests to mock them out more easily to in order to change the namespace identification and cleanup behavior. Change-Id: I76cb2dc43a0ca4a7ea27c2ea71b27068b92154ce Related-Bug: #1446261	8 years ago
John Schwarz	304d68d974	Add full-stack test ... Currently, the full-stack framework has only one test which only uses the neutron-server. This patch adds an actual test which makes sure that once a router is created, an actual namespace is create for it. Since this test requires 3 processes (neutron-server, l3-agent, ovs-agent), existing full-stack code is modified to add more streamlined support for such code. Partially-Implements: blueprint integration-tests Change-Id: Id5a8852d38543590b90e4bbed261a7a458071a9a	8 years ago