Overview of the OTH environment

The OTH environment consist of a set of VMs (or discrete servers), as described in the server architecture section in this document. We refer to the ansible-playbook installation guide, for installing or upgrading your OTH solution.

The VMs that are configured as a frontend, runs a HAProxy instance and should be the only node in the setup that are publicly exposed to the internet.

The VMs that are configured as application nodes primarily runs a set of docker services, each providing a specific function/service to the OTH eco-system. Each docker service communicates through either the frontend (HAProxy), that forwards all inbound traffic to the application node or through the RabbitMQ service. The application node delegates the traffic with Traefik, based on the URI called, to the receiving services. All data put into the system are stored in the database.

The VM node that are configured as the database/storage back-end runs a MySQL compatible server and also serves as RabbitMQ server and if needed a minio object-storage server. All 3 services are running in a docker environment.

All services are installed/upgraded and configured by ansible. The OTH ansible playbook ensures the correct configuration and that the right versions of the images are installed.