summaryrefslogtreecommitdiffstats
path: root/testcases/OpenStack/vPing/vping_util.py
AgeCommit message (Collapse)AuthorFilesLines
2016-09-08make use of functest_utils.get_parameter_from_yamlSerenaFeng1-24/+23
JIRA: FUNCTEST-463 Change-Id: I1d54a65c5bfa2542f2fd3a2e408967641e6e4ac9 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-09-07remove imported FUNCTEST_REPO objectSerenaFeng1-6/+7
According to openstack style guidelines in http://docs.openstack.org/developer/hacking/ **** Do not import objects, only modules (*) **** so direct FUNCTEST_REPO import should be avoided from functest.utils.functest_utils import FUNCTEST_REPO as FUNCTEST_REPO JIRA: FUNCTEST-459 Change-Id: Iac0d07a54957cd7419391de183660ac1ce0efd49 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-09-01stop hardcoded FUNCTEST_REPO path everywhereSerenaFeng1-3/+2
functest repo is used by almost every testcase, each place we get it like: REPOS_DIR = os.getenv('repos_dir') FUNCTEST_REPO = ("%s/functest" % REPOS_DIR) provide a common interface in functest_util.py JIRA: FUNCTEST-453 Change-Id: Ie0635dacc761ed2d05b7e606530368844f32ebaf Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-09-01Merge "unify functest_yaml obtain process"Jose Lausuch1-5/+2
2016-08-31unify functest_yaml obtain processSerenaFeng1-5/+2
functest_yaml is needed in almost all of the testcases, the obtain process is the same: with open(os.environ["CONFIG_FUNCTEST_YAML"]) as f: functest_yaml = yaml.safe_load(f) f.close() abstract a method to unify the process, and provide the interface JIRA: FUNCTEST-447 Change-Id: I96a9a9962d7b466f10bbd3b5ab2495957524e22a Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-08-31Remove all logers as utils method args.Cédric Ollivier1-1/+0
As it modifies method params, it could break the testcases. JIRA: FUNCTEST-428 Change-Id: I4263d9bd812f1803e513464e3c321cc4a7281958 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2016-08-26refactor create or get image process to eliminate reduplicateSerenaFeng1-18/+5
Some places when create image is referred, they check if image exist, if exist use it directly, else create a new one. Abstract a method to integrate the process JIRA: FUNCTEST-432 Change-Id: I83d1112aa5cb0d3cdfab92fd49cd5f2c1cceff82 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-08-23delete useless image_exists in vpingSerenaFeng1-3/+1
In rally, image_exists is used to decide whether the image resource should be cleaned or not. But unlike rally, image_exists in vping is only assigned but not never be actually used. JIRA: FUNCTEST-426 Change-Id: Id2089dd2a9734ba957cc1c80d4dc31bc27907b0a Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-08-22Mend create_image() functionMichael Polenchuk1-0/+2
Change-Id: I91681736817f881ca53e5124328bd4399aa54740 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2016-08-22refactor vpingSerenaFeng1-0/+479
There are lots of common processes in vPing_userdata.py and vPing_ssh.py, abstract and refactor them. JIRA: FUNCTEST-414 Change-Id: I4cd2c635318c063319d2a3c31f9a1e512eeea6c8 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>