Age | Commit message (Collapse) | Author | Files | Lines |
|
Rename TGs and VNFs to follow a single naming convention, for all VNFs:
name: trafficgen_0
role: tg__0
name: vnf_0
role: vnf__0
JIRA: YARDSTICK-1578
Change-Id: I233b1ba24c85c2e93b831eefbcfe6757f5edf5ca
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
Implement code to support traffic_duration field in test case options.
This updates the 'duration' in Landslide session profile.
traffic_duration should always be much less than runner duration/timeout.
JIRA: YARDSTICK-1427
Change-Id: I51094bade683ca8758136ccb619e8894a2ecef72
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|
|
This test case runs on Spirent Landslide TG. All vEPC entities are
emulated on Landslide test server.
Test run configuration is performed in following files:
1. test case file
2. pod file
3. session profile file (landslide_session_default_bearer*.yaml)
The structure of these files represents configuration of different
parts of test cases in this test session. The order of test cases should
always match.
Spirent Landslide test types involved: "SGW_Node", "SGW_Nodal".
Test case actions sequence:
- create default bearers (as per value of "Sessions" key) with
specified rate (session profile key "StartRate")
- send traffic flow(s) (pre-configured in traffic profile) for a number
of seconds (specified in session profile key "duration")
- remove N default bearers with specified rate (session profile key
"DisconnectRate")
Parameters with ALL_CAPS values are placeholders.
User should replace them with their own condifuration.
Session profile file placeholders do not need to be replaced as long as
these parameters are overriden in other files (e.g. pod, test case).
Test results are dispatched according to runner configuration options.
For fully emulated test runs like this one, best suited runner is "Search"
type. In case of testing against real EPC VNFs, user could prefer
different runner type.
JIRA: YARDSTICK-1348
Change-Id: I5caf4878fb212b38d4148a297c5dba03b8ab98a8
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
|