the new vping scenario does not use the userdata/cloudinit functions
JIRA: FUNCTEST-3
Change-Id: Ia535a50a9cfd50d520b87c2dd9195747a61b0f1f
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
(cherry picked from commit
4475765f05a24e14f1d90db28941ff5ba5ca1be7)
python ${FUNCTEST_REPO_DIR}/testcases/vPing/CI/libraries/vPing2.py \
--debug ${report}
;;
+ "vping_userdata")
+ info "Running vPing test using userdata/cloudinit.... "
+ python ${FUNCTEST_REPO_DIR}/testcases/vPing/CI/libraries/vPing.py \
+ --debug ${report}
+ ;;
"odl")
info "Running ODL test..."
neutron_ip=$(keystone catalog --service identity | grep publicURL | cut -f3 -d"/" | cut -f1 -d":")
# and if vPing is failing is usually not needed to continue...
test_exec_priority:
1: vping
- 2: tempest
- 3: odl
- 4: onos
- 5: ovno
- #6: doctor
- 7: promise
- #8: policy-test
+ 2: vping_userdata
+ 3: tempest
+ 4: odl
+ 5: onos
+ 6: ovno
+ #7: doctor
+ 8: promise
#9: odl-vpn_service-tests
#10: opnfv-yardstick-tc026-sdnvpn
#11: openstack-neutron-bgpvpn-api-extension-tests
functest:
vims:
vping:
+ vping_userdata:
tempest:
rally:
odl:
git_version = functest_utils.get_git_branch(REPO_PATH)
pod_name = functest_utils.get_pod_name(logger)
functest_utils.push_results_to_db(TEST_DB,
- "vPing",
+ "vPing_userdata",
logger, pod_name, git_version,
payload={'timestart': start_time_ts,
'duration': duration,