The OpenUAV is a simulation environment developed for Unmanned Aerial Vehicles. The goal of this framework is to have an easy to setup, UAV testing framework for single and multi-UAV simulations. The containerized architecture makes this framework capable of scaling and hosting mutiple simulations in an on-premise or cloud environment. This project is a modification of the willkessler/nvidia-docker-novnc to include PX4/QGroundControl software packages UAV simulations.
To create a simulation session, please create an account at Cyber-Physical Systems Virtual Organization (CPS-VO) https://cps-vo.org/group/OpenUAV. If you are using it for educational use-cases, please mention the reason and university while creating an account. For more details, https://openuav.us/#cpsvo
Authors: Harish Anand, hanand4 (at) asu (dot) edu;
Prof. Jnaneshwar "JD" Das, Distributed Robotic Exploration and Mapping Systems Laboratory, ASU School of Earth and Space Exploration
us-east-1c seems to be the best choice as of April 1, 2018./root/build or wherever you like as a temporary location.preinstall.sh. This just runs apt-get update and puts in screen and emacs for getting started.build.sh. This will build everything needed to start up a nvidia-docker2 container with Ubuntu 18.04 and Lubuntu desktop.nvidia-xconfig --query-gpu-info and modify the autonomous_sys_build/xorg.conf with your GPU's BusId and name.preinstall.sh. This runs apt-get update and puts in screen and emacs for getting started.build.sh. This will build everything needed to start up a nvidia-docker2 container with Ubuntu 18.04 and Lubuntu desktop.To run the container on this host, use run.sh. Note that NoVNC will
expect connections on port 40001. Then surf to your host on that port.
There are 3 docker images created after running build.sh,
The first image contains a basic linux ubuntu 18.04 desktop with chrome and pycharm installed. These session are used for python programming courses and can avoid any of the GPU requirements (change the base image in Dockerfile.base to nvidia/opengl:1.0-glvnd-runtime). Second image is a robotics specific image that contains ros melodic and gazebo 9.0.0 installed. The third image installs all the necessary PX4 and QGroundControl software to do flight simulations.
To access, containers through the sub-domain based url, you need to setup a dns proxy to obtain the docker internal DNS for routing. This can be achieved by creating a reverse proxy NginX container, that serves the internal DNS to host machine.
docker network create -d bridge cpsvo.docker run --name dns-proxy --network=cpsvo -d nginx.apt update && apt install vim net-tools)Replace the NginX containers /etc/nginx/nginx.conf with the following conf. This provides docker DNS to host machine (127.0.0.11 from inside docker)
user nginx;
worker_processes 1;
error_log /var/log/nginx/error.log warn;
pid /var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
include /etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
sendfile on;
#tcp_nopush on;
keepalive_timeout 65;
#gzip on;
include /etc/nginx/conf.d/*.conf;
}
stream {
upstream ssh_openuav {
server 127.0.0.11:53;
}
server {
listen 53 udp;
proxy_pass ssh_openuav;
}
}Install NginX on the host machine and modify the /etc/nginx/sites-enabled/default file to include the following server configuration.
You should replace \.openuav\.us$; with your domain name and the cpsvo in the beginning can be replaced with a any other name. You must
also replace 172.18.0.2 in resolver 172.18.0.2 valid=2s; to the IP address of the NginX container (docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' dns-proxy). You must also replace the ssl_certificate and ssl_certificate_key variables with your variables.
server {
server_name ~^cpsvo-(?<uuid>\S+)\.openuav\.us$;
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/openuav.us-0001/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/openuav.us-0001/privkey.pem; # managed by Certbot
resolver 172.18.0.2 valid=2s;
location / {
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://cpsvo-$uuid:40001;
proxy_hide_header 'x-frame-options';
proxy_read_timeout 61s;
add_header Cache-Control "no-store";
# Disable cache
proxy_buffering off;
}
}
Paper https://arxiv.org/abs/1910.00739
/usr/lib/xorg/Xorg -core :1 -seat seat1 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch -config /etc/X11/xorg.conf.openuavGLX issues
Applications like Gazebo need libX11.so and libGLX.so to work. For all applications inside the container, X11 is provided by the TurboVNC's Xvnc (acting both as X window server and as a vnc server). VirtualGL is used to redirect applications (like Gazebo or Unity) that make GLX calls (3D rendering) to run the graphics rendering in a dedicated GPU and we achieve this by preloading each command you run in the terminal through vglrun command. Thus VirtualGL takes care of libGLX.so.
Regarding env variables, the DISPLAY env variable points to :1.0 which is the TurboVNC X window session (Xvnc), and for applications that needs 3D acceleration, the application does GLX calls which are handled by an Xserver (with GPU) running at :0.0. We provide details of second X server using the variable VGL_DISPLAY which is set to :0.0 on all containers. If VGL_DISPLAY is not set on the container, it assumes the value :0.0.
You can check for any GLX issues, by using the command glxgears. Glxgear application's 2D window will be handled by TurboVNC (Xvnc) and 3D rendering will be handled by an X with GPU (virtualGL should redirect this correctly).
If you are facing GLX issues, try checking X server running at (:0.0) with GPU support is connected properly. You can pass a host X server with GPU ti the inside of the container as /tmp/X11-unix/X0. This connection is usually the issue for most GLX problems.
build.sh.