diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/release/release-notes/release-notes.rst | 34 | ||||
| -rw-r--r-- | docs/testing/developer/devguide/results/results.rst | 42 |
2 files changed, 50 insertions, 26 deletions
diff --git a/docs/release/release-notes/release-notes.rst b/docs/release/release-notes/release-notes.rst index c2dff390..e4c5f6c8 100644 --- a/docs/release/release-notes/release-notes.rst +++ b/docs/release/release-notes/release-notes.rst @@ -2,6 +2,40 @@ .. http://creativecommons.org/licenses/by/4.0 .. (c) OPNFV, Intel Corporation, AT&T and others. +OPNFV Euphrates Release +======================= + +* Improvement of stepdriven testcases +* Support for graph plotting from vsperf results +* Support for vHost User client mode in OVS and VPP +* Support for DPDK 17.02 +* Support for dpdk driver NIC binding by drivectl tool +* Several bugfixes and small improvements + +* vSwitches + + * Support for VPP virtual switch + * OVS: Support for jumbo frames + +* Traffic Generators: + + * Support for Trex traffic generator + * Support for huge number of streams + * Ixia: L3, L4 or vlan headers can be turned off/on, support of 1 NIC connection + between DUT and Ixia, bugfixing + * MoonGen: fix multistream support + * Xena: option for final verification, JSON refactoring, support for xena + pairs topology and port removal options, bugfixes + +* Guest specific: + + * Support for additional QEMU cpu features + * Support for pinning of vCPU threads + +* Integration tests: + + * New VPP related testcases + * New multistream testcases focused on L3 and L4 performance of OVS and VPP OPNFV Danube Release ==================== diff --git a/docs/testing/developer/devguide/results/results.rst b/docs/testing/developer/devguide/results/results.rst index df9c52cb..0a0ab75d 100644 --- a/docs/testing/developer/devguide/results/results.rst +++ b/docs/testing/developer/devguide/results/results.rst @@ -7,32 +7,22 @@ OPNFV Test Results VSPERF CI jobs are run daily and sample results can be found at https://wiki.opnfv.org/display/vsperf/Vsperf+Results -The following example maps the results in the test dashboard to the appropriate -test case in the VSPERF Framework and specifies the metric the vertical/Y axis -is plotting. **Please note**, the presence of dpdk within a test name signifies -that the vswitch under test was OVS with DPDK, while its absence indicates that -the vswitch under test was stock OVS. +Testcase names shown in the dashboard are combination of orignal testcase +name from VSPERF framework and indication of used vswitch. -===================== ===================== ================== =============== - Dashboard Test Framework Test Metric Guest Interface -===================== ===================== ================== =============== -tput_ovsdpdk phy2phy_tput Throughput (FPS) N/A -tput_ovs phy2phy_tput Throughput (FPS) N/A -b2b_ovsdpdk back2back Back-to-back value N/A -b2b_ovs back2back Back-to-back value N/A -tput_mod_vlan_ovs phy2phy_tput_mod_vlan Throughput (FPS) N/A -tput_mod_vlan_ovsdpdk phy2phy_tput_mod_vlan Throughput (FPS) N/A -scalability_ovs phy2phy_scalability Throughput (FPS) N/A -scalability_ovsdpdk phy2phy_scalability Throughput (FPS) N/A -pvp_tput_ovsdpdkuser pvp_tput Throughput (FPS) vhost-user -pvp_tput_ovsvirtio pvp_tput Throughput (FPS) virtio-net -pvp_b2b_ovsdpdkuser pvp_back2back Back-to-back value vhost-user -pvp_b2b_ovsvirtio pvp_back2back Back-to-back value virtio-net -pvvp_tput_ovsdpdkuser pvvp_tput Throughput (FPS) vhost-user -pvvp_tput_ovsvirtio pvvp_tput Throughput (FPS) virtio-net -pvvp_b2b_ovsdpdkuser pvvp_back2back Throughput (FPS) vhost-user -pvvp_b2b_ovsvirtio pvvp_back2back Throughput (FPS) virtio-net -===================== ===================== ================== =============== + Example: -The loopback application in the VNF was used for PVP and PVVP scenarios was DPDK + Testcase ``phy2phy_tput`` is executed for three vSwitch types: ``OvsDpdkVhost``, + ``OvsVanilla`` and ``VppDpdkVhost``. In this case, following testcase names + will be used in the dashboard: ``phy2phy_tput_ovsdpdkvhost``, + ``phy2phy_tput_ovsvanilla`` and ``phy2phy_tput_vppdpdkvhost``. + +In case of RFC2544 Throughput test, the recorded metric is FPS (frames per +second) without packet loss. For RFC2544 Back2Back test, the recorded metric +is back-to-back value (number of frames) without packet loss. + +The loopback application in the VNF used for PVP and PVVP scenarios was DPDK testpmd. + +Guest interface types are ``vhost-user`` for ``OvsDpdkVhost`` and ``VppDpdkVhost`` +and ``virtio-net`` for ``OvsVanilla``. |