Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
outlinetrue
Introduction

ICN Pod Topology

View file
nameAkraino ICN Pod Topogoly.pptx
height250

Jenkins Information

ICN project leverages Akriano Akraino community has a public Jenkins cluster. ICN leverages the Akriano public Jenkins to run CI jobs. But we run 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.

...

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

...

We support the following  jobs

CI job

...

  • triggered by gerrit patch creation/update. 
  • Run a make command, which builds golang pkgThe job runs verify.sh under icn project. The verify.sh currently has integrated the golang test and bashate test.
  • Post +1/-1 for gerrit patch if the build succeeds/fails
CI job for shell
  • triggered by gerrit patch creation/update. 
  • Run a make command, which runs bashate to check shell scripts
  • Post +1/-1 for gerrit patch if the check passes/failsUpload the job log to Nexus server in post-build actions
CD job for test
  • triggered daily automatically (We can also trigger it manually)
  • Run a make command, which creates VM(s) and deploys ICN components on the VM(s)
  • Send daily report to mailing listUpload the job log to Nexus server in post-build actions

CI jobs detail

Update the verify.sh can update the CI job content.

Image Modified

CD job detail

...

  1. On our private Jenkins node, we provision a VM by vagrant. A Vagrantfile which defines the VMs properties is needed. We can define many VM properties in the Vagrantfile:
    • VM hostname
    • VM memory 64G, cpu 16, disk 300GB
  2. Login to the VM and run 'make verifier' which installs the components in the VM
  3. We destroy the VM as the last step of the job

Test Bed

Pod Topology

ICN Master Baremetal Deployment Verifier

Image Added


ICN Master Virtual Deployment Verifier

Image Added

Baremetal deployment

Hostname

CPU Model

Memory

BMC 

Firmware

Storage

1GbE: NIC#, VLAN,

(Connected

extreme 480 switch)

10GbE: NIC# VLAN, Network

(Connected with IZ1 switch)

40GbE: NIC#

Jump

Intel

2xE5-2699

64GB

 1.46.9995

3TB (Sata)
180 (SSD)

IF0: VLAN 110 (DMZ)
IF1: VLAN 111 (Admin)

IF2: VLAN 112 (Private)
VLAN 114 (Management)
IF3: VLAN 113 (Storage)
VLAN 1115 (Public)


node1

Intel

2xE5-2699

64GB

1.46.9995

3TB (Sata)
180 (SSD)

IF0: VLAN 110 (DMZ)
IF1: VLAN 111 (Admin)

IF2: VLAN 112 (Private)
VLAN 114 (Management)
IF3: VLAN 113 (Storage)
VLAN 1115 (Public)


node2

Intel

2xE5-2699

64GB

1.46.9995

3TB (Sata)
180 (SSD)

IF0:  VLAN 110 (DMZ)
IF1: VLAN 111 (Admin)

IF2: VLAN 112 (Private)
VLAN 114 (Management)
IF3: VLAN 113 (Storage)
VLAN 1115 (Public)

IF4: SRIOV

...

The gerrit comments contains the CI log url. All the CI logs are under this folder folder ICN : https://logsjenkins.akraino.org/production/vex-yul-akraino-jenkins-prod-1/view/icn/job/icn-master-verify/

Latest CI logs

CD Logs:

ICN Master Baremetal Deployment Verifier

...