Introduction

KNI PAE IE is tested against 3 platforms: libvirt, aws and baremetalGoogle Cloud Platform (GCP). A typical test consist onof:

• cleaning environment
• deploying a

...

• management hub cluster via blueprint on the target platform
• deploying an industrial edge cluster via blueprint on the target platform
• letting the industrial edge cluster auto-register with the management hub and deploy its workloads from the blueprint
• destroy cluster

Overall Test Architecture

Our tests are performed

...

by Akraino Jenkins at https://jenkins.akraino.org/view/kni/.
Following the different tests per platform are explained

kni-installer-verify-binary, kni-installer-verify-installer

Those tests are executed each time that there is a change in https://gerrit.akraino.org/r/admin/repos/kni/installer. It tests the code in this client tool. The verify-binary one is testing that is possible to construct a binary from the code. The verify-installer one compiles the code of installer, and checks that is valid.
They are executed on a Centos-8g node, provided by Akraino CI

kni-blueprint-

...

ie-verify-deploy-

...

gcp

Those tests are executed each time that there is a change on https://gerrit.akraino.org/r/admin/repos/kni/blueprint-pae , on the generic and on libvirt profiles.
It executes a deployment of the cluster and applies workloads based on libvirt. All the VMs are run on a baremetal server stored inside Red Hat, connected as a Jenkins slave.
Logs are deployed on https://nexus.akraino.org/.

Following there is the architecture *:

Image Removed

* Green=Akraino dependencies, Orange=system under test, Blue=components created

kni-blueprint-pae-verify-deploy-aws

Those tests are executed each time that there is a change on https://gerrit.akraino.org/r/admin/repos/kni/blueprint-pae , on the generic and on AWS profiles.ie.
It executes a deployment of the cluster and applies workloads based on AWS. The bootstrap VM is run on a baremetal server, connected as a Jenkins Slave. The master and worker nodes are executed inside a testing AWS cluster.
Logs are deployed on https://nexus.akraino.org/.

Following there is the architecture *:

* Green=Akraino dependencies, Orange=system under test, Blue=components created

kni-blueprint-pae-verify-deploy-baremetal

Those tests are executed each time that there is a change on https://gerrit.akraino.org/r/admin/repos/kni/blueprint-pae , on the generic and on baremetal profiles.
It executes a deployment of the cluster and applies workloads based on baremetal. The bootstrap VM is run on a baremetal server, connected as a Jenkins Slave. The master and worker nodes are also baremetal slaves, running on a local lab.
Logs are deployed on https://nexus.akraino.org/.

Following there is the architecture *:

Image Removed

* Green=Akraino dependencies, Orange=system under test, Blue=components created

...

This is performed through Akraino Blueprint Validation project framework.

However the tests are currently launched manually after a cluster is deployed, integration with the CI is still pending, as we are hitting issues with the framework itself:
https://jira.akraino.org/projects/VAL/issues/VAL-108
https://jira.akraino.org/projects/VAL/issues/VAL-109
https://jira.akraino.org/projects/VAL/issues/VAL-110

...