aboutsummaryrefslogtreecommitdiffstats
path: root/testcases/functest_utils.py
AgeCommit message (Expand)AuthorFilesLines
2016-01-13Merge "Fix dns problem on E/// pod"boucherv1-4/+20
2016-01-13Fix dns problem on E/// podboucherv1-4/+20
2016-01-13Remove references to foreman installer.jose.lausuch1-1/+1
2016-01-12Cleanup functionality improvedViktor Tikkanen1-4/+10
2016-01-11Add mechanism to check whether the test can be run or not according to the sc...Morgan Richomme1-12/+131
2016-01-07Searching for shared private networksViktor Tikkanen1-2/+2
2016-01-05Using shared private networkViktor Tikkanen1-0/+10
2016-01-04Update cinder volume quota for new tenant 'vIMS'grakiss1-0/+13
2015-12-30Merge "Update orchestrator (cloudify) version from 3.2 to 3.3"boucherv1-1/+2
2015-12-28Support for removing hanging portsViktor Tikkanen1-0/+13
2015-12-27Update orchestrator (cloudify) version from 3.2 to 3.3boucherv1-1/+2
2015-12-23Add 'check if file exists' when creating the glance imagejose.lausuch1-2/+7
2015-12-14OpenStack cleanup scriptjose.lausuch1-1/+117
2015-12-09Create a common network for functest for all the testsjose.lausuch1-0/+11
2015-12-07condensing python code in utils check_credentialsDan Radez1-19/+2
2015-11-30Add functions to retrieve POD name in FunctestMorgan Richomme1-0/+15
2015-10-29Fix error when deleting the network in vPing test.jose.lausuch1-0/+7
2015-10-28vIMS test integration and move "push_results_to_db" methodboucherv1-0/+18
2015-10-13Fix version number returnMorgan Richomme1-2/+1
2015-10-13add functions in utils and fix vPingMorgan Richomme1-38/+98
2015-10-09Bugfix: urllib-->urllib2.jose.lausuch1-1/+1
2015-10-07Dockerfile for Functestjose.lausuch1-1/+1
2015-10-05vIMS deployment and cleanupboucherv1-2/+38
2015-10-02Add get_networks_list function in functest_utils.pyjose.lausuch1-20/+33
2015-09-18Adding some methods on functest_utils.pyunknown1-0/+87
2015-09-15Remove OS_REGION_NAME from OpenStack credentials checkjose.lausuch1-4/+0
2015-06-18functet_utils: bugfix check_internet_connectivity exceptjose.lausuch1-1/+1
2015-06-18replace default web site for testing internet connectivityMorgan Richomme1-1/+1
2015-06-03functest_utils.py : bugfix: logg-->loggerjose.lausuch1-1/+1
2015-06-02vPing.py: Fixed IPs for VMs, Not DHCPjose.lausuch1-0/+14
2015-05-30Improvementsjose.lausuch1-0/+231
ately 5 hours. (The time may vary due to different | | | VM cpu configurations) | | | | +--------------+--------------------------------------------------------------+ |references | spec_cpu_2006_ | | | | | | ETSI-NFV-TST001 | | | | +--------------+--------------------------------------------------------------+ |pre-test | To run and install SPEC CPU 2006, the following are | |conditions | required: | | | * For SPECint 2006: Both C99 and C++98 compilers are | | | installed in VM images; | | | * For SPECfp 2006: All three of C99, C++98 and Fortran-95 | | | compilers installed in VM images; | | | * At least 4GB of disk space availabile on VM. | | | | | | gcc 4.8.* and g++ 4.8.* version have been tested in Ubuntu | | | 14.04, Ubuntu 16.04 and Redhat Enterprise Linux 7.4 image. | | | Higher gcc and g++ version may cause compiling error. | | | | | | For more SPEC CPU 2006 dependencies please visit | | | (https://www.spec.org/cpu2006/Docs/techsupport.html) | | | | +--------------+--------------------------------------------------------------+ |test sequence | description and expected result | | | | +--------------+--------------------------------------------------------------+ |step 1 | cpu2006-1.2.iso has been saved under the yardstick/resources | | | folder (e.g. /home/opnfv/repos/yardstick/yardstick/resources | | | /cpu2006-1.2.iso). Additionally, to use your custom runspec | | | config file you can save it under the yardstick/resources/ | | | files folder and specify the config file name in the | | | runspec_config parameter. | | | | +--------------+--------------------------------------------------------------+ |step 2 | Upload SPEC CPU 2006 ISO to the target VM using scp and | | | install SPEC CPU 2006. | | | | +--------------+--------------------------------------------------------------+ |step 3 | Connect to the target server using SSH. | | | If custom runspec config file is used, copy this file from | | | yardstick to the target VM via the SSH tunnel. | | | | +--------------+--------------------------------------------------------------+ |step 4 | SPEC CPU 2006 benchmark is invoked and SPEC CPU 2006 metrics | | | are generated. | | | | +--------------+--------------------------------------------------------------+ |step 5 | Text, HTML, CSV, PDF, and Configuration file outputs for the | | | SPEC CPU 2006 metrics are fetched from the VM and stored | | | under /tmp/result folder. | | | | +--------------+--------------------------------------------------------------+ |test verdict | None. SPEC CPU 2006 results are collected and stored. | | | | +--------------+--------------------------------------------------------------+