1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, 2017 Intel Corporation.
6 ******************************************************
7 Yardstick Test Case Description: NSB PROX MPLS Tagging
8 ******************************************************
10 +-----------------------------------------------------------------------------+
11 |NSB PROX test for NFVI characterization |
13 +--------------+--------------------------------------------------------------+
14 |test case id | tc_prox_{context}_mpls_tagging-{port_num} |
16 | | * context = baremetal or heat_context; |
17 | | * port_num = 2 or 4; |
19 +--------------+--------------------------------------------------------------+
20 |metric | * Network Throughput; |
21 | | * TG Packets Out; |
22 | | * TG Packets In; |
23 | | * VNF Packets Out; |
24 | | * VNF Packets In; |
25 | | * Dropped packets; |
27 +--------------+--------------------------------------------------------------+
28 |test purpose | The PROX MPLS Tagging test will take packets in from one |
29 | | port add an MPLS tag and forward them to another port. |
30 | | While forwarding packets in other direction MPLS tags will |
33 | | The MPLS test cases are implemented to run in baremetal |
34 | | and heat context an require 4 port topology to run the |
35 | | default configuration. |
37 +--------------+--------------------------------------------------------------+
38 |configuration | The MPLS Tagging test cases are listed below: |
40 | | * tc_prox_baremetal_mpls_tagging-2.yaml |
41 | | * tc_prox_baremetal_mpls_tagging-4.yaml |
42 | | * tc_prox_heat_context_mpls_tagging-2.yaml |
43 | | * tc_prox_heat_context_mpls_tagging-4.yaml |
45 | | Test duration is set as 300sec for each test. |
46 | | The minimum packet size for MPLS test is 68 bytes. This is |
47 | | set in the traffic profile and can be configured to use |
48 | | higher packet sizes. |
50 +--------------+--------------------------------------------------------------+
52 | | PROX is a DPDK application that can simulate VNF workloads |
53 | | and can generate traffic and used for NFVI characterization |
55 +--------------+--------------------------------------------------------------+
56 |applicability | The PROX MPLS Tagging test cases can be configured with |
60 | | * test durations; |
61 | | * tolerated loss; |
63 | | Default values exist. |
65 +--------------+--------------------------------------------------------------+
66 |pre-test | For Openstack test case image (yardstick-samplevnfs) needs |
67 |conditions | to be installed into Glance with Prox and Dpdk included in |
70 | | For Baremetal tests cases Prox and Dpdk must be installed in |
71 | | the hosts where the test is executed. The pod.yaml file must |
72 | | have the necessary system and NIC information |
74 +--------------+--------------------------------------------------------------+
75 |test sequence | description and expected result |
77 +--------------+--------------------------------------------------------------+
78 |step 1 | For Baremetal test: The TG and VNF are started on the hosts |
79 | | based on the pod file. |
81 | | For Heat test: Two host VMs are booted, as Traffic generator |
82 | | and VNF(MPLS workload) based on the test flavor. |
84 +--------------+--------------------------------------------------------------+
85 |step 2 | Yardstick is connected with the TG and VNF by using ssh. |
86 | | The test will resolve the topology and instantiate the VNF |
87 | | and TG and collect the KPI's/metrics. |
89 +--------------+--------------------------------------------------------------+
90 |step 3 | The TG will send packets to the VNF. If the number of |
91 | | dropped packets is more than the tolerated loss the line |
92 | | rate or throughput is halved. This is done until the dropped |
93 | | packets are within an acceptable tolerated loss. |
95 | | The KPI is the number of packets per second for 68 bytes |
96 | | packet size with an accepted minimal packet loss for the |
97 | | default configuration. |
99 +--------------+--------------------------------------------------------------+
100 |step 4 | In Baremetal test: The test quits the application and unbind |
101 | | the dpdk ports. |
103 | | In Heat test: Two host VMs are deleted on test completion. |
105 +--------------+--------------------------------------------------------------+
106 |test verdict | The test case will achieve a Throughput with an accepted |
107 | | minimal tolerated packet loss. |
108 +--------------+--------------------------------------------------------------+