Installation

A Reemo instance is installed in two ways: with the reemo-infra Ansible role, which deploys and configures the environments from an inventory, or from an OVA appliance image ready to import into a hypervisor. The choice depends on the context: fine-grained control and cluster deployment on one side, quick setup on the other.

Installation types

Ansible installation

The reemo-infra role installs the environments (INFRA, and depending on licenses PROVISION, RELAYWS, TURN) on one or more servers. You describe the infrastructure and the license key in an inventory, then run a playbook (see INFRA Installation). This method covers both a single server and a high-availability cluster, and gives access to every configuration option: portals, database, certificates, registry.

OVA installation

An OVA image is a virtual appliance prepared by Reemo, to import into a hypervisor. It bundles a pre-assembled environment, which shortens setup — suited to an evaluation or a standard deployment without Ansible configuration.

Image provisioning

For an Ansible installation, each target machine must be able to reach the platform’s Docker images before the final install. The reemo-infra role supports several modes, chosen according to the available network access (see Registry and Images):

• Online: machines reach the Reemo registry (registry.reemo.io) directly over HTTPS.

• Proxy: machines reach the registry through a corporate HTTP/HTTPS proxy.

• Offline: no Internet access; images are pre-packaged as tarballs, generated and then loaded onto the nodes.

• Dedicated registry: images are loaded onto your own registry, then the install runs in Online mode against that registry.