Test architecture/topology
The test environment consists of three virtual machines in total.
- one physical server for Jenkins CI.
- one physical server for TarsFramework and Jenkins slave
- one physical server for TarsNode and Jenkins slave.
Software Version
OpenStack: Rocky
k8s:1.15.0
Java:
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
Jenkins: Ver 2.190.2
CentOS 7
Mysql Ver 14.14 Distrib 5.6.26, for Linux
Devices Under Test
Hostname | Core | RAM | HDD | NIC | Role |
Node-0 | 8 | 40GB | 3TB | 1GB | Jenkins Master |
Node-1 | 8 | 96GB | 3TB | 1GB | Tars Framework |
Node-2 | 8 | 96GB | 3TB | 1GB | Tars Node (CVB + Type4 Application + Virtual Classroom Teacher Client + Virtual Classroom Student Client) |
Test Script
The test is to fulfill by Jenkins Job. The test script includes:
- Compile the Tars Framework
cd /usr/local/robert/testCompileCode
git clone -b arm https://github.com/qiuxin/Tars.git
cd /usr/local/robert/testCompileCode/Tars
git submodule update --init --recursive
cd /usr/local/robert/testCompileCode/Tars/framework/build
chmod u+x build.sh./build.sh all
rm -rf /usr/local/robert/testCompileCode/Tars
- Call the service deployed by Tars Framework
/usr/local/testClient/CVAppClient
The log is triggered periodically.
The log is updated to
https://nexus.akraino.org/content/sites/logs/tencent/job/TestCompileCode/
https://nexus.akraino.org/content/sites/logs/tencent/job/TestConnectVehicleService/
https://nexus.akraino.org/content/sites/logs/tencent/job/CD_Install_Tars/