summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2017-08-03Merge "DRAFT: remove apexlake"Ross Brattain110-11580/+4
2017-08-03Merge "replace yaml.load with yaml.safe_load"Ross Brattain9-9/+10
2017-08-02Merge "Fix adding right deb repo based on the distro we are running on"Ross Brattain2-7/+15
2017-08-02Merge "Add task-args(from yaml file) candidates in ↵Jing Lu2-1/+7
/api/v2/yardstick/testcases API"
2017-08-02Add task-args(from yaml file) candidates in /api/v2/yardstick/testcases APIchenjiankun2-1/+7
JIRA: YARDSTICK-766 We have the demand to get all task-args candidates in test case yaml file, so that user get easily change it. The response will like: { 'status': 1, 'result': { 'testcase': case content, 'args': { 'image': {'description': '', 'type': 'String'} } } } In this patch, I add jinja2schema 0.1.4 in requirements.txt. Change-Id: I450082402370add5ab29090286f026fe3cc8c36e Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-08-02Merge "Add spec cpu2006 test case"Jing Lu11-0/+538
2017-08-01test_env_action: speedup unittest, don't sleepRoss Brattain1-2/+2
Change-Id: Ib662032e5133b8fead1c6858905bd13ca40f4dd6 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-01replace yaml.load with yaml.safe_loadRoss Brattain9-9/+10
yaml.safe_load is safer, obviously. anteater will check for this template_format use specialized constructor based on yaml.SafeLoader JIRA: YARDSTICK-760 Change-Id: Ia3b0b3aa0765385a0ee472a4d83f49d424b5a77f Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-01Bugfix: port_security_enabled issueJingLu51-3/+4
JIRA: YARDSTICK-765 When port_security_enabled is not set, VMs are assigned with security group 'default'. When using 'default' security group, all egress traffic and intercommunication in the default group are allowed and all ingress from outside of the default group is dropped by default (in the default security group). This causes yardstick cannot ssh into VMs. If port_security_enabled is not set, we should still add the security group that created by yardstick to the VMs. Change-Id: Ifd22fb452e0077581b6900f8f51c4e3c342a30aa Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-31DRAFT: remove apexlakeRoss Brattain110-11580/+4
apexlake is unmaintained, so remove it From some reason orchestrator/heat.py started failing so fixup those unittests Change-Id: Ie06508b5ab7c9dcf9fdfca83e173a188a894d564 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-01Merge "bugfix: enable vlan and physical netwok able to set"Jing Lu17-1/+188
2017-08-01Merge "Add more parameters in iperf3 taml"Jing Lu1-0/+2
2017-07-31cover.sh: delete .testrepository before running coverageRoss Brattain1-4/+4
When running py27 and py3 test ran into problems with .testrepository already exists, but testr thinking it was corrupt running testr No repository found in /home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master. Create one by running "testr init". error: testr failed (3) The fix seems to be to delete .testrepository before running testr coverage Change-Id: Ib8cd3ab9d3384935380ac29ce365439c6464adc3 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-08-01Merge "Bugfix: yardstick always report 'PASS' to DB"Rex Lee1-1/+7
2017-08-01Merge "Add yardstick logo in GUI"Rex Lee15-57/+72
2017-08-01Merge "Add container ping VM test case"Jing Lu1-0/+57
2017-08-01Add yardstick logo in GUIchenjiankun15-57/+72
JIRA: YARDSTICK-767 We have yardstick logo in opnfv community. We have the demand to display it in yardstick GUI. Change-Id: Ief5807c918754e679e95ae1d1f3a769ab2d6d4b2 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-08-01Merge "add opnfv_os-odl-sfc-ha_daily.yaml test suite"Jing Lu1-0/+62
2017-07-31Merge "run_tests: don't write python bytecode"Ross Brattain1-0/+3
2017-07-31cover: another 'db type could not be determined' workaroundRoss Brattain1-0/+3
Change-Id: Ib94ff2dfc86725e5367908296b5160f9565442b8 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-31run_tests: don't write python bytecodeRoss Brattain1-0/+3
we usually disable .pyc generate during unittests Change-Id: I7d7af7c6d188f5a592d24aa90322edb217ffd8ba Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-31Merge "NSBperf: don't exit during import time"Ross Brattain1-7/+0
2017-07-31cover.sh: workaround 'db type could not be determined' bugRoss Brattain1-0/+3
https://bugs.launchpad.net/testrepository/+bug/1229445 rm -f .testrepository/times.dbm remove that file before running testr Change-Id: I178efefebe600a65d1a28beb9b01f7dfecaa4d00 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-31NSBperf: don't exit during import timeRoss Brattain1-7/+0
This was breaking testr unittests. Don't do this like this during import time, only do them in if __name__ sections, otherwise when anything else tries to import this module it exists. Change-Id: Ia17f5e1a5cbe07ab287d3b95e96489b8a6248170 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-31add opnfv_os-odl-sfc-ha_daily.yaml test suiteJingLu51-0/+62
Change-Id: I56961d143bdd723f4e957a4c02ba4127ccddadb3 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-31Merge "Testing live migration using qemu"Rex Lee4-0/+429
2017-07-31Add container ping VM test casechenjiankun1-0/+57
JIRA: YARDSTICK-769 This is demand from openretriever project(https://jira.opnfv.org/browse/CONTAINER-19). Since we have the kubernetes context now and we have first container test case. We can have a new test case that make container(k8s) ping VM(openstack). Change-Id: Ia1724130d92d447836529b370510fe1bf1738723 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-07-31Bugfix: yardstick always report 'PASS' to DBchenjiankun1-1/+7
JIRA: YARDSTICK-768 Now yardstick will not stop if test case failed, so that we can run the rest test case in the suite. CI judge task status by the cmd return code. In this way, the 'yardstick task start' cmd will always return 0. So we will always report 'PASS' to DB. In this patch I add a judgement in cmd, if the status is not 'PASS', we will raise a RuntimeError. Change-Id: I655424dd9cd3782869986963a17b24acfb340345 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-07-31Add more parameters in iperf3 tamlAce Lee1-0/+2
JIRA: YARDSTICK-755 The parameters that iperf3 testcase support now maybe insufficient in some usecase. The test case should support parameters such as: windows size and length of buffer. This work is about adding more parameters in testcase yaml file Change-Id: I8c900a4a8909d97543cf837a02c76a6aee19f439 Signed-off-by: Ace Lee <liyin11@huawei.com>
2017-07-31Add spec cpu2006 test caseJingLu512-0/+542
JIRA: YARDSTICK-764 This work is about support run SPEC CPU2006 benchmark. users must get a "cpu2006-1.2.iso" from the SPEC website, save it under the /home/opnfv/yardstick/yardstick/resources folder (e.g. /home/opnfv/yardstick/yardstick/resources/cpu2006-1.2.iso), user may also supply a runspec cfg file (e.g. /home/opnfv/yardstick/yardstick/resources/files/yardstick_spec_cpu2006.cfg). Change-Id: If4aecc1c14635a07589555196d2edc8bd37d7bdb Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-29Heat: support vnic_type in heat type contextJingLu54-8/+15
JIRA: YARDSTICK-757 Some test scenarios require VM with specific vnic type. This work is about supporting using different vnic types in heat type context. context: name: demo image: cirros-0.3.5 flavor: yardstick-flavor user: cirros placement_groups: pgrp1: policy: "availability" servers: athena: floating_ip: true placement: "pgrp1" ares: placement: "pgrp1" networks: test: cidr: '10.0.1.0/24' vnic_type: "normal" Change-Id: Ia229fda72f47b04288ea107e2d58fd3e8ac91dd9 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-29Heat: support create and attach volume in heat type contextJingLu54-0/+151
JIRA: YARDSTICK-756 Some test scenarios require VM with volume attached. This work is about supporting create and attach volume in heat type context. context: name: demo image: cirros-0.3.5 flavor: yardstick-flavor user: cirros placement_groups: pgrp1: policy: "availability" servers: athena: floating_ip: true # per-vm inline volume definition. if no volume size specified, then this # volume should be an existing volume in the openstack environment volume: yardstick-volume placement: "pgrp1" ares: # per-vm inline volume definition. if volume size is specified, then this # volume will be crated and attach to the vm volume: name: test-volume size: 10 # volume mountpoint is also configurable volume_mountpoint: /dev/vdb placement: "pgrp1" networks: test: cidr: '10.0.1.0/24' Change-Id: Ief87b313980a59eac229eb4780d93ffc929ceb66 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-29bugfix: enable vlan and physical netwok able to setrexlee877617-1/+188
Enable vlan and physical netwok able to set by parameters for heat context. It won't affect the original test case, but enable vlan to be set directly by pass task-args to command: yardstick -d task start samples/ping.yaml --task-args '{"provider": "vlan"}' JIRA: YARDSTICK-763 Change-Id: I96f96a61991cceb1506d055867a006d56689a008 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-07-29Merge "bugfix: enable vlan and physical netwok able to set"Kubi1-1/+10
2017-07-29Merge "Update NSBPerf CLI to adapt to new output format"Rex Lee1-5/+6
2017-07-28Merge "Test Case: OPNFV_YARDSTICK_TC023: VM availability during live migration"Rex Lee32-1/+1428
2017-07-28bugfix: enable vlan and physical netwok able to setrexlee87761-1/+10
enable vlan and physical netwok able to set by parameters for heat context this is a sample, if it's ok, i'll copy it to other yaml. it won't affect the original test case, but enable vlan to be set directly by pass task-args to command. yardstick -d task start samples/ping.yaml --task-args '{"provider": "vlan"}' JIRA: YARDSTICK-763 Change-Id: Ie35dac4b5e80404558a1eb45d49fa0bb6ab45a98 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2017-07-28Merge "leave port_security_enabled undefined by default"Rex Lee2-4/+6
2017-07-27Adding support for multi-dispatcherDeepak S4-6/+32
JIRA: YARDSTICK-684 This patch adds the support to enable multi-dispatcher of result. e.g. [DEFAULT] debug = False dispatcher = file, http Change-Id: Id0e1a1bba14edd899fcf5b275be1f0a091b6db77 Signed-off-by: Deepak S <deepak.s@linux.intel.com> Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-27leave port_security_enabled undefined by defaultRoss Brattain2-4/+6
some deployments don't have port security ML2 plugin enabled, so we have to leave port security undefined by default RuntimeError: Resource CREATE failed: BadRequest: resources.yardstick-TC072-19be2f60-test: Unrecognized attribute(s) 'port_security_enabled' https://build.opnfv.org/ci/user/narindergupta/my-views/view/joid/job/yardstick-joid-baremetal-daily-master/1276/console Change-Id: I69178f869f6215f42d90ea4cfb297dad3d799f83 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-27Merge "Yardstick GUI & GUI deployment"Jing Lu79-50/+8554
2017-07-27Yardstick GUI & GUI deploymentchenjiankun79-50/+8554
JIRA: YARDSTICK-758 As E release plan, we have the need of yardstick GUI. This patch is GUI front end code and deployment. The backend code is yardstick API. Change-Id: Ib15f78bcc50168c7828beff97256e9939c6da809 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-07-26Test Case: OPNFV_YARDSTICK_TC023: VM availability during live migrationchenjiankun32-1/+1428
JIRA: YARDSTICK-174 This live migration test case is based on share storage, default share storage is enabled. This test case will do some config work. And do live migration and calculate the migration time and downtime. Change-Id: I6601601edebdd0ac6434ba632b1eba9e9bd4fda0 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-07-26fix sriov/ovs-dpdk unittests on systems with fewer than 10 coresRoss Brattain4-15/+10
we need to wrap vcpupin modulo number of cores. also mock time.sleep Change-Id: I6433418a99505b469c61c81a9a023d84434fa0ee Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-07-26Bugfix: plugin remove command use "JUMP_HOST_IP" if ip is set to localJingLu51-2/+2
JIRA: YARDSTICK-762 Change-Id: Id4a94ef8bbe578944e3664e5e7c24fdf7478805b Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-26Merge "Bugfix: supoort insecure mode in checking openstack environment"Jing Lu1-1/+6
2017-07-26Bugfix: supoort insecure mode in checking openstack environmentJingLu51-1/+6
Change-Id: I18346aa177689bc995eb7d4883f4a66383e827ba Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-07-26Merge changes from topic '35521'Rex Lee19-52/+2983
* changes: Setup OVS-DPDK Standalone Context Adding new SRIOV Standalone Context
2017-07-26Merge "vnfdgen: replace yaml.load with yaml.safe_load"Rex Lee1-1/+1
2017-07-26Merge "Add intermediate variable for HA test"Rex Lee7-17/+71