...
The results are stored inside the container in the /opt/akraino/results folder. If a volume was mounted to this folder (e.g. /home/ubuntu/results) then they can be viewed from the host where the test was ran. The results can be viewed with a browser, using the report.html file that the robot framework provides. In case of failures, the sonobuoy archive can be used to inspect all the logs
| Code Block |
|---|
ubuntu@ubuntu:~$ ls results/k8s/conformance/ 201909110859_sonobuoy_376a4ddc-4498-49fc-af2e-999242c4c245.tar.gz Conformance.Conformance.log log.html output.xml report.html |
Troubleshooting
In case of failures, the sonobuoy archive can be used to inspect all the logs. For live troubleshooting the container for a specific layer can be started with the command below:
| Code Block |
|---|
docker run -ti -v <mount-volume-to-access-the-cluster> akraino/validation:<layer>-latest /bin/sh |
Tests can be invoked directly using the bluval.py script located at /opt/akraino/validation/bluval/
Tests are located at /opt/akraino/validation/tests/ and they can be locally modified to print more output.
The OS layer
TBD
The Hardware layer
...
The Networking layer
TBD
The Kubernetes layer
| Test | 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). |
Container needs to be started with the Kubernetes access folder mounted. Optionally, the results folder can be mounted as well; this way the logs are
stored on the local server.
| Code Block |
|---|
docker run -ti -v /home/jenkins/k8s_access:/root/.kube/ \
-v /home/jenkins/k8s_results:/opt/akraino/results/ \
akraino/validation:k8s-latest -c "python3 /opt/akraino/validation/bluval/bluval.py <blueprint_name> -l k8s" |
...
| 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