diff options
| author |   Abhijit Sinha <abhijit.sinha@intel.com> | 2017-11-13 17:23:27 +0000 |
|---|---|---|
| committer | Abhijit Sinha <abhijit.sinha@intel.com> | 2017-11-14 13:27:58 +0000 |
| commit | 4b0bf9ea920b461b6464d0c6888b3b0bcc9a0004 (patch) | |
| tree | 15e68f86ad5bc6f8924db0a24b85307d65ec052e /ansible/cpu_pin_teardown.yaml | |
| parent | 349660091288e47c3c5032e6dec9d29e9a2f251f (diff) | |
NSB Prox BM test case fixes for scale up
YARDSTICK-839
In a scale-up test the VNF number can start from
0 to MAX (num_vnf-1)
The NSB PROX BM test nodes are currently marked as:
tg__0: trafficgen_1.yardstick
vnf__0: vnf.yardstick
They need to be changed to the below:
tg__0: tg_0.yardstick
vnf__0: vnf_0.yardstick
Changes done are:
- All BM Prox test cases have tg_0 and vnf_0 as default
test nodes
- The prox-baremetal-1/2/4.yaml sample pod file
- Cleaned Up some unused Prox test/config files
Change-Id: I819011bcb35eda62b17dd3e1035918918c582b13
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
Diffstat (limited to 'ansible/cpu_pin_teardown.yaml')
0 files changed, 0 insertions, 0 deletions