3 # Relative to the path where the repo is cloned:
4 dir_vping: testcases/vPing/CI/libraries/
5 dir_odl: testcases/Controllers/ODL/CI/
6 dir_rally: testcases/VIM/OpenStack/CI/libraries/
7 dir_rally_scn: testcases/VIM/OpenStack/CI/suites/
8 dir_vIMS: testcases/vIMS/CI/
9 dir_onos: testcases/Controllers/ONOS/Teston/CI/
12 dir_repos: /home/opnfv/repos
13 dir_repo_functest: /home/opnfv/repos/functest
14 dir_repo_rally: /home/opnfv/repos/rally
15 dir_repo_releng: /home/opnfv/repos/releng
16 dir_repo_vims_test: /home/opnfv/repos/vims-test
17 dir_repo_bgpvpn: /home/opnfv/repos/bgpvpn
18 dir_repo_onos: /home/opnfv/repos/onos
19 dir_repo_promise: /home/opnfv/repos/promise
20 dir_functest: /home/opnfv/functest
21 dir_results: /home/opnfv/functest/results
22 dir_functest_conf: /home/opnfv/functest/conf
23 dir_rally_res: /home/opnfv/functest/results/rally/
24 dir_functest_data: /home/opnfv/functest/data
25 dir_vIMS_data: /home/opnfv/functest/data/vIMS
26 dir_rally_inst: ~/.rally
29 # branch and commit ID to which the repos will be reset (HEAD)
30 functest_branch: master
31 functest_commit: latest
35 rally_commit: 2c34d1896a7a9f2955a2a09531a9c3eb3f88517b
36 vims_test_branch: stable
37 vims_test_commit: latest
42 promise_branch: master
43 promise_commit: latest
46 image_name: functest-img
47 image_file_name: cirros-0.3.4-x86_64-disk.img
48 image_disk_format: qcow2
50 #Public network. Optional
51 neutron_public_net_name: net04_ext
52 neutron_public_subnet_name: net04_ext__subnet
53 neutron_public_subnet_cidr: 172.16.9.0/24
54 neutron_public_subnet_start: 172.16.9.130
55 neutron_public_subnet_end: 172.16.9.254
56 #Private network for functest. Will be created by config_functest.py
57 neutron_private_net_name: functest-net
58 neutron_private_subnet_name: functest-subnet
59 neutron_private_subnet_cidr: 192.168.120.0/24
60 neutron_private_subnet_start: 192.168.120.2
61 neutron_private_subnet_end: 192.168.120.254
62 neutron_private_subnet_gateway: 192.168.120.254
63 neutron_router_name: functest-router
67 vm_flavor: m1.small #adapt to your environment
68 vm_name_1: opnfv-vping-1
69 vm_name_2: opnfv-vping-2
70 vping_private_net_name: vping-net
71 vping_private_subnet_name: vping-subnet
72 vping_private_subnet_cidr: 192.168.130.0/24
73 vping_router_name: vping-router
80 tenant_description: Tenant for Tempest test suite
82 user_password: tempest
85 deployment_name: opnfv-rally
90 tenant_description: vIMS Functionality Testing
93 image_url: 'http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img'
94 image_name: ubuntu_14.04
96 image_url: 'http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud-1510.qcow2'
100 url: https://github.com/boucherv-orange/cloudify-manager-blueprints.git
106 keystone_username: ""
107 keystone_password: ""
108 keystone_tenant_name: ""
110 manager_public_key_name: 'manager-kp'
111 agent_public_key_name: 'agent-kp'
114 external_network_name: ""
119 file_name: 'openstack-blueprint.yaml'
120 name: "clearwater-opnfv"
121 destination_folder: "opnfv-cloudify-clearwater"
122 url: 'https://github.com/Orange-OpenSource/opnfv-cloudify-clearwater.git'
124 deployment-name: 'clearwater-opnfv'
127 os_image: ubuntu_14.04
132 external_network_name: ''
133 public_domain: clearwater.opnfv
136 onosbench_username: 'root'
137 onosbench_password: 'root'
138 onoscli_username: 'root'
139 onoscli_password: 'root'
149 test_db_url: http://213.77.62.197
151 ########################################################################
152 # This part lists the dependencies of the tests
154 # it is used to managed the complexity of the possible combination
156 # 17 projects have been declared for Brahmaputra (D Milestone)
157 # 89 testcases are associated with these 17 projects
159 # in B-Release, Functest deals with 6 companion projects:
167 # constraints may be declared at the testcase or the test project level
169 # By default we consider that all the tests can be run on any configuration
171 # we defined 3 constraints
172 # - installer (e.g. my test can be run only with installer Compass)
173 # possible values: apex, compass, fuel, joid
175 # - the controller (odl, onos, opencontrail)
177 # - the scenario (ovs, kvm, QEMU, proc) based on Fuel proposal
178 # see https://git.opnfv.org/cgit/fuel/tree/deploy/scenario/scenario.yaml
179 # e.g my test is only possible with OVS 2.3.2 on odl
180 # not fully clear as the controller may be included with the scenario
182 # In a first step, our main need is to trigger ad hox controller suite
183 # In second step we may focus with scenario parameter
185 # - either controller suite
187 # - suites that should be runnable on any conf, any scenario
189 #######################################################################
205 controller: 'opencontrail'
209 opnfv-yardstick-tc026-sdnvpn:
211 scenario: 'os_ovh_ha'
212 odl-vpn_service-tests:
214 scenario: 'os_ovh_ha'
215 openstack-neutron-bgpvpn-api-extension-tests:
217 scenario: 'os_ovh_ha'