Table of Contents
Introduction
This document covers both ELIOT Blueprint Use Case.
...
ELIOT Cluster Number of Nodes remains same as Release 1.0 and Release 2.0
- 1 Node - ELIOT Manager
- 1 Node - ELIOT Edge Node (uCPE)
...
- ELIOT Cluster with Kubernetes on Ubuntu OS 16.04
In Release 2.0 Test Environment was :-
- ELIOT Cluster with Kubernetes on Cent OS 7.5
In Release 3.0 Test Environment is :-
- ELIOT Cluster with Kubernetes on Cent OS 7.5
Test Environment Topology
The Test Environment consists of one topology :
...
In ELIOT Manager Docker, K8S is installed and in ELIOT Edge Docker is installed.
CI Details
For CI , SD-WAN / WAN Edge / uCPE Blueprint is using Akraino Community Jenkins Server.
For CD, SD-WAN / WAN Edge / uCPE Blueprint is using Private Huawei Lab Jenkins Server. Daily deployment build gets executed and logs are uploaded to nexus repo.
CI Jobs
- Triggered by gerrit patch creation/update, the job runs verify.sh under eliot project.
- Upload the job log to Nexus server in post-build actions
CD Jobs
- Triggered daily automatically , can also be executed manually.
- Executes an bootstrap shell script command to install the complete the environment and executes verify script to check the ELIOT - SD-WAN / WAN Edge / uCPE cluster.
- Upload the job log to Nexus server in post-build actions
Traffic Generator
N/A
Test API description
The Test cases in Release 3.0 remains same as Release 2.0; the verification is to check setup of ELIOT Cluster on Cent OS.
In this version BluVal and Security Sub-Committee mandatory test cases is integrated with the ELIOT CD environment and the logs are pushed to the Akraino Nexus Repository.
ELIOT Platform Test
Test Case 1: Test Kubernetes cluster check.
Test Input :
Execute the bootstrap script to setup the ELIOT Platform
...
akraino-slave-0002 Ready <none> 18h v1.16.0
Test Case 2:
The Test inputs
There should be a nginx.yaml configuration files which is used for deploying the Nginx on ELIOT Edge Node.
Test Procedure
The setup.sh script will deploy nginx server in the ELIOT Edge Node after Kubernetes Installation.
Expected output
It will check nginx deployment and result the details in the log.
Test Results
root@akraino-slave-0001:~# kubectl get pods
...
nginx-deployment-74d48dbfb8-kvx9q 1/1 Running 0 18h
CI/CD Logs:
Nexus Repo Path:-
Blueprint Validation tests
Integrated with Blu-Val validation tools
1. For K8S layer
- Sonobuoy
- Kube-Hunter
2. For OS Layer
- Vuls
- Lyns
Nexus Repo Path:-
K8S LAYER MANDATORY TESTS
1.1 Conformance Test:
(New Test Case)
Test Execution Step :
Blu-Val Validation test suite Kubernetes conformance test case is executed on ELIOT Platform
Test Result :
All Test cases are passed.
CI / CD Logs
Logs are pushed in nexus repo:-
1.2 Kube-Hunter
(New Test Case)
Test Execution Step :
Blu-Val Validation test suite kube-hunter test case is executed on ELIOT Platform
Test Result :
All critical Test cases are passed.
CI / CD Logs :
Logs are pushed in nexus repo:-
OS LAYER MANDATORY TESTS
2.1 Lynis
(New Test Case)
Test Execution Step :
Blu-Val Validation test suite Lynis test case is executed on ELIOT Platform
Test Result :
All critical Test cases are passed.
CI / CD Logs :
Logs are pushed in nexus repo:-
2.2 Vuls
(New Test Case)
Test Execution Step :
Blu-Val Validation test suite Lynis test case is executed on ELIOT Platform
Test Result :
All critical Test cases are passed.
CI / CD Logs :
Logs are pushed in nexus repo:-
Feature Project Tests
Work In Progress
...