This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
brahmaputra_testing_page [2016/01/15 22:53] Ashlee Young [Table] |
brahmaputra_testing_page [2016/01/26 10:13] Fatih Degirmenci [Jenkins Job Structure] update the jenkins project type to freestyle |
||
---|---|---|---|
Line 118: | Line 118: | ||
| 3 | bm odl_l2-ha | IPv6 | GENESIS-72 to bypass the gap in ODL Lithium that doesn't support IPv6 L3 Routing | IPv6 | see Apex comment | | | IPv6 | see Apex comment | | | 3 | bm odl_l2-ha | IPv6 | GENESIS-72 to bypass the gap in ODL Lithium that doesn't support IPv6 L3 Routing | IPv6 | see Apex comment | | | IPv6 | see Apex comment | | ||
| 4 | virt odl_l2-ha | IPv6 | see Apex comment on scenario 3 | IPv6 | see Apex comment on scenario 3 | IPv6 | see Apex comment on scenario 3 | IPv6 | see A.3 note | | | 4 | virt odl_l2-ha | IPv6 | see Apex comment on scenario 3 | IPv6 | see Apex comment on scenario 3 | IPv6 | see Apex comment on scenario 3 | IPv6 | see A.3 note | | ||
- | | 5 | virt onos-ha | ONOSFW | | | | ONOSFW | | ONOSFW | | | + | | 9 | virt ODL Beryllium with SFC, GBP, and OVSDB SouthBound. OVS with NSH. | Apex | | | | Fuel/SFC | | | | |
- | | 9 | virt ODL Beryllium with SFC, GBP, and OVSDB SouthBound. OVS with NSH. | | | | | Fuel/SFC | | | | | + | |
| 10 | bm VSPERF | | | | | Fuel | | | | | | 10 | bm VSPERF | | | | | Fuel | | | | | ||
| 11 | bm, nosdn-dpdk_ovs * Ubuntu 14.0.4 * No ODL Backend * networking-ovs-dpdk mech driver * libvirt > 1.2.10 * Qemu 2.1+ * One NIC must be provided solely for OVS-DPDK for the private network (and I guess in case DVR is enabled two interfaces needs to be reserved – Public and private - not sure yet). | | | | | OVSNFV | FuncTest tests only (initially) | | | | | 11 | bm, nosdn-dpdk_ovs * Ubuntu 14.0.4 * No ODL Backend * networking-ovs-dpdk mech driver * libvirt > 1.2.10 * Qemu 2.1+ * One NIC must be provided solely for OVS-DPDK for the private network (and I guess in case DVR is enabled two interfaces needs to be reserved – Public and private - not sure yet). | | | | | OVSNFV | FuncTest tests only (initially) | | | | ||
Line 129: | Line 128: | ||
| 18 | virt os-opencontrail-nofeature-ha | Apex | | Compass | | N/A | | JOID | | | | 18 | virt os-opencontrail-nofeature-ha | Apex | | Compass | | N/A | | JOID | | | ||
| 19 | bm os-opencontrail-nofeature-ha | Apex | | Compass | | N/A | | JOID | | | | 19 | bm os-opencontrail-nofeature-ha | Apex | | Compass | | N/A | | JOID | | | ||
+ | | 20 | virt, Ubuntu 14, ONOS with OpenStack neutron-l3-agent being disabled | | | ONOSFW | | | | | | | ||
+ | | 21 | bm, Ubuntu 14, ONOS with OpenStack neutron-l3-agent being disabled | | | ONOSFW | | | | | | | ||
+ | | 22 | virt, CentOS 7, with ONOS neutron-l3-agent being disabled | ONOSFW | | | | | | | | | ||
+ | | 23 | virt, Ubuntu 14, ONOS with OpenStack neutron-l3-agent being disabled | | | | | ONOSFW | | ONOSFW | | | ||
+ | |||
Line 182: | Line 186: | ||
===== Jenkins Job Structure ===== | ===== Jenkins Job Structure ===== | ||
- | Jenkins jobs switched using Jenkins MultiJob plugin in order to have an easy way to see what happened with a specific execution, trigger and control related jobs together. | + | Jenkins jobs use Freestyle project type. |
Please take a look at the examples from [[https://build.opnfv.org/ci/job/fuel-os-odl_l2-nofeature-ha-opnfv-jump-2-daily-brahmaputra/ | this]] or [[https://build.opnfv.org/ci/job/joid-os-ocl-nofeature-ha-intel-pod6-daily-master/ | this]] link to see job structuring. | Please take a look at the examples from [[https://build.opnfv.org/ci/job/fuel-os-odl_l2-nofeature-ha-opnfv-jump-2-daily-brahmaputra/ | this]] or [[https://build.opnfv.org/ci/job/joid-os-ocl-nofeature-ha-intel-pod6-daily-master/ | this]] link to see job structuring. | ||
- | In this new job structure, there is 1 parent job per scenario-pod-branch, controlling the executions of deploy, functest, and yardstick jobs. Parent jobs are used for setting triggers, triggering jobs manually or automatically, or grouping related jobs together. | + | In this new job structure, there is 1 main job per scenario-pod-branch, controlling the executions of deploy, functest, and yardstick jobs. Main jobs are used for setting triggers, triggering jobs manually or automatically. |
There is 1 job for each of the deploy, functest, and yardstick for pod-branch and these jobs take scenario short names from parent job and do what they are supposed to do with given scenario on the POD. | There is 1 job for each of the deploy, functest, and yardstick for pod-branch and these jobs take scenario short names from parent job and do what they are supposed to do with given scenario on the POD. | ||
Line 250: | Line 254: | ||
| QTIP | QTIP test suite | Dell POD3 | Fuel | Daily Jenkins Job for QTIP test suite. | | | QTIP | QTIP test suite | Dell POD3 | Fuel | Daily Jenkins Job for QTIP test suite. | | ||
| VSPERF | VSPERF test suite | Intel POD3 | None | Daily Jenkins Job for VSPERF test suite. | | | VSPERF | VSPERF test suite | Intel POD3 | None | Daily Jenkins Job for VSPERF test suite. | | ||
+ | | bottlenecks | rubbos and VSTF test suite | Huawei | Compass | Daily Jenkins Job; Responsible for testing: bottlenecks; Responsible for documentation: bottlenecks | |