From 7d6fed5dc2c8ccb27473935a21d68ca3459997f3 Mon Sep 17 00:00:00 2001
From: Boden R <bodenvmw@gmail.com>
Date: Tue, 7 Mar 2017 13:10:55 -0700
Subject: [PATCH] Clarify pep8 inclusion in periodic job

Now that we have a single hacking check factory in lib [1],
we've followed-up by enhancing the neutron-lib periodic job
to include pep8 checks (see depends on patch). This patch
makes a few doc clarifications as to the pep8 inclusion in the
job.

[1] I0a8b39052c0f81f2ecbab3923353be1537b89a65

Change-Id: I035ffa8d34b0ebdabf730e99200739365f041343
Depends-On: I9bb173071abcbc5078a3fd728c41c34bf1b83ca2
---
 doc/source/releasing.rst | 7 ++++---
 doc/source/usage.rst     | 3 ++-
 2 files changed, 6 insertions(+), 4 deletions(-)

diff --git a/doc/source/releasing.rst b/doc/source/releasing.rst
index 35bfb14..3e2ae00 100644
--- a/doc/source/releasing.rst
+++ b/doc/source/releasing.rst
@@ -22,9 +22,10 @@ that starts with DNM (Do Not Merge) to indicate that the change is just a test,
 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 against the master version of neutron-lib
+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-failure-rate?panelId=4&fullscreen>`_
+being an example). Checking Grafana's `periodic <http://grafana.openstack.org/dashboard/db/neutron-lib-failure-rate?panelId=4&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.
+before going ahead with a full blown sentinel patch. Periodic failures can be
+debugged by viewing the `periodic logs <http://logs.openstack.org/periodic>`_
diff --git a/doc/source/usage.rst b/doc/source/usage.rst
index ca6e063..fcf5805 100644
--- a/doc/source/usage.rst
+++ b/doc/source/usage.rst
@@ -55,7 +55,8 @@ To adopt neutron-lib's hacking checks:
    ``enable-extensions`` in their ``tox.ini``.
 
 #. Actively adopt neutron-lib hacking checks by running and monitoring
-   the neutron-lib periodic job (as per `stadium guidelines
+   the neutron-lib `periodic job <http://grafana.openstack.org/dashboard/
+   db/neutron-lib-failure-rate?panelId=4&fullscreen>`_ (as per `stadium guidelines
    <https://review.openstack.org/389397/>`_ and
    watching for announcements. Announcements regarding neutron-lib adopter
    hacking checks will be communicated via openstack-dev email list