openstack/project-config
Code Issues Proposed changes
1b7cd80f90
project-config/grafana/neutron.yaml

103 lines
18 KiB
YAML
Raw Normal View History

Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
dashboard:
title: Neutron Failure Rate
rows:
- title: Description
height: 100px
panels:
- title: Description
content: |
**This dashboard is managed by [Grafyaml](http://docs.openstack.org/infra/system-config/grafyaml.html).**
If you would like to make changes to this dashboard, please see the grafana directory in [project-config](https://git.openstack.org/cgit/openstack-infra/project-config/tree/grafana/neutron.yaml).
type: text
- title: Graphs
height: 320px
panels:
- title: Unit Tests Failure Rates (Check queue)
span: 4
targets:
grafana: In Neutron dashboard split Xenial and Trusty graphs Previously jobs that used "or expression" tripled, while only one showed data, the rest remained on constant zero line. Also all three lines had the same label. The patch removes usage of "{-ubuntu-trusty,-ubuntu-xenial}" and creates two definitions instead. This way it's clear what job is running which distribution. Change-Id: Ia9251b4597921995f310ad1c8363fbd1fa714479
2016-11-22 04:34:43 -05:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-python27-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-python27-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-python27-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-python27-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-python27-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-python27-ubuntu-xenial')
Fix neutron unit test job names in grafana dashboard The neutron unit test jobs no longer have '-constraints' in their names. Change-Id: I1e8ee502b0e562087391e27c1cc935756bd879aa
2016-04-12 07:30:38 -04:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-python34.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-python34.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-python34')
Append ubuntu-xenial to gate-neutron-python27 for Neutron Grafana This is the new job's name. Also include py35 graphs as these are up and running. Change-Id: Ida17eb5589a8f4cebe5f763d526e6cfefbafa63a
2016-07-28 18:10:08 -07:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-python35.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-python35.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-python35')
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
type: graph
- title: Unit Tests Failure Rates (Gate queue)
span: 4
targets:
grafana: In Neutron dashboard split Xenial and Trusty graphs Previously jobs that used "or expression" tripled, while only one showed data, the rest remained on constant zero line. Also all three lines had the same label. The patch removes usage of "{-ubuntu-trusty,-ubuntu-xenial}" and creates two definitions instead. This way it's clear what job is running which distribution. Change-Id: Ia9251b4597921995f310ad1c8363fbd1fa714479
2016-11-22 04:34:43 -05:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-neutron-python27-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-neutron-python27-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-python27-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-neutron-python27-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-neutron-python27-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-python27-ubuntu-xenial')
Fix neutron unit test job names in grafana dashboard The neutron unit test jobs no longer have '-constraints' in their names. Change-Id: I1e8ee502b0e562087391e27c1cc935756bd879aa
2016-04-12 07:30:38 -04:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-neutron-python34.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-neutron-python34.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-python34')
Fix queue for py35 Neutron unit test job Change-Id: I01b46b1d3b43eb8254a8601e83a5a570a9001106
2016-08-08 15:04:15 -07:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-neutron-python35.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-neutron-python35.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-python35')
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
type: graph
grafana: added a dashboard with periodic jobs for neutron Among others, we include python jobs that validate neutron unit tests against oslo libraries from master instead of pypi. This will hopefully raise visibility for the new failures that would affect neutron unit tests when next oslo library releases will land PyPI and upper-constraints.txt. Change-Id: I0b1f67657cd8f29e34dee85b12e88af90067e62b
2016-04-19 00:23:05 +02:00
- title: Periodic jobs
span: 4
targets:
User right pipeline for neutron periodic jobs The periodic pipeline is where the stats counts for these jobs are located. Change-Id: I55f7a7eb7f39588777d11ec1ac2ff37debae7af2
2016-05-04 16:23:50 -07:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.periodic.job.periodic-neutron-py27-with-oslo-master.FAILURE),sum(stats_counts.zuul.pipeline.periodic.job.periodic-neutron-py27-with-oslo-master.{SUCCESS,FAILURE})),'24hours'), 'periodic-neutron-py27-with-oslo-master')
Move py34-with-oslo-master jobs to xenial Use py35 instead of py35 and run all jobs on xenial. Update everywhere for the change. Change-Id: Iac709afe104b8242b8a99946f823afb8a310533c
2016-09-27 19:49:48 +02:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.periodic.job.periodic-neutron-py35-with-oslo-master.FAILURE),sum(stats_counts.zuul.pipeline.periodic.job.periodic-neutron-py35-with-oslo-master.{SUCCESS,FAILURE})),'24hours'), 'periodic-neutron-py35-with-oslo-master')
Move periodic-python-jobs-with-neutron-lib-master to xenial Use xenial as node - and py35 as environment - for these jobs that run on master. We have switched the py34 job already to py35 with xenial. Update grafana for the change. Update tox environment to use a variable. Change-Id: Iadc4e03a4176a83e97c3b166c6043516ac57bcd8
2016-09-27 16:22:57 +02:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.periodic.job.periodic-neutron-py35-with-neutron-lib-master.FAILURE),sum(stats_counts.zuul.pipeline.periodic.job.periodic-neutron-py35-with-neutron-lib-master.{SUCCESS,FAILURE})),'24hours'), 'periodic-neutron-py35-with-neutron-lib-master')
Add periodic check for neutron on postgres This change adds a periodic job that runs on the master branch that aims at catching breaking DB changes for PostGres deployments. Change-Id: I02142ba178daf5ae5abea63ffb3d676022d17e14
2016-12-08 15:17:46 -08:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.periodic.job.periodic-tempest-dsvm-neutron-pg-full-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.periodic.job.periodic-tempest-dsvm-neutron-pg-full-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'periodic-tempest-dsvm-neutron-pg-full-ubuntu-xenial')
Add periodic check for neutron functional job It helps assess the stability of the job over time. Change-Id: I4c04e3a95a1ef9c0f03d4f348b4daf32bd5a8928
2017-01-27 08:38:05 -08:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.periodic.job.periodic-neutron-dsvm-functional-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.periodic.job.periodic-neutron-dsvm-functional-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'periodic-neutron-dsvm-functional-ubuntu-xenial')
grafana: added a dashboard with periodic jobs for neutron Among others, we include python jobs that validate neutron unit tests against oslo libraries from master instead of pypi. This will hopefully raise visibility for the new failures that would affect neutron unit tests when next oslo library releases will land PyPI and upper-constraints.txt. Change-Id: I0b1f67657cd8f29e34dee85b12e88af90067e62b
2016-04-19 00:23:05 +02:00
type: graph
grafana: split neutron integrated gate dashboard For some reason, sometimes we don't see all targets in this dashboard. We suspect we hit some internal limitation of Grafana. Let's split the dashboard into two separate pieces: one for grenade and another one for tempest jobs. It is beneficial to have two separate dashboards for different job types anyway. Change-Id: I32b3219168d1417f7623561bbb04e73e665ddfc4
2016-07-25 19:15:59 +02:00
- title: Integrated Tempest Failure Rates (Gate queue)
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
span: 4
targets:
grafana: In Neutron dashboard split Xenial and Trusty graphs Previously jobs that used "or expression" tripled, while only one showed data, the rest remained on constant zero line. Also all three lines had the same label. The patch removes usage of "{-ubuntu-trusty,-ubuntu-xenial}" and creates two definitions instead. This way it's clear what job is running which distribution. Change-Id: Ia9251b4597921995f310ad1c8363fbd1fa714479
2016-11-22 04:34:43 -05:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-full-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-full-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-full-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-full-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-full-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-full-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-full-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-full-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-full-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-full-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-full-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-full-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-neutron-dsvm-api-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-neutron-dsvm-api-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-dsvm-api-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-neutron-dsvm-api-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-neutron-dsvm-api-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-dsvm-api-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-dvr-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-dvr-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-dvr-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-dvr-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-dvr-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-dvr-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-linuxbridge-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-linuxbridge-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-linuxbridge-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial')
grafana: split neutron integrated gate dashboard For some reason, sometimes we don't see all targets in this dashboard. We suspect we hit some internal limitation of Grafana. Let's split the dashboard into two separate pieces: one for grenade and another one for tempest jobs. It is beneficial to have two separate dashboards for different job types anyway. Change-Id: I32b3219168d1417f7623561bbb04e73e665ddfc4
2016-07-25 19:15:59 +02:00
type: graph
- title: Integrated Grenade Failure Rates (Gate queue)
span: 4
targets:
Add -ubuntu-trusty to gate-grenade-dsvm Change-Id: I89c3dcbf58033bf471f3bc296de36a43447fb65c
2016-08-25 18:31:58 -07:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-ubuntu-trusty')
Append -ubuntu-xenial prefix to some grafana trends for neutron The suffix was added to most jobs, but some trends were still using job names without it, which made the trends vanish from dashboards due to no events to track. Change-Id: I409189807d66ee5a886f3f1b6bf247a22bcc2ab1
2017-03-06 01:59:03 +00:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-multinode-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-multinode-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-multinode-ubuntu-xenial')
grafana: In Neutron dashboard split Xenial and Trusty graphs Previously jobs that used "or expression" tripled, while only one showed data, the rest remained on constant zero line. Also all three lines had the same label. The patch removes usage of "{-ubuntu-trusty,-ubuntu-xenial}" and creates two definitions instead. This way it's clear what job is running which distribution. Change-Id: Ia9251b4597921995f310ad1c8363fbd1fa714479
2016-11-22 04:34:43 -05:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-multinode-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-multinode-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-multinode-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-multinode-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-multinode-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-multinode-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.gate.job.gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial')
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
type: graph
Add neutron-identity-v3-only-full-nv to Grafana for Neutron Before making this voting, let's keep an eye on its failure rate. Change-Id: I6ab28e392022e8572f3946d70e4aeff6886fe840
2016-07-13 10:12:37 -07:00
- title: API/Functional/Fullstack Failure Rates/KeystoneV3 (Check queue)
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
span: 4
targets:
grafana: In Neutron dashboard split Xenial and Trusty graphs Previously jobs that used "or expression" tripled, while only one showed data, the rest remained on constant zero line. Also all three lines had the same label. The patch removes usage of "{-ubuntu-trusty,-ubuntu-xenial}" and creates two definitions instead. This way it's clear what job is running which distribution. Change-Id: Ia9251b4597921995f310ad1c8363fbd1fa714479
2016-11-22 04:34:43 -05:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-api-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-api-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-dsvm-api-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-api-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-api-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-dsvm-api-ubuntu-xenial')
Introduce functional/fullstack Neutron Xenial jobs These jobs are part of experimental queue for now, until we are confident enough to switch check queue for using Xenial as well. Change-Id: Ice5a6561fe4fee9f98a6a92307f9392b37e28497
2016-08-29 13:14:19 +02:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-functional-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-functional-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-dsvm-functional-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-fullstack-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-fullstack-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-dsvm-fullstack-ubuntu-trusty')
Add neutron-identity-v3-only-full-nv to Grafana for Neutron Before making this voting, let's keep an eye on its failure rate. Change-Id: I6ab28e392022e8572f3946d70e4aeff6886fe840
2016-07-13 10:12:37 -07:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-identity-v3-only-full-nv.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-identity-v3-only-full-nv.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-identity-v3-only-full-nv')
Neutron: Move Xenial functional/fullstack tests to check queue We are aproaching to point where all gaps in functional/fullstack tests are resolved [1]. Once the patch is merged, we can move these jobs to check queue to get them tested more often before we replace trusty jobs. [1] Icc9d9811e6fc1935966241ed499c5e597a675877 Change-Id: Ibfc9a236d8b74a96746c81325567b997e4b87468
2016-11-15 19:12:26 +01:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-functional-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-functional-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-dsvm-functional-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-fullstack-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-neutron-dsvm-fullstack-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-neutron-dsvm-fullstack-ubuntu-xenial')
Introduce functional/fullstack Neutron Xenial jobs These jobs are part of experimental queue for now, until we are confident enough to switch check queue for using Xenial as well. Change-Id: Ice5a6561fe4fee9f98a6a92307f9392b37e28497
2016-08-29 13:14:19 +02:00
type: graph
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
- title: DVR/LinuxBridge/Multi-node Failure Rates (Check queue)
span: 4
targets:
Append -ubuntu-xenial prefix to some grafana trends for neutron The suffix was added to most jobs, but some trends were still using job names without it, which made the trends vanish from dashboards due to no events to track. Change-Id: I409189807d66ee5a886f3f1b6bf247a22bcc2ab1
2017-03-06 01:59:03 +00:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-full-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-full-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-full-ubuntu-xenial')
grafana: In Neutron dashboard split Xenial and Trusty graphs Previously jobs that used "or expression" tripled, while only one showed data, the rest remained on constant zero line. Also all three lines had the same label. The patch removes usage of "{-ubuntu-trusty,-ubuntu-xenial}" and creates two definitions instead. This way it's clear what job is running which distribution. Change-Id: Ia9251b4597921995f310ad1c8363fbd1fa714479
2016-11-22 04:34:43 -05:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-dvr-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-dvr-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-dvr-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-dvr-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-dvr-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-dvr-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-linuxbridge-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-linuxbridge-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-linuxbridge-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-linuxbridge-ubuntu-xenial')
Append -ubuntu-xenial prefix to some grafana trends for neutron The suffix was added to most jobs, but some trends were still using job names without it, which made the trends vanish from dashboards due to no events to track. Change-Id: I409189807d66ee5a886f3f1b6bf247a22bcc2ab1
2017-03-06 01:59:03 +00:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-multinode-full-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-multinode-full-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-multinode-full-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-dvr-multinode-full-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-dvr-multinode-full-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-dvr-multinode-full-ubuntu-xenial')
grafana: In Neutron dashboard split Xenial and Trusty graphs Previously jobs that used "or expression" tripled, while only one showed data, the rest remained on constant zero line. Also all three lines had the same label. The patch removes usage of "{-ubuntu-trusty,-ubuntu-xenial}" and creates two definitions instead. This way it's clear what job is running which distribution. Change-Id: Ia9251b4597921995f310ad1c8363fbd1fa714479
2016-11-22 04:34:43 -05:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-multinode-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-multinode-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-multinode-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-multinode-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-multinode-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-multinode-ubuntu-xenial')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-trusty')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-dvr-multinode-ubuntu-xenial')
neutron: move grenade multinode linuxbridge job into check queue It's still non-voting, we are moving it into check queue to collect more stats before making it voting. Change-Id: Ia359377f8dc26ec69d6e0f39291dfa4b020bc31c
2016-12-09 19:08:25 +00:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-linuxbridge-multinode-ubuntu-xenial-nv.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-grenade-dsvm-neutron-linuxbridge-multinode-ubuntu-xenial-nv.{SUCCESS,FAILURE})),'24hours'), 'gate-grenade-dsvm-neutron-linuxbridge-multinode-ubuntu-xenial-nv')
Neutron: Fix DVR multinode job in Grafana DVR multinode job was by a mistake added among other jobs from Integrated gate queue. It runs only in the check queue as non-voting and this patch puts it to the correct spot. Change-Id: Ibc002070a7b354daadca72aebc13c419c1973f02
2017-01-23 10:32:03 +01:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv')
neutron: Move linuxbridge Neutron scenario to -nv check queue Similarly to OVS job running Neutron scenarios [1] this patch moves linuxbridge job from experimental to check queue as non-voting. New failure trend for Grafana has been added too to monitor stability. [1] Ib71417c0b79d4f14becdaec2dcd2c08fa8bd2737 Change-Id: I98bb3b73b55f9edbfa8a5906946450031c6a63dc
2017-02-17 12:21:00 +01:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-scenario-linuxbridge-ubuntu-xenial-nv.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-tempest-dsvm-neutron-scenario-linuxbridge-ubuntu-xenial-nv.{SUCCESS,FAILURE})),'24hours'), 'gate-tempest-dsvm-neutron-scenario-linuxbridge-ubuntu-xenial-nv')
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
type: graph
Revert "grafana: track new rally py35 job for neutron" This reverts commit 774f8cb2f71dd38f013413f09937a1958b179ea5. Now that we revert the patch that broke grafana, we should also revert to the old grafana dashboard definition too. Change-Id: I013492dd81642b6f291c6f8b2a722641b451532a
2017-02-24 19:16:17 +00:00
- title: Rally Failure Rates
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
span: 4
targets:
Revert "grafana: track new rally py35 job for neutron" This reverts commit 774f8cb2f71dd38f013413f09937a1958b179ea5. Now that we revert the patch that broke grafana, we should also revert to the old grafana dashboard definition too. Change-Id: I013492dd81642b6f291c6f8b2a722641b451532a
2017-02-24 19:16:17 +00:00
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-rally-dsvm-neutron-neutron-ubuntu-trusty.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-rally-dsvm-neutron-neutron-ubuntu-trusty.{SUCCESS,FAILURE})),'24hours'), 'gate-rally-dsvm-neutron-neutron-ubuntu-trusty (check)')
- target: alias(movingAverage(asPercent(transformNull(stats_counts.zuul.pipeline.check.job.gate-rally-dsvm-neutron-neutron-ubuntu-xenial.FAILURE),sum(stats_counts.zuul.pipeline.check.job.gate-rally-dsvm-neutron-neutron-ubuntu-xenial.{SUCCESS,FAILURE})),'24hours'), 'gate-rally-dsvm-neutron-neutron-ubuntu-xenial (check)')
Add Neutron Failure Rate dashboard to Grafana It is incredibly useful to see failure rates over time and Grafana is an excellent tool for this. This patch creates a dashboard that captures the failure rates of Neutron check and gate jobs. Change-Id: If7552e10bcafd17e245b3a5de839bcaa0ef12b97
2016-02-10 18:09:10 -08:00
type: graph
Copy Permalink