Age | Commit message (Collapse) | Author | Files | Lines |
|
* Update docs/submodules/yardstick from branch 'master'
- Disable VNF deploy by default
Change-Id: I27bcc41c855f34fb1fd0332fc24e7bf0b2af4ec2
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "NSB PROX test hang fixes"
- NSB PROX test hang fixes
The PROX tests were hanging in the duration
runner.
These are fixes for various errors:
raise error in collect_kpi if VNF is down
move prox dpdk_rebind after collectd stop
fix dpdk nicbind rebind to group by drivers
prox: raise error in collect_kpi if the VNF is down
prox: add VNF_TYPE for consistency
sample_vnf: debug and fix kill_vnf
pkill is not matching some executable names,
add some debug process dumps and try switching
back to killall until we can find the issue
sample_vnf: add default timeout, so we can override
default 3600 SSH timeout
collect_kpi is the point at which we check
the VNFs and TGs for failures or exits
queues are the problem make sure we aren't silently blocking on
non-empty queues by canceling join thread in subprocess
fixup duration runner to close queues
and other attempt to stop duration runner
from hanging
VnfdHelper: memoize port_num
resource: fail if ssh can't connect
at the end of 3600 second test our ssh connection
is dead, so we can't actually stop collectd
unless we reconnect
fix stop() logic to ignore ssh errors
Change-Id: I6c8e682a80cb9d00362e2fef4a46df080f304e55
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "exec_tests: remove releng clone code"
- exec_tests: remove releng clone code
we bind-mount the credentials into the container
so we don't need to clone releng
Change-Id: I838745a1470015a693f1801c93b930e8df06ef4b
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Ensure that at least one handler is available"
- Ensure that at least one handler is available
https://jira.opnfv.org/browse/YARDSTICK-773?filter=-3
Remove dependency of yardstick on utils methods
Change-Id: Iadf502364a7f08c279a8f0d17d7e45e8047f4066
Signed-off-by: Edward MacGillivray <edward.s.macgillivray@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "runners: add timeout to queue put"
- runners: add timeout to queue put
we don't want to block the test waiting to put KPIs
Add moderate timeout. In case we do timeout, it
doesn't matter if we drop intermitten KPIs
Change-Id: I049c785355993e6b286748a5c897d54dd2923dc9
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Enable multi-port perf in trex as TG
set TRex -c option for threads per port based on
hardware number of queues.
We can't auto-detect number of queues and we can't
use more than one thread per core on systems with single-queue
interfaces, so move the option to the config file
options:
tg_0:
queues_per_port: 2
also enable trex debug by removing >/dev/null redirection
options:
tg_0:
trex_server_debug: true
Change-Id: I46da187849282bf28f4ef5b333e1ae890e202768
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "add collectd resource node capability"
- add collectd resource node capability
allow manually adding collectd nodes using Node context.
if a node is present with a collectd config dict then
we can create a ResourceProfile object for it
and connect to collectd.
example
nodes:
-
name: compute_0
role: Compute
ip: 1.1.1.1
user: root
password: r00t
collectd:
interval: 5
plugins:
ovs_stats: {}
Change-Id: Ie0c00fdb58373206071daa1fb13faf175c4313e0
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "ansible: add grub.cfg hugepages regexp replace"
- ansible: add grub.cfg hugepages regexp replace
when building the image in chroot we can't run
update-grub of grub-mkconfig because both commands
probe for root partitions, which doesn't work
in the chroot.
Instead we manually regexp replace the kernel boot
line in /boot/**/grub*.cfg
Change-Id: I31fac2a3db4d1d044f11357b1715119066509676
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Optimize Core usage for the sampleVNFs"
- Optimize Core usage for the sampleVNFs
Change-Id: I80aa7e796b9ca4c4881c78310860e293a4a75560
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- load_images.sh: Add missing ssh_options
Empty ssh_options led to ssh login failure, which stopped the whole
script.
Change-Id: I8374a30a02b14d04eb0f623a0c58d7ebed77a589
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "CI: add new test cases into CI so they can have result"
- CI: add new test cases into CI so they can have result
Change-Id: Ib2b165c41121b29b2af378dc420c2360786de3f0
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Enabling multi_VM & multi port launch in standalone context"
- Enabling multi_VM & multi port launch in standalone context
new context names:
- SRIOV - StandaloneSriov
- OvsDpdk - StandaloneOvsDpdk
- Seperate helper, libvirt, server info class
- Allow multi-port and multi-VM support.
Change-Id: I3c65e4535082fa0e2f4c6ee11c3bca9ccfdc01b8
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Martin Banszel <martinx.banszel@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "drain runner queue and undo cancel_join_thread"
- drain runner queue and undo cancel_join_thread
Sometimes the runners can hang. Initially
debugging lead to the queue join thread, so I thought
we could cancel all the join threads and everything would be okay.
But it turns out canceling the queue join threads can lead
to corruption of the queues, so when we go to drain the queues
the task hangs.
But it also turns out that we were not properly draining
the queues in the task process. We were waiting for all
the runners to exit, then draining the queues.
This is bad and will cause the queues to fill up and hang
and/or drop data or corrupt the queues.
The proper fix seems to be to draining the queues in a
loop before calling join with a timeout.
Also modified the queue drain loops to no block on queue.get()
Revert "cancel all queue join threads"
This reverts commit 75c0e3a54b8f6e8fd77c7d9d95decab830159929.
Revert "duration runner: add teardown and cancel all queue join threads"
This reverts commit 7eb6abb6931b24e085b139cc3500f4497cdde57d.
Change-Id: Ic4f8e814cf23615621c1250535967716b425ac18
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Grafana Dashboard update for Prox Tests"
- Grafana Dashboard update for Prox Tests
JIRA: YARDSTICK-802
Updated the Grafana dashboards to collect KPI's
correctly & incorporate scale up changes in topology
Influx-db stores the KPI’s fields as: <TG><Port><kpi>
TG has changed from : tg__1 to tg__0
VNF has changed from : vnf__1 to vnf__0
Change-Id: I3bd8be61210906bc4de95c9b1986033572d93277
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Prox L3FWD 2-port test fix
JIRA: YARDSTICK-802
Updated the handle config for l3fwd 2 port test
The tx and rx descripters is removed as they
were not there in original DATS config.
The BM test was dropping packets beacuse of this.
Change-Id: I40d113267cbb3376a772b5a5aaecf74bea9d06fb
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Fix src/dst ip update in ixia configuration"
- Fix src/dst ip update in ixia configuration
Change-Id: I03976c182e164a512a5ef48ad20928f27451c3f6
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Adding example testcase to enable multiport support for http"
- Adding example testcase to enable multiport support for http
Change-Id: I780aa3ea6b04df08baffb5ee5beff66bdc37f37e
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "NSB: cancel all queue join threads"
- NSB: cancel all queue join threads
In some cases we are blocking in base.Runner join() because the
queues are not empty
call cancel_join_thread to prevent the Queue from blocking the
Process exit
https://docs.python.org/3.3/library/multiprocessing.html#all-platforms
Joining processes that use queues
Bear in mind that a process that has put items in a queue will wait
before terminating until all the buffered items are fed by the
"feeder" thread to the underlying pipe. (The child process can call
the cancel_join_thread() method of the queue to avoid this behaviour.)
This means that whenever you use a queue you need to make sure that
all items which have been put on the queue will eventually be removed
before the process is joined. Otherwise you cannot be sure that
processes which have put items on the queue will terminate. Remember
also that non-daemonic processes will be joined automatically.
Warning
As mentioned above, if a child process has put items on a queue (and
it has not used JoinableQueue.cancel_join_thread), then that process
will not terminate until all buffered items have been flushed to the
pipe.
This means that if you try joining that process you may get a deadlock
unless you are sure that all items which have been put on the queue
have been consumed. Similarly, if the child process is non-daemonic
then the parent process may hang on exit when it tries to join all its
non-daemonic children.
cancel_join_thread()
Prevent join_thread() from blocking. In particular, this prevents the
background thread from being joined automatically when the process
exits – see join_thread().
A better name for this method might be allow_exit_without_flush(). It
is likely to cause enqueued data to lost, and you almost certainly
will not need to use it. It is really only there if you need the
current process to exit immediately without waiting to flush enqueued
data to the underlying pipe, and you don’t care about lost data.
Change-Id: I61f11a3b01109d96b7a5445c60f1e171401157fc
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "code inspection fixes: test_pktgen"
- code inspection fixes: test_pktgen
Change-Id: I05cb069984b7674924cfcb1ed023048c0aa0c444
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "duration runner: add teardown and cancel all queue join threads"
- duration runner: add teardown and cancel all queue join threads
calculate timeout once
catch exceptions in benchmark.teardown()
In some cases we are blocking in base.Runner join() because the
queues are not empty
call cancel_join_thread to prevent the Queue from blocking the
Process exit
https://docs.python.org/3.3/library/multiprocessing.html#all-platforms
Joining processes that use queues
Bear in mind that a process that has put items in a queue will wait
before terminating until all the buffered items are fed by the
"feeder" thread to the underlying pipe. (The child process can call
the cancel_join_thread() method of the queue to avoid this behaviour.)
This means that whenever you use a queue you need to make sure that
all items which have been put on the queue will eventually be removed
before the process is joined. Otherwise you cannot be sure that
processes which have put items on the queue will terminate. Remember
also that non-daemonic processes will be joined automatically.
Warning
As mentioned above, if a child process has put items on a queue (and
it has not used JoinableQueue.cancel_join_thread), then that process
will not terminate until all buffered items have been flushed to the
pipe.
This means that if you try joining that process you may get a deadlock
unless you are sure that all items which have been put on the queue
have been consumed. Similarly, if the child process is non-daemonic
then the parent process may hang on exit when it tries to join all its
non-daemonic children.
cancel_join_thread()
Prevent join_thread() from blocking. In particular, this prevents the
background thread from being joined automatically when the process
exits – see join_thread().
A better name for this method might be allow_exit_without_flush(). It
is likely to cause enqueued data to lost, and you almost certainly
will not need to use it. It is really only there if you need the
current process to exit immediately without waiting to flush enqueued
data to the underlying pipe, and you don’t care about lost data.
Change-Id: If7b904a060b9ed68b7def78c851deefca4e0de5d
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- cancel all queue join threads
In some cases we are blocking in base.Runner join() because the
queues are not empty
call cancel_join_thread to prevent the Queue from blocking the
Process exit
https://docs.python.org/3.3/library/multiprocessing.html#all-platforms
Joining processes that use queues
Bear in mind that a process that has put items in a queue will wait
before terminating until all the buffered items are fed by the
"feeder" thread to the underlying pipe. (The child process can call
the cancel_join_thread() method of the queue to avoid this behaviour.)
This means that whenever you use a queue you need to make sure that
all items which have been put on the queue will eventually be removed
before the process is joined. Otherwise you cannot be sure that
processes which have put items on the queue will terminate. Remember
also that non-daemonic processes will be joined automatically.
Warning
As mentioned above, if a child process has put items on a queue (and
it has not used JoinableQueue.cancel_join_thread), then that process
will not terminate until all buffered items have been flushed to the
pipe.
This means that if you try joining that process you may get a deadlock
unless you are sure that all items which have been put on the queue
have been consumed. Similarly, if the child process is non-daemonic
then the parent process may hang on exit when it tries to join all its
non-daemonic children.
cancel_join_thread()
Prevent join_thread() from blocking. In particular, this prevents the
background thread from being joined automatically when the process
exits – see join_thread().
A better name for this method might be allow_exit_without_flush(). It
is likely to cause enqueued data to lost, and you almost certainly
will not need to use it. It is really only there if you need the
current process to exit immediately without waiting to flush enqueued
data to the underlying pipe, and you don’t care about lost data.
Change-Id: I345c722a752bddf9f0824a11cdf52ae9f04669af
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "dpdk: pciutils and lspci is required for dpdk-devbind.py"
- dpdk: pciutils and lspci is required for dpdk-devbind.py
Change-Id: I8529f33d849fc659b557e1d19761c0765ebda57e
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "replace ansible modules"
- replace ansible modules
Change-Id: Ia7c1ce781075142910a6c618a9a23f34a710dfe9
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Adapt getting the image architecture to mcp"
- Adapt getting the image architecture to mcp
The part which gets the image architecture still uses the old fuel command.
Adapted the script to use the mcp command.
JIRA: ARMBAND-285
Change-Id: Iddce77c3a856ea11f9994861151db89a402e735e
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "bugfix: tc054 default value is wrong"
- bugfix: tc054 default value is wrong
management route ip is not common in most SUTs, so it should
be removed.
also huawei pod1 ipmi info should updated so this test case
can be added into ci later
Change-Id: I3a29c59c473ee7087d4d61753ffc955b061571fb
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Remove checkno.png and checkyes.png due to license issue"
- Remove checkno.png and checkyes.png due to license issue
JIRA: YARDSTICK-817
Since checkno.png and checkyes.png is not Apache-2 license based.
so we need to remove them.
Change-Id: I40dd303fb54a3736ca969ac1c186d2cd23408436
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Auto create ixia config based on the traffic profile
Change-Id: I031cc7f24f0c0816eb577a4d1606a714f68a5f83
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "NSB: ignore VNF node if there is no VNF model"
- NSB: ignore VNF node if there is no VNF model
Change-Id: I571289c744441a6114c6d45ac6cbd7cfc0dafef2
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Adjusted IPs in some prox tests.
Change-Id: Iff39fa5b90d1ae5534ce1fff31dfb84c1e47340c
Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "add collectd ansible"
- add collectd ansible
required DPDK fixes to enable building collectd with dpdkstats
need /usr/lib/dpdk-pmd symlinks
Compiling all this code requies more space than the default ubuntu
cloud-image, so we need to resize the cloud image somehow
Change-Id: Ib39fc94ba8101ca1aebc7d2a710be88b0338f7c3
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Switched to stable/euphrates for samplevnfs projext
Change-Id: I0305c263740c25bdfa3bb2667838ca2b75d33ba0
Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "vnf_generic: Fix str object has no attribute items"
- vnf_generic: Fix str object has no attribute items
When an IP range is specified in src_ip/dst_ip like:
src_ip:
- '152.16.100.180-152.16.100.181'
yardstick would return str object has no attribute items error.
This change will return the IP range as is if type is str.
Change-Id: I3b097777f0d85b0600207157bebba18987ea2275
Signed-off-by: Dino Simeon Madarang <dinox.madarang@intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Added hw_vif_multiqueue_enabled metadata to the added samplevnfs image in OpenStack.
Change-Id: Iad1dce6b0d0a1c010aa62f2fdf54c5d0560ed0c7
Signed-off-by: Maciej Skrocki <maciej.skrocki@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Addition of Prox NSB BNG and BNG-QoS test"
- Addition of Prox NSB BNG and BNG-QoS test
JIRA: YARDSTICK-802
Added Prox BNG and BNG-QoS Test
- The tests supports BM, Openstack Heat
- Supports 4 ports
- Test added for BNG traffic profile
- Fixed the Prox heat test cases with
proper upstream and downstream links
- Grafana Dashboard for BNG & BNG-QoS added
- Increased the test Duration to 300
TODO:
- Test does not Terminate correctly
Update:
Added new helper class for run_test: Genric, MPLS
and BNG tests.
Change-Id: Ib40811bedb45a3c3030643943f32679a4044e076
Signed-off-by: Abhijit Sinha <abhijit.sinha@intel.com>
Signed-off-by: Edward MacGillivray <edward.s.macgillivray@intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "collectd: add config file templates as package_data"
- collectd: add config file templates as package_data
needed for pkg_resources.resource_string
Change-Id: Ief7a8fcd88fd6d371851a26e1559351963979e68
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Get node IPs and IDs according to env"
- Get node IPs and IDs according to env
Extract node IPs and IDs for each node having a controller or compute
role (name starting with the "cmp" or "ctl" prefix) and add them into
the $pod_yaml file, analogous to the previous implementation.
Since node IDs are expected to be unique and integers (condition that
does not match the salt node ID format), they are substituted with an
incremented index for each controller/compute node in the environment.
Change-Id: Id90626edc3f098bd96343336b2be179721dee5a1
Signed-off-by: Catalina Focsa <catalina.focsa@enea.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Create test suite for Euphrates release
JIRA: YARDSTICK-814
Test suite:
"opnfv_os-odl-fdio-ha_daily.yaml",
"opnfv_os-odl-dvr-noha_daily.yaml",
"opnfv_os-odl-sfc-noha_daily.yaml"
are missing in yardstick-apex-baremetal-daily-euphrates job.
We need to create them.
Change-Id: I6d8bbeb17cd887776f1f3b401ec80523ea90d3c1
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "[PATCH] Patch for Yardstick arm64 netperf_install.bash"
- [PATCH] Patch for Yardstick arm64 netperf_install.bash
Change-Id: Ic384c4603e7482f150fd4c4d2d6a6448a45ddb9e
Signed-off-by: Trevor Tao <trevor.tao@arm.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "collectd: write config file from Jinja2 template"
- collectd: write config file from Jinja2 template
We have the collectd.conf inside the python package
so instead of copying it from various places,
write the template directly to the remote system.
collectd: read collect.conf template with pkgresources
read the collectd.conf file as a string directly
and upload without creating temp file
use Jinja2 template, disable failing plugins
use proper Jinja2 template, disable the plugins that
were failing to load and blocking startup
add support for per-testcase collectd.conf config
using YAML
add support for custom interval, default is 25 seconds
Change-Id: Id904f7b7c9f41a9dd7adf5dfa06c064d65c25d2d
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Terminate the run traffic if initiated after traffic is closed
Change-Id: I89fc4bccb5b5a0d49d804fca72b59e53ff77a805
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Adding multi-port support for ixia taffic generator"
- Adding multi-port support for ixia taffic generator
Change-Id: Ic8aa130f3cdc7bd8dec39d06a6b824340bf658b2
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Fix vPE VNF characterization issues."
- Fix vPE VNF characterization issues.
Change-Id: Ia934128777d2839f6d2b940857c266fc3e2bd4a1
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Enable IP_ROUTING for netperf UDP_STREAM test"
- Enable IP_ROUTING for netperf UDP_STREAM test
To avoid the following ERROR when netperf test between
2 different subnets:
ERROR netperf: send_omni: send_data failed: Network is unreachable
For detail, please see:
https://serverfault.com/questions/802320/netperf-iptables-\
masquerade-network-unreachable
Or:
https://stackoverflow.com/questions/11981480/error-in-running-\
netperf-udp-stream-over-openvpn
Change-Id: I62b202844861440deaf3bf0f65b41561bd87ae87
Signed-off-by: Trevor Tao <trevor.tao@arm.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Read user & password from yardstick.conf in Grafana configuration"
- Read user & password from yardstick.conf in Grafana configuration
JIRA: YARDSTICK-812
Currently grafana data source configuration is hardcoding .
It is a risk.
so I read it from yardstick.conf.
Change-Id: I8a9c8afbce6c4534fc43a0bfb5c56d67a8b59db0
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "bugfix: tc055 fail due to options with no value"
- bugfix: tc055 fail due to options with no value
JIRA: YARDSTICK-816
Change-Id: Ib7eb411b940775915c6c9f87ac5cdc9825069467
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Add nodeSelector to enable selecting the desired Kubernetes running node when creating containers for Kubernetes context"
- Add nodeSelector to enable selecting the desired
Kubernetes running node when creating containers for
Kubernetes context
For example, a yaml file may looks like:
servers:
host:
image: xxx
command: /bin/bash
nodeSelector:
xxx: yyy
Synchronously change the unit test for this function
Change-Id: If74c9dad9b1a70395bb79f34708a0fde04e7e650
Signed-off-by: Trevor Tao <trevor.tao@arm.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- task: fixup s/exe_info/exc_info
JIRA: YARDSTICK-785
Change-Id: Ib37498e8df6a520f1d03256b73346fcedab3a177
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "Log each test case status in a task"
- Log each test case status in a task
JIRA: YARDSTICK-785
Currently if one test case failed, we will log error.
But if one case success, we do not have any tips.
We need log success when one case success.
Change-Id: I0f41ac55f2569f44b787133e3f2594a5c5547f4a
Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "tg_rfc2544_ixia: log exceptions and fix list iter"
- tg_rfc2544_ixia: log exceptions and fix list iter
Change-Id: Ia9722604b7c8ae23e784e780f113d012de544d4b
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
* Update docs/submodules/yardstick from branch 'master'
- Merge "bugfix: tc025 should use ipmi to poweroff"
- bugfix: tc025 should use ipmi to poweroff
if it use shutdown, it'll take several minutes to shutdown,
leads to the ipmi power on command fails
Change-Id: I74b61325cbcc3a6ec070d2fa103accf84f29b0fa
Signed-off-by: root <limingjiang@huawei.com>
|