From bb313eecf9c7cfa2269126b2fcc0d31b4db74d08 Mon Sep 17 00:00:00 2001 From: Thomas Bechtold Date: Tue, 22 Oct 2019 10:50:36 +0200 Subject: [PATCH] docs: Fix link to ceph/qa suites in intro_testers.rst According to [1], ceph-qa-suite is deprecated (last commit is from 2016) and the QA suites are now in the ceph git repo in the qa/ directory. So point to that directory. [1] https://github.com/ceph/ceph-qa-suite/ --- docs/intro_testers.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/intro_testers.rst b/docs/intro_testers.rst index aae0272cc..d5361af26 100644 --- a/docs/intro_testers.rst +++ b/docs/intro_testers.rst @@ -17,10 +17,10 @@ Terminology =========== In the abstract, each set of tests is defined by a `suite`. All of our suites -live in the `ceph-qa-suite repository -`__, in the `suites` subdirectory. Each -subdirectory in `suites` is a suite; they may also have "sub-suites" which may -aid in scheduling, for example, tests for a specific feature. +live in the `ceph` git repository in the `qa/suites/ directory +`__ . +Each subdirectory in `suites` is a suite; they may also have "sub-suites" which +may aid in scheduling, for example, tests for a specific feature. In concrete terms, a `run` is what is created by assembling the contents of a `suite` into a number of `jobs`. A `job` is created by assembling a number of @@ -31,10 +31,11 @@ Each `job` definition contains a list of `tasks` to execute, along with `roles`. `Roles` tell `teuthology` how many nodes to use for each `job` along with what functions each node will perform. -To go into more depth regarding suite design, see `ceph-qa-suite`'s `README`. +To go into more depth regarding suite design, see the `README +`__. One example of this is the `smoke -`__ suite. +`__ suite. Scheduling -- 2.47.3