ELIOT R5 - IoT Gateway Test Document

Owned by Srinivasan Selvam
Last updated: Aug 20, 2021 by khemendra kumar
3 min read

Introduction

This document covers  Test Deployment Environment and Test Case Result for  ELIOT IoT Gateway Blueprint. 

The number of nodes in the ELIOT Cluster remains same as Release 1.0 and Release 2.0;  one virtual machine  node for ELIOT Manager and one Virtual Node for ELIOT Edge Node (IoT Gateway)

The changes include testing of the new software included in the ELIOT Platform Stack.

Akarino Test Group Information

Not Applicable

Overall Test Architecture

ELIOT Cluster Number of Nodes remains same as Release 1.0 / 2.0

  • One Node for ELIOT Manager.
  • One Node for ELIOT Edge Node.

Both the nodes are running on Virtual Machine.

In Release 1.0 the Test Environments were :-

  • ELIOT Cluster with Kubernetes  on Ubuntu OS.
  • ELIOT Cluster  with KubeEdge on Ubuntu OS

In Release 2.0 the Test Environments were :-

  • ELIOT Cluster with Kubernetes  + EdgeX Platform on Ubuntu OS.
  • ELIOT Cluster with Kubernetes  + OPC-UA on Tailored OS
  • ELIOT Cluster with KubeEdge  on Cent OS

In Release 3.0 the Test Environments are :-

  • ELIOT Cluster with Kubernetes  + EdgeX Platform on Ubuntu OS. (Integrated with Blu-Val validation and  Akraino Security Sub-committee recommended Security Tools )

In Release 4.0 the Test Environments are :-

  • ELIOT Cluster with Kubernetes  + EdgeX Platform + Edge Gallery services + AppStore + Developer Platform + k3sautomated using Ansible tool on Ubuntu OS. (Integrated with Blu-Val validation and  Akraino Security Sub-committee recommended Security Tools )

In Release 5.0 the Test Environments are :-

  • ELIOT Cluster with Kubernetes + EdgeX Platform + Edge Gallery services automated using Ansible tool on Ubuntu OS. ( Integrated with Bluval validation and Akraino Security Sub-committee recommended Security Tools )

Traffic Generator

N/A

Test API description

Some test cases are re-used from Release 2.0. Test cases are marked as inherited from Release 2.0 and New Test Cases.

Test Environment

The Test Environment for ELIOT IoTGateway Blueprint is a Virtual Machine Environment hosted on Huawei Public Cloud, which are in the same network, having public IP's.

Note: Testing in Bare-Metal environment is not done, theoretically it will function.

ELIOT Cluster with Kubernetes + EdgeX Platform on Ubuntu OS

CI Details 

For CI IoT Gateway Blueprint is using Akraino Community Jenkins Server. 

For CD, IoT Gateway 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 - IoT Gateway cluster.
  • Upload the job log to Nexus server in post-build actions

1.1 ELIOT Platform Test

Test Case 1 :

Test K8s Cluster, EDGE Gallery MEC platform , EdgeX Platform  on IOTGateway node 

Test K8s, EDGE Gallery Services on ELIOT Master node

(Inherited from Release 2.0)

Test Input :

Execute the ansible playbook command to setup the ELIOT Platform.

Test Procedure:

root@akraino-slave-0001:~# kubectl get nodes

NAME                              STATUS   ROLES   AGE  VERSIONOT platform and Soft dia

akraino-slave-0001      Ready   master   18h    v1.18.7


CI/CD Logs:

Nexus Repo Path:-

https://nexus.akraino.org/content/sites/logs/huawei/job/eliot-build/18/home/jenkins/log/

Blueprint Validation tests

Integrated with Blu-Val validation tools 

1. For K8S layer 

  • Kube-Hunter

2. For OS Layer 

  • Vuls
  • Lyns

Nexus Repo Path:-

https://nexus.akraino.org/content/sites/logs/huawei/job/eliot-security-validation-build/4/results/

K8S LAYER MANDATORY TESTS

1.1 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:-

https://nexus.akraino.org/content/sites/logs/huawei/job/eliot-security-validation-build/4/results/k8s/kube-hunter/

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:-

https://nexus.akraino.org/content/sites/logs/huawei/job/eliot-security-validation-build/4/results/os/lynis/

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:-

https://nexus.akraino.org/content/sites/logs/huawei/job/eliot-security-validation-build/4/results/os/vuls/

Feature Project Tests

Not applicable

Test Dashboards

Single pane view of how the test score looks like for the Blue print.

Total Tests

Test Executed

Pass

Fail

In Progress

44400


Additional Testing

N/A

Bottlenecks/Errata

N/A