...

Jenkins Information

Akraino community has a public Jenkins cluster. ICN leverages the Akriano public Jenkins to run CI jobs. While the CD jobs run in our private Jenkins cluster.

We have the following Jenkins slave nodes joined Akriano Jenkins. ICN CI jobs are supposed to be scheduled to our slave nodes by label icn-dev.

...

N/A. 

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

Akraino Test Group Information

N/A

To add more Jenkins slave nodes, please follow the akriano jenkins guide

To setup private jenkins, please refer to the README.md under icn/ci/

The private jenkins cluster is setup on pod14-node2. We can visit the jenkins with the node ip address: http://10.10.140.22:8080/

Currently we support only AIO private Jenkins.

Akarino Test Group Information

not applicable

Overall Test Architecture

Test Architecture

Test Bed

Pod Topology

ICN Master

...

Bare-metal Deployment Verifier

...

Bare-metal deployment

...

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. To be able tu use Kata Containers, we also use Containerd runtime interface in Kubernetes instead of the default docker-shim. 

Testing

CI Testing:

Bashate:

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

...