v2xhub-application
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.
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!
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.
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.