aboutsummaryrefslogtreecommitdiffstats
path: root/nsb_setup.sh
AgeCommit message (Collapse)AuthorFilesLines
2017-07-17Fix adding right deb repo based on the distro we are running onDeepak S1-1/+1
JIRA: YARDSTICK-669 Change-Id: I0f3848b7803bc62c88effd00e850755e514893c4 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-04-26Point to user guide to get started on VNF testingDeepak S1-1/+1
Change-Id: Id050d06deff665e6eaa97876d50e1698697e61e5 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-03-09Bugfix: Using the right trex version to support both py2.7 & py3Deepak S1-5/+6
Updating the trex version and downloading the right version for vnf testing :) Change-Id: Iaca74ce627a05128a60bdc331968d2c56c06522f Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-03-05update trex version for constants.so import bugRoss Brattain1-1/+1
Previously before we disabled Trex in the unittests we were hitting an error when running Python3.5, see full description in 28209 https://gerrit.opnfv.org/gerrit/#/c/28209/ File "/home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master/trex/scripts/external_libs/pyzmq-14.5.0/python3/fedora18/64bit/zmq/backend/cython/__init__.py", line 6, in <module> from . import (constants, error, message, context, ImportError: cannot import name 'constants' It looks like this was an actual upstream Trex bug and it was fixed in https://github.com/cisco-system-traffic-generator/trex-core/commit/9808fce2b0b3b5b7c9b28303e99486501a1cc10d zmq: fix wrong constants.so (was used from 3.5 to both versions) Yaroslav Brustinov <ybrustin@cisco.com> This Trex fix should be in v2.20. We don't test Trex in unitests, but people running Trex on Python3 should hit this issue. Change-Id: Ic914e48819d7fd3e951628f7c3d3778849da7d94 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-01-19Setup yardstick_virtual environments for Network Service TestingDeepak S1-0/+244
JIRA: YARDSTICK-521 Change-Id: Ib91d231120067e58d2e1df7f1b42db216d15c468 Signed-off-by: Deepak S <deepak.s@linux.intel.com>