Introduction

...

Introduction

Connected Vehicle Blueprint can be flexibly deployed in physical machines, virtual machines, containers and other environments.

TARS framework is an important open source component of Connected Vehicle Blueprint, which can efficiently complete the massive deployment and governance of micro-services.

License

Apache License v2.0

How to use this document

The document includes details of prerequisites /pre-installation, installation and uninstalls steps. 

The prerequisites and pre-installation software and hardware should be ready before executing the installation steps.

Deployment Architecture 

Due to the hardware source limitation, Connected Vehicle Blueprint is deployed in three Virtual Machines in Amazon Web Service.

...

Pre-Installation Requirements

Hardware Requirements

Minimum Hardware Requirements

Recommended Hardware Requirements

...

Software Prerequisites

• CentOS 8 
• mysql  MySQL  Ver 14.14 Distrib 5.6.26
• OpenStack: Rocky
• k8s:1.15.0

Database Prerequisites

N/A

Other Installation Requirements

N/A

Installation High-Level Overview

...

The detail of the Jenkins script is depicted in the Test Document.  

CVB Test Doc for R3

...

Verifying the Setup 

N/A

Developer Guide and Troubleshooting

Uninstall Guide

1. Stop all tars processes

            /usr/local/app/tars/tars-stop.sh

       2. Delete files

           rm -rf /usr/local/app/tars

           rm -rf /usr/local/app/patchs

           rm -rf /usr/local/app/web

           rm -rf /usr/local/tars

       3. Delete crontab

           crontab -e

           **Delete this line " * * * * * /usr/local/app/tars/tarsnode/util/monitor.sh "**

Troubleshooting

1. You can’t deploy service on IP 127.0.0.1 for the following reasons:
  a)Each service has at least one obj to serve foreign clients;
  b)Each service has a obj for administration, it binds to ip 127.0.0.1 and the same port which servant obj binds to.

2. After executing of tars_start.sh, please execute command ps -ef|grep tars to check that the core service processes of Tars are alive,
  i.e., tarsregistry, tarsAdminRegistry, tarsnode, tarsconfig and tarspatch.

3. The paths in which services deployed as below:
  a)Log file path: /usr/local/app/tars/app_log/${Application}/${ServiceName}/, such as
     /usr/local/app/tars/app_log/Test/HelloServer/
  b)Executable file path: /usr/local/app/tars/tarsnode/data/${Application}.${ServiceName}/bin/, such as
     /usr/local/app/tars/tarsnode/data/Test.HelloServer/bin/
  c)Template config file path: /usr/local/app/tars/tarsnode/data/${Application}.${ServiceName}/conf/, such as
     /usr/local/app/tars/tarsnode/data/Test.HelloServer/conf/
  d)Cache file path: /usr/local/app/tars/tarsnode/data/${Application}.${ServiceName}/data/, such as
     /usr/local/app/tars/tarsnode/data/Test.HelloServer/data/

4. How to check logs
  For example, there will be a log file named Test.HelloServer.log in directory
  /usr/local/app/tars/app_log/Test/HelloServer/. If something failed, please check it.

5. tarsnode can not run java server: cannot execute java
  Please restart tarsnode after install jdk
  /usr/local/app/tars/tarsnode/util/start.sh

Maintenance

Blueprint Package Maintenance

Frequently Asked Questions

N/A

License

Any software developed by the "Akraino Enterprise Applications on CVB is licensed under the
Apache License, Version 2.0 (the "License");
you may not use the content of this software bundle except in compliance with the License.
You may obtain a copy of the License at <https://www.apache.org/licenses/LICENSE-2.0>

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

References

N/A

Definitions, acronyms and abbreviations

N/A