summaryrefslogtreecommitdiffstats
path: root/test/test_lb.py
AgeCommit message (Expand)AuthorFilesLines
2019-06-18fib: fib api updatesNeale Ranns1-7/+13
2019-04-11Tests: Refactor tearDown show command logging, add lifecycle markers.Paul Vinciguerra1-2/+3
2019-04-10Tests Cleanup: Fix missing calls to setUpClass/tearDownClass.Paul Vinciguerra1-0/+4
2019-03-22tests: update test_lb.py to use api call lb_conf.Paul Vinciguerra1-4/+4
2019-03-11vpp_papi_provider: Remove more wrapper functions.Ole Troan1-2/+5
2019-03-11VPP-1508: Use scapy.compat to manage packet level library differences.Paul Vinciguerra1-4/+6
2019-03-07Tests: Refactor payload_to_info()Paul Vinciguerra1-1/+1
2018-08-31Support lb on both vip and per-port-vip caseHongjun Ni1-55/+218
2018-06-26L3DSR fix ip checksum issue and add testHongjun Ni1-0/+6
2018-05-18Rework kube-proxy into LB pluginHongjun Ni1-1/+70
2018-02-02Add L3DSR feature in LB pluginHongjun Ni1-8/+36
2017-12-16Use crc32 wrapper (VPP-1086)Gabriel Ganne1-1/+1
2017-10-31lb plugin tests - wipe flowtable after each unit testGabriel Ganne1-0/+4
2017-10-24fix test_lb_ip4_gre6() cleanupGabriel Ganne1-1/+1
2016-12-23make test: improve handling of packet capturesKlement Sekera1-6/+5
2016-12-19make test: filter IPv6 RAs out by defaultKlement Sekera1-11/+2
2016-12-16make test: improve robustness and performanceKlement Sekera1-5/+11
2016-12-05make test: fix missing log/packet messagesKlement Sekera1-4/+3
2016-11-10Enable verification received packet for LB testMatej Klotton1-12/+4
2016-11-09Disable non-working checks in load-balancer test and rename ip->ip4Klement Sekera1-8/+11
2016-10-26refactor test frameworkKlement Sekera1-118/+134
2016-10-10Test: Add test case for Load Balancer pluginPierre Pfister1-0/+210
| Unit tests and Python test harness | ## Getting started In general anyone interested in building, developing or running VPP should consult the [VPP wiki](https://wiki.fd.io/view/VPP) for more complete documentation. In particular, readers are recommended to take a look at [Pulling, Building, Running, Hacking, Pushing](https://wiki.fd.io/view/VPP/Pulling,_Building,_Run ning,_Hacking_and_Pushing_VPP_Code) which provides extensive step-by-step coverage of the topic. For the impatient, some salient information is distilled below. ### Quick-start: On an existing Linux host To install system dependencies, build VPP and then install it, simply run the build script. This should be performed a non-privileged user with `sudo` access from the project base directory: ./extras/vagrant/build.sh If you want a more fine-grained approach because you intend to do some development work, the `Makefile` in the root directory of the source tree provides several convenience shortcuts as `make` targets that may be of interest. To see the available targets run: make ### Quick-start: Vagrant The directory `extras/vagrant` contains a `VagrantFile` and supporting scripts to bootstrap a working VPP inside a Vagrant-managed Virtual Machine. This VM can then be used to test concepts with VPP or as a development platform to extend VPP. Some obvious caveats apply when using a VM for VPP since its performance will never match that of bare metal; if your work is timing or performance sensitive, consider using bare metal in addition or instead of the VM. For this to work you will need a working installation of Vagrant. Instructions for this can be found [on the Setting up Vagrant wiki page] (https://wiki.fd.io/view/DEV/Setting_Up_Vagrant). ## More information Several modules provide documentation, see @subpage user_doc for more end-user-oriented information. Also see @subpage dev_doc for developer notes. Visit the [VPP wiki](https://wiki.fd.io/view/VPP) for details on more advanced building strategies and other development notes. ## Test Framework There is PyDoc generated documentation available for the VPP test framework. See @ref test_framework_doc for details.