With the presented system architecture, a deployment is both possible on-premise, using hardware and infrastructure provided by the customer, and in the cloud, using Laboperator as cloud provider.
In each scenario, multiple setups can be realized, depending on individual requirements. (For a detailed server setup and installation guide, please read Network Setup and Installation.)
TABLE OF CONTENTS
- On-Premise Scenarios
- Cloud Scenarios
- Software installation
Completely isolated (for demo purposes)
On a single server instance, the full stack is deployed to provide an isolated server installation which could be run in a standalone network setup. This requires a separate DHCP and DNS server. For this, a FRITZ! Box router by AVM or similar devices can be used, which at the same time act as wireless access point for Connector Boxes and tablet PCs. The wireless range can be extended by respective products to ensure coverage of all areas.
For remote maintenance purposes, an UMTS stick can be used in the router, if desired by the customer. No data from the devices or the system will be transported to an external network, which makes this setup ideal for a proof-of-concept or demo scenario.
In customer’s VM infrastructure
Both a single server instance, or a multi-server installation, can be deployed on a virtual machine (VM) infrastructure provided by the customer. Hereby, the network connectivity between the VM and the Connector Boxes and end user devices needs to be managed by the customer. For this, a VLAN is a very good technique, if the customer’s infrastructure supports this. If not, separate LAN segments can be used to separate Connector Boxes and their network adapters from the regular office networks. If this is also not possible, technically it’s feasible to use any existing network, as long as it supports DHCP and DNS and is routed to the Laboperator server.
For all cloud scenarios, the customer’s network must fulfill the following requirements for Connector Box connectivity: A DHCP server needs to provide IP addresses, and a DNS server needs to resolve the server URL. Outgoing connections to the cloud URL via port 443 need to be allowed.
The public cloud is hosted by Laboperator on an AWS instance, and provides software-based multi-tenant support. The server infrastructure is shared with other customers. No separate VPN layer can be applied in this scenario, as the server URL is accessible from the public internet.
The private cloud setup allows for a separate server instance, hosted by a cloud provider of the customer’s choice. The customer can choose between Google, Microsoft or Amazon as infrastructure providers. The location of the servers can be fully determined by the customer, by default the servers would be located in Europe, Frankfurt when possible. The private cloud can be additionally secured by a VPN tunnel, which only gives access to the servers via a dedicated VPN connection. This VPN connection can be handled on customer’s side via a central routing, to bridge the Connector Box network and eventually the office network with the VPN network. Thus, all data is wrapped in the private, encrypted VPN connection, in addition to the already existing SSL encryption.
For on-premise installations with a single server, the software comes pre-installed in a virtual machine appliance package (OVA file). This can easily be imported into any major virtualization infrastructure such as VMWare, VirtualBox or Hyper-V.
For multi-server installations, the deployment happens via installation scripts and an orchestrated console access. This requires a remote maintenance access for Laboperator, which allows ssh login with root permissions on each individual server. The servers need to be pre-installed with the operating system and a root user account.