Remove CLI testing once and for all

The cli tests have been marked for removal for ~6 months and the framework was the first thing included in tempest lib. There has been more than enough time for all the projects to pick this up in the client repos. So let's remove it all! As part of this a couple of missing entries for tempest's requirements.txt were found. These dependencies were being installed by the clients so the fact they were missing was never noticed prior to this. This commit also adds these missing entries back into the requirements file. Change-Id: I4f8638f1c048bbdb598dd181f4af272ef9923806
openstack · May 7, 2015 · 464d287 · 464d287
1 parent 7af6760
commit 464d287
Show file tree

Hide file tree

Showing 22 changed files with 6 additions and 786 deletions.
diff --git a/README.rst b/README.rst
@@ -18,7 +18,7 @@ Tempest Design Principles that we strive to live by.
   incorrect assessment of their cloud. Explicit is always better.
 - Tempest uses OpenStack public interfaces. Tests in Tempest should
   only touch public interfaces, API calls (native or 3rd party),
-  public CLI or libraries.
+  or libraries.
 - Tempest should not touch private or implementation specific
   interfaces. This means not directly going to the database, not
   directly hitting the hypervisors, not testing extensions not

diff --git a/doc/source/field_guide/cli.rst b/doc/source/field_guide/cli.rst
diff --git a/etc/tempest.conf.sample b/etc/tempest.conf.sample
@@ -201,27 +201,6 @@
 #build_interval = 1
 
 
-[cli]
-
-#
-# From tempest.config
-#
-
-# enable cli tests (boolean value)
-#enabled = true
-
-# directory where python client binaries are located (string value)
-#cli_dir = /usr/local/bin
-
-# Whether the tempest run location has access to the *-manage
-# commands. In a pure blackbox environment it will not. (boolean
-# value)
-#has_manage = true
-
-# Number of seconds to wait on a CLI timeout (integer value)
-#timeout = 15
-
-
 [compute]
 
 #

diff --git a/requirements.txt b/requirements.txt
@@ -9,10 +9,8 @@ testtools>=0.9.36,!=1.2.0
 boto>=2.32.1
 paramiko>=1.13.0
 netaddr>=0.7.12
-python-glanceclient>=0.15.0
-python-cinderclient>=1.1.0
-python-heatclient>=0.3.0
 testrepository>=0.0.18
+pyOpenSSL>=0.11
 oslo.concurrency>=1.8.0,<1.9.0         # Apache-2.0
 oslo.config>=1.9.3,<1.10.0  # Apache-2.0
 oslo.i18n>=1.5.0,<1.6.0  # Apache-2.0
@@ -24,3 +22,4 @@ iso8601>=0.1.9
 fixtures>=0.3.14
 testscenarios>=0.4
 tempest-lib>=0.5.0
+PyYAML>=3.1.0
diff --git a/tempest/README.rst b/tempest/README.rst
@@ -14,7 +14,6 @@ to make this clear.
 
 | tempest/
 |    api/ - API tests
-|    cli/ - CLI tests
 |    scenario/ - complex scenario tests
 |    stress/ - stress tests
 |    thirdparty/ - 3rd party api tests
@@ -38,16 +37,6 @@ projects themselves, possibly as functional tests in their unit test
 frameworks.
 
 
-:ref:`cli_field_guide`
-----------------------
-
-CLI tests use the openstack CLI to interact with the OpenStack
-cloud. CLI testing in unit tests is somewhat difficult because unlike
-server testing, there is no access to server code to
-instantiate. Tempest seems like a logical place for this, as it
-prereqs having a running OpenStack cloud.
-
-
 :ref:`scenario_field_guide`
 ---------------------------
 

diff --git a/tempest/cli/README.rst b/tempest/cli/README.rst
diff --git a/tempest/cli/__init__.py b/tempest/cli/__init__.py
diff --git a/tempest/cli/simple_read_only/README.txt b/tempest/cli/simple_read_only/README.txt
diff --git a/tempest/cli/simple_read_only/__init__.py b/tempest/cli/simple_read_only/__init__.py
diff --git a/tempest/cli/simple_read_only/heat_templates/heat_minimal.yaml b/tempest/cli/simple_read_only/heat_templates/heat_minimal.yaml
diff --git a/tempest/cli/simple_read_only/heat_templates/heat_minimal_hot.yaml b/tempest/cli/simple_read_only/heat_templates/heat_minimal_hot.yaml
diff --git a/tempest/cli/simple_read_only/image/__init__.py b/tempest/cli/simple_read_only/image/__init__.py