- Select your scenario
- Network Setup:
Select your scenario
The following articles guides you through the setup procedure:
For the server installation, please prepare your infrastructure to the install Laboperator server.
There are 3 options for your server installation:
If you already have a virtualization infrastructure, in which you would like to import the Laboperator server as an appliance, follow the instructions for the Laboperator server in your virtualization infrastructure.
- If it is not possible in your case to import the Laboperator server as an appliance, an alternative would be an installation of the server from scratch, on a bare metal server provided by you, and afterwards following the instructions "requirements for a customer-hosted server".
- If both options are not possible, consider a local installation on an independent computer, and continue with the regular installation of the Laboperator server in your virtualization infrastructure.
For your network setup, select the scenario which applies to your company setup:
- Your company allows the integration of the Laboperator platform in the network infrastructure.
- Your company runs an independent, standalone setup.
After the server installation, make sure to install the root certificate on your browsers and mobile devices.
Installation requirements for Laboperator server in your virtualization infrastructure
The Laboperator server is a Linux-based system, which is usually provided as virtual machine image. It contains Ubuntu Linux with all necessary services already pre-installed, and packed into a runnable appliance. It is provided as .ova file (Open Virtualization Format) This makes it compatible with any virtualization infrastructure such as VirtualBox, VMware, Hyper-V, and others.
In your virtualization environment, you need to import the image file. If your virtualization environment does not support .ova containers directly, use the VMware Workstation Pro tool to convert it to a VMware format.
Check the following virtual machine settings after the import is done:
- 2 cores
- 16 GB RAM
- 128GB SSD
- 2 network adapters (bridged mode)
The virtual machine will contain a complete Linux Server image (Ubuntu 16.04 LTS 64-bit).
To select the right network setup, please refer to "Network setup for company network infrastructure".
Ensure the virtual machine is turned on and check the console window, if the usual Linux login screen appears to make sure the server is up and running.
Installation requirements for a customer-hosted server
If the virtual machine provided by Laboperator cannot be imported or used in the customer's infrastructure, or a managed server needs to be used, the requirements for a bare metal installation are as follows:
Minimum hardware requirements
- CPU cores: 2
- RAM: 16 GB
- SSD: 128 GB
- Ubuntu 16.04 LTS 64-bit
- Root user "ubuntu" with password
- SSH server enabled, route and firewall configured to allow remote SSH dial in for Laboperator
Laboperator will then perform a script-based installation of the necessary packages and services.
Network setup with local WiFi router for standalone scenario
Your router needs at least 2 LAN ports, one for the server, and one for each connector box. If you consider using a tablet PC for operation, choose a router which supports 5GHz Wi-Fi bands.
Usually, the router allows the configuration of an upstream (WAN) port, which should be set to “DHCP client” in a NAT routing. This prevents unwanted network traffic in case the WAN port is connected to an internet connection such as a company intranet, but still allows downloading updates and remote maintenance on the Laboperator server in case this is required and desired.
An UMTS stick can be connected via USB to the router to allow internet connection and remote maintenance even in scenarios which do not allow the usage of existing network infrastructure such as ethernet cables from a company network.
The local network needs to have a DHCP server, which issues local IP addresses in a range like 192.168.178.x.
Additionally, a DNS server which is announced in the DHCP needs to be up and running and allow resolving of local hostnames from the DHCP lease list. This is an important factor as some routers do not fully support this.
An NTP server on the router should act as time server and the time and local time zone should be set correctly.
Proven models are:
- AVM FRITZ!Box 4020 (2,4GHz Wifi only)
- AVM FRITZ!Box 4040 (supports Connector Box 3B+ with 5GHz Wifi)
- Linksys WRT-series (only with OpenWRT firmware)
The following hostname entry can be used in scenarios where local hostnames cannot be resolved due to a router model which are not supported:
Network setup for company network infrastructure
There are certain requirements which need to be fulfilled to setup the Laboperator system in a company network infrastructure.
Requirements needed for setup Laboperator system:
There should be 2 separate VLAN segments, each mapped to one of the virtual network adapters in bridged mode.
- One VLAN ("web") is used by users to access the web interface and thus needs to be routed accordingly.
- One VLAN ("connector") is used by connector boxes to connect to the server.
The following services and routes need to be enabled in the "connector" VLAN:
- DNS needs to resolve the hostname of the server
- DHCP needs to assign IP addresses to Connector Boxes (static IP addresses are not possible, use DHCP reservations instead)
- NTP server needs to be available
The following firewall rules need to be set for each VLAN on the server network interface:
- Inbound TCP ports: 443 (HTTPS)
The following firewall rules may be set for the "web" VLAN on the server network interface:
- Outbound TCP port 22 (SSH) for remote maintenance (reverse tunnel to www.laboperator.com)
- Outbound TCP ports 22 (SSH), 80, 443 (web) for remote updates (e.g. from github.com)