neutron-fwaas: Add a non-voting job to run networking-midonet unit tests

It runs networking-midonet unit tests which includes its
neutron-fwaas integration, to expose regressions earlier and
save the effort in both of projects.  Briefly discussed in
a fwaas meeting. [1]

[1] http://eavesdrop.openstack.org/meetings/fwaas/2017/fwaas.2017-06-27-14.02.log.html#l-165

Background: Neutron-fwaas changes sometimes break networking-midonet's
fwaas v1 driver.  It's mainly due to the non-ideal way how the driver
is written.  Ideally we should have a real driver api for fwaas v1.
But the development focus has already moved to fwaas v2.

Note: This job runs the identical set of tests as the voting
counterpart, gate-networking-midonet-python35.  While it includes
tests which are not related to fwaas, it doesn't seem to worth
reducing it to minimum.  We can revisit it if it turns out to be
a problem.

Closes-Bug: #1703328
Change-Id: I0ae979ef0a34f2b75f40f8315cf3f80a0b0c07e0

grafana/neutron-fwaas.yaml

@@ -18,6 +18,7 @@ dashboard:
           targets:
             - target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-fwaas-python27{,-ubuntu-xenial}.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-fwaas-python27{,-ubuntu-xenial}.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-fwaas-python27')
             - target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-fwaas-python35.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-fwaas-python35.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-fwaas-python35')
+            - target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-cross-networking-midonet-python35.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-cross-networking-midonet-python35.{SUCCESS,FAILURE})),'24hours'), 'gate-cross-networking-midonet-python35')
           type: graph
         - title: Docs/Pep8/Functional Failure Rates (check)
           span: 4

jenkins/jobs/projects.yaml

@@ -7505,6 +7505,7 @@
     jobs:
       - coverage-jobs
       - python-jobs
+      - 'gate-cross-{name}-python35'
       - python-newton-bitrot-jobs
       - python-ocata-bitrot-jobs
       - pypi-jobs

zuul/layout.yaml

@@ -1981,7 +1981,7 @@ jobs:
     files: ^upper-constraints.txt$
 
   # Only run the cross 35 unittests on upper-constraints.txt updates
-  - name: ^gate-cross-.*-python35.*$
+  - name: ^gate-cross-(?!networking-midonet).*-python35.*$
     files: ^upper-constraints.txt$
     branch: ^master
 
@@ -1989,6 +1989,9 @@ jobs:
   - name: ^gate-cross-.*-func-.*$
     files: ^upper-constraints.txt$
 
+  - name: ^gate-cross-networking-midonet-python35
+    voting: false
+
   # Aims to break when a new version of Puppet is released
   # For now, run the jobs only on master so if the job starts to
   # break due to Puppet new major release, we will see which branch
@@ -12469,6 +12472,7 @@ projects:
       - gate-grenade-dsvm-neutron-fwaas-multinode-nv
       - gate-neutron-fwaas-v1-dsvm-tempest-multinode-nv
       - gate-neutron-fwaas-v2-dsvm-tempest-multinode-nv
+      - gate-cross-networking-midonet-python35
     gate:
       - gate-neutron-fwaas-v2-dsvm-tempest
       - gate-neutron-fwaas-v1-dsvm-tempest