...
The use cases for the Connected Vehicle Blueprint are itemized below. For R2R3, we release the Microservice Platform Tars, which supports the multiple connected vehicle application deployment/management/orchestration/monitor.
...
- Commodity Hardware, Arm/X86 Physical Server.
- IaaS Software, like Openstack, IaaS and so on
- Tars Microservice Platform
- Connected Vehicle Applications Applications + Virtual Classromm(VR) Applications
The combination of Commodity Hardware and IaaS Software provides flexible deployments, like Bare Metal, Virtual Machine as well as Container.
...
The following is the general architecture of Tars, which is a major component in R2R3.
Refer to the enclosed PDF document for the detail Tars introduction.
| View file | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Main Progresses for Release
...
3
Release 2 3 is the first second release for Connected Vehicle Blueprint. So everything is new.
Build Of Materials (BOM) / Hardware requirements
Connected Vehicle Blueprint can be flexibly deployed in Bare Metal, Virtual Machine as well as the container.
For R2R3, we deploy it in Amazon Web Service inwinSTACK Private LAB for Release. The detailed hardware is itemized below:
...
CPU+Memory
...
Drive
...
Deployment
...
8Core * 16G
...
15G
...
Jenkins Master
...
8Core * 16G
...
10+50G
...
TarsFramework
...
8Core * 16G
...
10G +20G
...
TarsNode + Application
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) |
Beyond of AWS, we deploy it in Ampere POD 1 in CI Lab as well.