From 745934320d7262e176b7c87a9a3a1e5fdc5d13ba Mon Sep 17 00:00:00 2001 From: Zac Dover Date: Wed, 17 Feb 2021 03:45:49 +1000 Subject: [PATCH] doc/dev: removing workbench docs (part 2) This removes a paragraph in the section "How Integration Tests Are Run" that described ceph-workbench. ceph-workbench is deprecated, so that paragraph is now gone. Signed-off-by: Zac Dover --- .../tests-integration-testing-teuthology-intro.rst | 9 --------- 1 file changed, 9 deletions(-) diff --git a/doc/dev/developer_guide/testing_integration_tests/tests-integration-testing-teuthology-intro.rst b/doc/dev/developer_guide/testing_integration_tests/tests-integration-testing-teuthology-intro.rst index 9e0bb4c8740..c5ae16fc397 100644 --- a/doc/dev/developer_guide/testing_integration_tests/tests-integration-testing-teuthology-intro.rst +++ b/doc/dev/developer_guide/testing_integration_tests/tests-integration-testing-teuthology-intro.rst @@ -164,15 +164,6 @@ non-trivial task, it `is` possible. Here are `some notes `_ to get you started if you decide to go this route. -If you have access to an OpenStack tenant, you have another option: the -`teuthology framework`_ has an OpenStack backend, which is documented `here -`__. -This OpenStack backend can build packages from a given git commit or -branch, provision VMs, install the packages and run integration tests -on those VMs. This process is controlled using a tool called -``ceph-workbench ceph-qa-suite``. This tool also automates publishing of -test results at http://teuthology-logs.public.ceph.com. - Running integration tests on your code contributions and publishing the results allows reviewers to verify that changes to the code base do not cause regressions, or to analyze test failures when they do occur. -- 2.39.5