...

1. Daily job:
   
   1. It is executed at INTEL POD.
   2. Requires a traffic generator (Ixia)
   3. Runs everyday in case that new change was merged into particular branch since the last daily job execution; Daily job runs duration is about 14 hours, but it can take over a day in case that VM running IxNetwork is slow. Please see FAQ section below for details.

   4. A set of performance tests is executed for OVS with DPDK support, Vanilla OVS, VPP and SRIOV. Ixia traffic generator is used to generate RFC2544 Throughput and Back2Back traffic.    

2. Merge job (similar to verify job):
   1. It is executed at INTEL POD or at Ericsson PODs.
   2. Does not require a traffic generator.
   3. Runs whenever patches are merged to the particular branch.
   4. Runs a basic set of integration testcases for OVS with DPDK support, Vanilla OVS and VPP.
   5. in case that documentation files were modified, then documentation is built.
3. Verify job (similar to merge job):
   
   1. It is executed at INTEL POD or at Ericsson PODs.
   2. Does not require a traffic generator.
   3. Runs every time a patch is pushed to gerrit. On success, the patch will be marked as verified (+1 for verification).
   4. Runs a basic set of integration testcases for OVS with DPDK support, Vanilla OVS and VPP.
   5. in case that documentation files were modified, then documentation is built

...

They are executed at POD12 or at ericsson Ericsson pods as they don't require a traffic generator. POD12 is used as a primary jenkins slave, because execution at ericsson Ericsson build machines was not reliable since other projects start to use it more extensively. It seems, that there is a clash on resources (hugepages). There was a attempt to avoid a parallel execution of VSPERF and other jobs, but it didn't help.  Contact for the Ericsson Pod: ________

FAQ

Q: Why VEFIY JOB has failed and my patch got -1 for verification?

...