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.
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 |
https://intl.cloud.tencent.com/document/product/213/9384?lang=en
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts.html
Refer to the following link for installing Jenkins Mater and connect to Jenkins Slave.
https://github.com/qiuxin/Connected-Vechicle
Refer to the following link for installing Tarsframework.
https://github.com/qiuxin/Tars/blob/arm/Install.md
The following is the picture for Tars Framework website.
Refer to the following link for installing Tarsnode and connect Tarsnode to Tarsframework.
https://github.com/qiuxin/Tars/blob/arm/Install.md
Create CI jobs and launch CI jobs in the following way.
The detail of the Jenkins script is depicted in the Test Document.