usdotfhwaops/v2xhub-application

By usdotfhwaops

Updated about 4 hours ago

Compose
0

10K+

usdotfhwaops/v2xhub-application repository overview

Introduction

This directory contains deployment and configuration instructions for deploying V2X-Hub on both ARM64(arm64) and x86(amd64) architectures.

Note

Separate deployment files/configurations are no longer necessary for arm64 and x86 deployments.
Deployment Instructions

Once downloaded, navigate to the configuration directory:

cd ~/V2X-Hub/configuration/

Run the initialization script:

./initialization.sh

Follow the prompts during installation.

You will be prompted to create a mysql_password. This is the password to the MySQL configuration database for the IVP user. Please create a unique and secure password and remember it

Example: ivp

You will also be prompted to create a V2X Hub username and password. You may make these whatever you’d like, but will need to use them to log into the web UI. Example:

Username: v2xadmin

Password: Changeme123!

After installation is complete, the script will automatically open a web browser with two tabs.

Enter the login credentials you created in the steps above and login.

Installation complete!

Simulation Setup

To support execution in a simulated environment, V2X-Hub is in the process of integrating with CDASim, a Co-Simulation tool built as an extension of Eclipse Mosiac. This extension will incorporate integration with several other platforms including CARMA-Platform and CARLA. The setup for this simply requires setting environment variables for the V2X-Hub docker compose deployment. These can be set via the initialization.sh script and can be manually edited after.

Docker Environment Vaeriables
  • V2XHUB_VERSION – Version of V2X-Hub to deloy ( Docker Tag/ GitHub Tag )
  • SIMULATION_MODE – Environment variable for enabling simulation components for V2X-Hub. If set to "true" or "TRUE" simulation components will be enable. Otherwise, simulation components will not be enabled.
  • KAFKA_BROKER_ADDRESS – Environment variable for storing Kafka broker connection string (including port).
  • TIME_SYNC_TOPIC – Environment variable for storing Kafka time sync topic.
  • SIMULATION_IP – Environment variable for storing IP address of CDASim application.
  • SIMULATION_REGISTRATION_PORT – Environment variable for storing port on CDASim that handles registration attempts.
  • TIME_SYNC_PORT – Environment varaible for storing port for receiving time sync messages from CDASim.
  • V2X_PORT – Environment variable for storing port for receiving v2x messages from CDASim
  • SIM_V2X_PORT – Environment variable for storing port for sending v2x messages to CDASim
  • V2XHUB_IP – Environment variable for storing IP address of V2X Hub.
  • INFRASTRUCTURE_ID – Environment variable for storing infrastructure id of V2X Hub.
  • V2XHUB_USER – V2X Hub Administrator Username to create on startup
  • V2XHUB_PASSWORD – V2X Hub Administrator Password to create on startup
  • SENSOR_JSON_FILE_PATH – Environment variable for storing path to sensor configuration file. This is an optional simulation environment variable that allows for setting up simulated sensor for a V2X-Hub instance. Example file can be found in the CDASimAdapterPlugin tests here.
Access V2X-Hub

To access V2X-Hub UI, either chromium or google-chrome browser can be used by running the following commands:

chromium-browser <v2xhub_ip>

or

google-chrome  <v2xhub_ip>

Note

V2X-Hub initialization script uses [mkcert](https://github.com/FiloSottile/mkcert), a simple tool for making locally-trusted development certificates for HTTPS communication and placing them in the `.ssl/` directory. For deployment, it is recommended that you generate your own trusted certificates from a real certificate authorities (CAs). MKCert can also be used to setup a local CA but that is up to deployers.

Note

If no certificates are present at start-up time, the V2X Hub container will create self signed certificates using `openssl` (see `container/generate_certificates.sh`). These certificates need to be explicitly trusted by the browser. To do this simply navigate to `https://` and accept the warning. After this you should be redirected to the login page.

Tag summary

Content type

Compose

Digest

sha256:f044ade3d

Size

6.5 kB

Last updated

about 4 hours ago