...
Integrated Edge Cloud (IEC) is an important part of Akraino project. It focuses on the multi-archtecture architecture based solution on the Edge and Cloud computing areas. In this document, we will give a brief introduction an overview about IEC test frameworktesting done in CI/CD.
This document is a successor of IEC Test Document R1.
Testing of the IEC platform is done in CI/CD using the validation labs described here.
Akarino Test Group Information
Currently, 2 or 3 virtual hosts are deployed on arm64 platform by fuel (compass) tools. For all the baremetal servers, those must meet those hardware and software requirements. In addition, the access to Internet is essential required for the CI platform.
Hardware Information:
...
Attention: Only the Arm64 platform was deployed in community CI platform so far.
Test
...
description
The validation of the IEC project in CI/CD consists in several steps:
- Automatically deploy the IEC platform and perform a basic platform test
Run the validation project K8S conformance tests
Info Enabling this step is still work in progress for Release2. Logs for this steps are not yet pushed to Nexus, but the results can be seen in Jenkins at https://jenkins.akraino.org/view/iec/job/validation-enea-daily-master
- Install SEBA use-case
- Cleanup the enviroment
The IEC project tests can be divided into 2 parts. The first part is about IEC platform tests which is used for testing the basic function of Kubernetes and Container Networking interface (CNI). And the
The second part is Feature tests which is about IEC functional test for verifying IEC user cases , just like SEBA and other user cases.(e.g. SEBA).
Automatic deploy
Platform tests
In IEC project, there are 2 cases in Platform test. One is about service deployment test for verifying the basic K8s K8S network function and deployment function end to end. The other is the K8s K8S smoke check for checking K8s environments.
Deployment case
This test will verify the K8s verifies the basic function of K8S by deploying a simple Nginx server. When After the Nginx server was is deployed, the test will issue a request to the server and verify the reply which is getted got from Nginx server for checking the basic function of K8s. And it can . The test can also be started by shell scripts nginx.sh.
...
If correct, it will return OK, otherwise is Error.
...
K8S Healthcheck case (not included in CI)
The second case is K8s K8S healthcheck which is used for checking the Kubernetes environments. It creates a Guestbook application that contains redis server, 2 instances of redis slave, frontend application, frontend service and redis master service and redis slave service. The test will write an entry into the guestbook application which will store the entry into the backend redis database. Application flow must work as expected and the data written must be available to read. In the end, you can directly run it from iec/src/foundation/scripts/functest.sh scripts shell.
...
# source src/foundation/scripts/functest.sh <master-ip> #Functest case
# source src/foundation/scripts/nginx.sh #Nginx case
Conformance
...
Test
| Info |
|---|
Enabling this step is still work in progress for Release2. Logs for this steps are not yet pushed to Nexus, but the results can be seen in Jenkins at https://jenkins.akraino.org/view/iec/job/validation-enea-daily-master/) |
Test Dashboards
Single pane view of how the test score looks like for the Blue print.
...