1 .. This work is licensed under a Creative Commons Attribution 4.0 International
3 .. http://creativecommons.org/licenses/by/4.0
4 .. (c) OPNFV, 2018 Intel Corporation.
6 *******************************************************
7 Yardstick Test Case Description: NSB EPC DEFAULT BEARER
8 *******************************************************
10 +-----------------------------------------------------------------------------+
11 |NSB EPC default bearer test case |
13 +--------------+--------------------------------------------------------------+
14 |test case id | tc_epc_default_bearer_landslide_{dmf_setup} |
16 | | * dmf_setup: single or multi dmf test session setup; |
18 +--------------+--------------------------------------------------------------+
19 |metric | All metrics provided by Spirent Landslide traffic generator |
21 +--------------+--------------------------------------------------------------+
22 |test purpose | The Spirent Landslide product provides one box solution which|
23 | | allows to fully emulate all EPC network nodes including |
24 | | mobile users, network host and generate control and data |
27 | | This test allows to check processing capability of EPC under |
28 | | different levels of load (number of subscriber, generated |
29 | | traffic throughput) for case when only one default bearer is |
30 | | using for transferring traffic from UE to Network. |
32 | | It's easy to replace emulated node or multiple nodes in test |
33 | | topology with real node or corresponding vEPC VNF as DUT and |
34 | | check it's processing capabilities under specific test case |
35 | | load conditions. |
37 +--------------+--------------------------------------------------------------+
38 |configuration | The EPC default bearer test cases are listed below: |
40 | | * tc_epc_default_bearer_create_landslide.yaml |
41 | | * tc_epc_default_bearer_create_landslide_multi_dmf.yaml |
45 | | * is set as 60sec (specified in test session profile); |
49 | | * UDP - for single DMF test case; |
50 | | * UDP and TCP - for multi DMF test case; |
54 | | * 512 bytes for UDP packets; |
55 | | * 1518 bytes for TCP packets; |
57 | | Traffic transaction rate: |
61 | | Number of mobile subscribers: |
65 | | Number of default bearers per subscriber: |
69 | | The above fields and values are the main options used for the|
70 | | test case. Other configurable options could be found in test |
71 | | session profile yaml file. All these options have default |
72 | | values which can be overwritten in test case file. |
74 +--------------+--------------------------------------------------------------+
75 |test tool | Spirent Landslide |
77 | | The Spirent Landslide is a tool for functional & performance |
78 | | testing of different types of mobile networks. It emulates |
79 | | real-world control and data traffic of mobile subscribers |
80 | | moving through virtualized EPC network. |
81 | | Detailed description of Spirent Landslide product could be |
82 | | found here: https://www.spirent.com/Products/Landslide |
84 +--------------+--------------------------------------------------------------+
85 |applicability | This EPC DEFAULT BEARER test cases can be configured with |
89 | | * traffic transaction rate; |
90 | | * number of subscribers sessions; |
91 | | * number of default bearers per subscriber; |
92 | | * subscribers connection rate; |
93 | | * subscribers disconnection rate; |
94 | | * DMF (traffic profile); |
95 | | * enable/disable Fireball DMF threading model that provides |
96 | | optimized performance; |
98 | | Default values exist. |
100 +--------------+--------------------------------------------------------------+
101 |references | ETSI-NFV-TST001 |
105 +--------------+--------------------------------------------------------------+
106 | pre-test | * All Spirent Landslide dependencies are installed (detailed |
107 | conditions | installation steps are described in Chapter 13- |
108 | | nsb-installation.rst and 14-nsb-operation.rst file for NSB |
109 | | Spirent Landslide vEPC tests; |
111 | | * The pod.yaml file contains all necessary information |
112 | | (TAS VM IP address, NICs, emulated SUTs and Test Nodes |
113 | | parameters (names, types, ip addresses, etc.). |
115 +--------------+--------------------------------------------------------------+
116 |test sequence | description and expected result |
118 +--------------+--------------------------------------------------------------+
119 |step 1 | Spirent Landslide components are running on the hosts |
120 | | specified in the pod file. |
122 +--------------+--------------------------------------------------------------+
123 |step 2 | Yardstick is connected with Spirent Landslide Test |
124 | | Administration Server (TAS) by TCL and REST API. The test |
125 | | will resolve the topology and instantiate all emulated EPC |
128 +--------------+--------------------------------------------------------------+
129 |step 3 | Test scenarios run, which performs the following steps: |
131 | | * Start emulated EPC network nodes; |
132 | | * Establish subscribers connections to EPC network (only |
133 | | default bearers are established); |
134 | | * Create the sessions and transmit traffic through EPC |
135 | | network nodes during the specified traffic duration time; |
136 | | * Disconnect subscribers at the end of the test. |
138 +--------------+--------------------------------------------------------------+
139 |step 4 | During test run, all the metrics provided by Spirent |
140 | | Landslide are stored in the yardstick dispatcher. |
142 +--------------+--------------------------------------------------------------+
143 |test verdict | The test case will create the test session in Spirent |
144 | | Landslide with the test case parameters and store the |
145 | | results in the database for benchmarking purposes. The aim |
146 | | is only to collect all the metrics that are provided by |
147 | | Spirent Landslide product for each test specific scenario. |
149 +--------------+--------------------------------------------------------------+