Introduction

ICN Pod Topology

Jenkins Information

N/A. 

This Blueprint currently does not has jobs in the public or private Jenkins clusters.

Akraino Test Group Information

N/A

Overall Test Architecture

Test Architecture

Test Bed

Pod Topology

ICN Master Bare-metal Deployment Verifier

Bare-metal deployment

Test Framework

All components are tested with end-to-end testing

Test description

The 'Multitenant Secure Cloud Native Platform' uses Kata Containers to launch non-infrastructure pods. In order to use Kata Containers, Containerd is used in Kubernetes instead of the default docker-shim. 

To launch Kata Containers pods in a Kubernetes cluster, we make use of a mutating admission controller that annotates Pods with the Kata RuntimeClass. Kubernetes and Containerd are previously configured with this RuntimeClass. 

Testing

CI Testing:

Bashate:

`bashate` test is used to check the shell scripts coding style. i.e. Trailing Whitespace. We find all files with suffix '.sh' and run `bashate` against the files. './cmd/bpa-operator/vendor/' directory is excluded.

Golang testing:

BPA Operator: 

• The BPA operator has unit tests using the go framework. The unit tests check the following;
  • Job is created with the right job name for KUD installation.
  • The job metadata has the right cluster name
  • Expected error is produced when a host with the specified MAC address is not found
  • Expected error is produced when no dhcp lease is found for the specified host

BPA Rest Agent: 

• Currently, automated unit tests are implemented using the Go testing framework.

CD Verifier(end-to-end testing):

All the test case are tested as follows:

Metal3:

Metal3 verifier will check all the servers are provisioned, Metal3 verifier check the status of the Baremetal servers for every 60 second for the provisioning status.

BPA Operator:

BareMetal host  Provisioning

• The bpa_verifier.sh script get the MAC addresses and IP addresses of the 2 VMs provisioned by metal3, then creates a fake DHCP lease file using the IP address and MAC address information. It also creates a provisioning CR using the MAC address information
• The script the creates an ssh secret key using the ssh keys of the test host, applies the the provisioning CR
• The script busy loops till the KUD installation job completes or fails. If it completes successfully, it does a curl command using the authentication info of the new cluster to confirm if it was successful or not. On completing all the steps, it does a teardown where it deletes everything it created.

BPA Rest Agent

• Test script, e2e_test.sh, creates dummy image file, creates test JSON file, checks bpa rest agent status, issues POST, GET, and PATCH requests sequentially.
• Next, e2e_test.sh checks uploaded MinIO image object size, and calls DELETE.
• If the script fails at any point then verification was unsuccessful.

Kubernetes Deployment (KuD)

KuD has test cases to verify if the add-ons are running correctly. All the test cases can be found in tests directory in the multicloud-k8s project. For each of these, we bring up the deployment that is specific to the addon, perform add-on specific actions on the pod related to the deployment

Multus:

• Multus CNI is a container network interface (CNI) plugin for Kubernetes that enables attaching multiple network interfaces to pods. This is accomplished by Multus acting as a "meta-plugin", a CNI plugin that can call multiple other CNI plugins.
• A 'NetworkAttachmentDefinition' is used to set up the network attachment, i.e. secondary interface for the pod. 
• A pod is created with requesting specific network annotations with bridge CNI to create multiple interfaces. When the pod is up and running, we can attach to it to check the network interfaces on it by running ip a command

OVN4NFV: 

• OVN4NFV provide Provider networks using VLAN networking and Service Function Chaining.
• After the pod is up and running we will be able to attach to the pod and check for multiple interfaces created inside the container. 
• OVN4NFV networking is setup and created along the EMCO composite vFW testing

CMK

• CPU Manager for Kubernetes provides cpu pinning for K8s workloads. In KUD, there are two test cases for the exclusive and shared cpu pools testing.

EMCO:

• EMCO Sanity testing check the health connectivity EMCO Micro service, once it is installed

BluVal Testing

Status as of June 25th 2021:

Release 4 Blueprint Scanning Status

Akraino CVE Vulnerability Exception Request

Akraino BluVal Exception Request

CD Logs:

ICN Master Baremetal Deployment Verifier

Test Dashboards

All the testing results are in logs

Additional Testing

not applicable

Bottlenecks/Errata

not applicable