...
Some of the tests need to install the testing tools directly on the SUT, so the SUT needs to have access to Internet.
...
Accessing the cluster
The containers are ran from a Jumpserver with access to the SUT. Some tests use ssh to connect to the cluster, some use other tools (e.g the k8s layer conformance test uses the kubeclt client). The input needed from user is specified in this guide. Before running the test, you need to manually retrieve the files needed to access the cluster. The tools needed by each test suite are specified in this guide. Below are some guidelines on how to retrieve these files.
| Tool | |||
|---|---|---|---|
| kubectl | Copy the folder ~/.kube from your Kubernetes master node to a local folder (e.g. ~/kube).
| ||
| ssh | ssh key file Copy the ssh key to access your cluster to a local folder (e.g. ~/.ssh). The location of where to get the ssh key varies based on how the installation was done. In case you are not sure where to get it, contact your cluster administrator. |
Using blucon to run the tests
Each layer has an individual container from which the tests run. The blucon script can be used to both start the container and run the tests. The tests run using the bluval tool. The tool takes as parameters the layer and the blueprint for which to run the tests. A base blueprint is given as an example here.
The blucon script can be used to both start the container and run the tests. The steps to do that are:
...
| Test suites | Access type |
|---|---|
| k8s confrormance | kubectl tool Before running the image, copy the folder ~/.kube from your Kubernetes master node to a local folder (e.g. ~/k8s_access). |
| ha | ssh key Before running the image, copy the ssh key to access your cluster to a local folder (e.g. ~/.ssh) |
The OpenStack layer
TBD