doc/dev: update teuthology priority guidance

Signed-off-by: Patrick Donnelly <[email protected]>

Author: batrick

doc/dev/developer_guide/testing_integration_tests/tests-integration-testing-teuthology-intro.rst

@@ -47,13 +47,22 @@ also reported on the `ceph-qa mailing list <https://ceph.com/irc/>`_.
 Testing Priority
 ----------------
 
-In brief: in the ``teuthology-suite`` command option ``-p <N>``, set the value of ``<N>`` to a number lower than 1000. An explanation of why follows.
+In brief: in the ``teuthology-suite`` command option ``-p <N>``, set the value
+of ``<N>`` to a number less than 500. An explanation of why follows.
 
 The ``teuthology-suite`` command includes an option ``-p <N>``. This option specifies the priority of the jobs submitted to the queue. The lower the value of ``N``, the higher the priority.
 
-The default value of ``N`` is ``1000``. This is the same priority value given to the nightly tests (the nightlies). Often, the volume of testing done during the nightly tests is so great that the full number of nightly tests do not get run during the time allotted for their run.
+The default value of ``N`` is ``1000``. Most nightly tests automatically
+scheduled by ``[email protected]`` are run with ``N >=
+500``. Some critical nightly tests are given higher priority, such as smoke
+tests or QA runs for an imminent major releases.
 
-Set the value of ``N`` lower than ``1000``, or your tests will not have priority over the nightly tests. This means that they might never run.
+.. note:: Often the volume of testing done during the nightly tests is so great
+          that the full number of nightly tests do not get run during the time allotted
+          for their run.
+
+Set the value of ``N`` lower than ``500`` or your tests will not have priority
+over the nightly tests. This means that they might never run.
 
 Select your job's priority (the value of ``N``) in accordance with the following guidelines:
 
@@ -79,7 +88,7 @@ Select your job's priority (the value of ``N``) in accordance with the following
    * - **150 <= N < 200**
      - Use this priority for 100 jobs or fewer that test a particular feature
        or fix.  Results are available in about 24 hours.
-   * - **200 <= N < 1000**
+   * - **200 <= N < 500**
      - Use this priority for large test runs.  Results are available in about a
        week.