Age | Commit message (Collapse) | Author | Files | Lines |
|
All references to submodules must be removed for docs to
work going forward.
Can be tested once your project has a local tox file
Change-Id: Id74581cc584f70ae0b31e31c9dd91593c7be6615
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
(cherry picked from commit 2ba5ef8eeac9f92436fcaed807fdd4ecaa79d2c0)
|
|
Add documentation to review the changes to original vEPC infrastructure
files to configure NSB test run in a specific test setup.
Add initial steps to prepare NSB to use Spirent Landslide for vEPC tests.
JIRA: YARDSTICK-1459
Change-Id: I3b937b1a21d6ec6851a92946e46c679385fdff9c
Signed-off-by: Orest Voznyy <orestx.voznyy@intel.com>
(cherry picked from commit dc55a775f7aa62be7ed17cc33aa1b0bac54c081f)
|
|
Change-Id: If308fde797dcb01e58f37ad81bb116fde542366a
Signed-off-by: Chornyi, TarasX <tarasx.chornyi@intel.com>
|
|
|
|
Added default values for pmd/lcore mask to the SampleVNF test case for
Trex TG.
lcore mask - specifies the CPU cores used for non-datapath OVS-DPDK
threads.
pmd mask - specifies the CPU cores used for data path packet processing.
Updated documentation for Standalone OVS-DPDK context.
JIRA: YARDSTICK-1246
Change-Id: I8d008a185c94d2047ffa4769d7974bc4d283fd7f
Signed-off-by: Stepan Andrushko <stepanx.andrushko@intel.com>
|
|
Add PROX and vFW scale out TCs with availability zone
configuration. To be able to specify the availability
zone for specific VNF or TG the following example of
command line option shoud be used:
yardstick -d task start --task-args='{
"num_vnfs": 2, "availability_zone":
{
"vnf_0": "az_0", "tg_0": "az_0",
"vnf_1": "az_1", "tg_1": "az_1",
... }}' <SCALE-OUT-TC-FILE>
The steps to run new scale-out TCs is documented in the
userguide.
JIRA: YARDSTICK-1203
Change-Id: Ib3878485c5483981fe9b48ab02995712bcc31ae5
Signed-off-by: Mytnyk, Volodymyr <volodymyrx.mytnyk@intel.com>
|
|
* Increment the numbering on chapters
* Fix some of the changes flagged by doc8
Change-Id: Ie03d165297671dfd50b9de339612cdc8bf00b988
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|