Remove refs to former binaries

Change-Id: I9008d21bb42c913e347df90eda814e638d5cdedd
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>

2 files changed, 0 insertions, 115 deletions

diff --git a/docs/testing/user/userguide/index.rst b/docs/testing/user/userguide/index.rst
index bfe8c95b2..ecbc7f5fd 100644
--- a/docs/testing/user/userguide/index.rst
+++ b/docs/testing/user/userguide/index.rst
@@ -12,7 +12,6 @@ Functest User Guide
    intro.rst
    test_overview.rst
    test_details.rst
-   runfunctest.rst
    test_results.rst
    reporting.rst
    troubleshooting.rst
diff --git a/docs/testing/user/userguide/runfunctest.rst b/docs/testing/user/userguide/runfunctest.rst
deleted file mode 100644
index aea8c02b7..000000000
--- a/docs/testing/user/userguide/runfunctest.rst
+++ /dev/null
@@ -1,114 +0,0 @@
-.. SPDX-License-Identifier: CC-BY-4.0
-
-Executing Functest suites
-=========================
-
-As mentioned in the :ref:`functest-install-guide`, Alpine docker containers
-have been introduced in Euphrates.
-Tier containers have been created.
-Assuming that you pulled the container and your environement is ready, you can
-simply run the tiers by typing (e.g. with functest-healthcheck)::
-
-  sudo docker run --env-file env \
-      -v $(pwd)/openstack.creds:/home/opnfv/functest/conf/env_file  \
-      -v $(pwd)/images:/home/opnfv/functest/images  \
-      opnfv/functest-healthcheck
-
-You should get::
-
-  +----------------------------+------------------+---------------------+------------------+----------------+
-  |         TEST CASE          |     PROJECT      |         TIER        |     DURATION     |     RESULT     |
-  +----------------------------+------------------+---------------------+------------------+----------------+
-  |      connection_check      |     functest     |     healthcheck     |      00:02       |      PASS      |
-  |         api_check          |     functest     |     healthcheck     |      03:19       |      PASS      |
-  |     snaps_health_check     |     functest     |     healthcheck     |      00:46       |      PASS      |
-  +----------------------------+------------------+---------------------+------------------+----------------+
-
-You can run functest-healcheck, functest-smoke, functest-features,
-functest-components and functest-vnf.
-
-The result tables show the results by test case, it can be::
-
-  * PASS
-  * FAIL
-  * SKIP: if the scenario/installer does not support the test case
-
-
-Manual run
-==========
-If you want to run the test step by step, you may add docker option then run
-the different commands within the docker.
-
-Considering the healthcheck example, running functest manaully means::
-
-  sudo docker run -ti --env-file env \
-    -v $(pwd)/openstack.creds:/home/opnfv/functest/conf/env_file  \
-    -v $(pwd)/images:/home/opnfv/functest/images  \
-    opnfv/functest-healthcheck /bin/bash
-
-The docker prompt shall be returned. Then within the docker run the following
-commands::
-
-  $ source /home/opnfv/functest/conf/env_file
-
-Tier
-----
-Each Alpine container provided on the docker hub matches with a tier.
-The following commands are available::
-
-  # functest tier list
-    - 0. healthcheck:
-    ['connection_check', 'api_check', 'snaps_health_check']
-  # functest tier show healthcheck
-  +---------------------+---------------+--------------------------+-------------------------------------------------+------------------------------------+
-  |        TIERS        |     ORDER     |         CI LOOP          |                   DESCRIPTION                   |             TESTCASES              |
-  +---------------------+---------------+--------------------------+-------------------------------------------------+------------------------------------+
-  |     healthcheck     |       0       |     (daily)|(weekly)     |     First tier to be executed to verify the     |     connection_check api_check     |
-  |                     |               |                          |           basic operations in the VIM.          |         snaps_health_check         |
-  +---------------------+---------------+--------------------------+-------------------------------------------------+------------------------------------+
-
-To run all the cases of the tier, type::
-
-  # functest tier run healthcheck
-
-Testcase
---------
-Testcases can be listed, shown and run though the CLI::
-
-  # functest testcase list
-   connection_check
-   api_check
-   snaps_health_check
-  # functest testcase show api_check
-  +-------------------+--------------------------------------------------+------------------+---------------------------+
-  |     TEST CASE     |                   DESCRIPTION                    |     CRITERIA     |         DEPENDENCY        |
-  +-------------------+--------------------------------------------------+------------------+---------------------------+
-  |     api_check     |     This test case verifies the retrieval of     |       100        |       ^((?!lxd).)*$       |
-  |                   |       OpenStack clients: Keystone, Glance,       |                  |                           |
-  |                   |      Neutron and Nova and may perform some       |                  |                           |
-  |                   |     simple queries. When the config value of     |                  |                           |
-  |                   |       snaps.use_keystone is True, functest       |                  |                           |
-  |                   |     must have access to the cloud's private      |                  |                           |
-  |                   |                     network.                     |                  |                           |
-  +-------------------+--------------------------------------------------+------------------+---------------------------+
-  # functest testcase run connection_check
-  ...
-  # functest run all
-
-You can also type run_tests -t all to run all the tests.
-
-Note the list of test cases depend on the installer and the scenario.
-
-Note that the flavors for the SNAPS test cases are able to be configured giving
-new metadata values as well as new values for the basic elements of flavor
-(i.e. ram, vcpu, disk, ephemeral, swap etc).
-The snaps.flavor_extra_specs dict in the config_functest.yaml file could be
-used for this purpose.
-
-Reporting results to the test Database
-======================================
-In OPNFV CI we collect all the results from CI. A test API shall be available
-as well as a test database `[16]`_.
-
-
-.. _`[16]`: http://testresults.opnfv.org/test/