Installation Architecture
Due to the hardware source limitation, Connected Vehicle Blueprint is deployed in three Virtual Machines in Amazon Web Service.
(Visit CI Lab Environment Setup if you want to set up connected vehicle blueprint in CI Lab.)
The following picture depicts the deployment architecture.
Server A : Deploy Jenkins.
Server B : Deploy Tars Master Node.
Server C ：Deploy Tars Slave(Node) and the connected vehicle applications.
Installation Hardware
Server Name | CPU+Memory | Drive | Deployment |
Jenkins | A1 8Core * 16G | 15G | Jenkins Master |
TarsFramework | A1 8Core * 16G | 10+50G | TarsFramework |
TarsNode | A1 8Core * 16G | 10G +20G | TarsNode + Application |
Installation Software
- CentOS 7 centos-7_aarch64 - ami-012355fc520b79a12
- mysql Ver 14.14 Distrib 5.6.26, for Linux (aarch64) using EditLine wrapper
Installation Step by Step
Step1: Lunch Instance In AWS
Step2: Install Jenkins
https://github.com/qiuxin/Connected-Vechicle
Step3: Install Tarsframework
https://github.com/qiuxin/Tars/blob/arm/Install.md
Step4: Tars Node
https://github.com/qiuxin/Tars/blob/arm/Install.md
Step5: Develop Application on top of Tars
Step6: Lunch CI jobs
