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_functest: /home/opnfv/functest
20 dir_results: /home/opnfv/functest/results
21 dir_functest_conf: /home/opnfv/functest/conf
22 dir_rally_res: /home/opnfv/functest/results/rally/
23 dir_functest_data: /home/opnfv/functest/data
24 dir_vIMS_data: /home/opnfv/functest/data/vIMS
25 dir_rally_inst: ~/.rally
28 # branch and commit ID to which the repos will be reset (HEAD)
29 functest_branch: master
30 functest_commit: latest
34 rally_commit: 2c34d1896a7a9f2955a2a09531a9c3eb3f88517b
35 vims_test_branch: stable
36 vims_test_commit: latest
43 image_name: functest-img
44 image_file_name: cirros-0.3.4-x86_64-disk.img
45 image_disk_format: qcow2
47 #Public network. Optional
48 neutron_public_net_name: net04_ext
49 neutron_public_subnet_name: net04_ext__subnet
50 neutron_public_subnet_cidr: 172.16.9.0/24
51 neutron_public_subnet_start: 172.16.9.130
52 neutron_public_subnet_end: 172.16.9.254
53 #Private network for functest. Will be created by config_functest.py
54 neutron_private_net_name: functest-net
55 neutron_private_subnet_name: functest-subnet
56 neutron_private_subnet_cidr: 192.168.120.0/24
57 neutron_private_subnet_start: 192.168.120.2
58 neutron_private_subnet_end: 192.168.120.254
59 neutron_private_subnet_gateway: 192.168.120.254
60 neutron_router_name: functest-router
64 vm_flavor: m1.small #adapt to your environment
65 vm_name_1: opnfv-vping-1
66 vm_name_2: opnfv-vping-2
67 vping_private_net_name: vping-net
68 vping_private_subnet_name: vping-subnet
69 vping_private_subnet_cidr: 192.168.130.0/24
70 vping_router_name: vping-router
77 tenant_description: Tenant for Tempest test suite
79 user_password: tempest
82 deployment_name: opnfv-rally
87 tenant_description: vIMS Functionality Testing
90 image_url: 'http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img'
91 image_name: ubuntu_14.04
93 image_url: 'http://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud-1510.qcow2'
97 url: https://github.com/boucherv-orange/cloudify-manager-blueprints.git
103 keystone_username: ""
104 keystone_password: ""
105 keystone_tenant_name: ""
107 manager_public_key_name: 'manager-kp'
108 agent_public_key_name: 'agent-kp'
111 external_network_name: ""
116 file_name: 'openstack-blueprint.yaml'
117 name: "clearwater-opnfv"
118 destination_folder: "opnfv-cloudify-clearwater"
119 url: 'https://github.com/Orange-OpenSource/opnfv-cloudify-clearwater.git'
121 deployment-name: 'clearwater-opnfv'
124 os_image: ubuntu_14.04
129 external_network_name: ''
130 public_domain: clearwater.opnfv
133 onosbench_username: 'root'
134 onosbench_password: 'root'
135 onoscli_username: 'root'
136 onoscli_password: 'root'
146 test_db_url: http://213.77.62.197
148 ########################################################################
149 # This part lists the dependencies of the tests
151 # it is used to managed the complexity of the possible combination
153 # 17 projects have been declared for Brahmaputra (D Milestone)
154 # 89 testcases are associated with these 17 projects
156 # in B-Release, Functest deals with 6 companion projects:
164 # constraints may be declared at the testcase or the test project level
166 # By default we consider that all the tests can be run on any configuration
168 # we defined 3 constraints
169 # - installer (e.g. my test can be run only with installer Compass)
170 # possible values: apex, compass, fuel, joid
172 # - the controller (odl, onos, opencontrail)
174 # - the scenario (ovs, kvm, QEMU, proc) based on Fuel proposal
175 # see https://git.opnfv.org/cgit/fuel/tree/deploy/scenario/scenario.yaml
176 # e.g my test is only possible with OVS 2.3.2 on odl
177 # not fully clear as the controller may be included with the scenario
179 # In a first step, our main need is to trigger ad hox controller suite
180 # In second step we may focus with scenario parameter
182 # - either controller suite
184 # - suites that should be runnable on any conf, any scenario
186 #######################################################################
202 controller: 'opencontrail'
206 opnfv-yardstick-tc026-sdnvpn:
208 scenario: 'os_ovh_ha'
209 odl-vpn_service-tests:
211 scenario: 'os_ovh_ha'
212 openstack-neutron-bgpvpn-api-extension-tests:
214 scenario: 'os_ovh_ha'