You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

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

Akarino Test Group Information

The Test Environment consists of three topologies :

  1. ELIOT topology with Kubernetes Cluster + EdgexPlatform on Ubuntu OS
  2. ELIOT topology with Kubernetes Cluster + OPC-UA on Tailored OS
  3. ELIOT Topology with KubeEdge

Overall Test Architecture

ELIOT topology with Kubernetes Cluster.
ELIOT Manager and single ELIOT Edge Node are installed VM having Ubuntu 16.04.

In ELIOT Manager the setup.sh is executed which internally installs docker ,k8s and tests k8s deployment by deploying nginx on ELIOT Edge Node

ELIOT topology with KubeEdge

ELIOT Manager and single ELIOT Edge Node are installed VM having Ubuntu 16.04.

In ELIOT Manager Docker, K8S , KubeEdge-EdgeController is installed and in ELIOT Edge Docker and KubeEdge-EdgeCore is installed.

In the KubeEdge init command the nginx is deployed in ELIOT - Edge Core.


Traffic Generator

N/A

Test API description

Deployment Type 1 Test Environment

ELIOT Cluster Deployment on Ubuntu OS

ELIOT Platform Test

Test Case 1: Test Kubernetes cluster, EdgeX Platform  Check.

Test Input :

Execute the bootstrap script to setup the ELIOT Platform

Test Procedure:

root@akraino-slave-001:-# cd eliot/blueprints/iotgateway/script

root@akraino-slave-001:-# source setup.sh

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

NAME                              STATUS   ROLES   AGE  VERSION

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

akraino-slave-0002      Ready   <none>  18h    v1.16.0


root@akraino-slave-0001:~# kubectl get pods -o wide

NAME                                                                                           READY                         STATUS                                 RESTARTS           AGE               IP                                            NODE                                    NOMINATED            NODE READINESS GATES

edgex-config-seed                                                                    0/1                          Completed                                      0                    26h          192.168.53.74                  akraino-slave-0002                      <none>                  <none>

edgex-core-command-5fb859467f-dkbkw                    1/1                           Running                                            0                   26h          192.168.53.69                 akraino-slave-0002                       <none>                  <none>

edgex-core-consul-5b6b5c7567-jlpqz                             1/1                           Running                                            0                   26h          192.168.53.76                 akraino-slave-0002                       <none>                 <none>

edgex-core-data-67b9677944-zp7tt                                1/1                            Running                                            0                   26h          192.168.53.72                akraino-slave-0002                       <none>                <none>

edgex-core-metadata-57f7fb45f8-nzsgq                       1/1                           Running                                             0                   26h          192.168.53.73                akraino-slave-0002                      <none>                <none>

edgex-device-virtual-59674ffc4c-vrz7b                         1/1                           Running                                             1                   26h           192.168.53.77               akraino-slave-0002                       <none>               <none>

edgex-export-client-578c48cc87-m92nl                        1/1                           Running                                             0                   26h           192.168.53.70               akraino-slave-0003                       <none>                  <none>

edgex-export-distro-66c679875d-2hhb2                       1/1                           Running                                             0                   26h           192.168.53.71                akraino-slave-0003                      <none>                 <none>

edgex-mongo-676d599f54-kzp87                                     1/1                           Running                                             0                   26h           192.168.53.80                akraino-slave-0003                      <none>                  <none>

edgex-support-logging-696ff8d9fc-5hbn2                    1/1                           Running                                             0                   26h           192.168.53.81                 akraino-slave-0003                     <none>                  <none>

edgex-support-notifications-86577b7b57-7xwsc      1/1                           Running                                              0                   26h           192.168.53.75                akraino-slave-0003                      <none>                  <none>

edgex-support-rulesengine-6b5765d57f-q8bf8          1/1                           Running                                              1                   26h           192.168.53.79                akraino-slave-0003                     <none>                   <none>

edgex-support-scheduler-bc8f4fd6-42bbj                     1/1                           Running                                              0                   26h           192.168.53.78                akraino-slave-0003                      <none>                  <none>

Test Case 2: NGINX deployment verification.

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

NAME                                                              READY    STATUS     RESTARTS AGE

nginx-deployment-74d48dbfb8-kvx9q 1/1       Running           0            18h

CI/CD Logs:

Nexus Repo Path:-

https://nexus.akraino.org/content/sites/logs/huawei/blueprints/iotgateway/job/eliot-iotgateway-deploy-k8s-virtual-daily-master/221/

Conformance Test:

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

https://nexus.akraino.org/content/sites/logs/huawei/blu-val/job/eliot-deploy-virtual-daily-master-validation/13/

Deployment Type 2 Test Environment

ELIOT Deployment on Tailored OS.

ELIOT Platform Test

Test Case 1: Test Kubernetes cluster & OPC_UA Platform  Check.

Test Input :

Execute the bootstrap script to setup the ELIOT Platform

Test Procedure:

root@akraino-slave-001:-# cd eliot/blueprints/iotgateway/script

root@akraino-slave-001:-# source setup.sh

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

NAME                              STATUS   ROLES   AGE  VERSION

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

akraino-slave-0002      Ready   <none>  18h    v1.16.0

OPC-UA Platform successful installation is integrated in the setup.sh. Console log will record the successful installation message, same is recorded in nexus repo, path is shared in CI/CD Log section.

CI/CD Logs:

Nexus Repository URL :

https://nexus.akraino.org/content/sites/logs/huawei/blueprints/iotgateway/job/eliot-deploy-iotgateway-minimal-os-virtual-daily-master/65/

Deployment Type 3 Test Environment

ELIOT Deployment  with KubeEdge

CI/CD Logs:

Nexus Repository URL :

https://nexus.akraino.org/content/sites/logs/huawei/blueprints/iotgateway/job/eliot-deploy-kubeedge-ubuntu-virtual-daily-master/12/

Blueprint extension tests

Not Applicable

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

33300


Additional Testing

N/A

Bottlenecks/Errata

N/A

  • No labels