blob: 6a4a376973accfe0ef54ae96d296556375c12e28 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, 2019 Viosoft Corporation.
***********************************************
Yardstick Test Case Description: NSB VPP IPSEC
***********************************************
+------------------------------------------------------------------------------+
|NSB VPP test for vIPSEC characterization |
| |
+--------------+---------------------------------------------------------------+
|test case id | tc_baremetal_rfc2544_ipv4_{crypto_dev}_{crypto_alg} |
| | |
| | * crypto_dev = HW_cryptodev or SW_cryptodev; |
| | * crypto_alg = aes-gcm or cbc-sha1; |
| | |
+--------------+---------------------------------------------------------------+
|metric | * Network Throughput NDR or PDR; |
| | * Connections Per Second (CPS); |
| | * Latency; |
| | * Number of tunnels; |
| | * TG Packets Out; |
| | * TG Packets In; |
| | * VNF Packets Out; |
| | * VNF Packets In; |
| | * Dropped packets; |
| | |
+--------------+---------------------------------------------------------------+
|test purpose | IPv4 IPsec tunnel mode performance test: |
| | |
| | * Finds and reports throughput NDR (Non Drop Rate) with zero |
| | packet loss tolerance or throughput PDR (Partial Drop Rate) |
| | with non-zero packet loss tolerance (LT) expressed in |
| | number of packets transmitted. |
| | |
| | * The IPSEC test cases are implemented to run in baremetal |
| | |
+--------------+---------------------------------------------------------------+
|configuration | The IPSEC test cases are listed below: |
| | |
| | * tc_baremetal_rfc2544_ipv4_hw_aesgcm_IMIX_trex.yaml |
| | * tc_baremetal_rfc2544_ipv4_hw_aesgcm_trex.yaml |
| | * tc_baremetal_rfc2544_ipv4_hw_cbcsha1_IMIX_trex.yaml |
| | * tc_baremetal_rfc2544_ipv4_hw_cbcsha1_trex.yaml |
| | * tc_baremetal_rfc2544_ipv4_sw_aesgcm_IMIX_trex.yaml |
| | * tc_baremetal_rfc2544_ipv4_sw_aesgcm_trex.yaml |
| | * tc_baremetal_rfc2544_ipv4_sw_cbcsha1_IMIX_trex.yaml |
| | * tc_baremetal_rfc2544_ipv4_sw_cbcsha1_trex.yaml |
| | |
| | Test duration is set as 500sec for each test. |
| | Packet size set as 64 bytes or higher. |
| | Number of tunnels set as 1 or higher. |
| | Number of connections set as 1 or higher |
| | These can be configured |
| | |
+--------------+---------------------------------------------------------------+
|test tool | Vector Packet Processing (VPP) |
| | The VPP platform is an extensible framework that provides |
| | out-of-the-box production quality switch/router functionality.|
| | Its high performance, proven technology, its modularity and, |
| | flexibility and rich feature set |
| | |
+--------------+---------------------------------------------------------------+
|applicability | This VPP IPSEC test cases can be configured with different: |
| | |
| | * packet sizes; |
| | * test durations; |
| | * tolerated loss; |
| | * crypto device type; |
| | * number of physical cores; |
| | * number of tunnels; |
| | * number of connections; |
| | * encryption algorithms - integrity algorithm; |
| | |
| | Default values exist. |
| | |
+--------------+---------------------------------------------------------------+
|pre-test | For Baremetal tests cases VPP and DPDK must be installed in |
|conditions | the hosts where the test is executed. The pod.yaml file must |
| | have the necessary system and NIC information |
| | |
+--------------+---------------------------------------------------------------+
|test sequence | description and expected result |
| | |
+--------------+---------------------------------------------------------------+
|step 1 | For Baremetal test: The TG and VNF are started on the hosts |
| | based on the pod file. |
| | |
+--------------+---------------------------------------------------------------+
|step 2 | Yardstick is connected with the TG and VNF by using ssh. |
| | The test will resolve the topology and instantiate the VNF |
| | and TG and collect the KPI's/metrics. |
| | |
+--------------+---------------------------------------------------------------+
|step 3 | Test packets are generated by TG on links to DUTs. If the |
| | number of dropped packets is more than the tolerated loss |
| | the line rate or throughput is halved. This is done until |
| | the dropped packets are within an acceptable tolerated loss. |
| | |
| | The KPI is the number of packets per second for a packet size |
| | specified in the test case with an accepted minimal packet |
| | loss for the default configuration. |
| | |
+--------------+---------------------------------------------------------------+
|step 4 | In Baremetal test: The test quits the application and unbind |
| | the DPDK ports. |
| | |
+--------------+---------------------------------------------------------------+
|test verdict | The test case will achieve a Throughput with an accepted |
| | minimal tolerated packet loss. |
+--------------+---------------------------------------------------------------+
|
