openstack/neutron-lib
Code Issues Proposed changes

update releasing doc links for zuul v3

Browse Source 
As part of the migration to zuul v3, a few of the links have changed.
In particular:
- The periodic job failure rate in grafana is now panel 6, not 4.
- The periodic logs are no longer in a single location and thus
can't be referenced with a single link.

This patch fixes up those issues.

Change-Id: Ifb60cebab4b9a2e61a15f21f9cb4fc13d52975ee
This commit is contained in:
Boden R 2018-01-02 13:33:21 -07:00
parent e2a9c397f7
commit 0996b3fc02
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/source/contributor/releasing.rst
View File

@ -23,12 +23,11 @@ or -2, if you have the right access permissions.
It is also worth noting that every Stadium project will have a periodic job
running unit tests and pep8 against the master version of neutron-lib
(`periodic-neutron-py35-with-neutron-lib-master <http://logs.openstack.org/periodic/periodic-neutron-py35-with-neutron-lib-master/>`_
being an example). Checking Grafana's `periodic <http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate?panelId=4&fullscreen>`_
Checking Grafana's `periodic <http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate?panelId=6&fullscreen>`_
dashboard can give you a glimpse into the sanity of the integration between
neutron-lib and the Stadium projects, and can be considered the quick check
before going ahead with a full blown sentinel patch. Periodic failures can be
debugged by viewing the `periodic logs <http://logs.openstack.org/periodic>`_
debugged by viewing the `periodic logs <http://logs.openstack.org/periodic/git.openstack.org/openstack/>`_
In addition, both the API reference as well as the project docs should be
validated to ensure there are no dead links. To do so run