openstack/neutron
Code Issues Proposed changes
6a350bf950
neutron/doc/source/devref/fullstack_testing.rst

42 lines
1.4 KiB
ReStructuredText
Raw Normal View History

Consistent layout and headings for devref The lack of convention for heading levels among the independently written devref documents was starting to make the Table of Contents look rather messy when rendered in HTML. This patch does not cover the "Neutron Internals" section since its layout is reasonably OK for now. Change-Id: I827c105599f05773bda7e4fc0a941ce04ebd51fa
2015-08-03 23:30:34 -04:00
..
Licensed under the Apache License, Version 2.0 (the "License"); you may
not use this file except in compliance with the License. You may obtain
a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
under the License.
Convention for heading levels in Neutron devref:
======= Heading 0 (reserved for the title in a document)
------- Heading 1
~~~~~~~ Heading 2
+++++++ Heading 3
''''''' Heading 4
(Avoid deeper levels because they do not render well.)
Full Stack Testing
==================
Add devref that explains fullstack testing and its direction The goal of this doc is to communicate what are full stack tests, how they benefit you and when would you write such a test. Additionally I'd like to communicate the way forward, and gather feedback about any areas in the code that can benefit from full stack tests, and any additional thoughts! Change-Id: Ifd4ff9be0ed0184a49df6566d238c31a328cd23f
2015-06-02 12:21:11 -04:00
Moved fullstack test doc content to TESTING.rst * Removed long term goals documentation (I don't see a need to document these). * Added and rearranged short term goals. Change-Id: If494533cb6507f18b84a41b3f1daf42cd10d9f51
2015-11-16 15:31:43 -05:00
Goals
Consistent layout and headings for devref The lack of convention for heading levels among the independently written devref documents was starting to make the Table of Contents look rather messy when rendered in HTML. This patch does not cover the "Neutron Internals" section since its layout is reasonably OK for now. Change-Id: I827c105599f05773bda7e4fc0a941ce04ebd51fa
2015-08-03 23:30:34 -04:00
-----
Add devref that explains fullstack testing and its direction The goal of this doc is to communicate what are full stack tests, how they benefit you and when would you write such a test. Additionally I'd like to communicate the way forward, and gather feedback about any areas in the code that can benefit from full stack tests, and any additional thoughts! Change-Id: Ifd4ff9be0ed0184a49df6566d238c31a328cd23f
2015-06-02 12:21:11 -04:00
Moved fullstack test doc content to TESTING.rst * Removed long term goals documentation (I don't see a need to document these). * Added and rearranged short term goals. Change-Id: If494533cb6507f18b84a41b3f1daf42cd10d9f51
2015-11-16 15:31:43 -05:00
* Stabilize the job:
- Fix L3 HA failure
- Look in to non-deterministic failures when adding a large amount of
tests (Possibly bug 1486199).
- Switch to kill signal 15 to terminate neutron-server & agents (Bugs
1487548 and 1494363).
* Convert the L3 HA failover functional test to a full stack test
* Write a test for DHCP HA / Multiple DHCP agents per network
Add devref that explains fullstack testing and its direction The goal of this doc is to communicate what are full stack tests, how they benefit you and when would you write such a test. Additionally I'd like to communicate the way forward, and gather feedback about any areas in the code that can benefit from full stack tests, and any additional thoughts! Change-Id: Ifd4ff9be0ed0184a49df6566d238c31a328cd23f
2015-06-02 12:21:11 -04:00
* Write DVR tests
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
2015-05-07 09:02:59 +03:00
* Write additional L3 HA tests
Add devref that explains fullstack testing and its direction The goal of this doc is to communicate what are full stack tests, how they benefit you and when would you write such a test. Additionally I'd like to communicate the way forward, and gather feedback about any areas in the code that can benefit from full stack tests, and any additional thoughts! Change-Id: Ifd4ff9be0ed0184a49df6566d238c31a328cd23f
2015-06-02 12:21:11 -04:00
* Write a test that validates DVR + L3 HA integration after
https://bugs.launchpad.net/neutron/+bug/1365473 is fixed.
Copy Permalink