blob: 87cc1036090081af54d2cf1d18c1c293a0eaa333 (
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
|
.. This work is licensed under a Creative Commons Attribution 4.0 International
.. License.
.. http://creativecommons.org/licenses/by/4.0
.. (c) OPNFV, 2017 Intel Corporation.
***********************************************
Yardstick Test Case Description: NSB PROX L3FWD
***********************************************
+-----------------------------------------------------------------------------+
|NSB PROX test for NFVI characterization |
| |
+--------------+--------------------------------------------------------------+
|test case id | tc_prox_{context}_l3fwd-{port_num} |
| | |
| | * context = baremetal or heat_context; |
| | * port_num = 2 or 4; |
| | |
+--------------+--------------------------------------------------------------+
|metric | * Network Throughput; |
| | * TG Packets Out; |
| | * TG Packets In; |
| | * VNF Packets Out; |
| | * VNF Packets In; |
| | * Dropped packets; |
| | |
+--------------+--------------------------------------------------------------+
|test purpose | The PROX L3FWD application performs basic routing of packets |
| | with LPM based look-up method. |
| | |
| | The L3FWD test cases are implemented for baremetal and heat |
| | context for 2 port and 4 port configuration. |
| | |
+--------------+--------------------------------------------------------------+
|configuration | The L3FWD test cases are listed below: |
| | |
| | * tc_prox_baremetal_l3fwd-2.yaml |
| | * tc_prox_baremetal_l3fwd-4.yaml |
| | * tc_prox_heat_context_l3fwd-2.yaml |
| | * tc_prox_heat_context_l3fwd-4.yaml |
| | |
| | Test duration is set as 300sec for each test. |
| | The minimum packet size for L3FWD test is 64 bytes. This is |
| | set in the traffic profile and can be configured to use |
| | a higher packet size for the test. |
| | |
+--------------+--------------------------------------------------------------+
|test tool | PROX |
| | PROX is a DPDK application that can simulate VNF workloads |
| | and can generate traffic and used for NFVI characterization |
| | |
+--------------+--------------------------------------------------------------+
|applicability | This PROX L3FWD test cases can be configured with different: |
| | |
| | * packet sizes; |
| | * test durations; |
| | * tolerated loss; |
| | |
| | Default values exist. |
| | |
+--------------+--------------------------------------------------------------+
|pre-test | For Openstack test case image (yardstick-samplevnfs) needs |
|conditions | to be installed into Glance with Prox and Dpdk included in |
| | it. The test need multi-queue enabled in Glance image. |
| | |
| | For Baremetal tests cases Prox and Dpdk must be installed in |
| | 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. |
| | |
| | For Heat test: Two host VMs are booted, as Traffic generator |
| | and VNF(L3FWD workload) based on the test flavor. |
| | |
+--------------+--------------------------------------------------------------+
|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 | The TG will send packet to the VNF. 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 64 byte |
| | packets 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. |
| | |
| | In Heat test: Two host VMs are deleted on test completion. |
| | |
+--------------+--------------------------------------------------------------+
|test verdict | The test case will achieve a Throughput with an accepted |
| | minimal tolerated packet loss. |
+--------------+--------------------------------------------------------------+
|
